PawaPay’s Orange Cameroon disruption continued on October 29, with the payment aggregator reporting an outage affecting both deposits and payouts in its latest update. A separate incident involving MTN Uganda, which temporarily affected web deposits, USSD deposits and payouts, was resolved later the same day after the mobile-money operator deployed a fix.
The incidents affected different countries and operators, and PawaPay has not established a common cause. Their contrasting recovery timelines nevertheless highlight the operational risks facing payment companies that depend on local mobile-money infrastructure to serve merchants across multiple African markets.
Orange Cameroon outage persists for a third day
PawaPay first reported instability affecting Cameroon Orange services at 05:17 UTC on October 27, saying it had escalated the issue to the mobile-money operator for resolution. The disruption subsequently affected both deposit and payout gateways, with updates on October 28 confirming that the company was still following up with the operator.
The situation remained unstable throughout October 29. At 00:22 UTC, PawaPay said its Orange Cameroon deposit gateway was still experiencing an outage. The company moved the incident into monitoring at 02:17 UTC after observing improvements in success rates, but reported another outage at 03:57 UTC.
At 06:20 UTC, the company described the deposit gateway as experiencing degraded performance. A further update at 13:43 UTC said instability had been identified and escalated to the mobile-money operator. By 17:41 UTC, however, PawaPay was again reporting an outage affecting both the deposit and payout gateways.
The latest update therefore indicated that the disruption had not been resolved, despite temporary improvements earlier in the day. PawaPay’s public notices did not identify the technical cause or provide a confirmed restoration time.
The distinction between deposits and payouts matters for merchants. Deposit failures can prevent customers from funding transactions or accounts through the affected route, while payout failures can interrupt the movement of funds to recipients. With both gateways affected in Cameroon, merchants relying on those services faced a broader operational problem than one limited to a single transaction direction.
Uganda MTN incident resolved after a brief disruption
PawaPay opened a separate incident affecting MTN Uganda at 10:58 UTC on October 29. The notice identified an outage involving three transaction channels: MTN web deposits, USSD deposits and payouts. The company initially said it was investigating the problem.
The situation improved within little more than an hour. At 12:03 UTC, PawaPay reported that MTN Uganda had deployed a fix and that success rates were improving. The incident was marked resolved at 12:42 UTC, according to the company’s incident history.
The MTN disruption lasted approximately one hour and 44 minutes between the initial investigation notice and the resolution announcement. Unlike the continuing Cameroon Orange incident, the Uganda MTN problem therefore reached a reported resolution on October 29.
There is an important qualification to the broader Uganda status. PawaPay’s status board continued to show degraded performance for Uganda overall because the Airtel USSD deposit gateway remained impaired. That separate issue should not be confused with the resolved MTN incident.
The contrast between the two cases is significant. MTN Uganda’s incident progressed from investigation to an operator-deployed fix, improving success rates and resolution within the same morning. Cameroon Orange, by comparison, continued to experience renewed outages after periods of improvement and monitoring.
PawaPay’s core platform remains operational
The incidents concern individual payment routes rather than a reported failure of PawaPay’s entire platform. The company’s status board continued to list its core platform, Merchant API, dashboard and payment-reconciliation services as operational, even as Cameroon Orange’s deposit and payout gateways were classified as experiencing a major outage.
This distinction is central to understanding payment infrastructure. An aggregator can maintain its own systems while an external mobile-money operator experiences difficulties that prevent particular transactions from completing. A functioning API does not guarantee that every downstream payment route is available.
Recent coverage of PawaPay and other providers reporting separate payment disruptions illustrates how operational problems can emerge across different integrations without necessarily indicating a single platform-wide failure.
Earlier, a Telecel Ghana outage affecting both PawaPay and Paystack also demonstrated how problems involving an underlying mobile-money operator can affect more than one payment processor. That precedent does not establish a shared cause for the Cameroon and Uganda incidents, which remain separate events in PawaPay’s published records.
Why the Cameroon disruption matters for payment businesses
The immediate concern is the duration and uneven recovery of the Cameroon Orange service. A brief interruption may be manageable for a merchant with alternative payment methods, but a disruption extending across several days can create more persistent operational uncertainty. Businesses may need to redirect transactions, communicate with affected customers and reconcile payments attempted while a gateway was unavailable.
For payment aggregators, this is a structural challenge. Their commercial value comes partly from simplifying access to multiple payment methods through a single integration. Yet that convenience does not eliminate dependence on the operators responsible for executing transactions locally. Reliability ultimately depends on both the aggregator’s own infrastructure and the availability of each underlying payment route.
The Cameroon incident also shows why status changes need to be interpreted carefully. PawaPay reported improvements and moved the incident into monitoring before subsequently describing renewed outages. Monitoring indicates that a service may be improving, not necessarily that normal transaction processing has been fully restored. Merchants should therefore distinguish between an initial improvement in success rates and confirmed, sustained recovery.
A previous PawaPay Monnify Nigeria outage that lasted nearly 37 hours similarly illustrated how disruptions can persist and how different integrations may recover at different times. These cases do not prove that the same technical issue is recurring, but they reinforce the importance of measuring availability at the individual integration level rather than relying exclusively on an aggregator’s overall platform status.
What merchants and investors should watch next
The next important development is a confirmed restoration of Orange Cameroon’s deposit and payout gateways. Merchants should look for explicit resolution notices and evidence that both transaction directions have recovered, rather than assuming that an improvement in deposits also means payouts are functioning normally.
Further updates from PawaPay or Orange Cameroon could clarify the cause, although neither the precise technical failure nor a restoration timetable had been disclosed in the latest reviewed notice. The duration of the disruption, any recurrence after a resolution announcement and the availability of alternative payment routes are the most relevant operational indicators to monitor.
Investors assessing payment infrastructure businesses should also examine how providers communicate outages, separate their own platform availability from partner performance, and help merchants manage failed or delayed transactions. A broader review of payment and wallet incidents highlights why these operational details deserve attention alongside product expansion and geographic coverage.
For now, the two October 29 incidents have different outcomes. MTN Uganda’s affected services were reported resolved, while Orange Cameroon’s deposit and payout gateways remained disrupted in PawaPay’s latest update. The official PawaPay status page remains the primary source for subsequent changes. Until Cameroon Orange recovery is confirmed, merchants using that route must continue to account for the possibility of failed deposits and payouts.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574