Can a MiCA-Authorised Crypto Firm Serve Clients Across the European Union?
For a crypto firm planning EU expansion, one MiCA authorisation can support cross-border service delivery, provided its service scope and notifications are properly aligned.

For a crypto firm planning EU expansion, one MiCA authorisation can support cross-border service delivery, provided its service scope and notifications are properly aligned.
The EU passport is available to authorised crypto-asset service providers
A crypto-asset service provider, or CASP, authorised under the EU Markets in Crypto-Assets Regulation can provide authorised crypto-asset services across the European Union.
This arrangement is commonly called MiCA passporting. It allows a CASP to operate in other Member States through:
- Freedom to provide services, without setting up locally.
- Establishment in another Member State, including through a branch.
Under Article 59 of MiCA, a host Member State cannot require the CASP to maintain a physical presence solely because it provides services cross-border.
For a firm with a multi-country operating model, this can reduce the need to seek separate crypto-service licences in each Member State. The passport does not, however, create a universal licence for every activity involving tokens, payments, investments or financial products.
The firm must be properly authorised as a MiCA CASP in its home Member State first. A pre-MiCA national virtual asset service provider registration is not the same as a current MiCA authorisation or an EU-wide passport.
MiCA passporting covers specific authorised services
The passport applies only to the crypto-asset services that the competent authority has authorised and that the CASP has notified for cross-border provision.
A CASP authorised for custody, for example, should not assume it can also operate a trading platform, exchange crypto-assets for funds, execute orders, provide advice, manage portfolios or transfer crypto-assets for clients.
MiCA requires the authorising authority to specify the services within the CASP’s permission. If the firm wishes to add a new regulated service, it must request an extension of its authorisation.
The distinction is commercially important. A customer journey may combine wallets, custody, token exchange, fiat payments, transfers, advice and token issuance. These activities can sit within different regulatory categories, and some may fall outside MiCA altogether.
| Activity or product | Does MiCA passporting automatically cover it? |
|---|---|
| A notified crypto-asset service within the CASP’s authorisation | Yes, subject to the Article 65 notification process |
| A new crypto-asset service not included in the authorisation | No. The CASP needs an authorisation extension |
| Token issuance or admission to trading | Not necessarily. Different MiCA rules may apply |
| Tokenised financial instruments | No. These may fall under MiFID II and related legislation |
| Payment services or fiat payment flows | No. Other regulatory requirements may apply |
| Asset-referenced tokens and e-money tokens | Not automatically. Issuer rules and other conditions may apply |
MiCA’s scope provisions exclude financial instruments, deposits, certain funds, securitisation positions, insurance products and several pension-related products. Tokenisation does not itself determine whether MiCA is the correct regulatory framework.
The CASP must notify its home authority before entering another Member State
A MiCA passport is not activated automatically when authorisation is granted.
Before serving clients in another Member State, the CASP must submit a cross-border notification to its home competent authority under Article 65 of MiCA. The notification must identify:
- The Member States where the CASP intends to provide services.
- The specific crypto-asset services it plans to provide.
- The intended start date.
- Any non-MiCA activities carried out by the CASP.
The home competent authority then has 10 working days to send the information to the relevant host-state contact points, ESMA and the European Banking Authority.
This is a notification procedure, not a second host-state licensing process. Still, it needs to be treated as part of the market-entry plan rather than an administrative step left until launch.
A firm should ensure that its public service descriptions, customer contracts, onboarding flows, custody model and operational controls match both its authorisation and its passport notification. Overstating service scope can create avoidable regulatory and commercial risk.
A CASP can begin cross-border services within the Article 65 timetable
A CASP may begin providing services in the notified Member State when its home authority confirms that it has transmitted the notification.
If that confirmation does not arrive first, the CASP may begin no later than 15 calendar days after submitting the required information to its home authority.
That timetable is short compared with a separate authorisation process, but it is not the full measure of expansion readiness. The legal notification may be complete while internal operations still need work.
A cross-border launch may require reliable arrangements for:
- Client onboarding and customer communications.
- AML and counter-terrorist financing controls.
- Crypto-asset transfer information requirements.
- Wallet and client-asset segregation.
- Complaints handling.
- Customer support and language coverage.
- Banking, custody and outsourcing arrangements.
- ICT security and business continuity.
The CASP authorisation requirements in Article 62 show the depth of evidence expected from applicants. They include governance, prudential safeguards, AML controls, ICT and security documentation, business-continuity plans, client-asset segregation procedures and service-specific policies.
A local branch may be useful, but it is not mandatory
MiCA allows a CASP to serve other Member States without establishing a local branch or office. A branchless model can reduce entity-management costs and avoid duplicating governance structures across the EU.
However, a local presence can still be commercially or operationally useful. A firm may choose to establish locally because of customer support needs, banking relationships, tax considerations, staffing, language requirements or institutional credibility.
The decision should therefore separate regulatory necessity from operating preference.
A local entity or branch is not required merely to exercise MiCA passporting rights. Yet one authorised EU entity must still have substantive EU presence. MiCA requires a CASP to have:
- A registered office in a Member State where it carries out at least part of its crypto-asset services.
- Its place of effective management in the Union.
- At least one director resident in the EU.
These requirements make a purely nominal EU structure unsuitable. Passporting supports centralised delivery, but it does not support a letterbox entity with all meaningful management and activity outside the Union.
Legacy VASP status does not create a current MiCA passport
National transitional regimes allowed certain existing crypto-asset providers to continue operating temporarily while MiCA authorisation processes were underway. Those arrangements were not equivalent to a MiCA CASP authorisation.
MiCA’s maximum transitional period ended on 1 July 2026, although Member States could shorten or decline the transition. In June 2026, ESMA called on unauthorised providers to wind down in an orderly way.
For counterparties, clients and acquisition teams, the relevant due-diligence questions are more specific than whether a firm is “regulated”:
- Is the entity currently authorised as a MiCA CASP?
- Which crypto-asset services does its authorisation cover?
- Which host Member States has it notified?
- What is the stated service start date?
- Does the proposed activity involve products excluded from MiCA?
The ESMA register requirements provide for publication of an authorised CASP’s services, intended host Member States and cross-border service start date. Register information is useful evidence, but it does not prove that every token, marketing claim or ancillary activity is compliant.
Cross-border delivery still requires a controlled operating model
MiCA passporting removes the need for repeated authorisation for the same in-scope crypto-asset service. It does not remove the need to operate that service consistently across markets.
The main risk is operational centralisation without adequate control. A governance, cyber-security, custody or AML failure at the authorised entity can affect multiple Member States at once. Outsourcing can support scale, but it does not transfer the CASP’s regulatory responsibility.
Crypto-asset transfer controls also need attention. The EBA’s Travel Rule guidelines require CASPs to identify and manage missing or incomplete information accompanying certain crypto-asset transfers.
MiCA passporting is therefore strongest when the firm has already designed its governance, controls, technology and client communications for repeatable EU-wide delivery. One authorisation can support broad market access, but only within a clearly defined and operationally sustainable perimeter.
