Identity API
Overview
Identity API
Check that a Ghanaian customer is who they say they are: match their ID details against the national registers, and confirm a live person is completing the check.
Two ways to use it
Hosted verification sessions
You create a session for a customer and send them the link. On a Sendexa-hosted page they enter their Ghana Card or Voter ID details, which we match against the register, then complete a short camera liveness check. You get the outcome by webhook or by polling.
Use this for onboarding, where you need both the ID match and a live person.
Hosted sessions →Direct KYC checks
Call a registry check from your own server with details you already hold, and get the answer in the same response. No end-user interaction.
Use this when you collect the details yourself, or to confirm a payout account.
KYC checks →Available checks
| Check | Endpoint | What it answers |
|---|---|---|
| Ghana Card | POST /v1/identity/ghana-card | Do these details match the NIA register? Returns a match flag and a name-match score. |
| Voter ID | POST /v1/identity/voter-id | Do these details match the EC voter register? Returns a match flag and a name-match score. |
| SIM name | POST /v1/identity/msisdn-name | Whose name is this phone number registered to? |
| Mobile Money | POST /v1/identity/mobile-money | Is this a registered MoMo wallet, and whose name is on it? |
| Bank account | POST /v1/identity/bank-account | Whose name is on this Ghanaian bank account? |
All checks cover Ghana only. Every check is billed per request from your Sendexa wallet, whether or not the details match. If the registry can't be reached, the charge is refunded automatically.
What this API doesn't do
There's no document scanning or OCR, no comparison of a selfie against the ID photo, and no PEP, sanctions or AML screening. Liveness combines gestures (blink, smile, turn your head) with a screen-flash check the server verifies: the face must reflect random colours issued for that attempt. That stops photos, replays and frozen feeds, and doubtful results go to your review queue, but it isn't certified presentation-attack detection. Plan your risk controls with that in mind.