The verdict in three sentences
A USSD timeout is not a payment failure, it's an unknown status: in 2026 in Kigali, between 5% and 12% of MTN MoMo USSD payments time out depending on network load. The gravest mistake is jumping to "failed" too fast and re-charging the customer. The right mechanics combine a confirmation window, spaced status polling and exponential backoff to recover an order of magnitude of +9% of transactions.
The confirmation window and status polling
When a customer approves a USSD payment, confirmation isn't instant. You must allow a 60-120 second window, then query status via polling, without hammering the API. Overly aggressive polling triggers a rate-limit and makes things worse.
| Returned status | Recommended action | Delay before next action |
|---|---|---|
| PENDING | Keep polling | 5s, then 10s, then 20s |
| SUCCESS | Confirm the order | immediate |
| FAILED | Offer a new payment | immediate |
| TIMEOUT (no response) | Extended polling then flag to verify | up to 120s |
| RATE_LIMITED | Slow the polling (backoff) | double the interval |
| UNKNOWN after 120s | Manual review / reconciliation | deferred |
The exponential backoff principle: instead of polling every 2 seconds, space it 5s, 10s, 20s, 40s. You stay under the rate-limit threshold while covering the confirmation window.
Timeout rate and recovery after retry
A well-built retry never re-charges: it checks status first. If the first payment eventually succeeded, you don't relaunch. Here are the 2026 orders of magnitude observed.
| Metric | Without handling | With timeout/retry handling |
|---|---|---|
| Raw timeout rate | 5 - 12% | 5 - 12% (unchanged) |
| Permanently lost transactions | 5 - 12% | 1 - 3% |
| Recovery via extended polling | 0% | +6 to +9% |
| Accidental double-charge | possible | ~0% |
| Customer satisfaction (clear message) | low | high |
The customer message makes the difference: "Payment being confirmed, don't close this page" stops them from relaunching on their side and creating a double-charge.
Mini case study
Claudine runs a delivery service in Kigali, 800 MTN MoMo USSD payments/month. At 10% timeout she lost 80 transactions/month, or ~400,000 FCFA at 5,000 FCFA per basket. By adding extended polling and backoff she recovers +8%, i.e. 64 saved transactions = ~320,000 FCFA/month regained. Development cost: ~200,000 FCFA one-off. Paid back in under a month.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
Why does a USSD payment take so long to confirm?
The USSD flow passes through several operator relays; confirmation can take 60 to 120 seconds under load. So you need a polling window, not an instant verdict.
Will retry charge my customer twice?
No, if built well: retry first checks the status of the first attempt. You only relaunch a payment if the status is clearly FAILED, never on a mere timeout.
How often should I poll status?
With exponential backoff: 5s, 10s, 20s, 40s. Polling every 2 seconds triggers a rate-limit and worsens things.
What do I do with an UNKNOWN payment after 120 seconds?
Flag it for reconciliation: an end-of-day job compares your orders to operator transactions and resolves the remaining cases (often < 1%).
How many sales can I really recover?
An order of magnitude of +6 to +9% of transactions that would be lost without handling, on a raw timeout rate of 5 to 12%.
Let's talk about your project. We harden your MTN MoMo USSD flows with polling, backoff and automatic reconciliation. 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.
