Binance Announced Its Russia Exit Through a Sale to CommEX

Binance said on September 27, 2023 that it had agreed to sell its entire Russia business to CommEX and leave the country. The announcement made the world’s largest cryptocurrency exchange by trading volume a test case for how a global trading platform would unwind a national market under sanctions and compliance pressure.

The seller disclosed no purchase price. Binance said Russian customers would be moved through an orderly off-boarding process lasting as long as one year, while its exchange services and other business lines in Russia would be shut over the following several months. It also said it would retain neither an ongoing revenue share nor an option to repurchase the business. Those were company representations on September 27, not independently audited completion records.

What Binance actually announced

The primary record establishes an agreement, not a completed transfer. Binance identified CommEX as the buyer and said some newly registered Russian users who had passed know-your-customer checks would immediately be redirected to the platform, with that redirection expanding over time. Binance and CommEX would jointly tell existing users how to migrate.

Noah Perlman, Binance’s chief compliance officer, attributed the decision to incompatibility between operating in Russia and Binance’s compliance strategy. Reuters independently reported the agreement on September 27 and confirmed that the financial terms were undisclosed. Interfax also reported the exit that date and noted that CommEX’s website described a centralized cryptocurrency exchange but disclosed no founders.

That lack of disclosed ownership mattered. CoinDesk reported that CommEX had announced its launch on September 26, 2023, only one calendar day before Binance named it as buyer. The available event-day record therefore did not establish CommEX’s controllers, capital, regulatory status, balance sheet or operational capacity. It also did not show how many customers, assets or liabilities were included in the sale.

Why the exit mattered

Centralized exchanges sit between public blockchains and national financial systems. Their users may hold crypto assets, but onboarding, identity checks, ruble payment channels, sanctions screening and account access depend on corporate infrastructure that can be restricted or withdrawn. Binance’s plan showed that geopolitical and compliance decisions could reshape access even without changing Bitcoin or Ethereum themselves.

The announcement also followed visible pressure around Binance’s Russian operations. In April 2022, after the European Union’s fifth sanctions package, Binance restricted trading and new deposits for covered Russian accounts holding more than €10,000 in crypto assets. In August 2023, the exchange removed several sanctioned Russian banks from payment options on its peer-to-peer service, according to contemporaneous reporting. By September 27, the company was no longer describing a narrower product restriction; it was announcing a full business exit.

Still, “full exit” described Binance’s intended end state. The company itself allowed up to one year for customer off-boarding and several months for service closures. Users therefore faced a transition period rather than an instantaneous shutdown. Binance’s assurance that customer assets were safe was an attributable company claim, not a reserve attestation or guarantee from a regulator.

What remained unknown

The event-day evidence did not disclose the contract, purchase price, customer count, asset volume or licensing arrangements. It did not independently verify that every balance could be migrated or withdrawn on the announced timetable. It also offered no defensible basis for attributing a bitcoin, BNB or broader market move to the sale, so this reconstruction makes no price or return claim.

Later record

On November 21, 2023, a later FinCEN consent order required an independent monitor to review controls connected to Binance’s announced Russia exit. That later enforcement record confirms the transaction’s compliance significance, but it must not be read backward as information available on September 27 or as proof that the announced migration had already been completed.