Adding a wallet is a business decision, not a logo-collection exercise
M-PESA dominates Kenya's mobile-money subscription base, but Airtel Money has grown into a meaningful second network. The Communications Authority reported Airtel Money at 11.1% of active mobile-money subscriptions in the quarter ending June 2026.
That does not automatically mean every merchant should integrate a second wallet.
Four reasons a second wallet can be worth it
1. Customers ask for it
The strongest signal is direct customer demand. Support requests, failed checkouts and sales feedback are more useful than market share alone.
2. It recovers final failed payments
If an M-PESA attempt ends unsuccessfully, another enabled wallet can give the customer a second path to settle the same invoice.
3. The merchant wants less dependence on one rail
A second wallet can reduce operational dependence on one provider route, though it does not eliminate the need for provider-specific incident handling.
4. The business serves customer segments with different wallet usage
A merchant's own audience can differ from national averages. Measure method preference by cohort rather than assuming the market-share chart describes every customer segment.
What changes after you add a second wallet
- Checkout or payment-link UX needs method selection.
- Recovery logic needs wallet-switch rules.
- Provider status has to be normalized.
- Finance needs one invoice ledger across both methods.
- Support staff need to understand which provider evidence belongs to which attempt.
- Merchant capability must be configured per wallet/provider rather than assumed globally.
What should not change
The commercial model should remain one customer, one invoice, one billing period and one final paid state.
For the detailed operating flow after a second wallet is enabled, see the M-PESA and Airtel Money workflow guide.
A simple decision test
- Demand: are customers asking for or attempting to use the second wallet?
- Recovery: would it recover a meaningful number of failed payments?
- Coverage: is the merchant actually approved for the route?
- Operations: can finance and support handle the additional provider evidence?
- Economics: do the expected benefits justify integration and operating cost?
If the answer is weak across all five, keep the payment experience simpler.
Measure the result after launch
- Share of successful payments by wallet.
- Wallet-switch recovery rate.
- Support contacts by payment method.
- Automatic match rate by provider.
- Manual reconciliation effort.
A second wallet should earn its place in the product.
Sources
- Communications Authority Q4 FY2025/26 sector report: https://www.ca.go.ke/sites/default/files/2026-09/Sector%20Statistics%20Report%20Q4%202025-2026.pdf
- Airtel Africa Developer Portal: https://developers.airtel.africa/
- Safaricom Daraja API catalogue: https://developer.safaricom.co.ke/apis
