November 15 brought fresh developments in cryptocurrency withdrawals and payment infrastructure across Asia and Africa. Binance reopened withdrawals across 87 blockchain networks during the week and set a target for restoring its remaining services. Meanwhile, Xendit experienced two Indonesian payout disruptions spanning November 13–15 local time, while Flutterwave reported separate payment-processing failures in Nigeria and South Africa. The incidents ranged from a major exchange recovering from a $6.3 billion hack to shorter interruptions affecting bank transfers, card payments and voucher collections.
Binance reopens withdrawals on 87 networks after $6.3 billion hack
Binance announced on November 14 that it had reopened cryptocurrency withdrawals across 87 blockchain networks during the preceding week, marking another recovery milestone following the October 29 security breach that resulted in approximately $6.3 billion in stolen assets.
The announcement, published at 03:52 UTC, identified Cardano, Avalanche, Stellar, Cosmos, NEAR, Litecoin, Filecoin, Aptos, Hyperliquid and Osmosis among the restored networks. Other reopened routes include Starknet, zkSync Era, Scroll, Linea, Mantle-related infrastructure and several additional Ethereum scaling networks.
The 87-network figure represents withdrawals restored throughout the week, rather than 87 networks newly reopened on November 14 alone. Binance did not provide a complete list of the remaining restricted networks or specify how many individual asset-network combinations were still unavailable.
The company said it aims to reopen withdrawals for all remaining networks and assets by the end of the following week, approximately November 22. This remains a target rather than a guaranteed restoration deadline.
Binance also warned that customers could encounter temporary processing delays or network congestion during the reopening process. Users were instructed to check the withdrawal page for their selected cryptocurrency and blockchain before attempting a transfer.
The operational recovery follows Binance’s November 13 confirmation that it had completed replacing more than $6.34 billion in stolen cryptocurrency assets. The exchange used its corporate treasury, Secure Asset Fund for Users and excess Futures insurance reserves to cover the losses.
Those assets have been replenished, yet the withdrawal routes have not all caught up.
Binance’s latest Proof of Reserves snapshot, taken on November 12, covers 198 cryptocurrencies, compared with 44 in its November 4 review. The expanded snapshot is a seperate process from restoring access to particular blockchain networks, and the company has not said that every customer can already withdraw every fully backed asset.
Law enforcement has also made progress tracing the stolen cryptocurrency. According to the US Department of Justice’s November 12 announcement, authorities and private-sector partners had frozen more than $2.7 billion linked to the attack, including more than $1.2 billion covered by court-authorized seizure or restraint measures.
The FBI attributed the theft to North Korea’s TraderTraitor operation. The frozen assets remain distinct from the replacement cryptocurrency Binance purchased using its own resources.
The exchange’s remaining recovery commitments also include rebuilding SAFU toward its approximately $1 billion target. Binance has not disclosed the precise allocation of the $6.34 billion replenishment among its funding sources or provided a firm deadline for restoring the emergency reserve.
For customers, the immediate test is whether a specific asset can actually be transferred over its intended blockchain, rather than whether the exchange reports that its overall customer balances have been restored.
Xendit suffers two Indonesian payout disruptions within 24 hours
Payment infrastructure provider Xendit reported two separate Indonesian payout disruptions across November 13 and 14 UTC, affecting transfers to major banks and electronic-wallet destinations.
The first incident began at 23:30 Western Indonesian Time (WIB) on November 13, equivalent to 16:30 UTC. Initial alerts identified problems with BCA and Mandiri destinations, with Xendit attributing processing delays to system issues involving a payment partner.
The disruption subsequently expanded to include Bank Negara Indonesia (BNI), Permata and other banking and e-wallet destinations. It affected payouts, disbursements, remittances and escrow transfers.
Xendit’s updates showed that restrictions were not uniform across destinations or transaction amounts. At one stage, Mandiri transfers between IDR 1 and IDR 250 million were affected, while other banks experienced interruptions involving smaller transactions below IDR 10,000 or larger payments exceeding IDR 100 million.
The affected ranges kept changing, sometimes within ten or twenty minutes of the previous update.
Xendit marked the first incident resolved at 05:20 WIB on November 14, approximately five hours and 50 minutes after its initial notice.
A second disruption began at 01:20 WIB on November 15, equivalent to 18:20 UTC on November 14. This time, the initial warning identified payout delays affecting BCA across all transaction amounts.
Within ten minutes, Xendit reported additional restrictions involving BNI, Mandiri, Permata and other banks and e-wallets. Some of the amount-specific restrictions resembled those documented during the previous incident.
The company marked the second disruption resolved at 02:10 WIB, producing a reported incident window of 50 minutes.
It was marked fixed, then another payout problem had appeared the next evening.
There is an unusual detail in the second resolution notice. Although Xendit classified the incident as resolved, the accompanying text continued to describe delays affecting BCA payouts across all amounts. The notice does not explain whether that wording was carried over from an earlier update or reflected an outstanding restriction.
The repeated incidents follow earlier Xendit payment and payout disruptions across Indonesia, the Philippines and Thailand, including October problems involving changing bank-specific transaction ranges.
Bank Indonesia’s payment-service-provider framework requires licensed providers to maintain risk controls and monitor supporting service partners. The latest Xendit notices attribute both disruptions to partner-system issues, but do not identify the affected partner or establish a common technical cause.
The available records also do not establish how many transfers were delayed, how many merchants were affected or whether any funds were lost. Xendit has not disclosed how many transactions were recieved late by their beneficiaries.
For merchants relying on Xendit to distribute funds, the amount-specific restrictions complicate transaction reconciliation. A transfer to one bank or within one amount range could proceed while another transfer through the same platform remained delayed.
Flutterwave restores Nigerian card payments after five-hour outage
Flutterwave reported a prolonged card-processing disruption in Nigeria on November 14, affecting customers attempting to complete card payments through merchant checkout systems.
The company published its initial incident notice at 13:30 UTC, warning that some card transactions could fail. Flutterwave said it had notified the affected processing provider and was working to restore normal operations.
The disruption affected Flutterwave Collections APIs, which merchants use to process incoming customer payments.
At 19:03 UTC, Flutterwave confirmed that card-processing services had returned to normal. The interval between its first notice and resolution was approximately five hours and 33 minutes.
That was a lengthy interruption for a checkout service, although the company did not establish that all Nigerian card payments were unavailable throughout the period.
Flutterwave did not identify the affected processor, publish a technical explanation or disclose the number and value of unsuccessful transactions. Its notice also did not distinguish between outright payment failures and transactions that might have remained pending during the temproary disruption.
The incident follows earlier Flutterwave collection and Nigerian payout disruptions in late October. On October 28–29, selected local payment methods across several African countries experienced interruptions, followed by a separate Nigerian problem affecting merchant balance visibility, payouts and foreign-exchange rate lookups.
Those earlier incidents affected different payment functions. The November 14 card-processing notice provides no evidence connecting the latest outage to the October problems.
The reported impact on merchant revenue cannot be calculated from the available information. Doing so would require transaction volumes, failed-payment rates, average order values and evidence about whether customers successfully completed their purchases through alternative payment methods.
Flutterwave reports separate South African voucher-payment failure
Just over an hour after confirming the restoration of Nigerian card payments, Flutterwave reported another disruption, this time affecting selected South African rand-denominated voucher transactions.
The company published the South African alert at 20:07 UTC on November 14, identifying a problem with an unnamed third-party service provider.
According to Flutterwave, certain ZAR voucher payments were not being processed successfully. The affected service was again classified under Flutterwave Collections APIs, although the payment method and reported provider problem differed from the earlier Nigerian incident.
The Nigerian service was back, and then South Africa appeared in the incident log 64 minutes later.
Flutterwave said it was in contact with the affected provider and advised merchants to use other availble payment methods while engineers monitored the disruption.
Unlike the Nigerian card-processing incident, the South African voucher issue had not received a restoration announcement in the status record available at the November 14 reporting cutoff.
The company did not identify the voucher-processing partner, specify which voucher products were affected or disclose the number of unsuccessful payments.
There is no evidence that the South African voucher failure and Nigerian card outage shared a technical cause. Their proximity in time does not establish that either disruption resulted from a fault within Flutterwave’s core infrastructure.
Both incidents concerned incoming payment collections, whereas Xendit’s Indonesian problems involved outgoing transfers to banks and other payment destinations. Binance’s restrictions involved cryptocurrency withdrawals following a confirmed security breach.
By the end of November 14 UTC, Binance had reported substantial progress reopening blockchain withdrawal routes, Xendit had resolved two payout incidents, and Flutterwave had restored Nigerian card processing while its South African voucher interruption remained without a published resolution. The outstanding operational questions are narrower now: which Binance routes remain restricted, whether Xendit’s partner-related payout problems recur, and when Flutterwave’s affected South African payment channel returns to normal.
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.