The verdict in three sentences
The raw failure rate of a mobile money payment in Lagos is 8 to 12 %, but 45 % of those failures are recoverable if you retry at the right moment. The most common error code is "insufficient funds" (30 % of cases), followed by USSD timeouts at 120 seconds and network drops. A retry logic at 2, 10 and 30 minutes paired with an SMS reminder recovers about +6 net conversion points.
Mobile money failure taxonomy
Not all failures are handled the same way. Insufficient funds is retried later; a timeout is retried fast; a config error is never retried. Here is the distribution observed across Paystack rails and mobile money.
| Failure type | Share of failures | Recoverable? | Retry delay |
|---|---|---|---|
| Insufficient funds | 30 % | Yes (deferred) | 30 min to 6 h |
| USSD timeout (120 s) | 22 % | Yes (fast) | 2 min |
| Network drop | 18 % | Yes | 2 to 10 min |
| Wrong PIN (3 tries) | 12 % | Partial | 10 min |
| Limit reached | 10 % | No same-day | T+1 |
| Merchant config | 8 % | No (must fix) | - |
Reading the error code returned by the provider drives the whole strategy: you do not retry "insufficient funds" the way you retry a "timeout".
The exponential backoff that recovers revenue
The principle: do not harass, but retry at growing intervals while switching channels. An immediate retry annoys; a retry at the right time converts.
| Attempt | Delay | Channel | Retry success rate |
|---|---|---|---|
| 1st retry | 2 min | Same funnel | 28 % |
| 2nd retry | 10 min | SMS with link | 19 % |
| 3rd retry | 30 min | SMS + amount reminder | 12 % |
| 4th retry | T+1 morning | SMS + WhatsApp | 8 % |
Combined, these retries recover a significant share of the 45 % recoverable failures. The key is idempotency: each retry must check no payment already succeeded, to avoid double charges.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Mini case study
Chidi sells clothing online in Lagos. He processes 1,500 orders/month at an average basket of NGN 25,000. With a 10 % raw failure rate, he loses 150 orders, i.e. NGN 3,750,000 in blocked potential revenue. By enabling a 2/10/30-minute retry logic that recovers 40 % of those failures, he saves 60 orders, i.e. NGN 1,500,000/month in extra revenue, with no marketing spend.
FAQ
What share of mobile money failures is recoverable? In 2026, the order of magnitude is 45 % of failures. The rest (merchant config, limits) needs manual action or waits until the next day.
What is the most common error code? "Insufficient funds" is about 30 % of failures. It is recovered by retrying after a delay, often once the customer has topped up their account.
How often should you retry? A backoff at 2, 10 then 30 minutes, plus a final attempt at T+1 morning. Retrying more often annoys without improving the success rate.
How many conversion points can you win back? A well-tuned retry logic recovers about +6 net conversion points, huge relative to an active store's revenue.
How do you avoid double charges on retries? With a per-order idempotency key: each retry checks the real payment status before triggering a new one. It is essential for customer trust.
Let's talk about your project. We implement idempotent retry logic that recovers your lost payments. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
