How does the customer re-verify?

From a link you send, in your app or in a browser. It is prefilled with who they are, and asks only for the steps you pick.

Can a risk event trigger a refresh?

Yes. A policy can start a re-verification when a signal arrives, such as a new device or a network flag, without waiting for the clock.

What if the name on the new document changed?

The result shows the difference, and the new ID is added to the same customer only when the names do not clearly disagree.

Do you keep checking customers after onboarding?

Yes. Customers are re-screened on a schedule that follows their risk, you are told before a verified document expires, and the transactions and logins you send are scored as they arrive.

Can we change the checks without a release?

Yes. Workflows are built and published in the dashboard. Your app keeps the same workflow ID and picks up the new version, and every earlier version is kept so you can see which one decided a past check.

Per check, from prepaid credit in US dollars. Each check is billed by the steps it runs, with no subscription, seat fee or minimum, and the sandbox is free. Every rate is published on the pricing page.

Use case · Perpetual KYC

Perpetual KYC

KYC is nota one-timeevent.

Documents expire, people move and risk changes. Instead of a remediation project every few years, Toden keeps a clock on each customer: it tells you before a verified document runs out, screens them again as lists change, and sends a re-verification link when something no longer holds.

Start free Read the docs

The workflow

A re-verification clock, ongoing screening and a living risk score on every customer. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

Document Intelligence

The renewed passport, licence or national ID

Per check

Step 02

Passive Liveness

A selfie with no prompts

Per check

Step 03

Facial Match

Selfie against the document photo

Per check

Step 04

Device Intelligence

Flags a device the customer has never used

Per check

Step 05

AML Screening ×3

Sanctions, PEP and adverse media: 3 screens

Per check

Then your rules decide

A starting rule set

The refreshed check passesApprove
The new document names a different personReview
A new screening match appearsReview
The customer does not respond before the deadlineReview

Every rule is yours to change on a visual canvas, and each result records which rule decided it. Publishing a new version needs no release.

Try the workflow builder

How it works

1

Every customer gets a clock

The date their verified document expires, or a year from verification where there is none, sets when they are next due.

2

You are told ahead of time

A webhook fires a month before a customer falls due, and the console lists everyone coming up.

3

They refresh only what changed

Send a link that asks for the expired document, the new address or a fresh selfie, and the result lands on the same customer record.

What powers it

Customers falling due appear in a renewals list and trigger a webhook, once per cycle, so nobody is chased twice.

Integrate

Mount the SDK with the workflow you published, or send a hosted link and write no code. The result arrives by signed webhook, and changing the workflow never needs a release.

Verify.tsxTypeScript · React

import { TodenVerification } from "@todenhq/sdk-react";
 
export function Verify({ userId }) {
  return (
    <TodenVerification
      apiKey="pk_test_..."
      workflowId="wf_AbC123dEf456"
      userId={userId}
      onSubmit={(s) => save(s.verificationId)}
    />
  );
}

verification.completedWebhook · JSON

{
  "event": "verification.completed",
  "data": {
    "verificationId": "ver_8fk2...",
    "status": "verified",
    "assuranceLevel": "gov_db",
    "idType": "bvn",
    "country": "NG",
    "dataMatch": true,
    "facialMatch": true,
    "facialConfidence": 91
  }
}