MiCAR Reporting Obligations for CASPs: Complete Implementation Guide

RegReportingDesk card: ESMA, European Securities and Markets Authority, European Union

Updated October 2026

Introduction

MiCAR (Markets in Crypto-Assets Regulation) establishes EU rules for CASP authorisation, prudential safeguards, operational records, market-abuse surveillance and specific reporting obligations. Major ICT-related incident reporting for CASPs within scope is governed separately by DORA, Regulation (EU) 2022/2554. Under Article 19 of DORA and Commission Delegated Regulation (EU) 2025/301, initial notification is due within four hours after classification as major and generally no later than 24 hours after awareness, subject to the late-classification rule; the intermediate report is due within 72 hours of the initial notification and the final report within one month of the intermediate or latest updated intermediate report. The Markets in Crypto-Assets Regulation (Regulation (EU) 2023/1114) represents the first unified rulebook for crypto-asset activities across the entire European Union.

Before MiCAR, crypto firms operated in a fragmented regulatory landscape where rules varied by jurisdiction. MiCAR unified this landscape: as a regulation (not a directive), it applies directly in all EU member states without requiring national transposition.

Crypto-asset services may generally be provided in the EU under Article 59(1) through CASP authorisation or the Article 60 notification route available to specified financial entities. Article 61 also provides a narrow exemption for certain third-country services initiated exclusively by the client. After authorisation, applicable obligations include Article 67 prudential safeguards, Article 68(9) record-keeping, Article 92 suspicious order and transaction reporting, Article 76 public trading transparency for platform operators, Article 22 CASP-to-issuer data provision where relevant, and DORA major ICT-incident notification for entities within its scope. These duties have different recipients, formats, triggers and deadlines.

MiCAR Article 66(5) additionally requires CASPs to make publicly available, in a prominent place on their website, information on the principal adverse impacts on the climate and other environment-related adverse impacts of the consensus mechanism used to issue each crypto-asset in relation to which they provide services. Commission Delegated Regulation (EU) 2025/422 prescribes the Table 2 indicators for those website disclosures. Further Table 3 disclosures apply where the CASP operates a trading platform or provides an exchange of crypto-assets for funds or for other crypto-assets and the yearly energy consumption reported under the mandatory energy-consumption indicator exceeds 500,000 kWh. The published information must be reviewed and updated at least annually, and updated without undue delay where material changes occur.

Related reading: MiCA CASP Wind-Down: What Unauthorised Providers Must Do as the Transitional Period Ends on 1 July 2026

The Regulatory Framework

MiCAR is Regulation (EU) 2023/1114, published in the Official Journal of the EU on 9 June 2023 and entered into force on 29 June 2023.

The regulation contains several structural elements:

  • Title II: Rules on crypto-asset offers (other than ARTs/EMTs) including white paper requirements
  • Title III: Rules on asset-referenced tokens (ARTs), covering reserve, governance, and disclosure requirements, supervised by EBA for significant ARTs
  • Title IV: Rules on e-money tokens (EMTs), which must generally be issued by authorised credit institutions or electronic money institutions (see the EMT section below for the Article 48(4) and (5) exemptions)
  • Title V: Authorization and operating conditions for CASPs
  • Title VI: Market abuse prevention for crypto-assets admitted to trading
  • Delegation to ESMA and EBA for detailed regulatory technical standards (RTS) and implementing technical standards (ITS)

Implementation Timeline

MiCAR implementation was phased, not all-at-once:

Phase 1, 30 June 2024:

  • Titles III and IV became applicable: the provisions governing asset-referenced tokens (ARTs) and e-money tokens (EMTs)
  • Issuers of ARTs and EMTs became subject to the authorization and white paper rules of those Titles. Under Article 143(4) and (5), ART issuers already issuing under applicable law could continue while their authorization (or, for credit institutions, white paper approval) was decided, provided they applied or notified before 30 July 2024
  • Reserve requirements, governance, and disclosure obligations for stablecoin issuers took effect

Phase 2, 30 December 2024:

  • Titles II, V, and VI became applicable
  • CASP authorization requirements took effect: crypto-asset services in the EU required MiCAR authorization from this date, subject to the transitional regime described below
  • White paper requirements for non-ART/non-EMT crypto-assets took effect
  • Market abuse provisions for crypto-assets became enforceable
  • The Transfer of Funds Regulation (TFR, Regulation (EU) 2023/1113) also began applying, imposing the Travel Rule on crypto transfers

