After MiCA: Which Stablecoins Can Europeans Actually Use?

There is no single useful answer to the question “Is this stablecoin available in Europe?” Access depends on the issuer, platform, service legal entity, country or regional scope, customer type, product function, payment or banking rail, supported blockchain network, and date.

One provider may stop spot trading but keep deposits and withdrawals. Another may stop both and convert balances. A Europe-locale product page may exist while actual availability still depends on the customer’s country and account. A token may also be directly minted or redeemed through an issuer or payment rail without relying on an exchange at all.

MiCA-era Europe is not a simple switch from one winner to another. Access is contracting in some places while new regulated issuance, redemption, banking, and distribution paths expand in parallel. This guide records reviewed examples, separates issuer status from service-provider status and actual access, and leaves unsupported functions unclaimed.

Scope note: in this guide, “Europe” is shorthand for the EU or EEA scope explicitly supported by each source. The UK, Switzerland, and other non-EEA jurisdictions are not treated as MiCA jurisdictions, even when one platform notice covers them together with the EEA.

Reporting based on a customer notice said Revolut would phase out USDT support. A public first-party policy page confirming the complete function-by-function schedule was not available in our review.

SOG therefore separates two layers: CySEC confirms the European crypto legal entity and MiCAR CASP authorization, while the reported USDT purchase, deposit, withdrawal, custody, and conversion schedule remains a reported policy layer.

The broader shift is visible across Binance, Kraken, Bitstamp, Coinbase, and other providers, and affects USDT as well as DAI, PYUSD, RLUSD, TUSD, FDUSD, USDP, USDD, and USDS.

This article focuses on observed access. For the legal framework, EMT and ART categories, and the full CASP transition explanation, read MiCA and Stablecoins.

The table below includes only functions supported by the reviewed sources. A missing function does not mean “available” or “unavailable”; it means this guide is not making that claim from the cited source.

Token-specific policy is only one layer. By July 2026, some platforms had broader service-state changes, while other pages exposed products without proving uniform access across every EEA country.

Specific regional policy outranks a generic product page. Kraken’s generic USDS product surface advertises buying and selling, while its EEA policy page explicitly blocks buying, selling, and trading for EEA clients. SOG therefore uses the more specific regional policy for the EEA conclusion.

RLUSD is a useful example of why this guide does not collapse company licensing, token status, and exchange access into one answer.

1. Ripple’s EU payments entity: Ripple announced full approval of an Electronic Money Institution licence from Luxembourg’s CSSF on February 2, 2026.
2. Ripple’s MiCA service-provider path: on June 23, 2026 Ripple announced preliminary approval for a MiCA CASP licence through a Green Light Letter subject to final conditions. On July 6, Ripple announced that it had obtained the EU CASP licence and described its European crypto operations as fully MiCA compliant.
3. The RLUSD issuer layer: Ripple’s public RLUSD user terms identify Standard Custody & Trust Company LLC as the issuer of RLUSD. The group’s European EMI and CASP authorizations therefore must not be rewritten as automatic proof that RLUSD itself is already a MiCA-authorized EMT.
4. Actual platform access: Kraken’s EEA policy blocks trading, buying, and selling of RLUSD while leaving deposits and withdrawals available. Bitpanda maintains a public page that describes buying RLUSD, but that page alone is not used to claim identical availability for every EEA country or account type.

The safe conclusion is narrower than either headline extreme: Ripple’s European regulatory footprint now includes both an EU EMI licence and an EU CASP licence, but that does not make RLUSD uniformly available across Europe or settle RLUSD’s token-level regulatory status by itself, and one platform restriction does not prove RLUSD is excluded everywhere.

Access contraction is only half the European market transition. New regulated paths are expanding, but regulatory readiness, retail eligibility, direct minting, redemption, payment rails, distribution scale, and current exchange access are still different questions.

Some fungible dollar stablecoins are issued inside and outside the EU. European authorities have not treated every policy question around these multi-issuance models as closed.

The EBA has said MiCA contains safeguards but has also awaited European Commission clarification. The ECB, ESRB, and some national authorities have raised concerns that stress or heavy redemptions could concentrate obligations on the EU side of a cross-jurisdiction structure.

This guide therefore treats a regulated European issuance path as an important fact, not as proof that every legal, liquidity, redemption, or platform-access question is permanently settled.

