> 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. # How Toden compares > A developer summary of what Toden covers in one platform, the rows used in the public provider comparisons, and links to each sourced comparison page. Toden is trust infrastructure for digital businesses: verify people and businesses, detect fraud, make risk decisions and monitor what changes. This page summarises what that covers for a developer choosing a provider. The full, sourced comparisons live on the Toden website. > **Note** > > **Last verified: 12 October 2026.** The website comparisons cite public product and pricing sources for every entry. Vendors change their products, so a comparison can go out of date. If something is wrong, [tell us](https://toden.co/contact) and we will correct it. ## What Toden covers in one platform The website compares providers on 16 rows in three groups. The table lists each row and what Toden does on it. Every Toden entry is checked against the product. ### Verification | Row | On Toden | | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Government database checks | Identity numbers checked against a government record in Nigeria, Ghana, Kenya, South Africa and Côte d'Ivoire | | Document and biometric verification | Document capture with liveness and face matching. Documents from 190+ countries | | Passport chip (NFC) reading | The chip is read on a phone and authenticated on the server against the issuing country's signature, for the countries the trust list covers | | Biometric re-authentication | A returning user proves it is still them with a live selfie matched against their enrolled reference | | Business verification with key people | A registry lookup plus the directors and beneficial owners behind the company. Company registries in 48 countries, and each person can be screened and verified | ### After onboarding | Row | On Toden | | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | | Sanctions, PEP and adverse-media screening | Customers screened at onboarding, with a reviewer deciding each match | | Transaction and event monitoring | Transactions, logins and other events scored against rules your team writes and backtests on stored events | | Investigation cases | Alerts grouped into cases with an owner, deadlines by priority and notes that cannot be edited | | Suspicious activity reports (SAR and STR) | Drafted from the case in the goAML structure with an XML export. The person who drafts a report cannot be the one who files it | | Ongoing re-screening and re-verification | Re-screening on a schedule, and re-verification falling due from the document's expiry date | ### Platform and commercials | Row | On Toden | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | | Decision rules with a recorded trace | Rules approve, decline or send to review, with a record of which rule decided. Every published set of rules is versioned | | Workflow builder | The flow is assembled in the console and changed without an app release. A published workflow runs from a hosted link or by id in the SDK | | SDKs for web and mobile | SDKs for web, React Native and Flutter | | Self-serve sandbox | Opens when you sign up, with test IDs for pass and failure outcomes | | Pay-per-check pricing | Prepaid, with the checks that ran itemised on every verification | | No monthly minimum | No minimum monthly spend and no platform fee | ## How the website marks other providers The comparison pages use three marks, and it helps to know what each one means before you read them. | Mark | Meaning | | -------------- | ----------------------------------------------------------------------------------------------------------------------- | | Tick | The vendor's own site, documentation or pricing page names the capability | | Partial | It is an add-on, limited to some plans, or narrower than the row | | Blank or cross | It could not be confirmed from the vendor's public pages on the review date, or the published terms differ from the row | > **Warning** > > A blank or a cross does **not** mean the vendor lacks the capability. It means we could not confirm it from public pages on the date shown. Where that is the case the page says so and suggests you ask the vendor. Each provider page lists its sources. Published list prices are quoted only with their source and date, and the pages do not state that any vendor is dearer or cheaper. ## Read the full comparisons The comparison hub covers all seven providers and a migration plan: an assessment of your current stack, bulk import, a parallel run and a security review. #### [Comparison hub](https://toden.co/switch) All providers, the methodology and how a move works. #### [Didit](https://toden.co/switch/didit) Sourced comparison with Didit. #### [Smile ID](https://toden.co/switch/smile-id) Sourced comparison with Smile ID. #### [Dojah](https://toden.co/switch/dojah) Sourced comparison with Dojah. #### [Veriff](https://toden.co/switch/veriff) Sourced comparison with Veriff. #### [Persona](https://toden.co/switch/persona) Sourced comparison with Persona. #### [AiPrise](https://toden.co/switch/aiprise) Sourced comparison with AiPrise. #### [Sumsub](https://toden.co/switch/sumsub) Sourced comparison with Sumsub. This page does not restate what each provider offers. Those entries carry a source and a review date, and they belong on the page that keeps both up to date. ## Test it on your own traffic A comparison table is a starting point, not a decision. The useful test is your own traffic: 1. Build against the sandbox. It opens at sign-up and is never charged. See [Sandbox testing](/get-started/sandbox-testing). 2. Import a sample of customers you have already verified. 3. Run both platforms side by side. 4. Compare the results before you commit to anything. For the security side of a vendor review, see [Security and compliance](/get-started/security/security-and-certifications) and [Status and reliability](/get-started/status-and-reliability).