Sun. Nov 22nd, 2026

Payment outages hit PawaPay, dLocal and Paystack

ByJohan Shamshad

November 22, 2026
PaymentsPayments

Payment providers reported seven service disruptions across Africa and Mexico on November 21–22, 2026, affecting mobile-money deposits, merchant payouts, bank processing and card transactions. Today’s payment outage roundup covers PawaPay incidents involving AirtelTigo in Ghana, Airtel in Malawi, Movitel in Mozambique, Orange in Mali and Zamtel in Zambia. It also examines a dLocal alert that named two different Mexican banks and another Paystack card-processing failure involving Nigeria’s Verve network. Most incidents were resolved, but Ghana’s AirtelTigo disruption remained active in the latest published update.

PawaPay reports AirtelTigo disruption in Ghana and Airtel failures in Malawi

Payment infrastructure provider PawaPay reported instability affecting AirtelTigo mobile-money services in Ghana on November 22, with both web deposits and payouts identified as affected.

The company first acknowledged the disruption at 08:33 UTC, stating that it had escalated the problem to the mobile-money operator for resolution.

At 09:13 UTC, PawaPay repeated its warning without announcing an improvement in transaction success rates or identifying an expected recovery time.

Both payment directions were affected, and Ghana had no restoration notice yet.

The incident concerns two separate transaction functions. Web deposits allow merchants to collect payments from AirtelTigo wallets, while payouts enable businesses to disburse funds to recipients using the same mobile-money service.

PawaPay’s status notice establishes that both integrations were experiencing degraded performance. It does not establish whether all transactions failed, whether some were merely delayed or whether customers using AirtelTigo outside PawaPay experienced equivalent disruption.

Ghana’s Bank of Ghana register of licensed payment service providers identifies Airtel Mobile Commerce (Ghana) Limited as a dedicated electronic money issuer. The incident record did not indicate whether the problem originated within the operator’s infrastructure or its connection with PawaPay.

PawaPay encountered another Airtel-related problem earlier on November 22, this time affecting three payment channels in Malawi.

At 05:55 UTC, the provider reported instability involving Airtel web deposits, USSD deposits and payouts. The disruption therefore extended beyond online collections to transactions initiated through mobile-phone USSD menus.

Airtel deployed a fix at 06:14 UTC, according to PawaPay, which subsequently reported improving transaction success rates.

The provider confirmed resolution at 07:38 UTC, giving the incident a recorded duration of one hour and 43 minutes.

The operator’s fix came first, and full recovery later, not at the same time.

The Malawi disruption followed an Airtel OpenAPI incident affecting four African countries on November 20. That earlier failure involved integrations in Kenya, Malawi, Tanzania and Uganda, with different combinations of deposits and payouts affected in each market.

Both incidents included Malawi, although PawaPay has not established whether the November 22 failure resulted from a recurrence of the earlier technical problem.

No transaction volumes, financial losses or outstanding payout amounts were disclosed for either the Ghana or Malawi incidents.

Movitel, Orange and Zamtel suffer separate payment outages

Three additional PawaPay incidents affected mobile-money services in Mozambique, Mali and Zambia between November 21 and 22.

In Mozambique, the provider identified an outage affecting Movitel web deposits at 14:39 UTC on November 21.

The disruption remained under investigation for more than five hours before PawaPay reported improving transaction success rates at 19:55 UTC.

At 20:32 UTC, the incident was marked resolved, approximately five hours and 53 minutes after the initial notification.

PawaPay did not disclose how many deposit requests were unsuccessful or whether payments initiated during the interruption were automatically retried after restoration.

In Mali, Orange mobile-money web deposits were affected by a separate outage beginning at 23:23 UTC on November 21.

The provider reported improving success rates at 00:58 UTC on November 22 and confirmed resolution at 04:01 UTC.

The Orange problem crossed midnight, and that was when recovery first showed up.

The recorded incident lasted four hours and 38 minutes, although the improvement notice indicates that some transactions were already succeeding before PawaPay declared the service fully restored.

The Mozambique and Mali incidents were confined to web deposits in their respective status records. Neither notice identified payouts as affected or established a nationwide outage of the underlying mobile-money operators.

Zambia experienced a different type of disruption involving payouts to Zamtel wallets through the NFS processing route.

PawaPay opened an investigation at 22:30 UTC on November 21 after identifying an outage affecting NFS-routed Zamtel payouts.

Transaction success rates began improving at 00:31 UTC on November 22, and the provider closed the incident at 01:24 UTC.

The recorded duration was two hours and 54 minutes. The affected service was specifically identified as NFS Zamtel Payout, rather than all Zamtel mobile-money functions.

