Skip to content

Use case · Audit-ready compliance records · $1.0514 per customer

Audit-ready compliance records

Who approved this,on what evidence,under which rule?

When a regulator or an auditor asks why a customer was approved, the answer is usually spread across inboxes, spreadsheets and memory. Toden records every check, every rule and every reviewer decision on the customer's record as it happens, so the answer is already written.

The workflow

Every decision recorded with its evidence, its rule and its reviewer, ready to export. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

$0.0714

Document Intelligence

Reads the ID and checks it is genuine

Step 02

$0.08

Facial Match

Selfie against the photo on record

Step 03

$0.90

AML Screening ×3

Sanctions, PEP and adverse media

Step 04

Included

Decision rules

The rule that decided, kept with its version

Then your rules decide

A starting rule set

  • Every check passesApprove
  • A screening match needs a personReview
  • A reviewer confirms a true matchDecline
  • The ID is not genuineDecline

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

What it costs

Added up from the published rate card as this page loaded. It is what one production run of the workflow above deducts from your credit.

$1.0514per customer

  • Document Intelligence$0.0714
  • Facial Match$0.08
  • AML Screening ×3$0.90

How it works

1

Run your checks as usual

Each verification records what ran, what it found and which version of your rules decided it.

2

Let people decide on the record

Approvals, declines and case decisions are stored with who made them, when and why.

3

Export what you are asked for

Download a customer's report, your audit log or a filing-ready report.

What powers it

  1. A changed decision adds a new entry. The earlier one stays where it was.

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

Coverage

Pick a country to see the IDs you can verify there, which documents carry a chip we read, and whether business checks are available.

All countries we cover

Frequently asked

  • Yes. Every result is pinned to the workflow version that decided it, and earlier versions are kept.

Audit-ready compliance records,in one workflow.

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