> Toden documentation. For the full index fetch /llms.txt. Every page is available as Markdown by appending .md to its URL. Identity verification uses /api/kyc, Risk Intelligence uses /api/v1; they are separate contracts with different error shapes. Never invent an endpoint, field or enum value: read the API reference page for the operation first.

# User Verification

> An overview of Toden User Verification (KYC): what it checks, how to start, videos, and where each guide lives.

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

#### [Quickstart](/get-started/quickstart-hosted)

A first sandbox verification with one API call.

#### [Choose an integration](/get-started/choose-integration)

Hosted link, SDK or server API.

#### [Verification lifecycle](/user-verification/concepts/verifications)

Every status and what to do with it.

## What can be checked

| Check                   | What it tells you                                                    | Guide                                                                  |
| ----------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Government ID           | The ID exists and its details match the record, in supported markets | [ID types](/user-verification/concepts/id-types)                       |
| Document reading        | The details printed on a passport, licence or ID card                | [Countries](/user-verification/concepts/countries)                     |
| Liveness and face match | A live person is present, and matches the ID photo                   | [Verification lifecycle](/user-verification/concepts/verifications)    |
| NFC chip                | The chip in a passport or ID card is genuine                         | [NFC chip verification](/user-verification/checks/nfc-chip)            |
| Address                 | Where the customer lives, and whether evidence supports it           | [Address Intelligence](/user-verification/checks/address-intelligence) |
| Duplicate accounts      | The same face already has an account                                 | [Lists and face search](/user-verification/workflows/lists)            |
| Decision rules          | Your own approve, review and decline rules                           | [Decisioning](/user-verification/workflows/decisioning)                |

## 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](/user-verification/workflows/workflows).

### 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](/user-verification/concepts/verifications).

### 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](/user-verification/workflows/decisioning).

### 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](/user-verification/workflows/lists).

## Next steps

#### [Design a workflow](/user-verification/workflows/workflows)

#### [Embed an SDK](/integrate/sdks/overview)

#### [Receive webhooks](/integrate/webhooks/overview)