Verified market examples and practical lessons for applicants

Successful Cases of MiCA and CASP Licensing in the EU

Published Updated

Successful MiCA licensing cases show how crypto businesses can enter the European market through a defined regulatory framework. The useful evidence is the permission granted to a named legal entity, the services it covers and its current status. This article examines public regulatory records and explains what applicants can learn from them, from service classification and capital planning to cross-border notifications and ongoing supervision.

  • A submitted application is not a MiCA authorisation.
  • Permissions belong to legal entities and cover specified services.
  • Article 60 notification and Article 63 authorisation are different routes.

3 essential points

  • Verify the legal entity behind the brand. A group may hold several financial permissions through different companies. A MiCA entry for one European entity does not cover every group website, product or offshore operation.
  • Plan for the rules now in force. The maximum EU grandfathering period ended on 1 July 2026. Historic VASP registration or a pending application no longer provides a general transitional right to continue services within MiCA’s scope.
  • Treat authorisation as the start of supervised operations. Cross-border expansion requires the applicable notification process, while capital, governance, client protection and operational resilience must remain effective after approval. A licence does not guarantee banking access or investment performance.

4 key figures shaping EU crypto services

  • 27 EU Member States
  • 10 Crypto-asset service categories defined by MiCA
  • 3 Capital classes in Annex IV
  • €150,000 Permanent minimum for a Class 3 trading-platform operator

Verified examples of MiCA market access

The cases below are public market examples, not a list of RUE client engagements. Regulatory registers establish permissions; they do not identify every adviser involved in an application. The dates below reproduce the authorisation or notification date field in ESMA’s CASP register downloaded on 18 November 2026. None of these selected records contained an authorisation end date in that snapshot.

Entity and market Home authority Date in ESMA register Recorded scope in brief
Payward Europe Solutions Limited
Ireland
Kraken brand
Central Bank of Ireland 25 June 2025 Custody, exchange, execution, placing, order transmission, portfolio management and transfers
Bitvavo B.V.
Netherlands
AFM 26 June 2025 Custody, operation of a trading platform and transfers
OKX Europe Limited
Malta
MFSA 27 January 2025 Trading platform, custody, exchange and additional listed services
Coinbase Luxembourg S.A.
Luxembourg
CSSF 20 June 2025 Custody, exchange, execution, placing, order transmission and transfers
Traders Place GmbH & Co. KGaA
Germany
BaFin 21 July 2025 Reception and transmission of orders under Article 60 notification

Regulatory reference: ESMA register of crypto asset service providers

Read the service scope as carefully as the brand name

The table deliberately distinguishes a trading-platform permission from exchange or order-execution services. Those activities can support different commercial models. For example, Bitvavo’s entry expressly includes operation of a trading platform. The selected Payward and Coinbase entities have other listed permissions; the presence of a familiar exchange brand does not justify adding a trading-platform permission that is absent from the specific record.

Check dates in their original context

A company announcement, home-state authorisation and host-state passport record can carry different dates. Bitvavo’s ESMA record gives 26 June 2025, while its French passport entry identifies 14 July 2025 as the intended start of services in France. These dates describe different events and should not be presented as contradictory licence decisions.

Regulatory reference: AMF record explaining the Bitvavo passport date

For a live transaction or partnership, repeat the register check and examine restrictions, service extensions and any withdrawal information. Public registers can be updated after the underlying decision, so material uncertainties should be resolved with the competent authority or the formal decision itself.

What the successful cases demonstrate

Kraken and Coinbase show why the contracting entity matters

The AMF confirms that Payward Europe Solutions Limited holds Irish MiCA permission and that Coinbase Luxembourg S.A. holds Luxembourg MiCA permission, with cross-border provision of services in France. These are permissions for the named European companies. They are not blanket approvals for all entities using the Kraken or Coinbase brands.

