Skip to navigation

User Verification

Establish who a person is, with the checks your risk appetite needs.

User Verification confirms that a person is who they say they are. You choose the checks in a workflow, the person completes them in a hosted page or your own app, and your backend receives one outcome: approved, declined or in_review.

Start here

What can be checked

CheckWhat it tells youGuide
Government IDThe ID exists and its details match the record, in supported marketsID types
Document readingThe details printed on a passport, licence or ID cardCountries
Liveness and face matchA live person is present, and matches the ID photoVerification lifecycle
NFC chipThe chip in a passport or ID card is genuineNFC chip verification
AddressWhere the customer lives, and whether evidence supports itAddress Intelligence
Duplicate accountsThe same face already has an accountLists and face search
Decision rulesYour own approve, review and decline rulesDecisioning

Watch: the essentials

Four short videos recorded in the Toden console. The written guides beside each one cover the same ground in full.

Set up onboarding once, deliver it anywhere

You will see onboarding set up as a workflow, published, and delivered through an SDK or a hosted link, then tried with test data. Written guide: Workflows.

How to Protect Your Fintech App From Fraud (3:43)

Liveness: can a photo open an account?

You will see the difference between a liveness check and a face match, and how unclear cases reach a reviewer. Written guide: Verification lifecycle.

Liveness Check (3:42)

Decision rules you can explain

You will see how approve, decline and review rules are read in order, and where the rule that decided appears on a verification. Written guide: Decisioning.

KYC Decision Rules (3:47)

One person, two accounts

You will see how face search finds a person who already has an account, how it is configured, and how a match appears on a verification. Written guide: Lists and face search.

Face Search (3:06)

Next steps