Transitional provisions (grandfathering), ended 1 July 2026: MiCAR Article 143(3) allowed crypto-asset service providers that provided their services in accordance with applicable national law before 30 December 2024 to continue until 1 July 2026 or until they were granted or refused MiCAR authorization, whichever came sooner. Member States could disapply the regime or shorten it, and several did; ESMA published the periods notified to it in its list of grandfathering periods. The outer limit of 1 July 2026 has passed, so the transitional period has ended in every Member State. In Luxembourg, the CSSF confirmed in a communiqué of 2 July 2026 that the transition period for virtual asset service providers ended on 1 July 2026 and that providers without CASP authorization must wind down their EU activities in an orderly manner.

Current position: Article 59(1) allows two routes to provide crypto-asset services in the EU: authorization as a CASP under Article 63, or the Article 60 notification route open to credit institutions, central securities depositories, investment firms, market operators, electronic money institutions, UCITS management companies and alternative investment fund managers for the services that article permits. A firm that held neither when its transitional period ended can no longer rely on Article 143(3). On the wording of Article 143(3), which ran to 1 July 2026 or the authorization decision, whichever came sooner, an application still pending on that date did not extend the period.

One Article 143 deadline is still running. For crypto-assets other than ARTs and EMTs that were admitted to trading before 30 December 2024, Article 143(2)(b) gives operators of trading platforms until 31 December 2027 to ensure that a crypto-asset white paper, where MiCAR requires one, is drawn up, notified and published, and updated under Article 12.

Level 2 measures: During MiCAR’s implementation phase, ESMA and the EBA developed draft RTS and ITS specifying detailed operational requirements, including business continuity, record-keeping, complaints handling, order book records, and market abuse procedures. ESMA reports that most of these measures have entered into application following adoption by the European Commission and approval by the European Parliament and the Council, and its overview table of Level 2 and Level 3 measures tracks each one. Many of these Level 2 measures are critical to understanding the precise reporting obligations.

Who Is Affected by MiCAR Reporting Obligations

Crypto-Asset Service Providers (CASPs)

Article 3(1)(16) identifies the following ten crypto-asset services. CASP status and authorisation requirements depend on the professional provision of those services to clients, the Article 3(1)(15) definition, the Article 59 route and any applicable exclusion, including Article 2(2):

  1. Custody and administration of crypto-assets on behalf of clients
  2. Operation of a trading platform for crypto-assets
  3. Exchange of crypto-assets for funds (fiat currency)
  4. Exchange of crypto-assets for other crypto-assets
  5. Execution of orders for crypto-assets on behalf of clients
  6. Placing of crypto-assets (assisting in token distribution)
  7. Reception and transmission of orders for crypto-assets on behalf of clients
  8. Providing advice on crypto-assets
  9. Providing portfolio management of crypto-assets
  10. Providing transfer services for crypto-assets on behalf of clients

Note that staking and lending are not explicitly listed as defined CASP services under MiCAR. Whether a specific staking or lending service falls within MiCAR scope depends on how it is structured: it may fall within one of the ten defined services or outside them. Firms should confirm the classification with their competent authority.

Firms already authorized under other EU financial services frameworks (credit institutions, central securities depositories, investment firms under MiFID II, market operators, electronic money institutions, UCITS managers, AIFMs) may provide certain crypto-asset services without a separate CASP authorization, subject to the notification requirements of MiCAR Article 60, which require the notification at least 40 working days before those services are provided for the first time.

Token Issuers

Token issuers face specific obligations:

  • Crypto-asset white papers are handled under the procedure of the token category before public offering or admission to trading (Title II for crypto-assets other than ARTs and EMTs, Title III for ARTs, Title IV for EMTs); the white-paper section below sets out how the procedures differ
  • Where MiCAR requires a crypto-asset white paper, the responsible person must comply with the applicable Title II, III or IV content, notification, approval and publication rules. Since 23 December 2025, Commission Implementing Regulation (EU) 2024/2984 also requires white papers to use the relevant prescribed template and to be prepared in XHTML format with the prescribed fields marked up using Inline XBRL 1.1
  • Amendment requirements differ by token category (Articles 12 and 25 for non-ART/non-EMT crypto-assets and for ARTs, with EMTs under Article 51); see the Ongoing Disclosure section below

Asset-Referenced Tokens (ARTs) and E-Money Tokens (EMTs)

