VerificationDocument and ID verification
Document and ID verification Genuine, and theirs.
Read the page, the MRZ and the chip. Check it’s real, and that it’s theirs.
Know the document is genuine, and that it belongs to the face holding it.
Genuine documents, matched to the face holding them.
Live capture
Feedback on angle, glare and focus, with the type recognised automatically.
Cross-checked
Data page, MRZ and barcodes read against each other.
Chip authenticated
The NFC chip in ePassports and eIDs verified cryptographically.
A document is only proof when every part of it agrees.
An edited field shows. A photo of a screen is caught.
- Document type
- Data page read
- MRZ cross-check
- Barcode cross-check
- NFC chip
Every part of the document, checked against the rest.
- Feedback on angle, glare and focus, with the type recognised automatically.
- Data page, MRZ and barcodes read against each other.
- The NFC chip in ePassports and eIDs verified cryptographically.
Document checks
- Document type
- Data page read
- MRZ cross-check
- Barcode cross-check
- NFC chip
PassportNumber: Z••••821
- Name
- Priya Sharma
- Expires
- 2033
Screen recapture
Build the journey around risk.
- Run it only where the risk calls for it.
- Fall back to manual review when it can’t finish.
- Change the order without an app release.
Start: scan your document
Document and ID verificationPassports, IDs, licences, permits
Next stepFace match to the portrait
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 FRMDOC_AUTHENTIC
- Document type
- Clear
- Data page read
- Clear
- MRZ cross-check
- Clear
- Barcode cross-check
- Clear
- NFC chip
- Clear
- Hologram
- Clear
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.
Which documents does it read?
Passports, national IDs, driving licences and residence permits, with the type recognised from the capture. The data page, the MRZ and barcodes are read on all of them, and the chip is read where the document has one.
What does the NFC chip add?
The chip in an ePassport or eID holds a signed copy of the data page and the portrait. Reading and authenticating it means the printed page cannot be forged on its own: the chip has to agree with it.
Can it catch a document shown on a screen?
Yes. A document photographed from a screen or a printout is caught in the capture, before any field is trusted.
Does it check documents other than IDs?
Supporting documents such as payslips and bank statements are checked for edits. They are evidence for your journey, and DeepID does not treat them as proof of who the customer is.
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.