The verdict in three sentences
On a slow connection, the USSD timeout is the number-one conversion killer: 10 to 18% of payments fail before confirmation, often while the customer was ready to pay. A three-attempt retry with progressive backoff plus a QR or payment-link fallback recovers most of these failures and pushes the success rate from 78 to 94%. The business gain is direct: about 9 points of checkout conversion and average confirmation time cut in half.
Why USSD payments fail on 3G/EDGE
A USSD payment depends on a round trip between the phone, the operator and your server. On low-bandwidth links each step can time out: the USSD menu never appears, the PIN arrives too late, or the confirmation webhook is lost. The customer, meanwhile, has no idea whether they paid.
| Cause of failure | Share of failures | Remedy |
|---|---|---|
| USSD menu not shown | 30 to 40% | Retry with prompt |
| PIN entered out of window | 20 to 30% | Link / QR fallback |
| Confirmation webhook lost | 15 to 25% | Status polling |
| Operator session expired | 10 to 15% | Retry + backoff |
| Insufficient balance | 5 to 10% | Clear customer message |
Most of these failures are not refusals to pay: they are technical breaks the right workflow recovers.
The retry and fallback logic
The principle: three spaced attempts (backoff 15, 30 then 60 seconds), and if USSD still fails, switch to a QR or payment-link fallback the customer opens when their connection returns. In parallel, the server polls status so it never misses a late confirmation.
| Metric | Before | After |
|---|---|---|
| Payment success rate | 78% | 94% |
| Checkout conversion rate | reference | +9 points |
| Average confirmation time | 45 s | 22 s |
| Unresolved pending transactions | 6 to 8% | 1 to 2% |
| Customer complaints / week | 12 | 3 |
The fallback is key: even if USSD fails three times, the customer keeps a payment path that does not depend on a fragile real-time session.
Mini case study
Moses sells airtime and accessories online from Kampala, with many customers in peri-urban areas on 3G. On 1,000 payment attempts per month he lost 180 transactions to timeout (18%), about UGX 5.4M of revenue at UGX 30,000 average basket. After adding the three-attempt retry and QR fallback, his failure rate drops to 6%: he loses only 60 transactions. He recovers 120 transactions/month, about UGX 3.6M of extra revenue, for a development cost amortised 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
How many retry attempts are reasonable?
Three are enough in most cases, with backoff of 15, 30 then 60 seconds. Beyond that the customer gives up; better to switch to the QR or link fallback.
Could retry double-charge the customer?
Not if each attempt uses the same idempotency key and the server polls status before retrying. This is the critical point not to skip.
Does the QR fallback work offline?
The QR displays once loaded; the customer scans with their wallet app as soon as connection returns. It is more robust than real-time USSD on EDGE.
What conversion gain should I expect?
The 2026 order of magnitude is +7 to +10 points of checkout conversion when moving from a bare USSD flow to retry + fallback + polling.
Do I need a powerful server for polling?
No. Polling every 5 seconds during the confirmation window is enough and very light. The key is to stop polling as soon as the status is final.
Let's talk about your project. We make your checkout robust even on 3G with retry, QR fallback and status polling. 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.
