The MiCA Article 48 transition window closes on July 1, 2026. After that date, any euro-denominated electronic money token without authorization from a competent EU authority cannot be offered to the public or admitted to trading on a venue regulated under MiCA. Exchanges with EU licenses are the choke point — they have to enforce the delisting whether the issuer filed or not.
I tried to pull a clean list of which euro stablecoin issuers actually filed and which ones quietly let the deadline approach. I could not get there from the public record alone. What I could do is check which exchanges in my dataset hold the EU authorizations that would force them to act. That is what this piece walks through. Where I have a number, the number is exact. Where I do not, I say so.
What does MiCA's July 1, 2026 deadline actually trigger?
The deadline ends the transitional regime that let pre-existing crypto-asset service providers and token issuers keep operating in the EU while their authorization applications were reviewed. After July 1, two things become enforceable simultaneously: an issuer of an e-money token (the MiCA category that covers euro stablecoins) needs explicit authorization from a national competent authority, and a trading venue regulated under MiCA cannot list a non-compliant token to EU users.
The mechanism is administrative, not theatrical. An exchange with a French AMF registration or a Cypriot CySEC license is legally obligated to remove non-authorized euro stablecoin pairs from its EU-facing interface. The token does not stop existing. It stops being tradable on regulated European venues. That distinction is the entire story of what happens that week.
Why am I writing about exchanges instead of issuers?
Because the issuer-side filing data is not something I can verify from the public surface. I can read press releases. I can read MiCA itself. I cannot independently confirm, on July 1, which euro stablecoin issuers submitted complete authorization dossiers to which national competent authority, and which ones quietly missed the window. National regulators publish authorization decisions on their own timelines, and the dataset I work from for this publication does not include those filings.
What I do have is exchange-side data. The exchanges in my dataset disclose their EU licensing posture, and that posture is what determines whether a non-compliant euro stablecoin actually gets delisted. An issuer can be non-compliant in theory and still trade in practice if no EU-licensed venue is enforcing the rule. So the choke point is the exchange. That is where I went.
Which exchanges in my dataset hold EU authorization that forces them to act?
Three of the five exchanges I cover have EU-jurisdiction licenses: Binance holds a limited license from France (AMF) and a limited license from Italy (OAM). Bybit holds a full license from Cyprus (CySEC). Bitget holds full licenses from Lithuania (FCIS) and Poland (KNF). Those five license entries are the entire EU-licensed surface in my exchange dataset.
OKX and MEXC do not appear in my dataset with any EU authorization. OKX's licensing entries are Dubai (VARA, provisional) and Bahamas (SCB, full). MEXC's only listed license is Seychelles (FSA, offshore). What that means for the July 1 deadline is straightforward: the obligation to delist a non-compliant euro stablecoin under MiCA falls on the exchanges with EU registrations. The others operate outside the regime's direct reach for the venues they themselves run.
What does Binance's limited license in France and Italy actually permit?
Both registrations are listed as "limited" — they are the older national PSAN-type registrations that predate MiCA's full passportable license regime. A French AMF limited registration and an Italian OAM enrollment let the exchange offer crypto-asset services to residents of those countries, but they were never the full investment-services license. Under MiCA's transition rules, these registrations are exactly the kind of thing the July 1 deadline is testing.
For Binance specifically, the SEPA fiat onramp listed in my data — EUR deposits at 0% fees with 1–2 day processing — is the channel through which euro liquidity enters and exits. If a euro stablecoin pair on Binance's EU-facing interface refers to a non-authorized token after July 1, the limited French and Italian registrations are the registrations that would be at risk. Whether Binance has prepared by listing only authorized euro stablecoins is a question I cannot answer from the licensing data alone.
Why does Bybit's Cyprus full license matter more than people think?
A full CySEC license is a passportable EU authorization. Once Cyprus authorizes a crypto-asset service provider under MiCA, that authorization gives the firm a route to operate across the European Economic Area without re-licensing in each member state. That is the post-transition design — one license, twenty-seven markets. Bybit's Cyprus registration sits inside that framework.
The practical consequence is that the July 1 deadline applies to Bybit's EU-facing surface uniformly. There is no jurisdictional patchwork to navigate. If a euro stablecoin pair is not backed by an issuer with valid MiCA authorization, it should not be available to EU users on Bybit. Bybit's SEPA fiat onramp listed in my data — EUR deposits at 0% fees with 1-day processing — is the rail most directly affected. Bybit's CER security score in my dataset is 9.1 and the last proof-of-reserves audit is dated 2025-03-12. Neither of those numbers tells me whether the EUR pairs available on July 2 will look the same as the ones available on June 30.
Where does Bitget's Lithuania-and-Poland posture put euro stablecoin pairs?
Bitget holds full licenses from both Lithuania (FCIS) and Poland (KNF). Lithuania has historically been the fastest EU jurisdiction for crypto-asset firm authorization, and a full FCIS license is the kind of authorization that under MiCA's passporting regime extends across the EEA. Poland's KNF full license adds a second member-state anchor. Two EU full licenses is a heavier compliance footprint than either limited registration Binance carries.
What's missing from Bitget's profile in my data is a SEPA fiat onramp — Bitget's listed onramps are PIX for Brazil and UPI for India, both at 0%. No EUR rail. That is interesting because it suggests Bitget's EU-licensed presence is leaner than the licensing footprint would imply. Whether Bitget lists euro stablecoin pairs on its EU-facing interface at all, and whether those pairs reference authorized issuers, is a question the licensing data does not answer.
What about OKX and MEXC — what is their exposure to the deadline?
Neither appears in my dataset with an EU license. OKX is registered with Dubai (VARA, provisional) and Bahamas (SCB, full). MEXC is registered only with Seychelles (FSA, offshore). For purposes of MiCA Article 48, these registrations do not trigger the same enforcement obligation that an EU license does. The legal pressure to delist a non-authorized euro stablecoin from an EU-facing surface does not apply to a venue that has no EU-facing surface in the regulatory sense.
OKX does list a SEPA fiat onramp in my data (EUR, 0%, 1–2 days), which is the kind of EU-facing rail that historically attracts regulator attention even without a local license. MEXC lists no EUR onramp. The exposure is not zero — EU users can still find their way to these venues — but the choke-point logic of the July 1 deadline is weaker. The enforcement mechanism MiCA was designed around is licensed venues policing their own pairs, not unlicensed venues being chased one by one.
What can't I verify from the public record on issuer filings?
The list of euro stablecoin issuers that filed for authorization, the national competent authority each one filed with, the date of submission, the date of decision, and the scope of authorization granted — none of that is in the data I work from. National regulators publish authorization registers, but they publish on their own cadence, in their own formats, in their own languages. Reconstructing the full picture requires pulling from at least twenty-seven sources and reconciling them against a list of euro stablecoin issuers that itself does not have an authoritative version.
I can read what specific issuers announce publicly. I can read what specific exchanges announce about which tokens they are delisting. I cannot verify the negative — that an issuer did not file. The absence of a public announcement is not proof of an absent filing. That is the asymmetric information problem this category lives inside, and the July 1 deadline does not solve it; it only forces it into the open for one short window of weeks.
What should a holder of a euro stablecoin do this week?
Two things, in order. First: check whether the specific euro stablecoin you hold has been confirmed as authorized under MiCA by the national competent authority of the EU member state where the issuer is established. The issuer's own public communications are the starting point, but the authoritative source is the regulator's register. Second: check whether the exchange you hold the token on has announced delisting timelines for non-authorized euro stablecoins. The two answers together determine your exposure.
If the exchange has an EU license — Binance's France/Italy limited registrations, Bybit's Cyprus full license, Bitget's Lithuania/Poland full licenses — the July 1 enforcement obligation applies and the delisting clock is running. If the exchange has no EU license listed, the legal mechanism is weaker but the operational risk of withdrawal channels closing during the same week is not weaker, because correspondent banking and SEPA gateways do not care about your licensing analysis.
This piece does not address which specific euro stablecoins are authorized — I could not verify the issuer-side data from the public record. It does not address USD-denominated stablecoin treatment under MiCA, which is a separate category with its own thresholds. And it does not address the secondary-market continuity question — whether a delisted token remains tradable peer-to-peer or through decentralized venues outside MiCA's scope. Each is a separate argument and worth its own piece.
FAQ
What is the exact date the MiCA delisting takes effect?
July 1, 2026 is the end of the Article 48 transitional period for crypto-asset service providers and token issuers. After that date, EU-licensed exchanges are legally obligated to remove euro stablecoin pairs whose issuers do not hold authorization from a competent EU authority. The token does not cease to exist; it ceases to be tradable on regulated European venues for EU users.
Which exchanges in this analysis are most exposed to the deadline?
The three exchanges with EU licenses listed in my dataset: Binance (limited registrations in France via AMF and Italy via OAM), Bybit (full CySEC license in Cyprus), and Bitget (full licenses in Lithuania via FCIS and Poland via KNF). These are the venues with the direct legal obligation to enforce delistings. OKX and MEXC, which list no EU licenses in my dataset, face weaker direct enforcement pressure.
Does this affect USD stablecoins like USDT or USDC?
This piece is specifically about euro-denominated electronic money tokens — the MiCA category covering euro stablecoins. USD-denominated stablecoins fall under different MiCA thresholds, including the asset-referenced token regime and separate caps on non-euro EMT issuance volume. The analysis here does not extend to those rules, and the July 1 deadline mechanics work differently for USD-denominated tokens than for euro-denominated ones.
Can I still hold a delisted euro stablecoin in self-custody?
Yes, in principle. MiCA regulates issuance and trading on regulated venues, not the underlying existence of a token. If you hold a euro stablecoin in a self-custody wallet, the token sits there regardless of any exchange action. The practical question is whether you have a redemption path or a secondary market that can accept it after the EU-licensed exchanges have removed the pair. That answer depends on the specific token and is not in the grounding I work from.
Why couldn't you confirm the issuer-side filings directly?
Because national competent authorities across the EU publish authorization decisions on their own timelines, in their own languages, in registers that are not consolidated. There is no single authoritative source for "euro stablecoin issuers that filed for MiCA authorization by July 1, 2026." Reconstructing that picture requires pulling from twenty-seven national registers and reconciling against a list of issuers that itself has no canonical version.
Will the Binance limited license in France be enough for MiCA passporting?
A limited registration is not the same as a full MiCA authorization. Limited registrations are the older national PSAN-type frameworks that predate MiCA's full passportable license. The July 1 deadline is exactly the moment when those registrations are tested. Whether the AMF and OAM registrations Binance currently holds are sufficient, or whether the exchange has a separate full MiCA application in progress, is not something the dataset I work from resolves.
Does the deadline apply to decentralized exchanges?
MiCA's enforcement architecture is built around regulated trading venues and authorized service providers. Genuinely decentralized protocols — ones with no identifiable issuer or operator — sit at the edges of the framework, and the regulation explicitly carves out fully decentralized services. In practice, the lines are contested, and several front-ends that route to decentralized infrastructure have already been treated as regulated venues by national authorities. The July 1 enforcement most clearly affects the centralized exchanges named in this piece.