Run a complete, consent-based Aadhaar eKYC: the person enters the OTP sent to their Aadhaar-linked mobile, and you receive their verified name, date of birth, gender, address and photograph. The gold standard for regulated onboarding.
Your application sends
emver API
Issues a hosted consent link, tracks the person's authorisation and assembles the result.
Completed via
UIDAI OTP on the Aadhaar-linked mobile
You receive by webhook
Where demographic validation only confirms a number is genuine, OTP-based eKYC proves the person in front of you controls the Aadhaar and returns the full KYC record from the authority: name, date of birth, gender, full address and photo. It is the identity check regulators expect for accounts, lending and high-value onboarding.
The flow is two calls: generate the OTP against the Aadhaar number, then submit the OTP the person received. emver hosts the consent screen if you want it, captures the consent artefact and returns a masked Aadhaar with the KYC data.
Consent is part of the contract
OTP-based eKYC is consent by construction: the person must enter the code sent to their own mobile. emver stores the consent text, timestamp and transaction reference with the request.
Full Aadhaar eKYC with a one-time password on the registered mobile.
Meets KYC expectations for accounts, loans and investment products.
Removes the need for a separate address proof for most onboarding flows.
Pair the returned photo with Face Match and Liveness to close the loop.
Every eKYC keeps its consent record for audits and data-subject requests.
Where the Aadhaar eKYC (OTP) API is typically called, and what it settles there.
Fully digital KYC for savings, current and demat accounts.
Identity and address in one step before disbursal or policy issue.
Verified identity and address for the personnel file.
Confirm date of birth for gaming, trading and other restricted services.
Request and response details, environments and a ready-to-import collection are in the developer console.
Call with your organisation API key. Sandbox and production use the same contract.
Send the person's details and the documents you need. You receive a hosted link to share on any channel.
They sign in and choose what to share. Nothing moves without their approval.
Verified documents and details arrive by webhook or on the status endpoint.
Privacy and security built in
Consent recorded · Payloads not retained beyond your retention window · Every request traceable
FAQ
What teams ask before adding the Aadhaar eKYC (OTP) API to their integration.
They cannot complete OTP eKYC. Fall back to DigiLocker, or to demographic Aadhaar validation combined with Face Match on an ID document.
No. emver can host the consent and OTP screens and hand the result back, or you can build your own and pass the consent record with the request.
No. Responses carry a masked Aadhaar, and the raw number is not persisted.
Usually called with the Aadhaar eKYC (OTP) API, on the same key.
Identity & KYC
Confirm an Aadhaar number is genuine and active, without OTP friction.
Identity & KYC
Let the person share government-issued documents with consent, verified at source.
Documents & Biometrics
Compare a selfie to the photo on an ID document or KYC record.
Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.