Payment processors Paysafe and Xendit reported fresh service disruptions on November 18–19, affecting merchant access, bank payouts and digital-wallet payments. Today’s payments roundup covers a 12-hour emergency maintenance window at Paysafe that produces misleading login errors, an Indonesian payout disruption involving BCA, BNI and Mandiri, and seven separate DANA QR-payment incidents recorded by Xendit within approximately 95 minutes. The incidents raise different operational concerns, from merchants losing access to account-management tools to delayed transfers and payment confirmations.
Paysafe takes merchant portal offline for 12 hours
Paysafe announced urgent maintenance of its Business Experience Portal on November 19, scheduling a 12-hour interruption between 10:30 and 22:30 UTC. The company published the notice at 10:16 UTC under incident reference INC0330782 and confirmed at 10:19 UTC that maintenance was in progress.
The unusual feature is the error shown to merchants attempting to access the portal. Rather than displaying a maintenance notification, Paysafe warned that users would receive an “Invalid Username/Email” message during the shutdown.
A twelve-hour shutdown, and the login screen points to an account problem instead.
The message normally suggests incorrect credentials or an unrecognized account, even though Paysafe has already identified scheduled service unavailability as the reason merchants cannot log in.
This creates a potential support problem for merchants who have not seen the status notice. A business could interpret the failed login as an account-access issue, attempt unnecessary password recovery or contact support about credentials that are not actually the cause of the error. Paysafe has not reported how many users have recieved the message or whether it has generated additional support requests.
The company did not explain why the maintenance was urgent, which technical components required intervention or whether merchants would lose access to specific reporting, settlement reconciliation or account-management functions.
The notice was quite precise about timing, not so precise about what needed fixing.
The published incident identifies the Business Experience Portal as the affected component. It does not establish that payment authorization, merchant acquiring or settlement-processing systems were also unavailable.
The maintenance follows other operational problems at Paysafe this month, including merchant-funding delays involving TSYS and recurring QR-payment failures reported in mid-November. Those earlier incidents involved payment processing and merchant funding rather than the Business Experience Portal, and Paysafe has not connected them to the latest maintenance.
For investors in the NYSE-listed payments company, the current disclosure provides no transaction-loss figures, affected-merchant count or financial estimate. The immediate measurable impact is the announced 12-hour portal interruption, not a verified interruption to all Paysafe payment services.
As of the latest available incident update, the maintenance remained classified as in progress, with completion scheduled for 22:30 UTC.
Xendit payout problems reach BCA, BNI and Mandiri
Indonesia-focused payment processor Xendit reported another disruption to its bank-transfer infrastructure during the early hours of November 19, affecting payouts, disbursements, remittances and escrow transfers.
The incident began at 00:30 Western Indonesian Time (WIB), equivalent to 17:30 UTC on November 18. Xendit attributed the delays to system problems at a partner and initially identified multiple affected payment destinations.
For Bank Central Asia (BCA), the disruption covered transfers from IDR 1 to IDR 4,999. Bank Negara Indonesia (BNI), Bank Mandiri and other banks and e-wallet destinations were initially listed as affected for transfers between IDR 1 and IDR 250 million.
By 01:00 WIB, Xendit had narrowed the affected amounts for BNI and other banks and e-wallets to two bands: IDR 1–9,999 and IDR 100,000,001–250 million. Mandiri remained affected across the entire IDR 1–250 million range, while BCA retained its narrower restriction.
At 01:10 WIB, Mandiri disappeared from the affected list. BCA, BNI and other banks and e-wallets remained listed under their respective transaction bands until Xendit declared the incident resolved at 01:30 WIB.
Mandiri dropped off, the other ranges stayed, and then the whole incident was closed.
The published timeline indicates a one-hour incident, but the changes in transaction-value bands are more revealing than the duration alone. Different transfer amounts were affected at the same institutions, and the scope changed during the recovery process.
Xendit has reported prevoius Indonesian payout disruptions involving changing transaction-value bands, including problems in October where the affected thresholds repeatedly moved between smaller transfers and amounts exceeding IDR 100 million.
The November 19 incident follows a similar pattern, although the records do not establish whether the underlying technical cause was the same. Xendit has not identified the partner responsible or explained whether the amount restrictions originated from bank limits, routing systems or another part of the payment-processing infrastructure.
Nor has the company disclosed how many transfers were delayed, their aggregate value or whether any instructions remained pending after the incident was marked resolved. A resolution notice confirms the reported service recovery, but it does not provide transaction-level evidence that every delayed instruction had completed.
Xendit records seven DANA QR failures after wallet errors
Xendit also reported repeated payment problems involving Indonesia’s DANA digital wallet, beginning with an e-wallet charge-request disruption on November 18 and continuing with a series of QR-payment incidents early on November 19.
The first incident was triggered at 21:52:15 WIB on November 18. Xendit reported intermittent timeouts when merchants attempted to create DANA e-wallet charge requests, with affected requests returning HTTP 503 responses and the error code CHANNEL_UNAVAILABLE.
More than 6.20% of requests in the preceding ten-minute observation window were affected, according to Xendit’s disclosure at 21:54 WIB. The company advised merchants to retry transactions returning the error and said reconciliation would not be required for that incident. It marked the disruption resolved at 22:06 WIB.
Several hours later, a seperate problem appeared in DANA’s QR-payment channel.
Xendit’s status history recorded seven DANA QR incidents beginning between 03:37 and 05:11 WIB on November 19, with the final recovery recorded at 05:12 WIB. The interruptions were individually short, some lasting only one or two minutes.
Seven disruptions in that short a stretch, with the channel returning and then failing again.
Unlike the earlier DANA e-wallet charge-request errors, the QR incidents involved payment completion rather than simply initiating transactions. Xendit warned that merchants could successfully initiate QR payments but might receive delayed callbacks confirming completion. It also reported that payment success rates had fallen below normal thresholds.
The distinction affects how merchants should handle interrupted orders. For the QR incidents, Xendit advised using alternative e-wallet providers and specifically instructed merchants to reconcile transactions initiated during the affected periods.
A payment could be started, but the confirmation of it, that was another matter.
The repeated interruptions resemble 20 LinkAja QR-payment failures recorded by Xendit in October, when numerous short outages repeatedly disrupted completion callbacks and required transaction reconciliation.
Indonesia’s Bank Indonesia QRIS payment framework identifies real-time transaction monitoring and reconciliation as functions of the national QR-payment system. Delayed callbacks can interfere with merchants’ ability to establish the final status of individual payments even when the original request has been accepted.
Xendit attributed the November disruptions to problems on its partners’ side but has not confirmed whether the DANA wallet timeouts and QR callback interruptions shared a technical cause. No aggregate transaction count, financial-loss estimate or merchant compensation figure was published.
All seven QR incidents were subsequently marked resolved. Their recurrence nevertheless leaves a measurable operational record: multiple separate failures within 95 minutes, following an earlier wallet-channel interruption on the same payment service.
Across the three developments, the outstanding information differs. Paysafe has not explained the urgent portal work or its effects on merchant reporting. Xendit has not published transaction-level completion figures for the Indonesian payouts, while its DANA records document repeated callback disruption without quantifying the resulting reconciliation workload. Those disclosures remain the principal gaps after the reported service recoveries, with Paysafe’s maintenance window still scheduled to run until late November 19.
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.

