Ways to integrate | Toden Docs

A complete integration has three parts: something that captures the verification, something that reads the result on your backend, and a webhook that tells you when the result is ready.

1. Capture: where the customer verifies

Hosted link

We host the page. You send a link. No client code.

React (web)

@myazahq/kyc-sdk-react, a drop-in component.

React Native

@myazahq/kyc-sdk-react-native, with native liveness and chip reading.

Flutter

myaza_kyc_sdk_flutter, for iOS and Android.

Client SDKs use a publishable key. Opening a hosted link inside a WebView or iframe? See Hosted link events.

2. Server: results and risk decisions

Your backend reads verification results and makes every Risk Intelligence call, with a secret key.

Server SDKs

Node, Go, Python and more: what is available today.

REST API

Every endpoint, with an explorer and code samples.

3. Webhooks: be told when something changes

Receive webhooks

Events, payloads and retries.

Verify signatures

Check every delivery before trusting it.

Test your endpoint

Send sample events from the console.

Which key goes where

Key	Prefix	Lives in	Can do
Publishable	`pk_test_`, `pk_live_`	Browser and mobile apps	Start a verification, upload captures, read minimal status
Secret	`sk_test_`, `sk_live_`	Your backend only	Read results and media, create sessions, all of Risk Intelligence

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