ARTs (crypto-assets other than EMTs that purport to maintain a stable value by referencing another value or right, or a combination thereof, including one or more official currencies):

  • As a general rule, an ART issuer must obtain authorisation under Article 21 or, if it is a credit institution, comply with Article 17. Article 16(2) provides exemptions from the ordinary authorisation requirement where the average outstanding value does not exceed EUR 5 million under the specified conditions, or where the ART is offered solely to qualified investors and can only be held by them. Exempt issuers remain subject to applicable white-paper requirements.
  • Reserve and ongoing public-disclosure requirements: Article 36(1) requires ART issuers to constitute and at all times maintain a reserve of assets. Article 30(1) requires the issuer to disclose on its website the amount of ARTs in circulation and the value and composition of that reserve, updated at least monthly. Under Article 36(9), an independent audit of the reserve is mandated every six months. Article 36(10) requires the results to be notified to the competent authority without delay and at the latest within six weeks of the valuation reference date, and published within two weeks of that notification, unless the competent authority instructs the issuer to delay publication on one of the grounds listed there. Article 30(2) and (3) also require publication of a summary and the full unredacted audit report, and disclosure as soon as possible of any event that has or is likely to have a significant effect on the token’s value or on the reserve.
  • MiCAR Article 22 requires issuers of ARTs with an issue value exceeding EUR 100 million to report quarterly to the competent authority; the authority may also impose that reporting below the threshold. Under Article 22(3), relevant CASPs must supply issuers with the information needed for those reports. Commission Implementing Regulation (EU) 2024/2902 specifies CASP templates S 06.00, S 07.01 to S 07.04 and S 08.00.
  • Under Article 4(2) of Implementing Regulation (EU) 2024/2902, CASPs must submit the information in the data exchange formats and representations specified by the relevant issuer. Quarterly CASP-to-issuer submissions are due on 21 April, 21 July, 21 October and 21 January; S 08.00 must be supplied daily by close of business. The issuer reports quarterly to the authority by 12 May, 11 August, 11 November and 11 February. The framework also applies, with adaptations, to EMTs denominated in a currency that is not an official currency of a Member State.
  • Under Article 2(2) and (3) of Implementing Regulation (EU) 2024/2902, the first quarterly reporting reference date is the quarter in which the ART’s issue value exceeds EUR 100 million. Where reporting is triggered by that threshold, the final reference date is the third consecutive quarter in which the issue value remains below EUR 100 million. Any competent-authority requirement to report below the threshold under MiCAR Article 22(2) must still be observed. Quarterly reporting reference dates are 31 March, 30 June, 30 September and 31 December. Weekend and public-holiday adjustments apply to the remittance dates.
  • Significant ARTs (determined by EBA based on criteria including market cap and transaction volume) face enhanced requirements and direct EBA supervision

EMTs (crypto-assets that purport to maintain a stable value by referencing the value of one official currency):

  • EMTs must generally be issued by an authorised credit institution or electronic money institution. Article 48(4) and (5) contains specific exemptions linked to Directive 2009/110/EC; the applicable exemption and surviving MiCAR requirements, including white-paper obligations, must be assessed before treating authorisation as mandatory in every case.
  • Holders must have a redemption right at par value at any time
  • Under MiCAR Article 54, where funds received by EMT issuers in exchange for EMTs are safeguarded in accordance with Article 7(1) of Directive 2009/110/EC, at least 30% of those funds must always be deposited in separate accounts with credit institutions. The remaining funds must be invested in secure, low-risk assets that qualify as highly liquid financial instruments and are denominated in the same official currency referenced by the EMT, subject to the other conditions of Article 54.
  • Where an electronic money institution issues a significant EMT, Article 58(1) subjects it to additional requirements, and under Article 117(4) EBA supervises its compliance with Articles 55 and 58. Articles 56(7) and 57(5) contain a derogation for significant EMTs denominated in a non-euro Member State’s official currency where the specified 80% concentration conditions are met; in those cases, supervision remains with the home Member State’s competent authority.

Prudential Reporting for CASPs

Own Funds Requirements

MiCAR Article 67(1) requires CASPs to have prudential safeguards in place at all times equal to at least the higher of:

(a) Permanent minimum capital, set by the Annex IV class of the services the CASP is authorized for:

  • EUR 50,000 (Class 1): CASPs authorized for execution of orders, placing, transfer services, reception and transmission of orders, advice and/or portfolio management
  • EUR 125,000 (Class 2): CASPs authorized for any Class 1 service and custody and administration, exchange of crypto-assets for funds and/or exchange of crypto-assets for other crypto-assets
  • EUR 150,000 (Class 3): CASPs authorized for any Class 2 service and operation of a trading platform for crypto-assets

(b) One quarter (25%) of the previous year’s fixed overheads, reviewed annually and calculated from the applicable accounting framework after subtracting the items listed in Article 67(3), such as profit-dependent bonuses and non-recurring expenses from non-ordinary activities. A CASP that has not been in business for one year uses the projected fixed overheads for its first 12 months submitted with its authorization application (Article 67(2)).

Under Article 67(4), the safeguards can take the form of own funds, an insurance policy or comparable guarantee, or a combination of both.

