Fintech · 9 min read
Designing KYC flows in India that convert and comply
Aadhaar, PAN, Video KYC, DigiLocker, CKYC: India offers powerful KYC rails. Here is how to combine them into onboarding that users finish and regulators accept.
Neha Kulkarni · 2 July 2026
Know which rules apply to you
KYC requirements in India depend on who regulates you. RBI-regulated entities such as banks, NBFCs and payment system operators follow the RBI Master Direction on KYC. SEBI governs brokers and investment advisers, and IRDAI covers insurers. Unregulated businesses, such as a real estate developer onboarding buyers, have lighter obligations but still need to verify identity and handle data carefully.
Your regulator determines which verification methods you may use, when full KYC is required, and how long records must be retained. Settle this before designing screens.
The main verification rails
Each rail has different strengths, costs and eligibility. Most good flows combine two or three of them.
- PAN verification through an authorised API to confirm name and status
- Aadhaar OTP-based e-KYC, available to entities permitted under the Aadhaar Act and regulations
- Offline Aadhaar XML or DigiLocker document fetch with user consent
- Video-based Customer Identification Process (V-CIP) for full KYC remotely
- CKYC registry search and download to reuse existing KYC records
- Penny-drop bank verification to confirm account ownership
Handling Aadhaar carefully
Aadhaar numbers are subject to strict handling rules. Entities that are not permitted to perform authentication should not collect the full number unnecessarily, and where an Aadhaar copy is collected, the number should be masked to show only the last four digits. Storage of Aadhaar numbers, where permitted, is expected to be in a dedicated, secured vault.
OCR on Aadhaar cards is useful for pre-filling forms, but treat it as data entry assistance, not verification. Mask the number immediately after extraction, capture explicit consent, and verify through an authorised channel when the use case requires it.
Designing for completion
KYC is where most fintech funnels leak. Ask only for what the current product tier requires, and defer higher-tier checks until the user needs the feature they unlock. Pre-fill wherever a verified source exists, and show progress clearly.
Expect failures and design for them: blurred photos, name mismatches between PAN and bank records, OTPs that never arrive. Give specific guidance on retry, allow switching to an alternative rail, and route genuine edge cases to a manual review queue with clear service levels.
Audit trail and data minimisation
Regulators expect you to show how each customer was verified. Record which rail was used, the response reference, timestamps, the reviewer for manual decisions and the consent captured. Store these as immutable events linked to the customer.
At the same time, the DPDP Act requires you to collect only what you need and delete it when no longer required, subject to regulatory retention periods. A good KYC system holds both requirements in tension deliberately, with retention rules defined per document type.