Nav.Wallet Overview
What is Nav.Wallet?
Nav.Wallet is a mobile money wallet platform built on top of ID.Banking’s core banking infrastructure. It delivers accessible financial services to customers across multiple channels — mobile app, USSD, and WhatsApp — targeting underbanked populations who may not have access to traditional banking.
Platform Architecture
Nav.Wallet operates as a thin API layer wrapping the existing ID.Banking platform, applying wallet-specific business logic:
- Tiered KYC — Progressive identity verification unlocking higher transaction limits
- Agent network — Physical cash-in/cash-out points with float management and commission tracking
- Phone-number routing — P2P transfers by phone number without exposing internal account identifiers
- Value-added services — Airtime purchases and bill payments directly from wallet balance
Key Metrics
| Metric | Target |
|---|---|
| Account opening time | < 2 minutes (Tier 1) |
| P2P transfer speed | Real-time |
| USSD session response | < 3 seconds |
| Agent network coverage | Scalable hierarchy |
| Channel availability | 99.9% uptime |
Business Model
Nav.Wallet generates revenue through:
- Transaction fees — Small percentage on P2P transfers, cash-out, and bill payments
- Agent commissions — Configurable rate structure for cash-in/cash-out operations
- VAS margins — Spread on airtime purchases and bill payment facilitation
- Float interest — Overnight interest on pooled wallet balances held in trust
Technology Stack
Nav.Wallet reuses the entire ID.Banking infrastructure:
- CILedger — All financial state (balances, transfers) managed by the existing double-entry ledger
- Party module — Customer identity and KYC document storage
- Fraud detection — Real-time transaction screening via IFraudDetection
- Notifications — SMS, push, and WhatsApp via INotificationService
- Authentication — JWT-based auth from the existing AuthenticationService
The wallet introduces a dedicated wallet PostgreSQL schema for wallet-specific data (proxy mappings, agent records, USSD sessions, commission configs) while keeping all financial data in CILedger.
Multi-Jurisdiction Deployment
Nav.Wallet is designed for pan-African portability — entering a new market requires configuration changes only, with no custom development per jurisdiction. All locale-specific values (currency, language, regulatory thresholds) are externalized into a single configuration layer, enabling rapid market entry measured in days rather than months.
Configuration-Only Market Entry
Unlike competitors that require bespoke builds for each country, Nav.Wallet uses a unified codebase with jurisdiction-specific configuration:
- Currency and locale — ISO 4217 currency codes, symbols, and BCP 47 locale identifiers driven by configuration
- Multi-language support — USSD, mobile app, and banking interfaces load translations from external files; new languages are added without code changes
- Regulatory parameters — KYC tiers, transaction limits, and fraud thresholds configured per jurisdiction
- Payment rail routing — Country-specific payment integrations selected at deployment time
Supported Jurisdictions
| Jurisdiction | Currency | Languages |
|---|---|---|
| South Africa | ZAR (R) | English, isiZulu, Afrikaans, Sesotho |
| Kenya | KES (KSh) | English, Swahili |
| Nigeria | NGN (₦) | English, Hausa, Yoruba, Igbo |
| Ghana | GHS (GH₵) | English, Twi, Ewe, Ga |
| Tanzania | TZS (TSh) | English, Swahili |
| Francophone West Africa | XOF (CFA) | French, Local languages |
Scalability Implications
Each new jurisdiction multiplies the addressable market without proportional engineering cost. The configuration-driven model means:
- Faster time-to-market — New country deployment in days, not months
- Lower marginal cost — No per-market development or maintenance overhead
- Consistent quality — Single codebase ensures all markets benefit from platform improvements
- Regulatory agility — Limit and threshold adjustments via configuration without release cycles