Flutterwave resolved a disruption affecting payment collections across several African markets on October 29, hours before a separate incident temporarily impaired Nigerian naira payouts, wallet-balance visibility and foreign-exchange rate lookups. The two incidents affected different parts of the payment process, while Flutterwave said unaffected payment channels continued operating during the collection disruption and customer funds remained safe during the subsequent Nigerian outage.
The first incident began at 22:22 UTC on October 28, equivalent to 01:22 Cairo time on October 29. Flutterwave’s official status page reported problems affecting selected mobile-money and local payment channels across Ghana, Côte d’Ivoire, Rwanda, Senegal, South Africa, Uganda and Zambia, alongside FawryPay and OPay.
Flutterwave marked the collection incident resolved at 05:53 UTC on October 29, or 08:53 in Cairo. The interruption therefore lasted approximately seven hours and 31 minutes between the published start and resolution notices.
A separate Nigerian payout issue had already been marked resolved at 06:01 UTC. However, Flutterwave opened another NGN incident at 07:54 UTC, warning that merchants might be unable to view wallet balances, initiate payouts or access currency-conversion and exchange-rate information. That incident was resolved at 09:13 UTC, lasting approximately one hour and 19 minutes between the published notices.
The Collection Failure Affected Multiple Local Payment Rails
Flutterwave’s October 28 alert identified Ghana’s Nsano, Wave in Côte d’Ivoire, MTN in Rwanda, Orange and Wave in Senegal, ZAR Flash in South Africa, Airtel in Uganda and Zynle in Zambia among the affected channels. The company also listed FawryPay and OPay as affected payment methods.
The incident was not described as a complete shutdown of Flutterwave’s payment infrastructure. The company explicitly stated that cards, bank transfers and unaffected mobile-money channels remained operational and were processing normally. Its notice warned that collections initiated through the listed channels could fail or experience delays.
This distinction matters for merchants operating across several African countries. A business may accept payments through a single payment gateway while relying on different mobile-money operators, local aggregators and processing arrangements depending on the customer’s location. A disruption affecting selected integrations can therefore interrupt particular payment options without disabling every route through which customers can pay.
For an online merchant in Ghana, for example, the temporary unavailability of a particular collection channel could prevent some customers from completing transactions through their preferred payment method. The availability of card payments, bank transfers or alternative mobile-money providers could reduce the impact, although the effectiveness of those alternatives would depend on customer preferences and the merchant’s configuration.
Flutterwave’s public notice did not disclose transaction volumes, the number of affected merchants, failed-payment totals or the financial value of disrupted collections. It also did not identify the underlying technical cause. The resolution notice confirmed that the selected collection channels had returned to normal, but it did not provide a technical postmortem explaining what went wrong.
The incident follows earlier Flutterwave disruptions across Ghana and Nigeria, when three separate incidents affected collection-account creation, outgoing bank transfers and withdrawals from Nigerian point-of-sale agent balances within 58 minutes on October 19. Those events involved different functions and were not established to share a common cause with the October 28–29 collection interruption.
A Separate NGN Incident Disrupted Payouts and FX Lookups
The second major incident affected the merchant-facing balance and payout functions associated with Nigerian naira accounts. At 07:54 UTC on October 29, Flutterwave warned that merchants might be unable to view wallet balances on the dashboard or initiate payouts. Currency conversion and exchange-rate lookups could also be unavailable or respond slowly.
Crucially, Flutterwave said incoming customer payments continued to be accepted during the incident. It also stated that dashboard balance updates could be delayed or temporarily unavailable even though customer funds remained safe and actual balances were intact.
The distinction between a displayed balance and the underlying account balance is operationally important. A merchant who cannot see a current balance may struggle to determine how much money is available for outgoing transfers, reconcile recent transactions or calculate the naira value of a foreign-currency payment. Even without a loss of funds, those limitations can delay routine treasury and accounting decisions.
Flutterwave advised merchants not to repeatedly retry failed payout requests, warning that repeated attempts could create duplicate requests. The company subsequently reported that wallet balances were displaying again, payouts could be initiated normally, and exchange-rate lookups had returned to normal. The resolution notice was published at 09:13 UTC.
Before this second incident began, Flutterwave had also marked an earlier NGN payout-pending problem resolved at 06:01 UTC. That notice attributed the pending status of some payouts to a temporary connectivity issue and said transactions would be updated once their final status was received from the banking network.
The sequence is noteworthy, but the available notices do not establish that the collection disruption, the earlier pending payouts and the later balance-and-FX outage shared a technical root cause. Their proximity in time is evidence of successive operational problems, not proof of a single underlying failure.
Payment Reliability Matters Beyond Whether Funds Are Safe
Flutterwave’s distinction between accepting payments and processing payouts illustrates how a payment platform can remain partially functional while still creating significant operational difficulties for merchants. Receiving money, displaying balances, converting currencies and sending funds to beneficiaries are connected functions, but they do not necessarily depend on identical systems or providers.
The broader pattern appears across the payments industry. Other payment and wallet incidents documented by Dave Finances have shown how banking-provider interruptions and mobile-money gateway failures can affect transaction completion without establishing that customer money has been stolen. In such cases, the immediate business problem is often uncertainty over whether a transaction succeeded, failed or remains pending.
That uncertainty can carry real costs. Merchants may delay fulfilling orders, contact customers to confirm payments, postpone supplier transfers or devote staff time to manual reconciliation. Businesses operating across several currencies face an additional challenge when exchange-rate lookups or displayed balances become unavailable, because they may be unable to determine the correct conversion value for a transaction at the time they need it.
International policy discussions have also recognized the operational risks created by interconnected financial infrastructure. A September 2026 BIS discussion of third-party service-provider risks, prepared by the Committee on Payments and Market Infrastructures and the International Organization of Securities Commissions, examines the challenges associated with financial market infrastructures’ reliance on providers delivering critical services. The paper is not a finding about Flutterwave, but it highlights the wider importance of managing dependencies across interconnected systems.
For payment processors operating across African markets, resilience depends partly on how effectively they manage these local dependencies. Alternative payment routes can help preserve collection capability when one operator experiences problems, while clear transaction-status reporting and reliable reconciliation procedures can reduce uncertainty when payouts are delayed.
However, having multiple payment options does not automatically eliminate disruption. Merchants must actually have access to alternative channels, customers must be willing and able to use them, and systems must prevent repeated payment attempts from producing duplicate transactions. The same applies to payouts: a dashboard that cannot confirm a transfer’s final status can complicate operations even after the underlying banking connection recovers.
Recent mobile-money disruptions affecting African operators also illustrate how country-specific payment dependencies can produce localized failures within otherwise functioning platforms. The October 29 Flutterwave incidents reinforce why reliability should be assessed at the level of individual payment functions and channels, rather than through a single overall uptime figure.
The immediate position is clearer than the underlying causes. Flutterwave reported that the multi-market collection disruption was resolved at 05:53 UTC and that the subsequent NGN balance, payout and exchange-rate incident was resolved at 09:13 UTC. It reported no loss of customer funds in the latter incident, but did not quantify the commercial impact of either event.
For merchants, the important follow-up is whether transaction reconciliation is complete, pending payouts have reached confirmed final statuses and affected collection channels remain stable. For Flutterwave, a more detailed explanation of the causes and preventive measures would help customers distinguish isolated provider interruptions from weaknesses that could recur across multiple markets.
Until such information is available, the incidents should be treated as separate, resolved operational disruptions rather than evidence of a platform-wide failure or a shared technical cause. Their significance lies in the practical lesson: payment acceptance, balance visibility, currency conversion and the ability to move money are distinct services, and merchants depend on all of them to operate reliably.
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