For an applicant, the practical lesson is to align the proposed licence holder with the customer agreement, custody arrangements, order flows and revenue model. If another group entity performs a material part of the service, its role must be assessed and documented. Customers and commercial partners should be able to identify which entity is responsible for each regulated activity.

Regulatory records: AMF Payward Europe Solutions | AMF Coinbase Luxembourg

Bitvavo and OKX illustrate different service combinations

Bitvavo B.V. and OKX Europe Limited both have trading-platform activity recorded in ESMA’s register, but their overall service lists differ. The commercial term “exchange” does not settle which MiCA permissions a business needs. A platform matching third-party interests, a dealer exchanging against its own capital and an intermediary transmitting orders must each be analysed against the statutory definitions.

The lesson is to design an activity map before preparing the application. Map the customer journey, assets and money flows to each service requested. A broader service list can create additional operational responsibilities; it should reflect a real, funded business plan rather than a wish to advertise every possible activity.

Regulatory reference: MiCA service definitions

Traders Place illustrates the Article 60 route

ESMA records Traders Place GmbH & Co. KGaA under Article 60 notification for reception and transmission of orders. It should therefore not be described as an Article 63 CASP authorisation. Article 60 allows certain already regulated financial entities to provide specified crypto-asset services, subject to their eligibility, existing permissions and the notification requirements.

This route is not available merely because a company has a payment account, an old VASP registration or a financial-services business description. The relevant financial-entity category and service equivalence must be established. Where the intended services exceed the available Article 60 route, the need for an Article 63 authorisation must be assessed.

Regulatory reference: Article 60 for existing financial entities

The transition has ended and approval must be evidenced

The CASP regime became applicable on 30 December 2024, subject to national transitional arrangements for qualifying existing providers. The maximum grandfathering period ended on 1 July 2026. As of this article’s update, it is no longer appropriate to describe that deadline as a future opportunity to continue under an old national registration.

An application acknowledgement, completeness assessment and substantive authorisation are different milestones. A pending application does not extend the expired EU grandfathering period. Businesses must establish a current lawful basis for each regulated service, including an applicable Article 60 route where relevant, before continuing operations.

Regulatory reference: ESMA statement on the end of transitional periods

The Czech Republic provides a clear practical example

On 11 February 2026, the Czech National Bank announced its first six MiCA authorisations and reported receiving 248 applications. The announcement distinguishes applications from granted permissions and explains that the CNB assesses the provider’s governance, controls, risks and capital. It does not certify a crypto investment as safe.

The CNB has been the Czech CASP licensing authority since 15 February 2025. A trade licence or registration with a Trade Licensing Office is not MiCA authorisation. The February 2026 announcement is a historical milestone, not a statement of the current number of authorised Czech providers.

Regulatory reference: CNB announcement of its first six authorisations

How to document a successful licensing case

Claim Evidence needed
The application was submitted Submission record and acknowledgement identifying the applicant and authority
The application was complete The authority’s completeness communication
The company was authorised Formal decision and register record with entity, date and service scope
The firm can serve another Member State Applicable cross-border notification evidence and the relevant service scope
An adviser delivered the project Engagement evidence and permission to publish the client relationship

This approach prevents application volumes from being presented as licence totals. It also keeps a firm’s own project history distinct from publicly documented industry examples. Confidential projects can be described anonymously only where the underlying facts remain accurate and the client’s confidentiality is respected.

Capital planning starts with the service model

MiCA groups CASPs into three capital classes. The applicable permanent minimum follows the services provided, while the overall prudential requirement can be higher because of the fixed-overhead calculation. These figures are safeguards for the operating business, not licence fees or a complete launch budget.

Class Services determining the class Permanent minimum
Class 1 Execution, placing, transfer services, reception and transmission of orders, advice and portfolio management €50,000
Class 2 Custody and administration, exchange for funds or exchange for other crypto-assets; may also include Class 1 services €125,000
Class 3 Operation of a trading platform; may also include services from the lower classes €150,000