A simple “USDT lost, USDC won” story removes too much information. At least nine layers can move independently:

1. the legal issuer and its authorization;
2. the token’s regulatory, notification, or white-paper status;
3. the CASP’s authorization and service legal entity;
4. where applicable, a separate payment-services authorization layer for EMT payment or transfer activity;
5. the platform’s internal product and risk policy;
6. the customer’s country, regional scope, B2B or retail eligibility, or customer cohort;
7. the exact function or route: buy, sell, trade, deposit, withdraw, custody, Earn, margin, convert, direct mint, direct redemption, or bank/payment rail;
8. the supported blockchain network or deployment;
9. the effective date and any wind-down or migration period.

The ESMA interim MiCA register itself separates different issuer, white-paper, CASP, and non-compliant-entity datasets. Recent Bit2Me and Crossmint cases also illustrate that some EMT payment or transfer activities can involve an additional payment-services authorization layer. This guide does not generalize that requirement to every EMT activity; it treats the applicable service and legal structure as a separate question. One authorization or one delisting notice cannot answer every layer.

• ESMA — MiCA register hub and current register datasets
• ESMA and European Commission — Guidance on non-compliant ARTs and EMTs
• Binance — 2025 EEA non-MiCA stablecoin transition notice
• Kraken — Stablecoin offerings for EEA clients
• Kraken — Generic USDS product page used only as a specificity contrast
• Bitstamp — EU/EEA MiCA update on selected assets
• OKX Europe — Europe-locale USDT product page
• OKX Europe — Europe-locale USDC product page
• Crypto.com — Europe/EEA regional service page
• Bybit EU — General EU product context
• Gemini — UK, EEA, and Australia account-closure notice surface
• Uphold Europe — Transition-period service notice
• Coinbase Germany — USDT product page
• Coinbase Germany — DAI product page
• Coinbase Germany — PYUSD product page
• CySEC — Revolut Digital Assets (Europe) Ltd CASP register entry
• Ripple — full EU EMI licence announcement
• Ripple — preliminary MiCA CASP approval announcement
• Ripple — EU CASP licence announcement
• Ripple — RLUSD user terms and issuer identification
• Bitpanda — RLUSD public product page
• Circle — EEA MiCA issuer announcement for USDC and EURC
• Monerium — EURe, Web3 IBAN, network, mint and payout context
• Paxos — EU MiCA page and EUROe redemption-only notice
• Global Dollar — USDG European and Singapore issuance paths
• Banking Circle — EURI launch and historical distribution context
• Société Générale-FORGE — EURCV regulatory restructuring and historical distribution context
• Quantoz — EURQ and USDQ European issuance model
• AllUnity — EURAU and B2B scope
• AllUnity — CHFAU access, eligibility, reserves, and supported networks
• AllUnity — SEKAU access, eligibility, and supported networks
• ODDO BHF — EUROD product, access, and circulation context
• Qivalis — future project and explicit not-yet-issued status
• Sky.money — USDS protocol and non-custodial interface context
• Reuters — EBA and European multi-issuance policy debate
• Reuters — Bank of Italy call for multi-issuance clarity
• Cinco Días — Bit2Me payment-services authorization context
• Cinco Días — Crossmint payment-services authorization context
• Financial Times — Binance EU service wind-down context
• Reuters — Binance MiCA authorization context before the deadline
• Cointelegraph report syndicated by TradingView — reported Revolut USDT customer-notice change

Platform policies can change. The most specific current regional policy page and regulator register should take priority when a newer or more specific source appears. Generic product pages and marketing surfaces are not treated as uniform regional availability proof when they contain geographic, account-level, customer-type, or network caveats. Reported Revolut token-policy details remain separated from the official CASP legal-entity record because a public first-party USDT policy page was not available in the publication review.

This guide is a reviewed snapshot current through July 6, 2026. It is not a complete legal opinion for every EU or EEA country, every customer entity, every stablecoin, every platform function, or every supported network. “Not confirmed” is not the same as unavailable.

SOG separates asset-specific function evidence, platform-wide service state, product-surface context, issuer and token regulatory paths, direct mint and redemption routes, payment or banking rails, supported networks, and general licensing or service context. Future material changes require source review, an editorial revision, an updated information-current-through date, and a revision-history entry. Monitoring output never updates this page automatically.

This guide is not investment, legal, financial, or tax advice.