Qualifying own funds are defined by reference to the CRR (Regulation (EU) No 575/2013): Common Equity Tier 1 items and instruments under Articles 26 to 30 of the CRR, such as paid-up capital, share premium accounts, retained earnings, and other reserves, after the deductions in full under Article 36 of the CRR (including intangible assets) and without the threshold exemptions in Articles 46 and 48.

Entities providing crypto-asset services through the Article 60 notification route are outside Article 67 (Article 60(10)); their own funds requirements stay with the sectoral framework under which they are authorized.

Insurance or Comparable Guarantee

MiCAR Article 67(4)(b) lets a CASP meet the Article 67(1) requirement with an insurance policy covering the territories of the Union where it provides crypto-asset services, or with a comparable guarantee, alone or combined with own funds. Under Article 67(5), the policy must be disclosed to the public on the CASP’s website, have an initial term of not less than one year and a cancellation notice period of at least 90 days, and be taken out from an undertaking authorized to provide insurance that is a third-party entity.

Article 67(6) requires the policy to cover the risk of all of the following:

  • Loss of documents
  • Misrepresentations or misleading statements made
  • Acts, errors or omissions resulting in a breach of legal and regulatory obligations, of the obligation to act honestly, fairly and professionally towards clients, or of obligations of confidentiality
  • Failure to establish, implement and maintain appropriate procedures to prevent conflicts of interest
  • Losses arising from business disruption or system failures
  • Where applicable to the business model, gross negligence in the safeguarding of clients’ crypto-assets and funds
  • Liability of the CASP towards clients under Article 75(8)

The last item links the policy to custody: Article 75(8) makes a CASP providing custody and administration liable to its clients for the loss of crypto-assets, or of the means of access to them, resulting from an incident attributable to it, with liability capped at the market value of the lost crypto-asset at the time of the loss.

Reporting Frequency

Article 67 sets the prudential requirement but contains no mandate for ESMA or the EBA to develop a reporting template or frequency for it, so the format and frequency of any recurring reporting of prudential metrics (own funds, fixed overheads, insurance coverage) are left to the national competent authority. Luxembourg shows what that looks like. On 10 September 2026 the CSSF announced that a dedicated circular, still to be published, will introduce specific recurring reporting obligations for CASPs authorized under Article 63, filed through eDesk:

  • 1 January to 31 March 2027: test submissions only through the new eDesk module, with official reports still sent through the current channel
  • From 1 April 2027: eDesk becomes the sole official channel for the reports concerned, including reports for earlier periods whose deadline falls on or after that date
  • Frequency: the CSSF announcement describes quarterly financial and human-resources data, monthly funds-segregation data and annual shareholding, branch, agent and distributor data, without stating which of these cycles will apply to CASPs

Our guide to CSSF prudential reporting for PIs, EMIs and CASPs on eDesk covers the testing window and the switch-over rule in detail.

Transaction Record-Keeping

Scope

MiCAR Article 68(9) requires CASPs to keep records of all crypto-asset services, activities, orders, and transactions they undertake. This is primarily a record-keeping and order-keeping obligation rather than a transaction-by-transaction reporting-to-the-regulator obligation (which is distinct from, for example, MiFIR Article 26 transaction reporting).

Record design must follow the applicable detailed standards, not only Article 68(9). Commission Delegated Regulation (EU) 2025/1140 specifies records, data fields and retention requirements for CASP services, activities, orders and transactions. Trading-platform operators must additionally retain order-book data under Commission Delegated Regulation (EU) 2025/416, including the prescribed fields in electronic JSON format using the ISO 20022 methodology. Subject to the applicable service, records must include:

  • Orders received and transmitted, with all details including client identity, instrument, quantity, and timing
  • Transactions executed, including all relevant details
  • Documents setting out the CASP’s and the client’s rights and obligations for its services, as specified in Article 4 of Delegated Regulation (EU) 2025/1140

Retention period: Records must be kept for five years and, where the competent authority requests it before the five years have elapsed, for up to seven years. They must be sufficient to enable the competent authority to fulfil its supervisory tasks and take enforcement measures, and must be provided to clients on request.

Public Trading Transparency and the MiFIR Boundary

MiCAR sets public trading-transparency obligations for trading platforms, and it has no general counterpart to the MiFIR Article 26 T+1 transaction report to the NCA for every crypto-asset transaction. Under Article 76(9) and (10), CASPs operating a trading platform must make public the bid and ask prices and the depth of trading interests advertised through the platform, continuously during trading hours, together with the price, volume and time of executed transactions as close to real time as is technically possible. Commission Delegated Regulation (EU) 2025/417 requires post-trade details to be published within thirty seconds after execution, using the prescribed Annex II fields and formats.

