MiCA has applied generally since 30 December 2024, while its stablecoin titles applied from 30 June 2024. The longest possible grandfathering period for pre-existing crypto service providers ended on 1 July 2026. Users should now verify a provider’s actual authorisation, not rely on an application, a national registration or an EU-looking website.
The dates that matter in July 2026
MiCA is not a single launch-day event. Titles III and IV, covering asset-referenced and e-money tokens, started applying on 30 June 2024. The remainder of the regulation applied from 30 December 2024. Article 143 allowed Member States to offer shorter transitional periods to firms already operating under national law, but never beyond 1 July 2026.
That distinction matters. A firm operating under a national grandfathering arrangement was not automatically a MiCA-authorised CASP. Once its applicable transition expired, it needed authorisation to continue the relevant service or had to stop until authorised. ESMA’s register and the relevant national competent authority are the starting points for verification.
- Check the exact legal entity, not only the trading brand.
- Match the service used—custody, exchange, execution or transfer—to the permission shown.
- Record the country and competent authority behind the authorisation.
- Treat “application submitted” as different from “authorised”.
What users will notice before they read the regulation
MiCA’s direct obligations fall mainly on issuers and service providers, but users experience them through product changes. A platform may change the tokens it offers, the countries it serves, custody terms, complaints process or the information requested before a transfer. A stablecoin can be available on one venue and restricted on another because each provider must assess its own regulatory position and risk.
Transfer transparency also comes from Regulation (EU) 2023/1113, often called the Travel Rule. It has applied since 30 December 2024 without MiCA’s CASP grandfathering. Information about originators and beneficiaries accompanies covered transfers, and interactions with self-hosted addresses can trigger verification steps. MiCA itself is not a tax law, so authorisation never proves that a user’s gains, income or reporting are tax-compliant.
A practical provider and records review
Build a provider inventory before moving assets under time pressure. List every exchange, custodian, broker, payment route and self-hosted address used by the person or company. For each provider, capture the contracting entity, jurisdiction, current licence status, available export formats, withdrawal rules and any notice about service changes.
Download transaction history while access is available. Preserve order records, deposits, withdrawals, wallet addresses, bank statements and evidence of the original acquisition. These records serve different questions: MiCA status concerns the provider; source-of-funds review concerns a particular transfer; tax treatment concerns the holder and relevant residence periods.
- Reconcile platform exports with wallet and bank records.
- Keep original files as well as a human-readable ledger.
- Document unexplained gaps instead of filling them with estimates.
- Review concentration risk without assuming that self-custody is suitable for everyone.
Where a fact-specific review is still required
MiCA does not make every token or decentralised arrangement equivalent. Financial instruments remain under other regimes; genuinely unique NFTs and fully decentralised services may fall outside particular MiCA provisions, but labels alone do not decide the analysis. Governance, marketing, fungibility, control and the service actually provided can change the result.
This briefing is a current framework, not an individual legal, tax or investment opinion. A founder serving EU users, an investor converting a historic position and a treasury holding stablecoins may face different licensing, AML, accounting and tax questions. Confirm the provider and national position at the time of the planned action.
Questions clients ask
Does MiCA require an individual holder to obtain a licence?
Ordinary holding for one’s own account does not itself make the holder a CASP. A person providing regulated crypto-asset services as a business needs a separate analysis of the activity, clients and jurisdiction.
Is a provider legal because it submitted a MiCA application?
No. An application is not an authorisation. After the applicable transition ended, the provider’s permission should be confirmed in ESMA or the relevant national authority’s records.
Does MiCA ban self-hosted wallets?
No general ban follows from MiCA. However, a regulated provider may need information or verification when transferring to or from a self-hosted address, and its risk policy may go beyond the regulatory minimum.