Demo
Try the verification flow
Step through a verification on sample documents. Nothing is uploaded.
Interactive tour with sample data. No verification runs and nothing is uploaded. Documents and faces on these screens are drawings made for this page.
The five screens of a verification
Step 1: Scan your document
The user photographs the ID.
Step 2: Reading your document
- Full name
- Sample Person
- Date of birth
- 14 March 1990
- Document number
- SAMPLE-ONLY
- Expiry date
- 14 March 2031
Fields appear as the document is read.
Step 3: Take a selfie
A clear image of the person.
Step 4: Follow the ovals
The face moves through two ovals.
Step 5: Approved
Example result
Approved
- Document authentic
- Face match
- Liveness
- No deepfake
The result card lists every check passed. These are sample results.
What happens here
Document recognition reads printed and handwritten text and the MRZ with checksum. Your integration starts the session with one call.
Module: Document verification
Integrator sees: POST /kyc/session/create returns a sessionId.
What happens here
Document anti-fraud checks for screen photos, photocopies, printouts, glued photos, edited images and logical data errors.
Module: Document verification
Integrator sees: a document entry in results.
What happens here
Face match compares the selfie with the document portrait. Deepfake and face-swap detection runs inside the selfie and liveness steps.
Module: Face verification
Integrator sees: a selfie entry in results.
What happens here
Active liveness: the user moves the face through two ovals, a movement challenge that helps detect presentation attacks.
Module: Liveness
Integrator sees: a liveness entry in results.
What happens here
The session ends with a result your system reads by status or receives as a webhook.
Module: Webhooks
Integrator sees: the SESSION_COMPLETE event, then /kyc/session/status.
What the tour shows
Three parts of every verification
Document recognition and anti-fraud
The document is read and checked for screen photos, photocopies, printouts, glued photos, edited images and logical data errors.
Document verificationFace match and liveness
The selfie is matched to the document portrait, and the user moves the face through two ovals, a movement challenge that helps detect presentation attacks.
LivenessDeepfake detection
Generated and swapped faces are spotted inside the selfie and liveness steps.
Face verification
What the tour leaves out
Production access adds your own scenario, AML screening, the dashboard and webhooks.
How to connect it to your product
REST API 2.0 and a branded web widget. Start with the quick start or read about the web SDK.
Questions, answered plainly
What can I try in the tour?
You can step through the five screens of a verification: scan a document, read its fields, take a selfie, follow the ovals and see an example result. All documents and faces are drawings made for this page.
Do I need to register?
No. The tour is open and needs no account.
Which documents does the platform support?
10,000+ document types, 195+ countries and territories. Ask us for the full document list for your markets.
What happens to data in the tour?
Nothing is collected. The tour runs in your browser on sample data. It does not use your camera and it sends nothing.
Do I need a camera?
Not for the tour.
How does the tour differ from a production integration?
In production you design your own scenario: the steps, documents, countries and rules. The tour shows a typical flow with sample data.
How do I move to a trial?
Through the welcome credit, or contact us and we will agree the next step.
Talk to us about a live demo
Tell us about your use case and we will set up a walkthrough with you.
Request a live demo