Article 3(2) of Delegated Regulation (EU) 2025/417 also requires publication of a cancellation report carrying the ‘CANC’ flag when a previously published trade report is cancelled. Under Article 3(3), correcting a published report requires publication of the original details with the cancellation flag and a corrected report with the ‘AMND’ flag. Article 76(11) also requires the information published under Article 76(9) and (10) to be made available free of charge in a machine-readable format 15 minutes after publication, and to remain published for at least two years. Article 77(4) separately requires CASPs exchanging crypto-assets for funds or other crypto-assets to publish information about the transactions they conclude, such as transaction volumes and prices. Additional regulatory interactions include:

  • If a crypto-asset qualifies as a financial instrument under MiFID II, it falls outside MiCAR (Article 2(4)(a)), and MiFIR Article 26 transaction reporting obligations may apply to it instead
  • Competent authorities may request transaction data at any time during supervisory reviews
  • AML/CFT obligations (including the TFR Travel Rule) create separate reporting streams for certain transfers

The boundary between “pure crypto-assets” (MiCAR only) and products that qualify as financial instruments (MiFID/MiFIR) is critical. ESMA has published guidelines on the conditions and criteria for qualification of crypto-assets as financial instruments; our guide to the ESMA crypto-asset classification guidelines walks through them.

White Paper Requirements for Token Issuers

Content and Filing Process

MiCAR white-paper requirements must be assessed by token category, type of offer, responsible entity and applicable exemption. Under Title II, responsibility may fall on the offeror, the person seeking admission to trading or the trading-platform operator, rather than solely on the token issuer. Articles 4 and 5 contain exemptions and conditions for non-ART/non-EMT crypto-assets; ARTs and EMTs are governed by their respective Titles III and IV procedures. Where a white paper is required, its content is specified by Article 6(1) and Annex I of MiCAR for crypto-assets other than ARTs and EMTs, by Article 19(1) and Annex II for ARTs and by Article 51(1) and Annex III for EMTs, and Implementing Regulation (EU) 2024/2984 prescribes a separate template for each category. The principal groups of information are:

  • Issuer information: Legal entity, governance structure, management details
  • Technical specifications: Token functionality, underlying technology, consensus mechanisms
  • Rights and obligations: What the token confers on holders
  • Risk factors: Technical, market, regulatory, and operational risks
  • Economic features: Token supply, issuance mechanics, distribution plan

Filing process:

  • White-paper procedures depend on the token category. For crypto-assets other than ARTs and EMTs, Article 8(5) requires notification at least 20 working days before publication, without prior approval. For EMTs, Article 51(11) provides for white-paper notification at least 20 working days before publication, while Article 48(6) separately requires notification of the intention to offer or seek admission to trading at least 40 working days beforehand. ART white papers are subject to the distinct approval arrangements in Articles 17 and 21.
  • Prior competent-authority approval is not required for Title II crypto-asset white papers or EMT white papers. ART white papers follow a different regime: approval forms part of the Article 21 authorisation process or, for credit institutions, the Article 17 procedure. Competent authorities also have supervisory powers to require corrections to non-compliant white papers.
  • White papers must be published on the website of the legally responsible party. Under Article 9, for crypto-assets other than ARTs and EMTs, that is generally the offeror or the person seeking admission to trading, and Article 5(2) and (3) can place those requirements on the operator of the trading platform instead. ART issuers publish the approved white paper under Article 28, and EMT issuers publish under Article 51(13). The public-availability and retention rules then follow the governing provision: Articles 9(1) and 28 require the white paper to remain available on that website for as long as the crypto-asset is held by the public

Ongoing Disclosure

  • Amendment requirements differ by token category. For crypto-assets other than ARTs and EMTs, Article 12 requires amended white papers to be notified to the competent authority at least seven working days before publication. For ART issuers, Article 25 requires notification of intended material changes at least 30 working days before the change and, where applicable, prior approval of the modified white paper. EMT issuers must follow their applicable Article 51 obligations.
  • Discontinuation duties depend on the token category and legal circumstances. For ART issuers, Article 24(1) requires notification to the competent authority where the issuer expressly renounces its authorisation or decides to cease operations.

Travel Rule: Transfer of Funds Regulation

The Travel Rule for crypto-asset transfers is established in the Transfer of Funds Regulation (TFR), Regulation (EU) 2023/1113, not in MiCAR itself. The TFR was adopted alongside MiCAR as part of the same legislative package and applies from 30 December 2024.

