Fund a wallet, run checks, see the cost of every call by source. Volume tiers kick in automatically.
Integrate against realistic test data, priced exactly as live — so what you spend building is what the flow will cost.
Live data from licensed identity and credit partners, priced per product and per source.
For lenders and banks running tens of thousands of checks a month.
The things worth knowing before you write any code — costs, data handling, what happens when a check fails. If something here is still vague, ask us and we will make it specific.
Sandbox keys are issued the moment you sign up, and every check is a single POST that returns one normalised answer. Most teams have identity verification running the same afternoon. A full lending flow — identity, credit, affordability and a decision — is usually a few days, most of it spent on your own rules rather than on us.
Yes, and without a card. The sandbox mirrors live exactly: same request, same response shape, same prices shown against every check, so nothing you build has to change when you switch. It ships with test people who fail in specific ways — a clean applicant, a thin credit file, one in arrears with a judgement debt, one who trips a watch list — so you can build the unhappy paths before you meet them.
A prepaid wallet, charged per check, in your own currency — cedis for Ghana, dollars elsewhere. No monthly minimum, no per-seat fee, no annual commitment. Every response carries the cost of that check and every charge lands on the statement against the run that caused it, so the bill reconciles to the work.
You are not charged for it. A check is billed only when a source actually answers, so a timeout, an outage or a registry that is down costs you nothing. If a source is slow or unavailable we try an alternative that can answer the same question before giving up, and the response tells you how many attempts it took.
Keep as little of it as the job allows. Selfies and document images are deleted within 24 hours of the check, bank statements within 30 days, and raw upstream payloads within 90. What remains is the normalised result you paid for. Identifiers, results, declarations and uploaded documents are encrypted at rest, so a copy of the database taken without the application is not a readable file of anybody’s identity.
Every credit check refuses to run without a permissible purpose and a consent reference, and both are stored alongside the result. Every action in the console is written to an audit log that records who did it, when, and from where — and the log is hash-chained, so an entry altered after the fact can be detected rather than merely trusted. All of it exports.
Yes. Five roles: owner, admin, developer, analyst and finance. An analyst can run and read checks but never touches API keys or the wallet; finance sees money and not identity data; developers hold keys and webhooks. Every view is logged either way.
Only if you want to. Hosted verification flows give you a branded journey — document capture, liveness, the lot — behind a single link you send or embed, with the result arriving in your dashboard and on your webhook. If you would rather own the interface, every step is available as an API call instead.
You get the degree of the match and the reason for it, not a verdict we invented on your behalf. A missing middle name is reported as a missing middle name, a transposed first and last name is reported as transposed, and where a document was checked against a registry we tell you which fields agreed and which did not. What counts as good enough is a threshold you set, because it differs between opening a wallet and approving a loan.
Ghana and Nigeria in full — identity, credit, fraud and messaging. Identity verification also covers Kenya, Uganda, South Africa, Zambia, Zimbabwe, Angola, the United Kingdom and Canada. Credit data is available for Ghana, Nigeria and Zimbabwe. The coverage page lists exactly which checks are live in each.
Keys are scoped to the products they may call, can be pinned to a set of IP addresses, and rotate with a grace period so you are never forced into a flag-day cutover. Sandbox and live are separate keys against separate wallets and separate data. Outbound webhooks are signed and timestamped so you can verify a delivery came from us and is not a replay.
The status page shows every source’s health in real time, and the dashboard shows the same for your own traffic — latency, failures and which checks are affected. Failures are visible in your verification list with the error and the attempts, not buried. Support is email and shared channel, and we answer.
Get sandbox keys in minutes, or talk to us about volume pricing, bring-your-own credentials and data residency.