Skip to content

Use case · Email and phone verification · $0.0621 per sign-up

Email and phone verification

A fake emailis wherefake accounts start.

Bonus abuse, spam sign-ups and throwaway accounts all begin with a contact nobody owns. Toden sends a one-time code to the email or phone, and tells you whether the address is disposable and whether the number is a virtual line.

The workflow

Confirm the customer holds the email and the phone, and learn what kind of contact it is. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

$0.02

Email Verification

A one-time code, plus disposable address detection

Step 02

$0.02

Phone Verification

A one-time code, plus the line type

Step 03

$0.0221

Device Intelligence

The phone and network behind the sign-up

Step 04

Included

Decision rules

Approve, review or decline on your rules

Then your rules decide

A starting rule set

  • Both codes are confirmed on an ordinary contactApprove
  • The phone is a virtual numberReview
  • The same number is on several other accountsReview
  • The email is a disposable addressDecline

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.0621per sign-up

  • Email Verification$0.02
  • Phone Verification$0.02
  • Device Intelligence$0.0221

How it works

1

Send a code

One API call sends a one-time code by email or SMS.

2

Check what they type

A second call confirms the code and returns what Toden learned about the contact.

3

Decide on the signals

Refuse disposable addresses, review virtual numbers, and let everyone else through.

What powers it

  1. Throwaway inboxes are flagged the moment the code is sent.

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. It is a separate API you can call at sign-up, at payout or when a customer changes their number.

Email and phone verification,in one workflow.

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