Habari
Your institution's activity on Nana.
Verifications run
0
Checked from this browser session — partner-wide totals aren't connected yet
Documents issued through Nana
Not connected yet
The API has no partner issuing endpoint.
The API has no partner issuing endpoint.
Recent activity
Verify a customer →Under Nana's rails
Every document issued through Nana is sealed and verifiable at asknana.co.ke/verify, and counts toward your customers' trade records. Your customers get proof; you get the audit trail.
Verify a customer
Check a Nana document or a customer's trade record before you lend.
Recent verifications
Issue a document
Generate a document through Nana's engine. It's sealed, verifiable, and branded as your institution.
How issuing works
1
You fill the document. Nana generates it under your brand.
2
Your customer confirms on WhatsApp with a PIN.
3
It locks, seals, and becomes verifiable — for both of you.
Issued documents
Every document your institution has issued through Nana — all verifiable.
Consents
Customers who've granted your institution access to their Nana trade records.
Data pulls
A complete, immutable log of every record your institution has accessed — for your audit team.
Compliance
Exports and controls for your audit and data-protection team.
Generate an export
Data protection
Your institution is the data controller for records it pulls under customer consent. Nana provides the consent mechanism and the immutable log. Under Kenya's Data Protection Act 2019, customers can view and revoke access at any time.
API credentials
For your engineering team's integration. Keys are managed here; the technical console lives in the developer portal.
Building the integration? Your developers create and revoke API keys, and manage webhooks and the sandbox, in the developer portal. This page is for oversight; that's for building.
Team
Staff with access to this partner console.
Billing
Usage-based — you pay for verifications run and documents issued.