Skip to content
toden

Use case · Reusable identity · $0.1428 per returning customer

Reusable identity

Verify once.Recognise themevery time after.

Asking a verified customer for their ID again costs you money and costs them patience, and a fraudster with a stolen login is never asked at all. Toden keeps the verified face on file, so a returning customer proves it is still them with one selfie.

The workflow

One full check at sign-up, then a selfie whenever you need to be sure. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

$0.06

Passive Liveness

Confirms a live person, with no prompts

Step 02

$0.0828

Biometric re-authentication

A live selfie against the verified photo on file

Step 03

Included

Decision rules

Pass or fail, sent to your backend

Then your rules decide

A starting rule set

  • The face matches the verified photoApprove
  • The match is close but not clearReview
  • No live person was detectedDecline
  • The face belongs to someone elseDecline

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.

$0.1428per returning customer

  • Passive Liveness$0.06
  • Biometric re-authentication$0.0828

How it works

1

Verify the customer once

A full identity check at sign-up puts a verified photo on their record.

2

Ask for a selfie when it matters

A new product, a new device or a large payment starts a face check, in your app or by link.

3

Get the answer in seconds

The selfie is matched to the verified photo and your backend receives pass or fail.

What powers it

  1. A selfie replaces the document, the form and the wait.

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

Products involved

This solution combines products you can use on their own too.

KYC

Identity Verification

Verify a person from their ID, a live selfie and, in five African markets, the government record. One SDK, one signed result.

Learn more
Beta

Risk Intelligence

Monitor transactions and account activity against your own rules, then investigate what they flag.

Learn more
No-code builder

Workflows

Build and version verification flows and decision rules visually, then publish without a redeploy.

Learn more

Related use cases

Account takeover protection

Score each login as it happens, and step up to a face check only when the risk is real.

Learn more

Account recovery

Recovery that depends on the person, for the moment their phone, SIM or email is not theirs.

Learn more

Tiered KYC

One customer record, several workflows: each tier adds evidence instead of starting again.

Learn more

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

  • No. One verified record serves every product you offer, and you decide when a selfie is asked for.

Reusable identity,in one workflow.

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

Start freeTalk to us