Is the search across all your customers?

No. A face is searched only against the people your own organisation has verified. Nothing is shared between organisations.

Do you track where my customers are?

No. Connections come from what a customer gave during verification: the address they pinned, the device they used and the country their connection came from. Nobody's movements are followed.

Will family members on one phone be blocked?

Not unless you say so. A shared device is a signal for your rules, and most teams send it to review rather than decline it.

What about the same person with two legitimate roles?

A match on the same verified ID number is treated as the same person, not as a duplicate.

Can I search a face on demand?

Yes. Your team can search one photo against your verified customers from the console, billed per search.

Can our team review borderline cases?

Yes. A workflow can send a result to review instead of approving or declining it. A reviewer then approves, declines or sends it back to the customer, and the decision is recorded with who made it and when.

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 · Multi-account and bonus abuse

Multi-account and bonus abuse

Ten sign-ups.One face.We notice.

Referral bonuses, sign-up credit and first-loan offers all pay out per account, which is why one person opens ten. Toden searches every new selfie against the customers you have already verified and shows when one face, one phone, one phone number or one address sits behind several names, drawn as a map of who is connected to whom.

Start free Read the docs

The workflow

Face search, device signals and blocklists that tie a new account to the ones behind it. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

Document Intelligence

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

How many people has this phone verified?

Per check

Step 05

Face Search

Searches every customer you have verified

Included

Then your rules decide

A starting rule set

The face, ID, phone or device is on your blocklistDecline
The same face under a different IDDecline
The same face under a different nameReview
The phone has verified several other peopleReview
A face you have not seen beforeApprove

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

Connection map

When a face, a phone or an address turns up again, the console draws everyone gathered around it and says in plain words what the connection means and how much weight it deserves.

Same faceSame faceSame face

One face4 people

Ada Okoro2 verifications

Grace NwosuOpened today

Ada Okoro1 verification

Blessing EzeOpened today

Needs review2 people with this face verified under a different nameA shared address does not explain a shared face. Compare the photos before deciding.
For context1 person with this face has the same name and documentThis may be a repeat verification. Check whether more than one account is expected.
An illustration with invented people. In the console each card opens the customer's record.

How it works

1

Verify the sign-up

The customer completes your normal verification. Nothing extra is asked of them.

2

Search the face and the device

The selfie is compared with every verified customer in your organisation, and the device with every device that has verified before.

3

Decide what a repeat means

A match under the same name is a returning customer. A match under another name or another ID goes to review or is declined, as you choose.

What powers it

Every verified selfie is searched against the customers you have already verified, at no extra charge, and you choose what each kind of match does.

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