Handling MTN MoMo USSD Timeouts and Retries in Kumasi (2026)

The verdict in three sentences

On weak networks, USSD confirmations time out constantly and users assume failure. In Kumasi in 2026, the USSD prompt window lasts only 30 to 120 seconds, and 10 to 20% of attempts time out on 2G/3G. A policy of exponential backoff retry, an idempotency key to prevent double charges and a WhatsApp/SMS fallback turns an apparent failure into a confirmed sale.

Why USSD confirmations time out

The problem is almost never the customer's balance. It is the technical chain: the push goes out, the operator shows the prompt, but the response does not return in time because of the network. With no strategy, your system marks the transaction "failed" while it may still be in progress.

A retry policy that never double-charges

The golden rule: never retry a payment without an idempotency key. Every attempt carries the same order identifier, so the operator recognizes the transaction and does not charge twice. You wait at least 90 seconds before a new push to let the first attempt resolve.

Server-side polling (every 3 to 5 seconds) checks the real status with the operator instead of trusting the customer's screen. Until the webhook confirms or definitively fails, the order stays "pending".

Mini case study

Ibrahim sells farming equipment in Kumasi. On 400 MTN MoMo payments per month, about 60 attempts (15%) time out on the first try. With no retry, he loses these sales: at an average basket of 35,000 FCFA (approx. 53 EUR), that is 2,100,000 FCFA/month of potentially lost orders. With a retry + WhatsApp fallback policy that recovers 50% of those timeouts, he saves 30 orders, or +1,050,000 FCFA/month — without a franc of extra advertising.

FAQ

Can a retry charge the customer twice?

No, if every attempt uses the same idempotency key tied to the order. The operator then recognizes the transaction and does not create a second charge. This is the essential technical protection before any retry policy.

How long to wait before retrying a USSD push?

At least 90 seconds. The USSD window lasts 30 to 120 seconds; retrying too early creates two competing prompts and confuses the customer. Meanwhile, polling checks whether the first attempt succeeds.

Why WhatsApp as fallback rather than SMS alone?

Because WhatsApp open rates reach 80 to 90% versus about 45% for SMS. A backup payment link sent on WhatsApp is far more likely to be seen and clicked in the minutes after a failure.

Does server-side polling use a lot of resources?

No, a 3 to 5 second interval for up to 3 minutes stays very light. It is infinitely cheaper than a lost sale or a support ticket for a "stuck payment".

Do you need a global maximum timeout?

Yes, usually 3 minutes on the interface before switching to fallback, then a close at 24h if no confirmation. Beyond that, you follow up via marketing rather than technical waiting.

Let's talk about your project. We design your USSD retry policy with idempotency and WhatsApp fallback so you stop losing sales on timeouts. WhatsApp +221 77 596 93 33.