Sat. Nov 21st, 2026

Payment outage roundup: NomuPay, Airtel, Xendit and MTN

ByJohan Shamshad

November 21, 2026
PaymentsPayments

Payment processors reported a series of disruptions across Asia and Africa on November 20–21, 2026, affecting merchant transactions, bank disbursements and mobile-money services in at least eight countries. Today’s payment outage roundup covers a NomuPay processing failure reported by dLocal in three Asian markets, an Airtel OpenAPI disruption spanning four African countries, repeated Philippine payout problems at Xendit and two consecutive MTN service failures in Zambia. All four incidents were marked resolved, although the providers disclosed little information about affected transaction volumes, outstanding payments or technical causes.

NomuPay processing failure disrupts payments across three Asian markets

dLocal reported payment-processing problems involving NomuPay across Thailand, the Philippines and Malaysia on November 21, identifying a processor-related disruption that appeared simultaneously in three national markets.

The company published its initial notice at 03:53 UTC, stating that it had identified processing problems involving NomuPay and contacted the provider for assistance. At 04:57 UTC, dLocal marked the incident resolved, giving it a recorded duration of one hour and four minutes.

Three markets, one notice, and not much detail on the failed payments.

Although dLocal’s incident description identified Thailand, the Philippines and Malaysia, its status record listed Thailand’s payment-processor component as the affected service. The company did not provide seperate transaction-success rates or recovery timelines for the three countries.

Nor did dLocal disclose whether the problem originated in a shared NomuPay integration, a regional processing system or several payment routes dependent on the same infrastructure.

The simultaneous country-level reports suggest that a common processing dependency warrants investigation, but the available evidence establishes only that dLocal experienced problems through NomuPay. It does not independently confirm that NomuPay’s entire platform was unavailable or that merchants using the processor outside dLocal experienced equivalent failures.

The disruption follows earlier payment-processing failures involving dLocal on November 3, when the company reported problems affecting a Brazilian payment integration. That incident involved a different market and payment service, with no demonstrated technical connection to the latest NomuPay problem.

dLocal did not report the number of affected merchants, the value of failed or delayed transactions, or whether payments initiated during the interruption required additional reconciliation after service restoration.

The company also did not clarify whether its 04:57 UTC resolution notice reflected confirmed normal processing across all three countries or recovery of the component monitored through its incident-management system.

Airtel OpenAPI disruption hits four African countries

Mobile-money payments provider PawaPay experienced a separate regional disruption involving Airtel OpenAPI services across Kenya, Malawi, Tanzania and Uganda on November 20.

The company opened its investigation at 20:31 UTC after detecting degraded performance affecting multiple Airtel integrations. Its incident record identified different combinations of web deposits, USSD deposits and payouts across the four markets.

In Uganda and Tanzania, all three channels were affected. Malawi experienced problems with web deposits and payouts, while the Kenyan incident specifically involved Airtel’s betting-related web deposits, USSD deposits and payout services.

Deposits took a hit, payouts did too.

PawaPay reported improving transaction-success rates at 21:38 UTC, approximately 67 minutes after its initial notice. The provider continued monitoring the affected services before declaring the incident resolved at 22:06 UTC, bringing the total recorded interruption to one hour and 35 minutes.

The incident is notable for the number of countries involved in a single provider announcement. Unlike several recent PawaPay outages that were confined to one mobile-money operator in one country, the November 20 Airtel incident covered four national integrations under the same OpenAPI incident record.

The available notice does not establish whether one underlying API failure caused every affected integration to deteriorate. It also does not identify which services recovered first or whether success rates returned to normal simultaneously across all four countries.

PawaPay had already documented another series of mobile-money disruptions across four African markets earlier on November 20. Those incidents involved Telecel Ghana, Orange Senegal, Orange Cameroon and Airtel Zambia, including both deposit and payout failures.

The two sets of incidents involved different service combinations and incident records. Their proximity in time does not establish a common regional outage, particularly without relevent technical disclosures from the participating mobile-network operators.

No transaction totals, merchant-loss estimates or outstanding settlement amounts were published for the four-country Airtel disruption. PawaPay also did not specify whether affected payment requests had been rejected outright, remained pending or were completed after a processing delay.

Xendit reports expanding Philippine payout delays across banks and wallets

Xendit experienced another disruption to Philippine payouts on November 20, initially affecting higher-value transfers through its PH_SEC destination before expanding to several major banks and electronic wallets.

The incident began at 16:10 UTC, equivalent to 23:10 Western Indonesian Time, when Xendit attributed delays affecting PH_SEC transactions above PHP 50,001 to problems with a payment partner.

Within ten minutes, the company reported delays covering additional destinations, including BPI, GCash, PayMaya, UnionBank and other Philippine banks and e-wallets. Several affected routes involved transactions between PHP 1 and PHP 50,000, while UnionBank was temporarily listed as affected for all transaction amounts.

The list changed, and then it changed again.

