The verdict in three sentences
USSD timeout is a silent conversion killer: it causes 25 to 30 % of abandonments at the exact moment of payment. In 2026 the USSD session lasts on average 90 seconds, but rural network latency adds 2 to 4 seconds and the STK push expires at 60 seconds, leaving little margin. The fixes — pre-generate the request, show a countdown, provide a web-link fallback — are cheap and recover most of these abandonments.
Diagnose the timeout window
The first reflex is to measure where the time is lost. The USSD session does not wait: between sending the request and the customer entering the PIN, every second counts.
| Latency segment | Typical 2026 duration | Impact |
|---|---|---|
| Operator USSD window | 60-120 s (avg 90 s) | Hard ceiling |
| Urban network latency | 0.5-1.5 s | Low |
| Rural network latency | 2-4 s | Moderate |
| Customer reaction time | 15-40 s | High |
| STK push (M-Pesa) | expires at 60 s | Critical |
| Webhook round-trip | 1-3 s | Low |
Customer reaction time is the biggest item: if they have to find the phone, unlock, read, type the PIN, you quickly near 60 seconds. Hence the importance of warning them BEFORE sending the request.
Fixes by cause
| Timeout cause | Fix | 2026 conversion gain |
|---|---|---|
| Customer caught off guard | "Keep your phone in hand" + countdown | +6 to 9 pts |
| Request sent too early | Pre-generate, send on explicit click | +3 to 5 pts |
| STK session expired | Instant "Resend request" button | +4 to 7 pts |
| Slow rural network | Web payment link fallback | +5 to 8 pts |
| No visual feedback | Synchronized progress bar | +2 to 4 pts |
| Accidental double send | 90 s anti-duplicate lock | Cuts disputes |
The visible countdown changes everything: the customer understands they have a limited window and acts. Combined with an instant resend button, it turns a timeout into a simple second attempt.
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
Aminata runs an online grocery in Thiès with many peri-urban customers. On 2,000 payments per month, 28 % failed on timeout, i.e. 560 lost orders, 12,000 FCFA average cart — 6,720,000 FCFA gone. After adding a countdown, a resend button and a web-link fallback, timeouts drop to 9 %. She recovers around 380 orders, i.e. 4,560,000 FCFA/month of saved revenue.
FAQ
Why does the STK push expire so fast? The STK standard (M-Pesa type) often caps the window at 60 seconds on the operator side, shorter than classic USSD. Always provide a resend button since you cannot extend that window.
Doesn't a countdown stress the customer? Quite the opposite: in 2026, showing it cuts timeouts by around 20 %. Uncertainty is more stressful than information; the customer knows what to do and acts fast.
Is the web-link fallback really useful? Yes, especially in rural areas where latency adds 2 to 4 seconds. The web link bypasses the USSD session constraint and recovers 5 to 8 conversion points.
How do you avoid double payments on resends? Place a 90-second anti-duplicate lock on the transaction reference. Any new attempt within that window reuses the same reference rather than creating a second one.
Can you measure timeouts precisely? Yes, log the request-send timestamp and the webhook-receipt timestamp. A gap beyond the operator window, with no confirmation, is a timeout to count separately from other failures.
Let's talk about your project. We audit your payment logs and fix USSD timeouts at the source. 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.
