How many countries do you cover for companies?

Company registries are covered in 220+ countries. In Nigeria the search reads the Corporate Affairs Commission's own register.

Do owners have to verify themselves?

Only the ones you require. You set the level for each role, from screening alone to a full identity check, and each person who needs one gets their own link.

What if the merchant leaves a director off the form?

People on the registry who were not declared are added and flagged as undisclosed, and your workflow can route on that.

Can a merchant save and come back?

Yes. An application keeps its progress, and the applicant can return to the same link to finish or to see who still has to verify.

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 · Merchant and seller onboarding

Merchant and seller onboarding

The company exists.Does the applicantspeak for it?

A registration number is public, so looking one up proves the company exists and nothing about who is applying. Toden checks the registry, reads the company's documents against that record, and verifies the applicant's own identity, then tells you whether they are a named officer.

Start free Read the docs

The workflow

Registry, documents, the applicant and the owners, in one application a merchant fills in once. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

Business Lookup

Nigeria, the company's registry record

Per check

Step 02

Company documents ×2

Two documents checked against the registry

Per check

Step 03

AML Screening ×2

The company: sanctions and adverse media, 2 screens

Per check

Step 04

Document Intelligence

The applicant's own ID

Per check

Step 05

Passive Liveness

The applicant's selfie

Per check

Step 06

Facial Match

The applicant against their ID

Per check

Step 07

Device Intelligence

Flags shared devices and risky networks

Per check

Step 08

Decision rules

Waits for the owners you require, then decides

Included

Then your rules decide

A starting rule set

The company is not on the registryDecline
The company is struck off or inactiveReview
A document names a different companyReview
The applicant is not a named officerReview
An owner or director is on a watchlistReview
Company active, applicant verified, owners clearApprove

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

The merchant finds their company

They search the registry by name and pick their business. The record comes back with its status, address, directors and shareholders already filled in.

2

They upload and verify

Company documents are read and checked against the registry, and the applicant verifies their own ID and face in the same sitting.

3

Your workflow decides

It can hold approval until the owners you require have verified, then approve, review or decline with the reason recorded.

What powers it

Name search is free and unlimited. Picking a company fills in its details and its people from the registry, so the merchant confirms rather than retypes.

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