Skip to content
Businesses

Onboard verified customers in seconds, not days.

Replace manual document review with a reusable credential your customers already hold. Lower cost per check, fewer drop-offs, less fraud.

NGA<<TRUEID<<VERIFIED<<2201<<9814<<NIN<<0912<<NIMC · NINMATCHNIBSS · BVNMATCHFRSC · LicenceMATCH
Onboarding

Every upload screen is a place customers leave.

Document collection is not one step. It is four, and each one loses people who fully intended to become your customer.

Start

Customer sees a document-upload screen and closes the tab.

They see a consent prompt for a credential they already hold.

Capture

Blurred photographs, cropped cards, glare on a laminated ID.

Nothing is captured. The credential was verified once, at source.

Review

Manual review queues measured in days, not seconds.

A signed attestation returns in real time, with an assurance tier attached.

Re-KYC

The same customer re-verified from scratch at renewal.

Batch re-verification confirms current status against the credential.

Improvement depends on your current flow, your assurance tier, and your customer mix. We would rather size it with you against your own funnel data than advertise a percentage we cannot stand behind.

What you get

A verification you did not have to perform.

Reusable credentials mean you stop paying for work another institution already did against the same source.

For your business
  • Faster, cheaper onboarding
  • Fraud-resistant KYC pipeline
  • Drop-in API and SDKs
  • Usage-based pricing

Fraud signal that compounds

Document tampering signals, device reputation, and velocity checks run on every request. Network-wide patterns surface anomalies no single institution sees alone.

Assurance tiers you select

Tier 1 for age assertions and low-value wallets, Tier 2 for standard KYC, Tier 3 where address confirmation and multiple sources are required.

Audit your regulator can read

Every share writes a consent receipt: requester, scope, attributes, timestamp. Exportable without commissioning a bespoke report.

Operational safety by default

Versioned endpoints with a published deprecation policy, idempotency keys on every write, and errors that name the field and the fix.

Integration

From sandbox key to live traffic.

Four steps, none of which require a sales call to begin.

01

Get sandbox keys

Self-serve from the dashboard. Fixtures cover every failure path, including manual review, so you build against reality rather than the happy case.

02

Choose an integration shape

REST API for full control, hosted verification for the fastest path live, or QR handoff for in-branch and point-of-sale.

03

Request the narrowest claim

Ask for "over 18" or "kyc_status" rather than a full profile. Narrower scopes convert better and shrink what you have to store.

04

Subscribe to webhooks

Revocation, re-verification, and status changes arrive as events. No polling, and no stale customer records.

Pricing

You pay per completed check.

Rates depend on assurance tier and volume, with discounts as usage grows. Requests that fail on our side, or never reach a source, are not billed. There is no minimum commitment on the business tier.

  • Verification stays free for individuals — partner fees fund the platform
  • Volume-tiered per-verification pricing, quoted directly until general availability
  • Enterprise and public-sector terms cover data residency, uptime credits, and named incident contacts

Onboard verified customers in seconds.

Tell us your use case and volume, and we will tell you honestly whether we fit yet.