Regulatory reference: MiCA Annex IV capital classes

The overhead test can be more important than the minimum

Under Article 67, prudential safeguards must cover at least the higher of the permanent minimum and one quarter of the preceding year’s fixed overheads. A new provider uses the relevant projections for its first 12 months. For example, a Class 3 firm with qualifying annual fixed overheads of €1.2 million would calculate an overhead-based requirement of €300,000, exceeding the €150,000 class minimum.

Safeguards may take the form of qualifying own funds, eligible insurance or a comparable guarantee, or a combination, subject to Article 67. Insurance is not a shortcut around its coverage conditions or around having sufficient resources to operate. The business also needs a funding plan for staff, technology, compliance and an orderly wind-down.

Regulatory reference: Article 67 prudential safeguards

Avoid licensing a business that the budget cannot support

An application should reconcile the services requested with the organisation and financial forecasts. A custody business needs a credible safeguarding and key-management model. A trading-platform operator needs rules and systems appropriate to that activity. A firm applying for advice or portfolio management must show how those services will be delivered and controlled.

For commercial planning, separate regulatory safeguards from application costs and working capital. Stress-test the effect of lower customer volumes, higher compliance costs, supplier replacement and delayed banking access. Client assets should not be treated as a source of finance for the provider’s own operations.

Building an application that can be assessed

The public cases demonstrate that authorisation is achievable through different home authorities and operating models. They do not reveal the complete confidential application files or prove that a particular adviser, document template or jurisdiction guarantees approval. The applicant must substantiate its own business.

Application area Evidence to prepare
Programme of operations Services, target clients, distribution channels and the role of each group entity
Ownership and management Ownership chain, qualifying holders, management suitability and allocation of responsibilities
Prudential resources Safeguards calculation, funding evidence and coherent financial projections
Risk and financial crime controls Business risk assessment, customer checks, monitoring, escalation and reporting processes
Technology and continuity System architecture, security measures, recovery arrangements and supplier dependencies
Client protection Safeguarding, complaints, conflicts management and service-specific procedures

Regulatory reference: Article 62 application requirements

A white paper is not a universal CASP application requirement

Token white-paper obligations and CASP authorisation address different regulatory questions. A service provider does not automatically need to issue its own token or produce an issuer white paper merely to obtain a CASP authorisation. If the project also offers tokens or seeks their admission to trading, those activities require a separate analysis. Publication of a Title II white paper in ESMA’s register does not mean that a regulator has approved the token or its investment merits.

Regulatory reference: ESMA explanation of MiCA registers and white papers

Understand the statutory clock

Article 63 provides for an initial completeness review within 25 working days and a substantive assessment within 40 working days after receipt of a complete application. An eligible request for further information can suspend the substantive assessment for up to 20 working days. These periods are not a guaranteed end-to-end launch timetable: preparation and remediation of an incomplete application happen outside that simple calculation.

Regulatory reference: Article 63 assessment procedure

A practical submission process should keep the business plan, policies, contracts and system descriptions consistent. Assign an owner to each regulatory question and maintain a controlled record of responses. If the business model changes during review, assess the effect across the application rather than correcting only the document mentioned in the regulator’s request.

Passporting and compliance after authorisation

Cross border access requires a defined notification

An authorised CASP intending to serve other Member States must provide the home authority with the information required by Article 65, including target states, services and intended start date. The authority communicates the notification to the relevant host authorities, ESMA and EBA. Service provision may begin following the specified communication or, at the latest, on the fifteenth calendar day after submission of the required information.

Passporting concerns the covered crypto-asset services. It does not automatically authorise unrelated payment services, investment services or token issuance. The EU has 27 Member States; the EEA additionally includes Iceland, Liechtenstein and Norway. EEA expansion should be checked against the applicable framework and the provider’s actual permissions and notifications.

Regulatory reference: Article 65 cross border services

