The MiCA Deadline Arrives: ESMA Draws a Line, and a Major Exchange Tests It

For eighteen months, the end of MiCA's transitional period has been a date on the horizon. On 1 July 2026, it becomes the present. In the final days before the deadline, two developments arrived close together that, read side by side, show what the transition from a transitional regime to full application actually means in practice. The first is a public statement from ESMA setting out what it expects of providers that are not authorised in time. The second is the decision by Binance, the largest crypto-asset exchange in the world, to withdraw its MiCA application in Greece and pursue authorisation elsewhere.

One is the rule. The other is the rule meeting reality.
‍

ESMA draws the line

On 23 June, ESMA issued a public statement addressed to a specific and consequential audience: crypto-asset service providers that will not hold MiCA authorisation by 1 July. While many CASPs will have secured authorisation by the deadline, ESMA acknowledged that others, including significant providers currently serving EU clients under national transitional regimes, may not.

The message to those providers is that there is no informal grace period beyond the deadline. From 1 July, providing crypto-asset services to EU clients without a MiCA licence is a breach of EU law, and ESMA expects an orderly wind-down to begin immediately.

In concrete terms, ESMA set out that unauthorised CASPs must:

• Stop onboarding new EU clients at once, cease marketing and solicitation, and open no new accounts or client relationships.
• Limit services to what is strictly necessary for an orderly exit, namely selling or transferring crypto-assets, reallocating assets, or closing positions. Custody may continue only for the period needed to complete the wind-down.
• Communicate clearly, promptly, and repeatedly with both retail and institutional clients about timelines, any automatic position closures, and which protections apply during the transition.
• Maintain full AML and CFT compliance throughout, including customer due diligence, transaction monitoring, sanctions screening, and suspicious activity reporting.

Two further points in the statement carry weight beyond the immediate wind-down population. Authorised CASPs may not outsource or delegate critical functions, including custody, to unauthorised third-country entities, even within the same corporate group. And clients of unauthorised providers do not benefit from MiCA's investor protection framework, which is why ESMA directed users to verify their provider's status in the ESMA Register and, where a provider is unauthorised, to move their assets to an authorised CASP or a self-hosted wallet.

The statement is best understood as a supervisory signal. ESMA is putting both market participants and national competent authorities on notice that operation without authorisation after the deadline will not be treated as a grey area, and that a disorderly exit will itself be regarded as a failure.
‍

The line meets reality

The following day, the framework acquired a live test.

On 24 June, Binance announced that it was withdrawing its MiCA licence application with the Hellenic Capital Market Commission (HCMC) in Greece and would pursue authorisation in another EU Member State, to be announced when ready. In its notice to users, the exchange said it had worked with the HCMC over many months but that, with no formal decision reached as the transitional period came to a close, it had taken what it described as the prudent decision to withdraw and refile elsewhere. Binance stated that user funds remain safe and accessible, that it would contact affected EU users directly, and that its commitment to operating under MiCA in Europe was unchanged.

It is worth being precise about what happened. Binance withdrew the application. No formal authorisation decision was issued by the HCMC, and the company has said it received no formal indication of rejection. Reporting ahead of the announcement had suggested the Greek regulator was inclined to decline the application, but the confirmed fact is a withdrawal, not a refusal. The distinction matters, because the two have different consequences and different signals attached.
‍

What the two developments reveal together

Taken on its own, either item is a news event. Together, they illustrate several features of how MiCA authorisation works that are easy to misunderstand.

Authorisation is a national decision, but not a purely national one. A MiCA licence is granted by a single Member State's competent authority, and because that licence passports across all 27 Member States, the choice of home state is genuinely consequential. It determines which regulator runs the substantive assessment, at what pace, and under what local conditions. Binance's own account, however, described HCMC review followed by review at ESMA level. ESMA does not grant or veto individual licences; its role is supervisory convergence, ensuring national authorities apply MiCA consistently and guarding against regulatory arbitrage. For the largest and most cross-border applicants, that EU-level consistency scrutiny carries particular weight, and a national authority's preliminary view is one input rather than the whole picture.

The home-state choice is consequential but reversible. A provider can withdraw an application in one jurisdiction and pursue authorisation in another. This is a feature of the system, and it gives applicants latitude. What it does not do is stop the clock.

Timing is the binding constraint. This is where the ESMA statement and the Binance decision intersect most directly. A provider that is unauthorised on 1 July must begin an orderly wind-down of its EU services, exactly as ESMA set out, even if a fresh application is already in progress in another Member State. Refiling elsewhere does not pause the wind-down obligation. The interim period, between withdrawing in one jurisdiction and securing authorisation in another, is precisely the situation ESMA's statement is written to govern.

A user's practical position turns on authorisation status, not on the provider's brand or scale. The protections a client enjoys, and the actions a client may need to take, depend on whether their provider holds a MiCA licence. This is true regardless of how large or well-known the provider is, which is exactly why ESMA has been directing clients to the ESMA Register rather than to reputation.
‍

Why this matters now

The end of the transitional period is the moment MiCA moves from a framework being implemented to a framework in full effect. ESMA's statement is the clearest signal yet that the deadline will be treated as a hard one, and that supervisory attention will extend to how providers exit, not only to whether they are authorised. The Binance decision shows what that looks like for even the largest participant: a major exchange recalibrating its European strategy in the final days, with real consequences for users that depend entirely on authorisation status.

For the rest of the market, the practical takeaways are straightforward. Providers should confirm their authorisation position and, where it is incomplete, plan an orderly path that meets ESMA's expectations rather than relying on an informal extension that will not come. Clients should verify their provider's status in the ESMA Register and understand what protections apply to them. And everyone operating in the European market should expect the interaction between national competent authorities and ESMA to remain one of the most consequential dynamics in how MiCA is applied in the years ahead.

The Alliance will continue to follow both threads, the supervisory expectations now in force and the authorisation decisions that will define the post-transition landscape, as they develop.

‍