Under the TFR, CASPs must collect and transmit originator and beneficiary information for crypto-asset transfers. Key points:

  • The TFR applies to crypto-asset transfers within Article 2, including relevant transfers involving self-hosted addresses, where the CASP of either the originator or the beneficiary has its registered office in the Union. It does not cover every transfer involving a CASP: Article 2 contains exclusions, including transfers where both the originator and the beneficiary are CASPs acting on their own behalf and qualifying transfers of electronic money tokens made with certain payment cards or devices. Transfers between two persons without a CASP are also outside its scope. For transfers within scope, Article 14 sets no minimum amount for the originator and beneficiary information that must accompany a transfer.
  • For transfers to a self-hosted (unhosted) address exceeding EUR 1,000, the originator’s CASP must take adequate measures to assess whether the address is owned or controlled by the originator (Article 14(5)). Article 16(2) places the same duty on the beneficiary’s CASP for transfers exceeding EUR 1,000 from a self-hosted address.
  • Before transferring crypto-assets, the originator’s CASP must verify the accuracy of the originator information on the basis of documents, data or information from a reliable and independent source (Article 14(6)), and may not initiate or execute the transfer before ensuring full compliance with Article 14.

Implementation challenges:

  • Crypto transfers occur across diverse platforms and blockchain networks without built-in information exchange mechanisms
  • Wallet addresses are pseudonymous; identifying beneficial owners of receiving wallets requires additional verification

AML/CFT Obligations

MiCAR operates alongside the EU’s existing AML/CFT framework. CASPs performing at least one crypto-asset service other than advice on crypto-assets are obliged entities under Directive (EU) 2015/849, as amended by Article 38 of Regulation (EU) 2023/1113. The AML/CFT requirements include:

  • Conduct customer due diligence (CDD) and know-your-customer (KYC) procedures
  • File suspicious transaction reports (STRs/SARs) with the national FIU
  • Conduct ongoing monitoring of the business relationship, including scrutiny of transactions (Article 13(1)(d) of Directive (EU) 2015/849)
  • Identify and verify beneficial ownership

These obligations exist under AML legislation (currently AMLD4/5, transitioning to the new AMLR, Regulation (EU) 2024/1624, which applies from 10 July 2027) rather than MiCAR itself, but CASPs must comply with both frameworks simultaneously.

Market Abuse Provisions

MiCAR Title VI applies to acts concerning crypto-assets admitted to trading or for which admission has been requested, including relevant activity outside trading platforms (Article 86). Article 88 requires issuers, offerors and persons seeking admission to trading to disclose inside information directly concerning them as soon as possible and to retain that information on their websites for at least five years. Disclosure may be delayed only where all Article 88(2) conditions are satisfied. Once the information is published, the competent authority must be informed of the delay; the obligation to provide a written explanation is subject to the Member State option in Article 88(3). Commission Implementing Regulation (EU) 2024/2861 specifies the technical means for public disclosure of inside information and for delaying it, including the electronic notification arrangements. Title VI also prohibits the following conduct:

  • Insider dealing: Using material non-public information about a crypto-asset to trade
  • Market manipulation: Coordinated trading, wash trading, or other practices to artificially affect prices
  • Unlawful disclosure: Disclosing inside information unlawfully, except where disclosure occurs in the normal exercise of an employment, profession or duties (Article 90)

Article 92(1) requires persons professionally arranging or executing crypto-asset transactions to maintain systems to prevent and detect market abuse. Commission Delegated Regulation (EU) 2025/885 additionally requires monitoring relevant aspects of distributed-ledger functioning, including consensus mechanisms, and prescribes the STOR template in its Annex. Where reasonable suspicion exists, reports must be submitted without delay on the STOR template in that Regulation’s Annex, using the competent authority’s specified electronic means.

The Annex to Commission Delegated Regulation (EU) 2025/885 makes all fields in Sections 1 to 4 of the STOR template mandatory. Where information cannot be provided for a particular field, the reporting person must enter ‘NA’ and briefly explain the reasons. That person must report any reasonable suspicion about an order or transaction, including a cancellation or modification, without delay to the competent authority of the Member State where it is registered or has its head office or, for a branch, where the branch is situated. Our guide to MiCAR STOR reporting for CASPs covers how these suspicious transaction and order reports are filed.

Luxembourg Specifics: CSSF as Competent Authority

Luxembourg’s CSSF supervises CASPs authorised in Luxembourg. Separately, where Luxembourg is the home Member State for a Title II crypto-asset white paper concerning a crypto-asset other than an ART or EMT, the CSSF’s communiqué of 27 July 2026 directs notification through its eDesk ‘White Paper Notification’ procedure, available since 3 August 2026. The iXBRL white paper must be compressed into a .zip file for upload, and the explanatory annex required under Article 8(4) is accepted in PDF format.

