Does presence verification track the agent?

No. The phone works out on the device whether it was at the pin, and sends one summary per day. Toden never receives a route or a location history.

What does the agent need?

Your app with the React Native or Flutter SDK, and location permission. Agents on a browser can still be verified and pinned, without the presence check.

What if an agent moves?

Always-on monitoring confirms the address again on the schedule you choose. If the agent is no longer there, you are told by webhook.

Can a workflow wait for the presence result?

Yes. A workflow can hold its approval until presence is confirmed, and send anything unresolved to your team.

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 · Agent network onboarding

Agent network onboarding

Know the agent.Know the shop.Know it is still there.

An agent network puts your cash and your brand in thousands of hands. Toden verifies each agent against the government record, pins the place they trade from, and can confirm over the following days that they really are at that address, without sending anyone to visit.

Start free Read the docs

The workflow

Identity, a verified trading address and ongoing checks for agent and POS networks. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

Phone Verification

Proves the phone number with a one-time code

Per check

Step 02

Government database validation

Nigeria, BVN record

Per check

Step 03

Passive Liveness

A selfie with no prompts

Per check

Step 04

Facial Match

Selfie against the photo on the BVN record

Per check

Step 05

Address Intelligence

A map pin and a shopfront photo

Per check

Step 06

Presence verification

Confirms over several days that they are at the pin

Per check

Step 07

Device Intelligence

Flags a phone shared between agents

Per check

Step 08

AML Screening ×3

Sanctions, PEP and adverse media: 3 screens

Per check

Then your rules decide

A starting rule set

The selfie does not match the record photoDecline
Location evidence was tampered withDecline
Presence could not be confirmed in timeReview
Several agents share one pin or one phoneReview
Identity verified and presence confirmedApprove

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.

Shared surnameShared surnameShared surname

One address4 people

Chidi OkaforLives here, confirmed

Ngozi OkaforLives here, confirmed

Emeka Okafor1 verification

Amara Okafor1 verification

ReassuringShared surnames over 412 days, on separate devicesRecords built up gradually and each person used their own phone. That fits a family home.
Reassuring2 confirmed as actually living hereTheir phones were at the address over several days, which supports that they live there.
An illustration with invented people. In the console each card opens the customer's record.

How it works

1

Verify the agent

A BVN or NIN lookup, a live selfie matched to the record photo, and a phone code, from your agent app or a hosted link.

2

Pin the trading address

The agent drops a pin on a map and photographs the shopfront. The pin is checked against the address on their records.

3

Confirm they are there

With the mobile SDK, presence verification confirms over several days that the agent's phone is at the pin, and reports the result by webhook.

What powers it

A pin, a shopfront photo and directions in the agent's own words, which is how a place is actually found where street addresses are loose.

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