What is Aadhaar verification?
Aadhaar verification is the step where you confirm that the Aadhaar identity a customer presents is in a usable state. You also check that the details the customer gave match the record held against it.
Most Indian digital onboarding journeys are built around this check, because Aadhaar is the credential the widest set of customers already holds.
The check is consent-led by design. Nothing runs until the holder has authorized it for a stated purpose, and what comes back is limited to what that authorization covers. A verification service carries a consented request to a trusted data source, and it does not open a window onto a government system.
How the Aadhaar Verification API works
Handled by hand, the check means collecting a document image, keying the details in and hoping a reviewer caught the mismatch. That work does not scale, and it fails quietly.
An API moves the same check inside your own application. Your product captures consent and the required details, then submits the request.
It receives a structured response your flow can route on: proceed, ask for something else, or send the case to a reviewer. The customer stays in one journey.
What you send with an Aadhaar check
A request starts from the Aadhaar number the customer submits, with the consent record for that purpose. Where your flow only checks consistency, you send the customer-supplied name and date of birth too, and the response reports the comparison outcome.
The holder-authorized step adds the one-time code sent to the mobile number attached to the customer's record. The customer enters it to release details for the stated purpose. Available fields vary by data source and record, and the response may report a match outcome in place of the underlying values.
Basic and Advanced coverage compared
| Capability | Basic | Advanced |
|---|---|---|
| Confirms the submitted number is well formed and in a usable state | Included | Included |
| Returns a structured status your flow can route on | Included | Included |
| Reports a match outcome for customer-supplied name and date of birth | Included | Included |
| Runs the holder-authorized step that releases identity details | Not included | Included |
| Returns released demographic details such as name, date of birth and address | Not included | Included |
| Returns a masked reference you can store in place of the full number | Not included | Included |
Which tier applies, and what each can return, depends on the selected service contract.
Who runs Aadhaar checks at onboarding
Lending and NBFC platforms can settle an applicant's identity at the top of a loan application. That stops underwriting time going into a file that will not survive verification.
Fintech and payment service providers can run the check when a limited account is upgraded. Transaction limits or a payout account depend on identity being established.
Insurers can confirm the proposer's identity on a proposal. The policy record and any later claim then rest on details checked at the start.
Telecom operators can settle identity before a connection is activated, since the subscriber record has to hold up long after the sale.
Staffing and gig platforms can verify a rider, driver or field worker before the first shift. The platform is accountable for who it puts in front of customers. Healthcare providers can resolve a returning patient to one record and avoid a history split across near-identical names.
Designing the Aadhaar step in your journey
Write the consent screen in language a customer can actually read, and keep what they agreed to joined to the request that followed. A verification you cannot trace back to an authorization is hard to defend later.
Design the paths that are not a clean pass. A customer may have no mobile number attached to their record, may not receive the code, or may decline. Each is an outcome to route, and each needs an alternative document path.
Store the decision, not the identity. Most workflows need the outcome, the timestamp and a masked reference, and holding more only increases what you have to protect.
Consent rules for an Aadhaar check
Aadhaar is sensitive personal information and carries obligations beyond ordinary customer data. Run a check only against consent that was informed, specific to the stated purpose, and revocable. Retain a masked reference in place of the full number, restrict access to the people whose work requires it, and keep retention to what the process needs.
Do not repurpose a result. Details released for onboarding are not a dataset for profiling, marketing or enrichment. Always offer an alternative officially valid document to a customer who declines.
Your business stays responsible for the notices it shows, the purposes it claims and the obligations of its own sector.