Use case · Passport chip onboarding
Passport chip onboarding
The chip sayswho issued it.We check the signature.
A photographed passport can be edited. The chip inside it cannot, because the issuing state signed its contents. Toden's mobile SDKs read the chip, our servers check that signature against the country's own certificate, and the selfie is matched to the portrait stored on the chip.
The workflow
Chip-grade onboarding for customers from any country that issues electronic passports. This is a starting point: add, remove or reorder any step in the workflow builder.
Step 01
Document Intelligence
Reads the photo page and its machine-readable zone
Step 02
NFC Chip Verification
Checks the issuing state's signature on the chip
Step 03
Passive Liveness
A selfie with no prompts
Step 04
Facial Match
Selfie against the portrait signed onto the chip
Step 05
Device Intelligence
Flags emulators, rooted phones and risky networks
Step 06
AML Screening ×3
Sanctions, PEP and adverse media: 3 screens
Then your rules decide
A starting rule set
- The chip's data does not match its signatureDecline
- The chip fails the copy checkDecline
- The selfie does not match the chip portraitDecline
- The phone has no NFC, so only the document was readReview
- A screening match is foundReview
- Chip verified, face matched, screening clearApprove
Every rule is yours to change on a visual canvas, and each result records which rule decided it. Publishing a new version needs no release.
Try the workflow builderHow it works
Scan the photo page
The camera reads the machine-readable zone, which is the key that unlocks the chip.
Tap the passport to the phone
The SDK reads the chip over NFC. Where the chip supports it, the phone also asks it to sign a fresh challenge from our servers, which a copied chip cannot do.
Match the face to the chip
A live selfie is compared with the portrait the issuing state stored and signed, and the result reaches your workflow with the highest assurance level.
What powers it
The phone only carries the bytes. The signature, the certificate chain and the copy check are all judged server-side, so a patched app cannot say yes for a forged chip.
Integrate
Mount the SDK with the workflow you published, or send a hosted link and write no code. The result arrives by signed webhook, and changing the workflow never needs a release.
import { TodenVerification } from "@todenhq/sdk-react"; export function Verify({ userId }) { return ( <TodenVerification apiKey="pk_test_..." workflowId="wf_AbC123dEf456" userId={userId} onSubmit={(s) => save(s.verificationId)} /> );}{ "event": "verification.completed", "data": { "verificationId": "ver_8fk2...", "status": "verified", "assuranceLevel": "gov_db", "idType": "bvn", "country": "NG", "dataMatch": true, "facialMatch": true, "facialConfidence": 91 }}Products involved
This solution combines products you can use on their own too.
Related use cases
Frequently asked
Chip verification runs for passports and chip identity cards from countries whose signing certificates we hold, which today is well over a hundred. A document from any other country is still verified from its photo page.
Passport chip onboarding,in one workflow.
The sandbox opens when you sign up. Usage-based pricing, no sales call.