VerificationIdentity and eKYC
Identity and eKYC Checked at the source.
Aadhaar, DigiLocker, PAN and CKYC, checked against the record that issued them. With consent.
Verify the identity against the records that issue it.
Identity verified at the source, before a face is matched to it.
At the source
Aadhaar offline KYC and DigiLocker, with consent, not a photocopy.
Every ID number
PAN, CKYC, passport, voter ID and driving licence checked against official records.
Matched across sources
Name, date of birth and address compared, and any difference named.
Verify once at the source, and keep the record true.
A difference is named. Your journey decides what it means.
- Aadhaar offline KYC
- DigiLocker document
- PAN record
- CKYC record
- Date of birth match
One identity, from every record that issues it.
- Aadhaar offline KYC and DigiLocker, with consent, not a photocopy.
- PAN, CKYC, passport, voter ID and driving licence checked against official records.
- Name, date of birth and address compared, and any difference named.
Identity checks
- Aadhaar offline KYC
- DigiLocker document
- PAN record
- CKYC record
- Date of birth match
Priya SharmaPAN: ABCPS••••K
- Aadhaar
- •••• •••• 4821
- Date of birth
- 14 Aug 1992
Name match
Build the journey around risk.
- Run it only where the risk calls for it.
- Fall back to video kyc when it can’t finish.
- Change the order without an app release.
Start: verify your identity
Identity and eKYCAadhaar, DigiLocker, PAN, CKYC
Next stepLiveness and face match
Approve
Every result, in one record.
- Sent to your app and your FRM.
- Each answer carries its reason code.
- Kept for your analysts and audit.
Returned to your app and FRMEKYC_VERIFIED
- Aadhaar offline KYC
- Clear
- DigiLocker document
- Clear
- PAN record
- Clear
- CKYC record
- Clear
- Date of birth match
- Clear
- Name match
- Review
Backed by the rest of DeepID.
Verification is one step. The same SDK reads the phone, links what it has seen before, and turns every check into one decision.
Device intelligenceThe phone is read at the same moment, so a virtual camera, an emulator or a cloned app is caught before anyone is trusted.Learn more Mule graphFaces, phones, PANs and accounts are linked across your customers, so one person behind many accounts shows.Learn more Journey builderChoose the checks, their order and the fallback for each market, and change them without an app release.Learn more DecisionEvery check becomes one answer with its reasons, sent to your app, your FRM and the audit log.Learn more
Questions banks ask.
Does DeepID do Aadhaar eKYC, or offline KYC?
Aadhaar offline KYC and DigiLocker, with the customer’s consent: the customer shares a signed copy of their Aadhaar details, and DeepID verifies the signature and reads the details from it. Aadhaar face authentication, in the Aadhaar app, is a login route on the same SDK.
Can we keep our current KYC provider?
Yes. A bank that already has a KYC provider keeps it and starts with one-tap login or the session. DeepID’s eKYC is there for banks that want sign-up on the same SDK as everything after it.
Which IDs are checked at the source?
Aadhaar through offline KYC and DigiLocker, PAN, CKYC, passport, voter ID and driving licence numbers, each against the record that issued it. Names, dates of birth and addresses are then matched across them.
What happens when the details do not match?
The difference is named in what comes back, such as a name that differs from the PAN record, and your journey decides what follows: a fallback such as video KYC, a review, or a stop. Nothing passes on a partial match unless your policy says so.
Try one-tap login on your own number.
See the network confirm your number with nothing to type, and the next check take over when it can’t. Then plan a shadow proof on one journey, measured on your own traffic.