At 16:30 UTC, Xendit identified BPI transfers between PHP 1 and PHP 50,000 alongside PH_SEC transfers above PHP 50,001. Another update at 16:40 UTC expanded the PH_SEC disruption to all transaction amounts, while the 17:00 UTC update again listed multiple banking and wallet destinations.

Xendit declared the incident resolved at 17:10 UTC, exactly one hour after the first notification. Its final announcement did not specify whether every delayed payout had been completed or whether some transfers still required processing.

The transaction-value differences offer an important technical clue, although they do not establish the affected payment route.

According to the Bangko Sentral ng Pilipinas’ National Retail Payment System guidance, InstaPay supports real-time transfers of up to PHP 50,000, while PESONet processes payments in batches and is designed to accommodate larger business and institutional transfers.

Xendit’s incident notices repeatedly distinguished transactions of PHP 50,000 or below from higher-value transfers. Those categories resemble the transaction limits used in the Philippine payment infrastructure, but Xendit has not confirmed that an InstaPay or PESONet component caused the disruption.

The processor also did not identify the intermediary responsible for the reported partner-side problems. Multiple destinations experiencing delays within the same hour could reflect a shared payout dependency, although the published updates do not provide the routing information needed to establish one.

The latest incident follows previous GCash and QR-payment disruptions involving Xendit, including separate Philippine payout problems documented on November 4.

Xendit’s status history also shows repeated Philippine payout incidents during November 18–20, including notices involving BPI and PH_SEC. The company has not established whether those episodes involved the same underlying partner failure.

Separately, its November 21 status page identified an ongoing partner-related disruption affecting ECPAY_LOAN over-the-counter payments in the Philippines. That notice concerned payment acceptance rather than the resolved payout incident, and no connection between the two has been confirmed.

Merchants have not recieved a published accounting of the total disbursements delayed during the latest episode, the amounts ultimately completed after recovery or the number of transactions requiring manual intervention.

Zambia MTN web deposits fail again hours after earlier recovery

PawaPay reported another period of instability affecting MTN mobile-money deposits in Zambia on November 21, less than six hours after resolving an earlier disruption involving the same operator.

The latest incident began at 07:34 UTC, when PawaPay identified degraded MTN services and escalated the problem to the mobile-network operator. Its component listing specifically identified MTN Web Deposit, without including MTN Payout in the affected services for this incident.

PawaPay reported improving success rates at 09:49 UTC and marked the problem resolved at 10:30 UTC. The latest disruption therefore lasted two hours and 56 minutes, including the period during which the provider monitored the improving connection.

The previous MTN Zambia incident had started at 23:57 UTC on November 20 and affected both web deposits and payouts. PawaPay moved that incident into monitoring at 01:04 UTC on November 21 and declared it resolved at 02:27 UTC.

It was back, the earlier MTN connection, but not for long.

Only five hours and seven minutes separated the first resolution announcement from the identification of the second disruption. Together, the two incident records cover five hours and 26 minutes of reported degradation or monitoring, excluding the interval between the incidents.

The second episode affected a narrower set of services than the first, but both involved Zambia MTN Web Deposit. This repeated component-level involvement provides a basis for examining whether the initial recovery was sustained or whether the morning incident resulted from a seperate fault.

PawaPay has not published a technical explanation linking the two events. Neither notice establishes whether the earlier repair failed, whether the operator experienced another independent problem or whether transactions were affected by a shared infrastructure dependency.

There was additional payment instability in Zambia during the same overnight period. PawaPay recorded a separate Zamtel incident beginning at 22:25 UTC on November 20 and ending at 05:08 UTC on November 21. That episode concerned another mobile-money operator and cannot be attributed to the MTN problem without further evidence.

The repeated MTN disruption is a documented recurence, but its customer impact remains unquantified. PawaPay disclosed neither the volume of failed web deposits nor the number of merchants affected during the two episodes.

Resolved on paper, the customer backlogs still aren’t counted.

Across the four payment developments, the official notices establish that the reported disruptions were eventually closed, with durations ranging from 60 minutes at Xendit to nearly three hours during Zambia’s second MTN incident. The NomuPay and Airtel reports involved multiple national markets, while Xendit and Zambia MTN experienced repeated problems involving particular payment destinations or operator integrations.

The unresolved evidence is operational rather than a confirmed financial loss: none of the providers supplied comprehensive transaction volumes, merchant-impact figures or a complete technical explanation. For payment businesses dependent on these services, those missing records prevent a reliable assessment of the financial exposure associated with the interruptions or how much delayed processing remained after recovery.

Editor-in-Chief at  | More Posts

Johan Shamshad is Editor-in-Chief at Dave Finances, covering financial markets, digital assets, trading platforms, brokers, fintech, payments and regulation. Since 2023, he has also worked as an editor at Gulf News, the UAE English-language newspaper published by Al Nisr Publishing LLC. His work focuses on market-moving developments, company disclosures, regulatory changes and trading infrastructure, with an emphasis on primary-source verification and practical context for traders and investors.

Disclaimer: This content is for informational purposes only and does not constitute financial, investment, legal, or trading advice. Trading and investing involve risk. Read our full Disclaimer.