Identity verification

Is this who they say they are?

Look a person up in the registry that issued their document, then score what they told you against what the registry says. You get a verdict and the field-by-field reasoning behind it.

  • 11countries with direct registry lookups
  • 20identity checks
  • <2stypical round trip
What you were given

GHA-000000000-2

  • First nameJohn
  • Last nameDoe
  • Date of birth1997-06-04
  • Phone+233 24…
What the registry says

National registry · Ghana

  • First nameJohn Kwame90
  • Last nameDoe100
  • Date of birth1997-06-04100
  • Phonenot returned

MATCH

95/100
How it works

Does the number exist, and does the person match it?

  1. 1

    You send a number

    A Ghana Card, a BVN, a NIN, a passport — whichever the country issues. Plus whatever the customer told you: name, date of birth, phone.

  2. 2

    We ask the registry

    Routed to the source licensed for that country. If one is down, the next takes it — your call does not change.

  3. 3

    We score the match

    Every field the registry returned is compared to what you supplied and weighted. A field the source never returned is excluded, not scored zero.

  4. 4

    You get one verdict

    MATCH, PARTIAL or NO_MATCH, with the per-field breakdown so a human can see exactly which detail disagreed.

In practice

One request. One envelope.

Every product on this page shares the same request shape, the same response envelope and the same audit trail. Adding one later is a new value in service, not a new integration.

  • Ghana Card
  • Ghana passport
  • GhanaPost GPS address
  • BVN
  • BVN validate
  • NIN
  • Nigeria phone
  • Kenya national ID
  • Kenya passport
  • KRA PIN
  • Uganda NIN · voter · telco
  • South Africa ID
  • Zambia NRC
  • Zimbabwe ID
  • Angola BI
  • UK eKYC
  • Canada eKYC
  • Consumer identity report
  • Consumer profile
  • Age verification
POST /api/v1/identity/gh/ghana-card
{
  "identifier": { "type": "ghana_card", "value": "GHA-000000000-2" },
  "params": { "firstName": "John", "lastName": "Doe" }
}
{
  "person": { "fullName": "John Kwame Doe", "dateOfBirth": "1997-06-04" },
  "match": {
    "verdict": "MATCH",
    "score": 95,
    "fields": {
      "firstName": { "supplied": "John", "found": "John Kwame", "score": 90 },
      "lastName":  { "supplied": "Doe",  "found": "Doe",        "score": 100 }
    },
    "notReturned": ["phone"]
  }
}
Where it is used

Reached for when the answer has to hold up.

Account opening

Confirm the ID before the account is funded, not after.

Loan origination

Tie the applicant to a real registry record before pulling bureau data.

Agent and rider onboarding

Verify at scale without a branch visit.

Worth knowing. A registry match proves the number belongs to that person. It does not prove the person in front of you is them — that is what biometrics are for.

Get started

Ready to trust every decision?

Get sandbox keys in minutes, or talk to us about volume pricing, bring-your-own credentials and data residency.