Telecom · Sub-Saharan Africa
Building a Multi-Rail Mobile Money Platform for a Regional Telecom Operator
Show how modular financial infrastructure can connect wallets, payments, agent networks and settlement across a growing mobile money ecosystem.
Regional telecom operator (anonymized)
- Faster Launch
- 30%
- Monthly Transactions
- 3M+
- Availability
- 99.99%
- Connected Rails
- 4
Faster Launch
Monthly Transactions
Availability
Connected Rails
Challenge
What needed solving
The operator ran wallet balances, airtime credit and merchant payments across separate systems, each with its own reconciliation process and its own definition of a transaction.
Adding a new bank or payment partner required a bespoke integration, which pushed every corridor launch into a multi-quarter engineering effort.
Agent liquidity and float positions were reported daily rather than continuously, limiting how quickly the network could grow past its existing regions.
Peak-period volumes exposed capacity limits in the legacy processing layer, with settlement batches completing well after the operating window closed.
Approach
How we sequenced it
Establish a single ledger as the source of truth for every balance, and treat each external partner as a replaceable rail behind a common transaction model.
Introduce jStack modules incrementally — ledger and wallet first, then payment orchestration, then settlement — so no existing service had to be switched off before its replacement was proven.
Model agent and merchant hierarchies natively so float, commissions and limits could be evaluated in real time rather than reconstructed in reporting.
Solution
What was deployed
Wallet Infrastructure
Consumer, agent and merchant wallets built on a shared double-entry ledger, with multi-currency support and configurable limits per wallet class.
Transaction Processing
An orchestration layer routing transfers, cash-in, cash-out and merchant payments across bank, card and mobile money rails with automatic failover.
Agent & Merchant Network
Hierarchical agent management with real-time float visibility, commission rules and tiered transaction limits applied at authorization time.
Reconciliation & Settlement
Continuous reconciliation between ledger entries and partner statements, with scheduled net settlement and exception queues for unmatched items.
Outcome
What changed
- New payment partners moved from bespoke projects to configuration against an existing rail interface, shortening the path to each new corridor.
- Reconciliation shifted from end-of-day batch review to continuous matching, reducing the volume of manual exceptions handled by operations.
- Agent float and commission positions became observable in real time, which allowed the network to expand into additional regions on the same platform.
- Peak-period processing ran within the operating window, with settlement completing on the same day as the transactions it covered.