Skip to content

Use case · Tiered KYC

Tiered KYC

Start light.Ask for morewhen limits rise.

A wallet that asks for everything on day one loses the customer. Tiered accounts open on one ID and unlock higher limits as the customer adds a second ID, an address and a face check. Toden runs each tier as its own workflow against the same customer record, so nothing is asked twice.

The workflow

One customer record, several workflows: each tier adds evidence instead of starting again. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

Government database validation

Nigeria, BVN: the ID the account opened on

Per check

Step 02

Government database validation

Nigeria, NIN: the second ID

Per check

Step 03

Passive Liveness

One selfie for both IDs

Per check

Step 04

Facial Match ×2

Selfie against each record photo

Per check

Step 05

Address Intelligence

A map pin checked against their records

Per check

Step 06

Device Intelligence

Flags shared devices and risky networks

Per check

Then your rules decide

A starting rule set

  • Fewer IDs pass than the tier requiresDecline
  • The two IDs name different peopleReview
  • The address is not supported by any recordReview
  • Both IDs pass and the address agreesApprove

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

Open on one ID

The first tier takes a phone number and a BVN or NIN. The account opens in seconds with low limits.

2

Upgrade with a second ID and an address

When the customer wants more, the next workflow asks for a second ID and where they live. One selfie covers both IDs.

3

Keep one record

Every tier lands on the same customer, keyed by your own user reference, with each verified ID, address and decision on one timeline.

What powers it

  1. Ask for two or three IDs in a single run, set how many must pass, and receive one result with each ID's outcome inside it.

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
}
}

Frequently asked

  • No. One selfie and one liveness check cover the whole run, and it is compared with each record photo.

Tiered KYC,in one workflow.

The sandbox opens when you sign up. Usage-based pricing, no sales call.