The Aadhaar Verification API is one of six services in the selected KYC family. It is intended for workflows where a customer consents to the use of Aadhaar details during onboarding.
Design the customer journey first
Before integration, explain why the document is requested and what will happen next. Keep the consent step close to the action it authorises, and provide a clear route back into your application.
A typical product flow has three parts:
- Your application starts the supported customer-authorisation step.
- The customer completes the consent step.
- Your backend receives the available status and structured fields for the configured API contract.
Your application can then apply its own onboarding, review or follow-up rules.
Define result handling
Plan for more than a successful response. Document how the product handles cancellation, expired sessions, incomplete journeys and technical errors. Give customers a useful next action instead of leaving them at a generic failure screen.
Minimise sensitive data
- Request only the data required by your use case.
- Mask sensitive values in product screens and support tools.
- Keep credentials and identity data out of logs.
- Set access and retention rules before going live.
Combine checks deliberately
If your policy also requires PAN, Voter ID, DL, Passport or document OCR, add only the relevant KYC API at the appropriate step. Face Match is available as a separate selected service when your workflow calls for a comparison step.
Review the Aadhaar Verification API, or talk to our team about your KYC flow.