Xendit’s status history recorded a series of separate payment and payout disruptions across Indonesia, the Philippines and Thailand on October 28–29, affecting LinkAja QR payments, Philippine QRPH notifications, bank transfers and direct-debit channels. The incidents varied in duration and scope, with some involving delayed transaction notifications and others affecting payouts to specific banks and transaction-value ranges.
The incidents do not establish a common technical cause or a platform-wide outage. Several were attributed to problems at banking or payment partners, while the reported impacts differed by country, payment method and transaction amount. Xendit’s official status history shows that the distinction between a completed payment, a delayed confirmation and a delayed payout was central to understanding the disruptions.
LinkAja QR Payments Faced Repeated Completion Problems
Xendit repeatedly reported problems with LinkAja QR payments in Indonesia throughout October 28, with separate incident notices appearing across the day. The company said merchants could initiate transactions successfully but might receive delayed callbacks confirming payment completion. It also reported that the successful-payment rate had fallen below its normal threshold.
Xendit attributed the interruptions to a disruption at its e-wallet partner and advised merchants to direct customers toward alternative e-wallet providers while the service was affected. It also warned that transactions initiated during the incident would require reconciliation.
A further LinkAja incident appeared on October 29 at 08:50 Western Indonesian Time, with the status page marking it resolved at 08:55. The recurrence matters because the operational problem was not necessarily an inability to initiate a payment. A transaction could enter the payment process while the merchant remained without timely confirmation of its final status.
The latest reports follow a similar pattern to earlier repeated payment failures across Indonesia and the Philippines, when LinkAja and several other payment routes experienced separate interruptions. The latest incidents provide further evidence of recurring route-specific problems, although they do not establish that every event had the same underlying cause.
QRPH Backlog Cleared After Payment Notifications Were Delayed
In the Philippines, Xendit reported delays affecting QRPH payment notifications on October 28. Customers’ payments were going through, but callbacks to merchants arrived later than usual, in some cases more than an hour after the transactions had been completed.
Xendit said the delay originated with its QRPH partner, which was increasing capacity to process the accumulated backlog. The company confirmed that completed payments had not been lost and that affected transactions would be updated to paid as the backlog cleared. QR-code creation and other payment channels were not affected by this particular incident.
The company reported that the backlog had cleared at 22:03 Western Indonesian Time on October 28, equivalent to 18:03 Cairo time. It had previously advised merchants not to ask customers to pay again for orders that still appeared as pending, warning that premature retries could result in duplicate payments.
This incident illustrates the difference between payment execution and payment-status reporting. A customer may have completed a transaction even when the merchant’s system has not received the confirmation needed to update an order, release a service or close a reconciliation record.
Indonesia Payout Delays Varied by Bank and Transaction Amount
A separate Indonesian payout disruption began at 23:30 Western Indonesian Time on October 28. Xendit reported delays affecting payouts, disbursements, remittances and escrow transactions across BCA, BNI, Mandiri, other banks and e-wallet destinations. The company attributed the problem to system issues at its partner.
The affected transaction-value ranges changed across successive updates. BCA was listed for transfers between IDR 1 and IDR 4,999. BNI and other destinations were affected across separate low-value and high-value bands, including IDR 1–9,999 and IDR 100 million–250 million. Mandiri’s reported ranges also changed during the incident, with one update listing IDR 1–9,999 and IDR 50 million–250 million.
Xendit marked the Indonesian payout incident resolved at 03:41 Western Indonesian Time on October 29. The shifting ranges are notable because they show that the reported impact was not uniform across all transaction values or destinations.
The incident resembles an earlier Indonesia payout outage involving changing transaction-value bands. In both cases, the published status updates provide more detail about the affected routes than about the underlying technical mechanism. They do not establish why particular amounts were affected while other ranges were not.
In the Philippines, Xendit separately reported payout delays affecting RCBC transactions between PHP 1 and PHP 50,000 on October 28, with the incident marked resolved at 21:30 Western Indonesian Time. On October 29, another incident affected Security Bank payouts above PHP 50,001 between 14:00 and 14:10 WIB. A further disruption affecting BPI payouts between PHP 1 and PHP 50,000 was reported at 21:12 WIB and marked resolved at 21:20.
These incidents involved different destinations and transaction-value ranges. Separately, Xendit reported that RCBC direct-debit payments were temporarily unavailable while the bank investigated a security concern on its side. Xendit said its own systems were not affected and that other Philippine payment channels remained operational. The separate RCBC direct-debit suspension should therefore be distinguished from the payout delays.
Thai Direct-Debit Channels Reported Completion Issues
Thailand also experienced a brief cluster of direct-debit problems on October 29. Xendit reported payment-completion issues involving Bank of Ayudhya, Siam Commercial Bank, Bank of Bangkok, Kasikornbank and Krungthai Bank. The incidents were opened at approximately 17:24 WIB and marked resolved at 17:31 WIB.
Xendit advised customers to use alternative payment methods and recommended waiting for the affected channels to stabilize before retrying transactions. It also stated that if a customer had been debited despite a failed transaction, a reversal would be processed within the next five business days.
The short reporting window does not establish how many customers were affected or whether all five banks experienced the same technical problem. It does, however, add another category of payment-completion risk to the incidents recorded across the three markets.
Why Delayed Callbacks Matter More Than They First Appear
The main operational risk in these incidents is the gap between what happened to a payment and what a merchant’s system knows happened. A delayed callback can leave an order marked as unpaid after the customer has already transferred the money. If the merchant automatically retries the transaction, asks the customer to pay again or releases an order only after receiving confirmation, the delay can create duplicate charges, fulfilment problems and additional support work.
Xendit’s warning during the QRPH incident addressed precisely this risk. Its confirmation that completed payments were not lost was important, but merchants still needed to wait for the status updates and reconcile transactions correctly. Reliable payment infrastructure therefore depends on more than successful transaction processing: it also requires accurate status reporting, idempotent retry handling and a clear process for resolving transactions whose final state is uncertain.
Amount-Specific Payout Failures Raise Questions About Resilience
The payout incidents raise a different concern. When disruptions are limited to particular banks or transaction-value ranges, merchants cannot assume that a payment route is either fully available or completely unavailable. Some transfers may proceed normally while others remain delayed, complicating cash-flow planning and the reconciliation of outgoing payments.
The changing Indonesian amount bands could reflect differences in processing paths or partner-side handling, but the published notices do not confirm such an explanation. It would be premature to infer a specific software defect, transaction limit or settlement mechanism from the affected ranges alone.
For investors assessing payment infrastructure providers, the important questions concern resilience and recovery. Multiple bank and e-wallet connections can broaden a provider’s reach, but the quality of those connections, the availability of fallback routes and the speed of partner escalation determine how useful that reach is during an incident.
The status records do not quantify affected transaction volumes, merchant losses or financial damage. The incidents therefore cannot establish a material financial impact on Xendit or demonstrate a company-wide failure. Their significance lies instead in the operational exposure they reveal.
The next indicators to watch are whether LinkAja and the affected payout routes experience further interruptions, whether Xendit provides more detail about partner-side causes, and whether merchants receive timely confirmation and reconciliation of delayed transactions. Repeated short-lived incidents can still create meaningful operational friction when they leave businesses uncertain about payment completion or the arrival of funds.
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