/v1/aadhaar-verificationillustrativeKYC
Consent comes first, and the Aadhaar number comes back masked
Your request reaches the source register only after the person agrees to this check, for a purpose you name. What comes back is already reduced. You learn who the holder is without receiving the full Aadhaar number you would then have to protect.
- You capture consent before the lookup, with the purpose recorded against it. The drawing uses customer onboarding, and a consent reference (cns_…) comes back beside the result.
- The customer then enters a six-digit one-time code, one cell at a time, the way they would in your own flow.
- The record comes back with aadhaar_number already masked to XXXX XXXX 4321. The first eight digits are never returned.
- Name and date of birth come back as the register holds them, both masked to *** in this sample.
The masking happens at the source, before the response reaches you. Nothing you store from this check holds a full Aadhaar number.
Explore KYC