Blogpost

Accessing the EU Crypto Market Without a MiCA License: How non-EU firms can operate in Europe and where the regulatory perimeter is drawn.

More and more crypto-asset businesses from the Middle East, the United Kingdom, and other third countries are looking to operate in Europe without going through the lengthy process of obtaining their own MiCA license. White-label structures make that possible. But they only work if one question is answered from the outset: Who sits where in the regulatory perimeter?

92
7 minutes reading time
EU crypto market, MiCA licence & FinTechs

Picture this: you have a functioning business model, an established client base, a clean compliance track record and still no access to the EU market, because the one license you need takes eighteen months to obtain. So, you approach a European CASP: Can we operate through your license in the EU?

This is not hypothetical. We encounter it regularly in practice with increasing frequency, particularly among companies from the UAE and other third-country jurisdictions looking to access the EU market without entering a full licensing process.

The short answer: yes, but not in the way most people assume.

The longer answer is what this article is about.

"Branding is not regulatory responsibility. Those who confuse the two find themselves outside the perimeter and realize it too late."

What MiCA Permits ─ and What It Does Not

Under MiCA, only an authorized Crypto-Asset Service Provider (CASP) may provide regulated crypto-asset services in the EU. Regulatory responsibility cannot be delegated. Outsourcing is permitted, but accountability remains with the CASP.

That said, MiCA does not prohibit distribution arrangements or white-label structures. Introducer and distribution models are explicitly permitted. And it is permissible for a non-licensed entity to operate under its own brand, provided it is unambiguously clear that regulated services are provided by the CASP, not the distributor.

Branding is not regulatory responsibility. This is the conceptual foundation of every white-label structure under MiCA and simultaneously the point at which most structuring errors occur.

The critical question is therefore not: Are we allowed to do this? It is: Who sits where in the regulatory perimeter and can the supervisory authority verify that at any point in time?

The Two Foundational Models

White-label structures under MiCA reduce to two fundamental approaches. Both are regulatorily viable. Both carry their own risk profile.

Model 1 ─ Your Brand, Their Regulated Infrastructure

The non-licensed entity, referred to here as the NLE, faces EU clients under its own brand. It operates its own website, its own application, its own client relationship. The CASP is the regulated backbone: it delivers all regulated services, holds client contracts, conducts AML monitoring, and files regulatory reports.

What the NLE may do: operate its own brand, define its own sales strategy, set its own pricing within agreed parameters, manage its own CRM, acquire its own clients, and run first-line customer support.

What the NLE may not do: touch client assets, make KYC decisions, conduct AML monitoring, file regulatory reports, or hold itself out as a regulated provider to clients.

The client contract for regulated services always runs between the client and the CASP, even if the client sees the NLE’s brand. This is standard practice in financial services white-labeling and is well established under regulatory frameworks. The NLE’s website must visibly state: Regulated crypto-asset services are provided by [CASP], authorized by [Regulator] under MiCA.

Omitting that disclosure, even in a single language version of the website, constitutes a perimeter breach. Supervisory authorities do not wait for external complaints. They look for themselves.

Regulatory perimeter question: Is it documented in writing, for every regulated touchpoint, including KYC decisions, asset custody, transaction monitoring, and regulatory reporting, that responsibility sits with the CASP and not the NLE?

Model 2 ─ Their Brand, Your Operational Engine

Here, the CASP operates under its own brand. The NLE works behind the scenes: as a technology partner, a business development arm, and an operational driver for client servicing, product development, and market expansion. The client sees the CASP, but the NLE powers the business.

In this model, the NLE can take on substantial operational responsibilities: technical integration, wallet UX, analytics, payment orchestration, first-line AML support, onboarding documentation, institutional relationship management, and go-to-market strategy. It can effectively run a dedicated business unit within the CASP.

What it still may not do: bear regulatory responsibility. The CASP remains accountable in every respect to clients, to supervisory authorities, and under the law.

Where this breaks down: when the NLE begins making independent AML decisions — even informally, even “provisionally.” Or when it starts coordinating client funds without clean contractual and operational separation. In such cases, the supervisory authority will argue that the NLE is de facto conducting regulated activities regardless of what the contract says. The CASP’s license is then at risk. In the scenarios we have seen, that risk materialized not through a formal investigation, but through a partner due diligence process that the CASP could not pass because its own house was not in order.

