Binance said UK restrictions targeted its affiliate, not its global site

On June 27, 2021, Binance publicly said a British regulatory action against Binance Markets Limited, its UK affiliate, did not directly alter services offered through Binance.com. The clarification followed a Financial Conduct Authority consumer warning first published on June 26 and a supervisory notice dated June 25. Together, the records exposed a consequential fault line in crypto regulation: a global platform could distinguish its website from a locally incorporated affiliate, while a national regulator could still use the affiliate’s permissions and consumer-protection powers to force prominent disclosures across the group’s customer channels.

The precise scope mattered. The FCA did not declare Bitcoin or Ether illegal, close Binance.com worldwide, or prohibit every UK resident from holding or trading spot cryptoassets. It imposed requirements on Binance Markets Limited, reference number 688849. The firm could not conduct activities covered by its Part 4A permission without the FCA’s prior written consent, effective immediately. The regulator separately stated that no other Binance Group entity held UK authorization, registration or a licence to conduct regulated activity.

What the FCA required

The June 25 supervisory notice required Binance Markets Limited to place a prominent warning on Binance.com, its applications and other communications by the close of business on June 30. It also required the firm to remove, or instruct the removal of, live advertising and financial promotions by that deadline; confirm its compliance in writing; and preserve records concerning UK consumers. The record-preservation material had to be held in the United Kingdom at a location disclosed to the FCA by July 2.

The FCA’s stated reasons went beyond a simple licensing technicality. It said Binance Markets Limited had not used its regulated permissions for more than 12 months and was failing, or likely to fail, the effective-supervision threshold condition. According to the notice, responses to two formal information requests in 2021 were incomplete and included refusals. The FCA said it had not received adequate information about the Binance Group’s organization, the routes UK customers could use to buy products, or the legal entity operating Binance.com. Those are regulator findings in the notice, not independently adjudicated facts.

Binance drew a corporate boundary

Binance’s June 27 response emphasized that Binance Markets Limited was a separate legal entity, had not launched its proposed UK business and did not provide services through Binance.com. The company said the FCA notice therefore had no direct effect on Binance.com services or its existing user relationships. That position was broadly consistent with a qualification inside the FCA-mandated disclosure itself: the requirements did not change arrangements for products or services delivered through Binance.com, and authorization was not required for unregulated activities.

That distinction prevented the episode from being accurately summarized as a blanket UK ban on cryptocurrency trading. But it did not make the intervention immaterial. The FCA had required the disclosure to appear on the global website and apps, and it warned that UK consumers using many cryptoasset investments might lack access to the Financial Ombudsman Service or Financial Services Compensation Scheme. The conflict was therefore about both legal perimeter and institutional accountability.

Why June 27 mattered

The exchange’s response turned a technical supervisory action into a public test of whether crypto groups organized across multiple entities could be effectively overseen at the national level. Binance argued that the regulated UK company and the global platform were distinct. The FCA’s notice, by contrast, said the wider group structure and incomplete answers prevented effective supervision of the authorized firm.

No market-price claim is made here. Crypto trades continuously across venues, and the surviving sources do not establish that the announcement caused a specific move during a defined trading window. The verifiable development on June 27 was the public clash over scope: services continued under Binance’s account of the situation, while the UK affiliate’s regulated permissions were constrained and group-wide authorization remained absent.