Each payment you send for a decision is one transaction assessment. The face check is billed only on the payments you challenge.

Do I need to send every payment?

Sending them all is what makes the customer's baseline meaningful, and it is priced for that. You can also send only the ones above a limit.

Can amounts be in naira?

Yes. Thresholds are set per currency, and an event is judged against the limit for its own currency.

Can my team see why a payment was blocked?

Yes. Each decision lists the rules that fired and what they read, and the alert sits on the customer's record.

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 · High-value payment approval

High-value payment approval

Before money moves,check whois moving it.

The costly moment in a takeover is not the login, it is the transfer. Score each payment as it is requested, let the ordinary ones through, and ask for a live selfie before a large payout, a new beneficiary or a changed limit goes ahead.

Start free Read the docs

The workflow

A decision on every payment, and a face check on the few that deserve one. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

Transaction assessment

Scores the payment against the customer's history

Per check

Step 02

Biometric re-authentication

A live selfie against the verified photo on file

Per check

Step 03

Decision rules

Release, hold for review, or block

Included

Then your rules decide

A starting rule set

An ordinary payment to a known beneficiaryApprove
A first payment to a new beneficiary above your limitAsk for more
An amount far outside this customer's normalAsk for more
Structured amounts just under a thresholdReview
The face check failsDecline

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

Send the payment before you release it

Amount, beneficiary, channel and device go to one endpoint. You get allow, review or block with the rules that fired.

2

Challenge the risky ones

Your rules pick the payments that need more: a first payment to a new beneficiary, an amount far above the customer's normal, a new device.

3

Release on a pass

The customer takes a selfie, your backend redeems the proof, and the payment continues. A fail holds it and raises an alert.

What powers it

Each payment is scored as it arrives against thresholds, velocity, new beneficiaries and the customer's own baseline, with no batch job.

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