Regulatory perimeter question: Is the NLE’s operational scope documented in sufficient detail that no supervisory authority could reasonably conclude it is conducting regulated activities?

Three Structural Variants Within Model 1

Within the branded NLE model, three practical structural options exist, each suited to different objectives, resources, and risk appetites:

Option A ─ EU Subsidiary as Tied Agent: The NLE establishes an EU subsidiary that is registered as a tied agent or appointed representative under the CASP’s umbrella. This creates a clear EU legal entity, increases regulatory acceptance, and makes the supervisory structure transparent to the relevant authority. Effort: moderate. Regulatory certainty: high.

Option B ─ Joint Venture as an Independent CASP: The CASP and NLE jointly establish an EU entity that applies for its own CASP authorization. This is the cleanest, and most time-intensive, path. Suitable where the NLE seeks full regulatory independence in the EU over the long term. Effort: high. Regulatory certainty: maximum.

Option C ─ Functional Separation: The NLE provides exclusively non-regulated services (e.g., technology infrastructure, wallet UX, analytics, payment orchestration) while the CASP provides the regulated wrapper. No new legal entity required. Well-suited for technology-driven NLEs with a clear product focus. Effort: low. Regulatory certainty: entirely dependent on the precision of activity delineation.

Comparing the Risk Profiles

Both foundational models are regulatorily defensible, but they differ on a dimension that is frequently underestimated in practice: the supervisory authority’s comfort level.

In Model 1 ─ the NLE operating under its own brand: the regulatory optics are more complex. The client sees a brand that holds no license. That is legal, but it requires explanation. EU supervisory authorities will scrutinize whether the actual structure reflects the documented one — whether the NLE is genuinely only distributing, or whether it is de facto providing regulated services.

In Model 2 ─ the NLE operating under the CASP’s brand: the external presentation is cleaner. The client sees the CASP. Regulatory defensibility is higher, supervisory risk lower. The tradeoff is reduced commercial independence for the NLE.

The choice between the two models is ultimately strategic: brand autonomy versus regulatory simplicity. Both are achievable. But only one can be justified without a sophisticated structural framework.

Partner Due Diligence: The Real Entry Point

For third-country companies looking to enter a white-label arrangement, the reality is often sobering: the CASP does not say no to the business model. It says no to the documentation.

The CASP bears liability. If the NLE conducts activities that are attributable to the CASP under regulatory principles, the CASP faces the consequences before the supervisory authority, up to and including license revocation. That means the CASP will need to fully understand who the NLE is: complete corporate and ownership structure, AML policies, client profile, transaction volumes, compliance history, and sanctions status of all beneficial owners.

Arriving with a pitch deck means losing the partner, not because of the business case, but because of the preparation. Arriving with complete partner documentation compresses the onboarding process from months to weeks. That is not a convenience. It is the difference between EU market entry in Q1 or Q3.

What This Means for Non-EU Companies in Practice

The EU market is open, but it is not unconditionally accessible. White-label structures under MiCA offer a legitimate, regulatorily sound path for third-country companies to operate in Europe. But they work only if three conditions are met.

First, the regulatory perimeter must be clearly drawn from the outset in writing, operationally, and documented in a manner that allows any supervisory authority to determine at any point in time who does what.

Second, the structure must fit the business model. Those seeking maximum brand autonomy choose Model 1 and accept the higher regulatory complexity that comes with it. Those seeking operational influence without market-facing presence choose Model 2.

Third, the NLE must pass the CASP’s partner due diligence. This is not a formality, it is the actual key to the EU market.

The structure is solvable. The question is whether you are prepared when the CASP starts asking questions.

We structure white-label arrangements under MiCA, for CASPs looking to establish partnerships on sound regulatory footing, and for third-country companies preparing EU market entry without their own license. This includes perimeter definition, partner documentation, and supervisory preparation across the EU and EEA.

If you want to know which model you can operate under and what it takes to get there: reach out now. Not after the first CASP has already declined.

Contact us

msg for banking supports FinTechs in preparing for bank and partner onboarding—from documentation to communication with the bank.

Emanuel Gedeon

Emanuel Gedeon

has extensive experience in compliance, regulatory consulting, and the optimisation of control processes for financial institutions. As an Executive Partner at msg for banking, he's leading the Governance & Regulatory Advisory division. Previously, he held senior positions at international consulting firms.

Write a comment

You must login to post a comment.