An Indonesia payout disruption at Xendit has evolved into something more unusual than a bank simply going offline: throughout October 10, the exact transaction-value ranges affected repeatedly changed, while the problem expanded from BNI into other banks and e-wallet destinations.
The incident began late October 9 and remained active into October 11 WIB, with Xendit attributing the delays to “system issues with our partner.”
Its public status history shows payouts, disbursements, remittances and escrow transactions becoming unavailable or delayed according not only to the receiving institution but also to precise rupiah-value bands.
At various points, transactions below IDR10,000 were affected while mid-sized transactions were not. Later, amounts between IDR50,000,001 and IDR100 million became the problem. At other times, transactions above IDR100 million or IDR250 million were singled out.
The changing thresholds suggest that the most interesting part of the incident is inside the payment-routing stack, although Xendit has not publicly disclosed the underlying technical mechanism.
BNI Moved From “All Amounts” to Narrow Bands and Back Again
The sequence began at 22:20 WIB on October 9, when Xendit said all BNI amounts were affected.
Ten minutes later, the affected range narrowed dramatically to transactions from IDR1 to IDR9,999 and those above IDR100,000,001.
At 23:00, BNI returned to “all amount.”
By 01:00 on October 10, Xendit had again narrowed the disruption to IDR1–9,999 and amounts above IDR100,000,001.
That alone is unusual.
If BNI connectivity itself had simply been unavailable, there would be little reason for a IDR50 million transaction to work while a IDR5,000 or IDR150 million transaction did not.
The public data instead shows amount-sensitive failure conditions somewhere in the processing chain.
Other Banks Then Began Showing the Same Segmentation
By 04:20 WIB, the incident had spread.
Xendit listed BCA transactions from IDR1 through IDR250 million, BNI transactions below IDR10,000 and above IDR100 million, and other banks and e-wallets in two separate ranges: IDR1–9,999 and IDR100,000,001–250 million.
At 05:00, BCA disappeared from the warning while BNI and the split ranges for other destinations remained.
At 06:10, Xendit described affected “other banks and Ewallets” as IDR1–9,999 and IDR100,000,001–250 million, specifically excluding BCA, BNI, BRI, Mandiri and Permata.
An hour later, the affected low-value range narrowed to IDR1–4,999.
At 07:30, it expanded again to IDR1–9,999 plus IDR100,000,001–250 million.
Ten minutes later, the pattern changed completely: the affected range became IDR50,000,001–100 million.
The Failure Bands Behaved Almost Like a Moving Routing Table
The most striking part of the incident is how cleanly some of the boundaries line up around transaction-size thresholds.
The repeated cutoffs include IDR5,000, IDR10,000, IDR50 million, IDR100 million and IDR250 million.
Those are not random-looking values.
They resemble transaction limits or processing tiers that could exist in payment-provider, banking or partner-routing infrastructure.
But that interpretation should remain a hypothesis.
Xendit has not said that these ranges represent separate banking rails, separate liquidity pools, different partner processors or routing rules. It has only attributed the issue to a partner system.
The changes could theoretically reflect several things: shifting mitigation routes, transaction-limit infrastructure, partner-specific processing rules, settlement constraints, liquidity management or simply the way Xendit grouped observed failures on its status page.
The public data is enough to show segmentation. It is not enough to establish why that segmentation exists.
Permata Then Appeared With Its Own Amount Pattern
At 08:10 WIB, Xendit listed Permata separately, with affected transactions between IDR1 and IDR7,999 and above IDR100,000,001.
Other banks and e-wallets were meanwhile listed across the much broader IDR1–250 million range.
Less than an hour later, the scope changed again.
At 09:00, 09:10 and 09:30, Xendit said the disruption applied to IDR50,000,001–100 million transactions at other banks and e-wallets, excluding BCA, BNI, BRI, Mandiri and Permata.
That configuration then remained on the status page for much of the day before another major expansion during the evening.
BCA and BNI Returned as the Incident Broadened
At 20:00 WIB, BCA appeared again.
This time the affected BCA bands were IDR5,000–9,999 and IDR100,000,001–250 million. Other banks and e-wallets continued showing problems in the IDR50,000,001–100 million bracket.
At 22:10, Xendit added BNI transactions above IDR250,000,001.
At 23:00, the problem became substantially broader: BCA was affected through IDR250 million, BNI at all amounts, Mandiri between IDR5,000 and IDR250 million, and other banks and e-wallets between IDR1 and IDR250 million.
The incident then crossed into October 11 WIB.
At 00:10, Xendit’s latest update broadened Mandiri further to IDR1–250 million while BNI remained affected at all amounts. BCA and other banks/e-wallets were also listed through IDR250 million.
As of that update, the incident had not been marked resolved.
This Is Not What a Normal “Bank Down” Incident Looks Like
The transaction-value segmentation changes the operational interpretation.
A merchant normally responds to a bank outage by disabling that payout destination or waiting for connectivity to return.
Here, whether a payout was affected sometimes depended on its exact amount.
That means two transfers to the same broad banking ecosystem could potentially receive different treatment merely because one was IDR40 million and another IDR75 million.
For platforms processing payroll, marketplace seller payouts, refunds or treasury movements, such distinctions matter operationally.
A payout scheduler may need to distinguish between transactions that can continue and those that must be queued, rather than simply disabling an institution altogether.
It also raises a more technical investigative question: if different amount bands are processed differently, where does that decision occur?
Payment companies often sit above several banks, processors and settlement partners. Dave Finances previously examined the risks created by this kind of layered architecture in its look at financial products that depend on multiple middleware and settlement layers.
The Moving Bands May Reveal More Than Xendit Intended
Status pages are normally designed to tell customers what is broken, not explain a company’s internal architecture.
In this case, the specificity of Xendit’s updates provides indirect clues about how the payout network behaves.
If one value range fails while another continues, some form of amount-sensitive processing logic must exist somewhere in the chain.
The unanswered question is whether that segmentation belongs to Xendit, its unnamed partner, receiving banks, a settlement network or several layers simultaneously.
The fact that the affected ranges repeatedly moved during recovery is particularly interesting.
One possible explanation is that engineers were shifting traffic between available paths as capacity returned. Another is that the upstream partner itself had multiple transaction-processing tiers recovering at different times.
Neither has been confirmed.
Xendit’s repeated reference to “system issues with our partner” tells merchants where the company believes the immediate fault sits, but not what failed technically.
The Oct. 11 Expansion Makes the Root Cause More Important
Had the disruption remained confined to unusual BNI amount brackets for an hour, it could have been dismissed as a narrow partner incident.
That is no longer the situation.
Over roughly 26 hours, the affected destinations expanded, disappeared, returned and shifted among multiple exact amount ranges. By the latest update, the scope covered BNI at all amounts and large portions of BCA, Mandiri and other banks and e-wallets.
No public evidence currently establishes a liquidity shortage, settlement problem or routing failure, and those possibilities should not be reported as fact.
But the status history supports a narrower conclusion: Xendit’s partner-side payout disruption is amount-sensitive, dynamic and increasingly broad.
That makes the next technical explanation more important than the eventual “resolved” timestamp.
If Xendit discloses why IDR4,999 could behave differently from IDR5,000, or why the affected window jumped from above IDR100 million to IDR50–100 million and then to nearly all amounts across several institutions, merchants may get an unusually clear view into infrastructure that is normally invisible.
Until then, the moving thresholds are the strongest clue the incident has produced.
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