Worldpay, Flutterwave and PawaPay reported a series of payment-processing disruptions between October 29 and October 30, affecting card payouts, refunds, Egyptian-pound collections and mobile-money transactions across several African markets. The incidents exposed different weaknesses in payment infrastructure, ranging from a database problem following scheduled maintenance to interruptions involving individual banking and mobile-money providers.
Worldpay’s Worldwide Payment Gateway experienced an internal database failure shortly after scheduled maintenance, affecting card payouts, online refunds and several order-management functions. Flutterwave separately faced an Egyptian-pound incoming-payment outage lasting approximately eight hours and 45 minutes, followed just 10 minutes after its resolution by an Orange Cameroon disruption. Meanwhile, PawaPay opened three separate incidents involving Orange in the Democratic Republic of Congo, Monnify in Nigeria and Airtel in Tanzania within less than four hours.
Although the incidents occurred within a relatively narrow period, there is no evidence that they shared a technical cause. Their significance lies instead in the range of payment functions affected and the dependence of payment processors on multiple underlying infrastructure providers.
Worldpay Database Failure Hits Payouts, Refunds and Order Management
Worldpay reported an internal database issue on its Worldwide Payment Gateway (WPG) shortly after completing scheduled maintenance on October 29, creating disruption across several payment and merchant-management services.
According to Worldpay’s official status history, the company began reporting the problem at 21:45 UTC, or 23:45 Cairo time. At 22:11 UTC, it confirmed that the issue involved an internal database following scheduled maintenance and estimated that restoration would require approximately another hour.
The affected products included Auto-capture, Card Payouts, Incremental Authorisation, Online Refund Processing, Order Inquiries, Order Modifications, Pay as Order, Synchronised Order Modifications and the Merchant Administration Interface.
The range of affected services is notable because the incident extended beyond transaction authorization. Card payouts and refunds are post-payment functions, while order inquiries and modifications support the administration and management of existing transactions. Merchants could therefore encounter problems across different stages of the payment lifecycle rather than simply experiencing failed new purchases.
Worldpay subsequently confirmed that its technical teams had resolved the internal database problem as of 22:36 UTC on October 29, although the formal resolution update was published at 23:07 UTC. The company said it would continue monitoring the environment to ensure stability.
The incident followed quarterly maintenance conducted on the separate WPG status platform between 17:27 and 23:15 UTC on October 29. That maintenance was marked completed at 23:15 UTC. The timing establishes that the database problem emerged during the wider maintenance period, but Worldpay’s public statement does not establish that the maintenance itself caused the failure.
The episode also highlights a distinction between authorization availability and the systems required to complete, refund, modify or disburse transactions. Even when customers can initiate payments, failures in downstream database or order-management components can complicate reconciliation and the handling of existing transactions.
Flutterwave Moves From an Egypt Collections Outage to Cameroon Disruption
Flutterwave experienced a prolonged interruption affecting incoming Egyptian-pound payments before reporting a separate disruption involving Orange Cameroon collections and payouts.
The first incident was opened at 21:31 UTC on October 29, when Flutterwave warned merchants that some customers could not complete incoming EGP payments and that certain transactions might fail. The company said it was investigating the disruption and working with the affected provider.
Normal processing was restored at 06:17 UTC on October 30, according to Flutterwave’s official status page. The interruption lasted approximately eight hours and 46 minutes, making it considerably longer than the other disruptions reported during the same monitoring period.
Only 10 minutes after the EGP restoration notice, at 06:27 UTC, Flutterwave opened another incident involving Orange Cameroon. The company warned that some customers might be unable to complete transactions through the mobile-money operator, affecting both collections and payouts.
External incident-monitoring records subsequently placed the duration of the Cameroon disruption at approximately 36 minutes. Flutterwave’s published notice attributed the response effort to engagement with the affected mobile-money provider, but did not disclose a detailed technical cause.
The sequence is particularly relevant to merchants operating across African markets. The Egyptian incident affected incoming payments, while the Cameroon problem covered both incoming and outgoing mobile-money transactions. These functions serve different commercial purposes: collections allow businesses to receive customer payments, whereas payouts enable them to transfer money to customers or other beneficiaries.
There is no evidence that the two incidents shared a technical cause or that the restoration of EGP processing triggered the Cameroon disruption. Nevertheless, the short interval between the events demonstrates how regional provider dependencies can create successive interruptions across a payment company’s network.
PawaPay Reports Three Fresh Provider Failures Across Africa
PawaPay experienced another concentration of payment disruptions on October 30, opening three separate incidents involving mobile-money providers in the Democratic Republic of Congo, Nigeria and Tanzania within approximately three hours and 38 minutes.
The first incident concerned Orange services in the DRC. PawaPay began investigating degraded performance at 05:38 UTC and subsequently confirmed at 08:15 UTC that both its deposit and payout gateways remained in outage. The company said it was following up with the mobile-money operator.
At 09:01 UTC, PawaPay opened a separate incident involving Monnify services in Nigeria, reporting an outage affecting the integration. Fifteen minutes later, at 09:16 UTC, it identified instability affecting Tanzania Airtel services and escalated the issue to the mobile-money operator.
By approximately 09:52–09:53 UTC, PawaPay had moved the Tanzania Airtel and DRC Orange incidents into monitoring as success rates improved. However, the earlier DRC update had confirmed that both deposit and payout gateways were unavailable, and monitoring did not necessarily mean that all transactions had returned to normal. The Nigeria Monnify incident remained under investigation in the captured status update.
The three incidents were separate provider-level problems, and PawaPay did not identify a common technical cause. Their simultaneous presence nevertheless created exposure across different transaction routes, with DRC Orange affecting both directions of money movement, Nigeria Monnify experiencing an outage and Tanzania Airtel reporting instability.
The company was also dealing with a longer-running problem involving Uganda Airtel. Its USSD deposit gateway remained degraded on October 30, with an update at 05:39 UTC confirming that the issue was still being followed up with the mobile-money operator. The problem had first appeared in the earlier incident history and remained unresolved through several subsequent updates.
Details of the incidents are available through PawaPay’s official service-status page.
Multiple Payment Failures Highlight the Importance of Provider Resilience
The incidents illustrate why payment availability cannot be measured through a single platform-wide operational indicator. A processor may maintain its API and core infrastructure while individual banking connections, card-processing components or mobile-money gateways experience substantial disruptions.
For Worldpay, the key issue was the breadth of functions affected by one internal database problem. The interruption crossed transaction processing, payouts, refunds and order administration, illustrating how a failure in a shared internal component can affect services that merchants may consider operationally distinct.
Flutterwave’s sequence demonstrates a different challenge. Its EGP collections channel recovered after an extended interruption, but another regional provider problem emerged shortly afterward. Merchants operating across several countries may therefore need to manage multiple independent payment dependencies even when their primary processor is functioning normally.
PawaPay’s incidents provide another example of this fragmentation. Its integrations rely on local mobile-money operators, meaning that the availability of deposits and payouts can vary by country and provider. A working Nigerian route does not guarantee that a DRC or Tanzanian route is functioning, while even separate deposit and payout gateways for the same operator can experience different conditions.
These distinctions have commercial implications. Failed collections can interrupt sales and customer funding, while payout failures can delay merchant settlements or transfers to beneficiaries. Refund problems create a separate customer-service burden, potentially increasing support requests and reconciliation work even after the original payment interruption has ended.
Dave Finances has previously examined multiple payment and wallet incidents across Africa and other markets, including disruptions involving PawaPay and underlying mobile-money providers. Its earlier coverage of PawaPay’s prolonged Monnify Nigeria outage also illustrated how deposit and payout functions can recover at different times.
For merchants and investors, the next important indicators are whether the affected payment routes remain stable, whether delayed transactions require reconciliation and whether the providers disclose additional information about their technical causes. None of the three companies has published figures quantifying failed transaction volumes, affected merchant numbers or financial losses from these particular incidents.
The events do not establish a systemic failure across the global payments industry. They do, however, demonstrate how a relatively short period can expose weaknesses across several layers of payment infrastructure, from internal databases and refund systems to regional banks and mobile-money operators. For payment processors competing on reliability, restoring individual services is only part of the challenge; ensuring that those services remain stable after recovery is equally important.
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