Operational resilience and outsourcing remain management duties

DORA applies to MiCA-authorised CASPs and brings requirements concerning ICT risk, incident handling, testing and third-party dependencies. A provider should be able to demonstrate how critical systems are controlled and how services would continue or be restored following disruption. Policies must reflect the systems actually used.

Regulatory reference: ESMA clarification of DORA applicability

Outsourcing technology, custody functions or compliance support does not remove the CASP’s responsibility for the outsourced activity. Article 73 requires effective oversight, retained expertise and arrangements that do not obstruct supervision. Contracts should address access to information, cooperation with the authority, service continuity and exit arrangements.

Regulatory reference: Article 73 outsourcing

Payments and crypto transfers need separate attention

Certain services involving electronic money tokens can also fall within payment-services regulation. The EBA’s February 2026 opinion addressed the end of its PSD2 and MiCA no-action transition on 2 March 2026 and set conditions for supervisory treatment of pending applicants. A CASP licence alone should not be presented as permission to provide every payment service involving stablecoins.

Regulatory reference: EBA opinion on the PSD2 and MiCA transition

Crypto transfers also require operational arrangements for applicable originator and beneficiary information under the Transfer of Funds Regulation and the EBA’s Travel Rule Guidelines. Customer onboarding, transfer monitoring and handling missing information should work together. Installing a screening tool is only one part of implementing those obligations.

Regulatory reference: EBA Travel Rule Guidelines

Frequently asked questions about successful MiCA cases

Does every register entry represent a new CASP licence

No. The register includes providers operating through different legal routes, including Article 60 notifications by eligible financial entities. Read the legal basis and authorised services before comparing firms or counting licence holders. A register entry should also be checked for an end date or other relevant status information.

Does MiCA approval cover every service offered by a group

No. The permission concerns the named entity and its authorised activities. Group companies, derivatives, payment services and token issuance may require separate assessments. A customer’s agreement should identify the entity actually providing the service.

Can an old VASP registration be upgraded automatically

No. A national registration is not itself MiCA authorisation. The maximum EU grandfathering deadline has passed, and a provider needs a valid legal basis under the current framework. Historic operating experience can inform an application but does not remove the applicable requirements.

Does a licence guarantee access to banking

No. Banks and payment providers conduct their own onboarding and risk assessments. MiCA status is relevant evidence, but it does not compel a bank to accept the business or remove questions about ownership, source of funds, customer geography and transaction flows.

Can a public case establish why an application succeeded

Only to a limited extent. A public record can establish the entity, authority, date and service scope. It normally does not disclose the full assessment, all remediation work or the advisers involved. Lessons drawn from a case should therefore be distinguished from facts about the confidential application process.

How Regulated United Europe supports MiCA projects

Regulated United Europe OÜ can assist businesses with planning and preparing MiCA authorisation projects. The work begins with the proposed services, ownership structure, customer markets and operational arrangements. This allows the licensing route and home-state strategy to be assessed against the actual business model.

Support can include a regulatory gap analysis, preparation of application documentation, coordination of governance and AML/CFT procedures, prudential planning and assistance with responses to the competent authority. Technology, safeguarding and outsourcing arrangements should be addressed alongside the legal documentation so that the application describes an operation capable of meeting its obligations.

After authorisation, RUE can assist with cross-border notifications, changes to the business model and ongoing compliance arrangements. Where a project requires specialist technical work or locally reserved professional services, the appropriate professionals should be involved. Authorisation decisions remain with the competent authority, and the regulated company retains responsibility for its business.

For an initial project assessment, prepare a concise description of the services you intend to offer, target customers, ownership, current registrations, technology providers and available resources. These details establish the scope of the work and provide a sound basis for assessing the route from application to supervised operations.

Related RUE services: MiCA licence assistance and white label crypto solutions.

Prepare an EU MiCA CASP application

Map proposed services, capital, governance and operational substance before committing to an authorisation project.