Toden documentation | Toden Docs

The fastest way to add identity and risk checks to your product

Toden is trust infrastructure for digital businesses. One console and one set of API keys cover User Verification (KYC), Business Verification (KYB) and Risk Intelligence: screening, transaction monitoring, wallet screening, Travel Rule and investigations. Verify a person, verify a company, and keep watching what happens after onboarding.

The video below shows the whole arc in under four minutes: set up onboarding as a workflow, publish it, deliver it through an SDK or a hosted link, and try it with test data. The written version is the hosted link quickstart.

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

190+

Countries for ID document and face verification

Countries with company registry verification

138

Countries with passport and ID chip verification

African markets with government-record checks

Built for decisions you can defend

Passing a check is the easy part. Toden is built for the question that comes later: why was this customer approved, and can you prove it?

Every result says how strong it is

A verification does not just pass. It reports whether it rests on the document’s chip, a government record or the document alone, so you can approve the strongest automatically and review the rest.

One customer, from sign-up to every payment

The person you verified is the same record you screen, monitor and investigate. No second vendor, no joining two systems by email address.

A record of who decided, and why

Each status change keeps its source: a rule, a reviewer or your own backend. Earlier attempts are kept, never overwritten, so an audit reads what was known at the time.

Test for free, pay for real checks

Sandbox costs nothing and has a test ID for every outcome. In production you pay per check from a prepaid balance, and a failure on our side is refunded automatically.

How you integrate: start small, go as deep as you need

Most teams ship a hosted link first and add an SDK later. Every route creates the same verification and delivers the same result, so nothing is thrown away when you move.

Sandbox in minutes

Hosted link

One API call returns a link to send your customer. No client code. Recommended first.

SDKs for web and mobile

React, React Native and Flutter, published today, with a publishable key.

Server API

Submit from your backend and read results with a secret key, in any language.

Hand it to your coding agent

One brief for Claude Code, Cursor or any agent. Every page is also plain Markdown, with an llms.txt index.

Your flow, your brand

Build the steps, rules, colours and wording in the console, without code. Import your brand from your website.

Ready for the agent you already use: Claude

See how

Getting started

Quickstart

A first sandbox verification in five minutes.

Authentication

Publishable and secret keys, and where each goes.

Webhooks

Receive results as they happen.

SDKs

Client SDKs, server SDKs and hosted pages.

Not sure which route fits? Choose your integration compares them side by side.

Learn the platform on video

Short screen recordings from the Toden console. Each one is also embedded on the guide it explains, with the full steps written out beside it.

Video	You will see	Read the guide
Protect your app from fraud (3:43)	Onboarding set up once as a workflow, then delivered by SDK or hosted link	Workflows
Liveness check (3:42)	Liveness versus face match, and when a reviewer decides	Verification lifecycle
KYC decision rules (3:47)	Approve, decline and review rules, and which rule decided	Decisioning
Face search (3:06)	Finding one person with two accounts	Lists and face search
KYB explained (3:44)	What a registry proves, and following owners and directors	Business verification
Transaction monitoring (3:37)	Per-payment decisions and where rules are set	Transaction rules
Sanctions screening (3:45)	Switching on screening and ongoing monitoring	Screening
Wallet screening (3:21)	Screening a wallet and reading the result	Wallet screening
Travel Rule (4:09)	Drafting and testing a rule, and missing details	Travel Rule

Product lines

From onboarding to continuous trust.

User Verification (KYC)

Government ID checks, document reading, liveness, face match, chip reading, address checks and decision rules.

Business Verification (KYB)

Company registry lookup, company documents, and the directors and owners behind the business.

Risk Intelligence

Screening, transaction and activity decisions, monitoring, wallet screening, Travel Rule and cases.

Hosted verification sessions

Our recommended integration. You create a session, we host the flow, and you receive the result.

Create a session

A link for one person, from your backend.

Workflow builder

Countries, ID types, checks and branding.

Read the result

The full outcome, with a secret key.

Webhooks

Be told when the status changes.

Call a check directly

No session and no customer present. Send a request from your backend and get a result.

Identity check

Check one ID against the record.

Business check

Look up one company in its registry.

Face match

Compare two face photos.

Email and phone

Prove a contact with a one-time code.

Risk decision

Allow, review or block a transaction.

Wallet screening

Screen one crypto wallet address.

How each check works

ID types and countries

What can be verified, and where.

NFC chip verification

Reading the chip in a passport or ID card.

Address Intelligence

Confirming where a customer lives.

Decisioning

Rules that approve, decline or send to review.

Screening

Sanctions, politically exposed persons and adverse media.

Travel Rule

Controls for crypto transfers.

Toden was previously called Myaza Trust. Some identifiers still carry the earlier name and are correct as written: webhook headers such as X-Myaza-Signature-V2, the Myaza-Version request header, and the client packages under @myazahq. Do not rename them in your code.

Need help?

Email us

hello@toden.co

Book a demo

Talk to the team about your use case.

Service status

Live status and incident history.