For most of our clients, the first payment their customers make will not be by card. It will be a mobile-money prompt on a feature phone or a smartphone. Getting that flow right — fast, clear and reconciled — matters more than any other part of checkout.
1. Design for the asynchronous reality
A mobile-money request is not instant. The customer receives a prompt, enters a PIN and the provider calls you back seconds — or minutes — later. Your product must treat every payment as pending until a verified callback arrives.
- Create a payment record before you call the provider.
- Show a clear “approve on your phone” state with a timeout.
- Handle callbacks idempotently — the same notification can arrive twice.
- Poll the provider’s status endpoint as a fallback when callbacks fail.
2. Reconcile every day
Even well-built integrations drift: network errors, reversed transactions and manual refunds all happen. A daily reconciliation job that compares your ledger with provider statements catches problems before your finance team does.
3. Support more than one rail
Customers are loyal to their network. Supporting both MTN Mobile Money and Airtel Money — directly or through an aggregator such as Pesapal — widens your reach and gives you a fallback if one provider is degraded.
4. Treat security as a feature
- Keep API keys in a secrets manager, never in the app.
- Verify callback signatures or source IPs.
- Log every state change with who, what and when.
- Apply least-privilege access to payment dashboards.
Where to start
If you are adding payments to an existing product, start with a short discovery sprint: map the money flows, choose providers, and prototype the riskiest path end-to-end in the sandbox before committing to a full build.