Choosing which checks to run at onboarding
APIZONE
·
·updated 8 Sep 2026 ·
1 min read
Running every available check on every user is slow and expensive. A decision tree keeps assurance high and cost sane.
On this page
Start from the product risk
A read-only analytics tool needs light identity assurance. A lending product needs strong assurance. Write down the maximum loss from a bad actor in each product and let that set the check depth.
Cheap checks for everyone, expensive checks on triggers
PAN structure and IFSC validity cost nothing, so run them universally. Reserve penny-drop, statement analysis and multi-source name joins for higher tiers or for users who failed a lighter check.
Review the tree with real data
After a quarter, look at where fraud actually got through and where good users dropped off. Move the thresholds. The tree is a living document, not a launch artefact.