The latest incident follows several earlier NFS-related Zamtel disruptions. PawaPay’s incident history records similar problems on November 15–16, November 16–17 and November 19–20, alongside further Zamtel instability around November 20–21.

The recurring incidents involve a relevent processing dependency, but the notices do not identify whether Zamtel, the NFS intermediary or their integration was responsible for each failure.

Unlike a single isolated outage, the repeated appearance of the same payout route provides grounds to examine whether earlier recovery measures addressed the underlying problem.

That question remains unanswered. PawaPay has not provided a consolidated technical explanation, reconciliation data or the number of delayed transfers associated with the repeated interruptions.

dLocal’s Mexico alert identifies two different banks

Nasdaq-listed payments provider dLocal reported a processing disruption in Mexico on November 22 that contained an inconsistency in the identification of the affected financial institution.

The incident began at 00:02 UTC and was marked resolved at 01:27 UTC, giving it a recorded duration of one hour and 25 minutes.

Its title identified Bancoppel S.A., while the incident description stated that dLocal had detected payment-processing problems involving Hey Banregio.

Two banks in one notice, but dLocal did not clear up which one.

The company said it had contacted the processor and would provide further updates. The subsequent resolution notice did not explain the conflicting identifiers.

Bancoppel and Hey Banregio are distinct Mexican banking institutions. The discrepancy leaves the affected processing relationship uncertain and prevents the status notice from being treated as confirmation that both institutions experienced outages.

The error could reflect an incorrect incident title, a processing-route label or another reporting inconsistency. The available disclosure does not establish which explanation is correct.

dLocal has previously reported payment-processing disruptions involving other banking partners in Latin America, including repeated BBVA Bancomer interruptions in Mexico during October.

Separately, PawaPay and dLocal reported simultaneous Airtel payment-processing failures in Kenya on November 5, demonstrating how separate providers can report overlapping problems involving the same mobile-money operator.

The Mexico incident presents a different evidentiary problem: the provider’s own notification contains inconsistent institution names, making the exact processing route difficult to establish.

dLocal did not publish affected merchant counts, failed-transaction values or a correction identifying which Mexican institution was involved.

Paystack reports fresh Verve card failures in Nigeria

Paystack experienced another card-processing interruption in Nigeria shortly before midnight on November 21, adding to a series of incidents involving domestic payment channels during November.

The company opened the incident at 23:51 UTC after detecting an unusually high failure rate on transactions involving cards issued by Nigerian banks.

Paystack attributed the problem to processor downtime and stated that it was working with its processing partner to restore normal service.

The incident was titled as a disruption involving Verve cards, although the initial description referred more generally to Nigerian-issued bank cards.

Paystack marked the problem resolved at 00:06 UTC on November 22, just 15 minutes after the first notification.

Fifteen minutes only, but not the first card-processing trouble this month.

The latest incident followed earlier Paystack payment-processing failures in Nigeria, including a November 12 disruption involving Nigerian-issued cards that lasted approximately two hours and 28 minutes.

Paystack also reported another card-processing incident on November 16 that remained recorded for approximately 48 minutes.

These failures have not been linked to a single processor or technical fault. Paystack has not publicly established whether the November 21 interruption involved the same service dependency as the earlier incidents.

The repeated card-processing notices also should not be interpreted as evidence that Nigeria’s entire Verve network was unavailable. They establish increased transaction failures within Paystack’s reported processing channels.

Paystack did not disclose the number of unsuccessful card payments, the institutions involved or whether merchants could route affected transactions through alternative acquiring connections.

Across the seven incidents, five were reported by PawaPay, with separate disclosures from dLocal and Paystack. Six were marked resolved, while Ghana’s AirtelTigo problem had no recovery confirmation in the latest reviewed notice.

The recorded durations ranged from 15 minutes for Paystack’s Nigerian card-processing disruption to nearly six hours for PawaPay’s Movitel deposit outage in Mozambique.

These figures measure the periods between incident notifications and official resolution announcements, not necessarily continuous transaction failure throughout each period.

The unresolved operational evidence differs by provider. PawaPay has not disclosed affected payment volumes or clarified the causes of repeated Zamtel payout failures. dLocal has not reconciled the conflicting bank identifiers in its Mexican incident. Paystack’s successive card-processing disruptions remain without a published explanation connecting or distinguishing their underlying processors.

Without transaction-level information, the succesful recovery of payment gateways cannot establish how many previously initiated customer payments required retries, refunds or subsequent reconciliation. The official records document restoration of most affected services, but leave their merchant-level financial impact unquantified.

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.