Four areas bear directly on MiCAR reporting readiness in Luxembourg:

  • Operational readiness: MiCAR Article 62(2)(j) requires the application to include the technical documentation of the ICT systems and security arrangements, together with a description in non-technical language
  • Data governance: MiCAR Article 62(2)(f) requires a description of the applicant’s governance arrangements, and Article 68(9) requires records of all crypto-asset services, activities, orders and transactions
  • AML/CFT controls: MiCAR Article 62(2)(i) requires the authorisation application to describe the applicant’s internal control mechanisms, policies and procedures to identify, assess and manage risks, including money laundering and terrorist financing risks
  • Incident management: DORA establishes ICT risk-management and major ICT-related incident reporting requirements for financial entities within its scope

Following authorisation under Article 63, CASPs must comply with the specific notification requirements applicable to the change concerned. Article 69 governs notification of changes to the management body, while Article 59(8) requires an application to extend authorisation before providing additional crypto-asset services. Other notification duties must be identified under their applicable legal or supervisory provisions.

Interaction with Other Regulatory Frameworks

MiCAR and MiFID II/MiFIR

Some crypto products may qualify as financial instruments under MiFID II. Tokenized securities, security tokens, and certain structured crypto products that qualify as financial instruments trigger MiFID/MiFIR obligations instead of MiCAR.

CASPs must classify crypto-assets correctly:

  • Pure crypto-assets (crypto-assets falling within MiCAR’s Article 2 scope that do not qualify as financial instruments or fall within another exclusion): MiCAR applies
  • Financial instruments in crypto form (tokenized securities, security tokens): MiFID/MiFIR applies; MiCAR explicitly excludes financial instruments from its scope
  • Hybrid cases may require analysis under ESMA guidelines on qualification of crypto-assets as financial instruments

MiCAR and EMIR

Where a crypto-derivative contract falls within EMIR, reporting and other obligations depend on the contract and the counterparties’ legal classification. EMIR Article 9 can apply to both financial and non-financial counterparties, subject to applicable responsibility rules and exemptions. A CASP that merely facilitates a transaction is not automatically the reporting counterparty.

MiCAR and DAC8/CARF

DAC8/CARF obligations apply to entities meeting the definition of a Reporting Crypto-Asset Service Provider under the applicable national implementation, rather than automatically to every MiCAR CASP. Luxembourg transposed DAC8 through the law of 27 March 2026. The Administration des contributions directes (ACD) states that the first information is communicated for calendar years from 1 January 2026, that reporting crypto-asset service providers established in Luxembourg report by 30 June of the year following the year to which the information relates, and that a zero-value message must be sent where there are no reportable users. The first annual deadline is therefore 30 June 2027. The obligation and the deadline derive from Luxembourg law; the ACD states that the practical data-transfer arrangements will be communicated at a later date.

See our separate article on CARF Crypto Tax Reporting. These obligations are distinct from MiCAR but overlap in terms of the customer data and transaction records that CASPs must maintain.

Frequently Asked Questions

What is MiCAR and when did it take full effect?

MiCAR (Regulation (EU) 2023/1114) is the EU’s comprehensive regulatory framework for crypto-assets. It entered into force on 29 June 2023. Stablecoin provisions (ARTs and EMTs) applied from 30 June 2024. CASP authorization, general token issuance, and market abuse provisions applied from 30 December 2024.

Can a firm still rely on the MiCAR grandfathering period?

No. The MiCAR Article 143(3) transitional period for entities that provided crypto-asset services under applicable national law before 30 December 2024 ended on 1 July 2026 at the latest, and earlier in Member States that shortened it. As a general rule, providing crypto-asset services in the EU requires CASP authorisation under Article 63 or, for the financial entities listed in Article 60, the notification route under that article. Article 61 provides a narrow exception where a client established or situated in the Union initiates a crypto-asset service from a third-country firm at its own exclusive initiative, subject to the anti-solicitation conditions in that article.

What are the own funds requirements for CASPs?

CASPs must maintain the higher of: (a) the permanent minimum capital (EUR 50,000 to EUR 150,000 depending on the Annex IV class of services), or (b) 25% of the previous year’s fixed overheads. This is specified in MiCAR Article 67, and the requirement can be met with own funds, an insurance policy or comparable guarantee, or a combination.

Does MiCAR require daily transaction reporting to regulators?

MiCAR primarily imposes record-keeping obligations (MiCAR Article 68(9)) rather than MiFIR-style daily transaction reporting to the NCA. CASPs must keep records of all services, activities, orders, and transactions for five years and make them available for supervision. A CASP operating a trading platform has a separate duty under Article 76(9) to (11) to publish pre-trade and post-trade transparency data to the public.

