M-PESA downtime: What happens when money leaves your account but never arrives?

A customer withdraws money from M-Shwari to M-PESA, receives no confirmation that the funds have arrived and discovers that the balance has not changed as expected. Another tries to pay a bill, only to receive an error message saying the request cannot be processed.

For millions of Kenyans who rely on mobile money for transport, shopping, business payments and emergencies, such disruptions raise an immediate question: Where is the money, and how can it be recovered?

The concern came into focus on Wednesday, October 28, 2026, after M-PESA customers complained on social media about failed transactions and difficulties accessing the service. One customer, @SonOfMaryAtieno, said money withdrawn from M-Shwari had failed to appear in her M-PESA wallet.

“I just withdrew money from Mshwari to mpesa and it disappeared in thin air.. What’s happening??” she posted on X.

Safaricom acknowledged that it was experiencing a system issue affecting M-PESA and said the matter had been escalated to the relevant team for resolution.

The company did not disclose the technical cause of the disruption, the number of affected customers, or whether the specific transaction had been traced and resolved.

While a failed transaction can be distressing, a missing confirmation does not automatically mean the money has been permanently lost. Understanding what may have happened, and what to do next, is essential for customers trying to recover their funds.

A mobile money transaction involves systems that must process the request and update the relevant accounts. When a service experiences a technical interruption, the transaction may not complete as expected or the confirmation may be delayed.

There are several possible scenarios when money appears to leave one account without reaching another.

These are possible explanations, not confirmed causes of the October 28 disruption. Safaricom had not publicly established which scenario applied to the individual complaints.

Customers who encounter a missing or delayed transaction should avoid making repeated payments before establishing what happened to the original transaction.

Confirm whether the money was actually deducted from your M-PESA wallet or M-Shwari account. Review the latest transactions and retain the original confirmation message or error notification.

For an M-Shwari withdrawal, check both the M-Shwari balance and the M-PESA wallet to establish whether the funds were credited, returned or remain unaccounted for.

Retain the transaction code, amount, date, time, and recipient or destination details. These details can help the service provider trace the transaction.

Do not delete the relevant SMS messages before the matter is resolved.

Report the transaction through Safaricom’s official customer-care channels and explain whether the source account was debited, whether the recipient received the money and whether any error message appeared.

Ask for the transaction to be traced and for guidance on when the funds will be credited or returned.

If a transaction appears to have failed, do not automatically send the same amount again. First establish whether the original payment went through.

Otherwise, a delayed transaction could eventually complete after a second payment has already been made, potentially resulting in a duplicate payment.

If Safaricom does not resolve the issue satisfactorily, customers can pursue the provider’s formal complaints process and, where appropriate, escalate the matter to the Communications Authority of Kenya (CA).

The regulator advises consumers to complain to their service provider first and retain evidence of that communication before seeking regulatory intervention.

A failed or delayed transaction and a completed transfer to the wrong recipient are different situations.

In a failed transaction, the payment may not have been completed or the accounts may require reconciliation. In a mistaken transfer, the money may already have reached another person’s account, meaning a reversal process may be necessary.

Safaricom has previously explained that reversals depend on the type of transaction and the applicable process. Its guidance for money sent to the wrong number, till or paybill includes requesting a reversal through supported channels. Some merchant payments may require the receiving organisation to assist, and processing times can vary.

Customers should therefore establish whether their transaction failed, remains pending or was completed before choosing the appropriate recovery process.

A reversal should not be assumed to be automatic in every case.

The impact of a mobile money disruption extends beyond inconvenience.

For a commuter who has no cash, a failed payment can mean being unable to pay a fare home. A small trader may be unable to confirm a customer’s payment or pay a supplier. A household may struggle to complete an urgent purchase, while a business relying on digital payments could lose sales during the interruption.

Kenya’s reliance on mobile financial services makes service availability and clear communication particularly important.

The Central Bank of Kenya’s 2024 FinAccess Household Survey documented consumer concerns around system downtime and money lost across financial services, including mobile money. In the survey’s mobile-money category, 21.1% of respondents reported system failures as a challenge, while 9.8% reported money lost. These are survey findings about consumer experiences, not measurements of the October 2026 M-PESA incident.

The figures underline why customers need accessible complaint channels and clear explanations when transactions fail.

Acknowledging a technical problem is an important first step, but customers also need practical information to make decisions about their money.

During a disruption, useful communication would clarify:

In its response to the complaints on October 28, Safaricom said the issue had been shared with the relevant team, but did not provide a restoration timeline or a detailed explanation of how affected transactions would be handled.

The lack of those details left customers seeking answers about both service availability and the status of their funds.

Although customers cannot control a provider’s technical systems, a few precautions can reduce the risk of duplicate payments and make disputes easier to resolve.

These measures cannot prevent a system failure, but they can help customers avoid additional losses and document unresolved transactions.