In today’s crypto and payments roundup, Binance Japan disclosed that withdrawals remained suspended for 29 assets more than ten days after Binance Global’s security breach. Coinbase reported an Indian banking-partner outage affecting rupee withdrawals and UPI services, while Mercado Pago recorded three payment-processing incidents in Argentina, including a renewed disruption late in the afternoon. The incidents have different causes and affect different services, with no evidence connecting them.
Binance Japan confirmed on November 9 that withdrawals remained unavailable for 29 cryptocurrencies, despite additional progress restoring services following Binance Global’s October 29 security breach.
In its seventh recovery notice, the Japanese exchange provided a detailed breakdown of withdrawal availability as of 16:00 Japan Standard Time, or 07:00 UTC. Withdrawals had fully resumed for 29 assets and partially resumed for another seven, leaving 29 assets without withdrawal access.
The suspended assets include Cardano (ADA), Litecoin (LTC), Stellar (XLM), Bitcoin Cash (BCH), NEAR, Hedera (HBAR), Polkadot (DOT), Cosmos (ATOM), Algorand (ALGO), Ethereum Classic (ETC), Pepe (PEPE) and several smaller cryptocurrencies.
Since its November 5 update, Binance Japan had restored full withdrawal access for eight additional assets: WBTC, APE, APT, AXS, CYBER, IMX, MEME and NEIRO. Filecoin (FIL) and Mask Network (MASK) also became partially available, meaning customers could withdraw them on some supported blockchains but not others.
The changes increased the fully restored category from 21 assets on November 5 to 29 on November 9. The partially restored category rose from six to seven, reflecting two additions and CYBER’s transition to full availabilty.
Ten days and then some, and those 29 withdrawal routes still were not back.
Binance Japan said cryptocurrency trading, fiat deposits and fiat withdrawals continued operating normally. Cryptocurrency deposits also remained available, apart from existing restrictions affecting DOT, QTUM and ZIL that the company said were unrelated to the security incident.
The restrictions follow Binance Global’s disclosure that attackers compromised its hot-wallet infrastructure on October 29, resulting in approximately $6.34 billion in unauthorized cryptocurrency withdrawals. Binance committed to absorbing the losses and replacing affected assets using corporate resources and its Secure Asset Fund for Users.
An earlier DaveFinances report on Binance’s $6.3 billion security breach documented the exchange’s initial asset replenishment and withdrawal recovery efforts.
Binance Japan has consistently maintained that customer assets were not affected. Its October 30 disclosure said locally held cryptocurrency was stored in cold wallets seperate from Binance Global’s compromised hot-wallet infrastructure.
That separation was central to the Japanese subsidiary’s response, although it did not prevent prolonged withdrawal restrictions. Binance Japan initially expected withdrawals to resume within 48 hours, but its November 9 notice confirmed that recovery was still incomplete.
The situation has also attracted regulatory attention. Abu Dhabi Global Market’s Financial Services Regulatory Authority said in an October 30 statement concerning Binance’s security incident that it was engaging with the exchange and monitoring developments involving unauthorized asset withdrawals.
The latest Japanese update builds on earlier reporting on Binance Japan’s phased withdrawal reopening, when only eight assets had fully regained withdrawal access as of November 2.
The reopening happened, but only token by token and sometimes chain by chain. Binance Japan has not provided a confirmed date for restoring withdrawals across the remaining 29 assets.
Coinbase reports Indian banking-partner outage affecting INR transfers
Coinbase disclosed a separate service disruption on November 9 affecting Indian users’ access to rupee withdrawals, bank-account linking and Unified Payments Interface (UPI) transactions.
The exchange published its incident notice at 03:07 Pacific Standard Time, equivalent to 11:07 UTC, identifying an outage at an unnamed banking partner.
According to Coinbase, affected customers could experience four problems: unsuccessful INR withdrawals, an inability to link new bank accounts, unavailable UPI functionality and delayed deposits.
The company classified the incident as under investigation and assured customers that their funds were safe. Its notice did not identify the banking partner or provide an estimated restoraton time.
The money can sit in the account while the banking route, that is the part not working.
Coinbase did not report that its broader cryptocurrency trading infrastructure had failed. The disclosed problem concerned local banking connectivity and associated payment functions, rather than a confirmed exchange-wide outage.
The scope of the disruption also remains unclear. Coinbase has not disclosed how many Indian users were affected, whether all supported banking connections were unavailable or how many withdrawal attempts failed.
UPI is India’s instant-payment network, and access through cryptocurrency platforms depends on the payment arrangements available to those platforms. Coinbase attributed this interruption specifically to its banking partner, without indicating a broader disruption to India’s payment network.
The incident therefore concerns customers’ ability to move rupees through Coinbase’s supported banking channels. No evidence in the public status notice establishes a restriction on cryptocurrency withdrawals through unrelated blockchain networks.
As of the latest November 9 status information reviewed, Coinbase had not published a resolution.
Mercado Pago records three Argentine payment disruptions
Mercado Pago experienced multiple payment-processing problems in Argentina on November 9, with two incidents resolved during the morning and another Point payment-approval anomaly reported late in the afternoon.
The first problem began at 07:18 GMT-3, when Mercado Pago identified an approval anomaly affecting its Point payment terminals in Argentina. The company marked the incident resolved at 08:56, giving it a reported duration of one hour and 38 minutes.
A second incident started at 08:09 GMT-3, involving degraded online payment processing in Argentina. Mercado Pago reported that service had been restored at 10:16, after two hours and seven minutes.
The two disruptions overlapped for 47 minutes, between 08:09 and 08:56. During that interval, the status notices identified problems affecting both Point approvals and online payment processing.
Morning had two incidents, and late afternoon another one again.
At 16:56 GMT-3, Mercado Pago opened a new Point approval-anomaly incident affecting Argentina. The company said it was investigating the problem, and the incident remained unresolved in the status information available at the time of review.
Mercado Pago did not provide technical explanations for the incidents or disclose how many payments, merchants or customers were affected. Its notices also did not establish whether the morning and afternoon Point incidents shared the same underlying cause.
The interruptions followed other recent operational problems. A November 6 DaveFinances report on Mercado Pago and other payment disruptions covered earlier delays affecting the processor’s payment notifications, alongside separate incidents involving Kraken and Wise.
Those earlier Mercado Pago problems involved delayed notifications of payment events, rather than confirmed failures of the underlying transactions. November 9’s incidents were described differently: approval anomalies at Point terminals and degraded online payment processing.
A merchant may see the approval fail and try again, and what happened to the first attempt is not clear from the notice.
Depending on the transaction state, that uncertainty may require merchants to check their payment records before retrying or completing an order. The company’s disclosures do not establish that duplicate charges, missing payments or financial losses actually occurred.
The repeated Argentine incidents also create a reconcilation problem for anyone trying to measure their operational impact. Mercado Pago reported incident start and resolution times, but supplied no transaction counts, approval-rate figures or financial estimates.
Across the three companies, the November 9 disruptions present distinct forms of restricted access: Binance Japan customers unable to withdraw particular cryptocurrencies, Coinbase users facing unavailable local banking functions, and Mercado Pago merchants encountering payment-processing anomalies.
Binance Japan’s case remains the longest-running of the three, with restrictions persisting more than ten days after the underlying security incident. Coinbase’s Indian outage and Mercado Pago’s latest Argentine Point incident remained under investigation in their respective public status records. Neither company had disclosed the financial impact of the interruptions.
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.