01
Reviewed access
Sandbox credentials are issued after a company review, not through an open public signup.
Built in and for Africa
Verify people, businesses, and AI agents across Africa
Nani gives teams building in and for Africa a reusable identity layer for knowing who is behind every account, company, and agent.
Request company accessReviewed access for sandbox teams
Sessions
hosted links and status
Billing
credit ledger per run
Evidence
session and account history
dashboard.nani.africa/sessions
Sessions
Recent verifications
20
sessions
12
pending
0
failed
| Session | Status | Country |
|---|---|---|
| ses_8f2a... | approved | KEN |
| ses_3c91... | processing | NGA |
| ses_b704... | review | ZAF |
Trust model
Access, evidence, and account actions stay controlled.
Nani is not positioned as an open signup widget. The platform is designed around reviewed company access, scoped workspaces, and traceable verification decisions.
02
Tenant isolation
Teams operate inside their own workspace with role-based access and scoped session data.
03
Event history
Session, billing, API key, webhook, and account actions are tracked for operational review.
04
Controlled access
Sensitive workspace tools stay behind authenticated access and are never promoted from the public site.
Why Nani exists
Africa is transacting faster than identity systems can keep up.
For over a decade, Solucien has built products across the Kenya, Côte d'Ivoire, DR Congo, Botswana South Africa, and beyond. One problem followed us into every product: identity.
In South Africa, an ID number acts as a source of truth across banks, government, employers, and regulated services. Most of Africa does not have that same shared foundation, yet millions of people and businesses transact every day.
Nani is the question at the heart of trust: who is this person, business, or AI agent, and can they be trusted?
We are building one reliable identity layer for companies building in and for Africa, so teams can fight fraud, onboard faster, and stop asking users to submit the same evidence again and again.
Identity scope
KYC, KYB, and KYA belong in one trust infrastructure.
The next generation of African products needs to verify real users, legitimate businesses, and the agents acting on their behalf.
01
People
Reusable KYC for real users across African products, reducing repeated document collection and fragmented trust.
02
Businesses
KYB for registrations, ownership structures, compliance checks, vendors, merchants, and partners.
03
Agents
KYA for the next wave of personal and business agents acting on behalf of people and companies.
Product
Verification, billing, and review workflows in one operational system
Built for teams that need a controlled user flow, developer APIs, tenant billing, and compliance review without exposing sensitive tools to the public web.
01
Hosted verification
A guided consent, document, liveness, and evidence capture flow that keeps users out of your engineering backlog.
02
Workspace review
Create, search, filter, cancel, and review verification sessions with applicant references and country-specific tiers.
03
Decision webhooks
Receive structured session events and decisions so your product can react without manual reconciliation.
04
Credit ledger billing
Every session debit, top-up, adjustment, and tenant balance change is visible and exportable.
05
Re-KYC workflows
Request a new verification when documents expire, risk changes, or a user needs another compliance pass.
06
Evidence trail
Billing adjustments, session events, API key changes, and account controls leave a reviewable history.
How it works
A verification flow your product can hand off cleanly.
Create a session
Pick country, tier, flow, applicant details, and your external user reference.
Send the hosted link
Nani gives you a verification URL your user can open on mobile or desktop.
User completes KYC
The flow guides them through document capture, liveness, and required evidence.
Receive the decision
Use the dashboard, API response, and webhooks to sync approval, rejection, or review states.
Developers
Built around sessions, not screenshots
Create a session from your backend, pass your user reference, send the hosted URL, and receive the decision through webhooks or the dashboard.
curl -X POST https://api.nani.africa/v1/sessions \
-H "x-api-key: sk_live_..." \
-H "content-type: application/json" \
-d '{
"country": "KEN",
"tier": "tier2",
"flow": "user",
"external_user_reference": "user_123"
}'Company access
Request access for your company
Tell us about your company, expected verification volume, and target markets. We review each request before creating sandbox access.
Launch access
Request company access
FAQ
What teams usually ask before requesting access.
Is this self-serve yet?
For launch, companies join the waitlist. We review each request and open sandbox access for qualified teams.
Which markets are you focused on?
Nani is built for African verification workflows first, with country and tier configuration handled per customer workflow.
Can developers integrate before launch?
Yes. Waitlist teams can get sandbox API keys, hosted verification links, and webhook examples when access opens.
What happens after I submit?
Your company request goes to the Nani review queue and your contact is added to the launch email list.
Launch access
Ready to request Nani access?
Join the waitlist now. We will review your company details before issuing sandbox credentials.