Five payment infrastructure providers reported disruptions across November 1 and 2, affecting merchant notifications, bank payouts, open-banking payment initiation, card settlements and mobile-money deposits. In today’s payment roundup, Mercado Pago recorded two waves of delayed payment notifications, Xendit’s Indonesian payout restrictions temporarily expanded to every transfer amount at BNI, and Tink reported repeated Nordea payment failures affecting 70% of users on a Finnish banking connection. Noon Payments also disclosed a 7.5-hour Mastercard settlement problem, while PawaPay’s Orange Mali deposit gateway experienced successive outages.
All five developments are documented in official provider status records. The incidents concern different payment functions and markets, with no evidence of a common technical cause. None of the providers disclosed comprehensive transaction counts or confirmed merchant financial losses.
Mercado Pago records two waves of notification delays
Mercado Pago reported four incidents involving delayed payment notifications across its supported sites on November 2, with Webhooks and Instant Payment Notification (IPN) services affected during two distinct periods.
The first IPN incident began at 15:01 GMT-3 and was marked resolved at 15:21. A separate Webhooks notification issue emerged at 15:18 and continued until 15:27, creating a nine-minute overlap between the two reported incidents.
Approximately 81 minutes after that recovery, Mercado Pago identified another increase in Webhooks response times at 16:48. The second Webhooks incident was resolved at 17:03, while IPN notification delays returned at 16:53 and continued until 17:07.
The two clusters therefore covered 15:01–15:27 and 16:48–17:07, or 45 minutes of combined incident windows. These were seperate incidents, not evidence of 45 minutes of complete payment-processing unavailability.
Two recoveries, and then the same notification services slowing down again.
Mercado Pago classified the problems as increases in notification response times rather than failures of the underlying payment-processing system. Its notices did not say that completed payments were reversed, notifications were permanently lost or merchants experienced duplicate charges.
The operational concern is that a successful payment and its merchant-facing confirmation are separate events. When a notification is delayed, an online store may continue displaying an order as unpaid even after the customer’s transaction has been processed.
Merchants relying on notifications to release digital products, confirm bookings or trigger shipping workflows could consequently experience delayed fulfillment. Automated retries may introduce additional complications if systems do not first establish whether an earlier payment succeeded. These are potential consequences of the reported latency, not confirmed outcomes of the November 2 incidents.
A comparable problem appeared in Xendit’s earlier GCash payment disruptions, when delayed callbacks reached more than nine hours despite some customer transactions processing successfully. Xendit explicitly advised merchants to reconcile affected payments.
Mercado Pago’s November 2 notices did not include equivalent latency measurements or reconciliation instructions. Without transaction-level data, the number of merchants who received late confirmations remains unknown.
Xendit payout restrictions expand, then narrow again
Xendit experienced an Indonesian payout disruption lasting approximately seven hours and 50 minutes, during which the reported restrictions on transfers to Bank Negara Indonesia (BNI) changed repeatedly.
The incident began at 22:20 Western Indonesian Time (WIB) on November 1, when Xendit identified delays affecting disbursements, remittances and escrow payments to BNI destinations above IDR 250,000,001. The company attributed the disruption to system issues involving its payment partner.
At 23:00 WIB, the scope expanded to all BNI transfer amounts, removing the original restriction to high-value payments.
By 01:00 WIB on November 2, Xendit’s notice had narrowed the affected ranges to transfers between IDR 1 and IDR 9,999 and those exceeding IDR 100,000,001. At 04:00, the notice reverted to amounts above IDR 250,000,001.
The reporting changed again at 05:20, when Permata Bank destinations between IDR 8,000 and IDR 100,000,000 were added alongside the BNI high-value restriction. Ten minutes later, Permata was no longer listed, leaving only the BNI restriction above IDR 250,000,001.
Xendit declared the incident resolved at 06:10 WIB on November 2.
For a while it was every BNI amount, and then just the low and high ends, then high-value transfers again.
The progression suggests that transaction eligibility differed across amounts and destinations at various stages of recovery. It does not establish whether Xendit was using separate settlement routes, imposing temporary risk controls or responding to changing capacity at its partner.
BNI’s appearance in the incident should not be interpreted as proof of a nationwide BNI banking outage. Xendit identified disruption within its reported partner-payment routes and did not establish that other BNI channels were similarly affected.
The incident also follows earlier Xendit payment interruptions involving BNI and other Indonesian banks, including cases in which affected transfer amounts changed during recovery.
Noon Payments would report a different type of payment problem during the same period: delayed settlement rather than restrictions on initiating payouts.
Tink’s Nordea failures recur as Mastercard settlements slow
Tink reported repeated payment-initiation failures involving Nordea in Finland on November 1 and 2, with both incidents affecting an estimated 70% of users on its monitored connection.
The November 1 disruption ran from 01:00 to 01:30 Central European Time (CET). Tink identified the affected function as Payment Initiation Services (PIS), reported that the bank was rejecting payments and identified the connection as fi-nordea-oauth2.
The issue returned on November 2 at 09:25 CET, according to another Tink incident report. The provider again reported that 70% of users were affected and attributed the immediate failure to bank-side payment rejections. Tink posted its resolution at 11:25 Eastern European Time, equivalent to 10:25 CET, indicating an approximately one-hour disruption.
The same connection had already experienced problems on October 31, when Tink reported payment-initiation failures affecting 90% of users. Three consecutive calendar days of reported problems, although the outages differed in duration and affected-user percentages.
The reported percentages refer to Tink users associated with the monitored Nordea connection, not 70% or 90% of Nordea’s entire banking customer base.
The recurrence is relevant to applications using open-banking payments rather than conventional card checkout. Customers attempting to authorize bank-to-bank payments through the affected integration may have encountered rejection errors despite continuing to access other banking services.
The European Commission’s payment services framework provides the regulatory background for these integrations, including the second Payment Services Directive (PSD2), which brought newer digital payment services into the EU’s regulatory framework.
DaveFinances previously documented back-to-back Tink connectivity outages involving BNP Paribas and Crédit Agricole in France. Those earlier incidents involved different banks and did not establish a shared cause with Nordea’s November failures.
Separately, Noon Payments reported a seven-and-a-half-hour window of intermittent Mastercard gateway settlement delays on November 1, running from 05:30 to 13:00 UTC.
At 08:35 UTC, Noon identified a disruption affecting Mastercard Payment Gateway Services across the Asia-Pacific, Saudi Arabian, North American and European regions. Its notice warned that customers could experience delayed settlement processing.
At 13:34 UTC, Noon published a resolution notice stating that Mastercard had confirmed service restoration. The reported disruption had ended at 13:00 UTC, before the final status update was posted.
The settlement window was long, though this was not a reported seven-and-a-half-hour shutdown of card purchasing.
Settlement delays can affect when merchants recieve funds and complete financial reconciliation, even where the original card transactions were successfully authorized. Noon did not quantify unsettled transaction values, identify delayed merchant funding dates or confirm that any particular merchant missed a scheduled payment.
The notice also does not establish a Mastercard-wide authorization outage. The confirmed incident concerned settlement processing through the Mastercard gateway services described by Noon.
PawaPay’s Orange Mali deposit outage returns repeatedly
Africa-focused payments infrastructure provider PawaPay reported another sequence of Orange Mali disruptions extending across November 1 and 2, including a prolonged deposit-gateway outage and a subsequent new incident after the earlier problem had been declared resolved.
The sequence began shortly before midnight UTC on October 31, when PawaPay opened an Orange Mali incident at 23:46. A monitoring update followed at 00:34 on November 1, but the company identified renewed instability at 01:10.
PawaPay subsequently reported improving success rates at 01:57 and declared the incident resolved at 03:52 UTC.
Another Orange Mali incident began at 11:35 UTC on November 1, less than eight hours after the previous resolution. PawaPay identified instability and said it had escalated the problem to the mobile-money operator.
By 21:57 UTC, the company confirmed that its Orange Mali deposit gateway remained unavailable. The incident continued overnight, with PawaPay reporting improving success rates at 02:56 UTC on November 2 before declaring recovery at 03:21.
That second incident remained open for approximately 15 hours and 46 minutes, although the public record does not establish that the gateway was completely unavailable throughout the entire period.
Recovery did not last through the following evening. At 21:02 UTC on November 2, PawaPay opened another incident reporting an outage of Mali Orange services. Its latest reviewed notice showed the new incident under investigation without a published resolution.
Resolved in the early morning, and another outage notice by evening.
The repeated incidents raise a specific question about the stability of the Orange Mali integration. The records show recurring problems on the same mobile-money route, but they do not establish whether the incidents shared one technical cause or resulted from seperate failures at the mobile-money operator.
Other PawaPay corridors have experienced similar provider-specific interruptions. DaveFinances recently covered PawaPay outages alongside Worldpay and Flutterwave disruptions, including difficulties involving Orange in the Democratic Republic of Congo and other African payment partners.
For merchants accepting mobile-money deposits through the affected Mali route, the unresolved question is whether failed attempts were rejected immediately or remained pending while the gateway was unavailable. Those outcomes require different handling: a definitively failed transaction can be retried, while an uncertain transaction may first require confirmation to avoid a duplicate payment.
PawaPay’s public notices did not provide unsuccessful deposit counts, transaction values or the number of merchants affected. Nor did they establish an Orange Mali network-wide outage beyond the services monitored by PawaPay.
The five providers’ incidents occurred across unrelated payment networks, and their effects should not be conflated. Mercado Pago’s notification delays concerned merchant visibility into payment status; Xendit reported bank-route payout restrictions; Tink identified rejected payment initiation; Noon disclosed delayed Mastercard settlements; and PawaPay reported mobile-money gateway outages. The published recovery times are clear in most cases, but whether transactions were subsequently reconciled, delayed funds reached merchants on schedule, or users had to repeat payments remains largely undisclosed.
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