MiCAR Article 22 establishes a separate CASP-to-issuer reporting stream where the issuer’s Article 22 reporting obligation applies. This generally concerns ARTs with an issue value exceeding EUR 100 million, or cases where the competent authority requires reporting below that threshold, and it extends, with adaptations, to EMTs denominated in a currency that is not an official currency of a Member State. Relevant CASPs provide daily S 08.00 and quarterly S 06/S 07 information under Implementing Regulation (EU) 2024/2902, and those submissions go to issuers, not directly to the competent authority.

Separate obligations under the TFR (Travel Rule), AML/CFT and, for crypto-assets that qualify as financial instruments, MiFIR create additional reporting streams.

Where is the Travel Rule for crypto transfers?

The Travel Rule is in the Transfer of Funds Regulation (TFR, Regulation (EU) 2023/1113), not in MiCAR. The TFR requires originator and beneficiary information for crypto-asset transfers within its Article 2 scope, without a general de minimis threshold. The Article 2 exclusions continue to apply, and a transfer above EUR 1,000 to or from a self-hosted address triggers a separate ownership-or-control assessment under Articles 14(5) and 16(2).

Are staking and lending regulated under MiCAR?

Staking and lending are not explicitly listed among the ten defined CASP services in MiCAR Article 3(1)(16). Whether a specific staking or lending service falls under MiCAR depends on how it is structured: it may fall within one of those ten services or outside them. The classification should be confirmed with the competent authority.

Key Takeaways

  • MiCAR has applied in full since 30 December 2024, with stablecoin provisions in effect since 30 June 2024. The Article 143(3) grandfathering period for existing providers ended on 1 July 2026 at the latest, earlier where a Member State shortened it.
  • Authorisation or a qualifying notification is generally required, subject to the limited Article 61 exception. CASPs must be authorized for each service type they offer. The financial entities listed in Article 60 may notify their competent authority instead of seeking separate CASP authorization.
  • Prudential safeguards are the higher of permanent minimum capital (EUR 50,000 to EUR 150,000 by Annex IV class) or one quarter of the preceding year’s fixed overheads, held as CET1 own funds, insurance or a combination. Check the exact calculation under MiCAR Article 67.
  • The core MiCAR duty is record-keeping rather than a general transaction report to the NCA, but trading platforms publish transparency data. MiCAR requires five-year record retention and provision to the competent authority on request, subject to the detailed standards in Delegated Regulations (EU) 2025/1140 and 2025/416. Article 76 transparency data goes to the public, within thirty seconds of execution for post-trade details. Article 22 CASP-to-issuer reporting for ART-related services, extended with adaptations to EMTs denominated in a currency that is not an official currency of a Member State (daily S 08.00, quarterly S 06 and S 07 templates), is a separate stream, as are the TFR, AML/CFT and potentially MiFIR.
  • The Travel Rule sits in the TFR (Regulation (EU) 2023/1113). The TFR imposes originator and beneficiary information requirements for crypto-asset transfers within its Article 2 scope, without a general de minimis threshold. Article 2 exclusions still apply, and the additional ownership-or-control assessment for certain self-hosted-address transfers exceeding EUR 1,000 is a separate requirement.
  • Market abuse rules cover crypto-assets admitted to trading or subject to an admission request, on or off a platform. Anyone professionally arranging or executing crypto-asset transactions must have detection systems and report reasonable suspicions to the competent authority without delay (Article 92).
  • Classification of crypto-assets matters. Products that qualify as financial instruments under MiFID II fall outside MiCAR and under MiFID/MiFIR instead. Misclassification creates compliance gaps.
  • Level 2 measures (RTS/ITS) specify detailed operational requirements. Record-keeping content, order book records, the white-paper format and the suspicious order and transaction report template are specified in Commission Delegated and Implementing Regulations (EU) 2025/1140, 2025/416, 2024/2984 and 2025/885; trading-platform transparency data sits in 2025/417 and the consensus-mechanism sustainability indicators in 2025/422; CASP prudential reporting runs through national channels, such as the CSSF’s eDesk reporting from 1 April 2027.

Sources and References

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts

  • CARF Reporting in Luxembourg: DAC8 Crypto Filing by 30 June

    Report Library › Tax ReportingCARF reporting in Luxembourg starts with the data a crypto-asset platform is already generating in 2026. The Law of 27 March 2026 (Mémorial A No. 144), which transposes Directive (EU) 2023/2226 (DAC8) and brings the OECD Crypto-Asset Reporting Framework into Luxembourg tax law, makes the calendar year 2026 the first reporting…

  • CARF: The New Global Tax Reporting Framework for Crypto

    Report Library › Tax ReportingIntroduction The Crypto-Asset Reporting Framework (CARF) represents a fundamental shift in how crypto-asset transactions are reported across borders for tax purposes. Developed by the OECD and endorsed by the G20, CARF establishes a common standard for automatic exchange of information about crypto-asset transactions – similar in scope to the Common Reporting…