> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/eu-level/soft-law/statement-on-mica-data-standards-format-requirements.md). # ESMA Statement — MiCA Data Standards and Format Requirements | | | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Authority** | ESMA | | **Legal basis** | [Articles 109](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-109.md) and [110](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-110.md) MiCA | | **Status** | In force | | **Source** | [ESMA](https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica) | ## Overview This ESMA statement provides practical guidance on the data formats required to comply with MiCA reporting and register obligations. It covers iXBRL formatting for crypto-asset white papers and a standardised JSON schema for order book records and trade data submitted by trading-platform operators. ## Key points * Specifies iXBRL as the required format for crypto-asset white papers submitted to ESMA's register under [Article 109](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-109.md) MiCA. * Provides a standardised machine-readable JSON schema for order book records and trade data under [Article 110](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-110.md) MiCA. * Defines a uniform structure for transaction metadata to support consistent reporting across CASPs. * Targets CASPs operating trading platforms and entities submitting or maintaining white papers. * Supports seamless data exchange between CASPs, NCAs and ESMA. * Reflects ESMA's role in maintaining the EU registers of white papers and authorised CASPs. ## Relevant MiCA articles * [Article 109](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-109.md) — ESMA register of crypto-asset white papers * [Article 110](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-110.md) — ESMA register of CASPs ## Full document Available on the [ESMA MiCA page](https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica). ## Statement ## to support the smooth implementation of MiCA data standards and format requirements MiCA technical format for the white paper and for the order book records to be kept by crypto-asset service providers operating a trading platform for crypto-assets and the data standards requirements applicable to all crypto-assets service providers and preparers of white papers | Obligation | Order-book records | Transparency | Records of orders transactions | & White papers | | ------------------ | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | | Entities concerned | To be maintained by: Crypto asset service providers operating trading platforms | To be published by: Crypto asset service providers operating trading platforms | To be maintained by: Crypto asset service providers operating trading platforms Crypto asset service providers providing any other service that would trigger the placement of orders or execution of transactions | To be published by: Issuers Offerors Persons seeking admission to trading Crypto asset service providers operating trading platforms | | Entry into force | 3 April 2025 | 3 April 2025 | 30 June 2025 | 23 December 2024 | | ------------------------ | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Application date | RTS apply as of entry into force | RTS apply as of entry into force | RTS apply as of entry into force | 23 December 2025 | | Technical specifications | JSON schema available at this link as of 28 November 2025 . 6 months lead time granted from the time of publication. | NA (Legal Entity Identifier 1 and Digital Token Identifier 2 requirements are already applicable ) 3 | Standardised ISO 20022 messages to facilitate compliance with Articles 6(2- 3) and 7(2) of the RTS. The messages are available at this link as of 28 November 2025. | XBRL taxonomy available as of 5 august 2025 A show case to generate an iXBRL white paper available at this link as of 8 October 2025. | ## Scope and purpose ESMA is issuing this public statement in relation to the technical specifications concerning the implementation of the following MiCA data standards and formats requirements: * The format of order book records for crypto-asset service providers (CASPs) operating a trading platform for crypto-assets as defined by the Commission Delegated [Regulation (EU) 2025/416](/eu-level/technical-standards/rts/regulatory-technical-standards-content-format-order-book-records-trading-platforms-crypto-assets.md), supplementing regulation (EU) 2023/ 1114 on Market in Crypto-Assets (MiCA), hereafter referred to as 'the order -book RTS'. * The data standards requirements for all CASPs as defined by the Commission Delegated [Regulation (EU) 2025/1140](/eu-level/technical-standards/rts/regulatory-technical-standards-records-crypto-asset-services-activities-orders-transactions.md) specifying records to be kept of all cryptoasset services, activities, orders and transactions undertaken, hereafter referred as 'the record -keeping RTS' * The manner in which CASPs operating a trading platform for crypto-assets are to present transparency data as defined by the Commission Delegated [Regulation (EU) 2025/417](/eu-level/technical-standards/rts/regulatory-technical-standards-presentation-transparency-data-trading-platforms-crypto-assets.md) of 28 November 2024 , hereafter referred to as ' the transparency RTS ' . * The format and data standards requirements for the MiCA white papers as defined by the Commission Implementing [Regulation (EU) 2024/2984](/eu-level/technical-standards/its/implementing-technical-standards-forms-formats-templates-crypto-asset-white-papers.md) of 29 November 2024 with regard to forms, formats and templates for the crypto-asset white papers, hereafter referred to as 'the white papers ITS'. * The data necessary for the classification of crypto-asset white papers as defined by the Commission Delegated [Regulation (EU) 2025/421](/eu-level/technical-standards/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable.md) of 16 December 2024 specifying the data necessary for the classification of crypto-asset white papers and the practical arrangements to ensure that such data is machine-readable, hereafter referred to as ' the white papers classification RTS '. The above-mentioned requirements are essential to ensure transparency, facilitate market surveillance and allow for the comparability of information across crypto-asset market participants. This public statement aims at providing further practical guidance to market participants. ## Legal background According to Article 1(2) of the order-book RTS, CASPs should keep records of relevant data relating to all orders (order book records) in JSON format, in accordance with the ISO 20022 methodology. According to recital (2) of the record-keeping RTS, competent authorities should be able to perform the same analysis on all record datasets, regardless of which crypto-asset service provider produced the record. In line with this principle, Articles 6(2)-(3) and 7(2) of the record-keeping RTS define how the information to be record kept by CASPs should be provided to the national competent authorities. According to recital (3) of the record keeping RTS, consistent and comparable records on services, activities, orders and transactions are essential in order for competent authorities to fulfil their supervisory tasks. It follows, therefore, that the data records required in accordance with the recordkeeping RTS should respect the same standards as defined in the order book RTS to ensure consistency between both In accordance with Article 2 of the white papers ITS, persons drawing up a crypto-asset white paper should prepare them in XHTML format marking the fields set out in the Annex to the ITS using Inline XBRL 1.1 specifications of the eXtensible Business Reporting Language (XBRL). The above-mentioned technical schemas have been prepared in line with the templates defined in the Annexes to the respective technical standards and, amongst others, include the below data standards requirements: * According to Article 14 of the record-keeping RTS, in the absence of any alternative identifier defined at Union level, all CASPs should identify clients that are legal entities with a legal entity identifier codes that comply with the ISO 17442 standard and are included in the Global LEI database maintained by the Central Operating Unit appointed by the Legal Entity Identifier Regulatory Oversight Committee. * According to Article 15 of the record-keeping RTS and Article 3 of the white paper classification RTS, in the absence of any alternative identifier defined at Union level, all CASPs and any other preparer of crypto-asset white papers should identify the crypto-asset by using a digital token identifier that is compliant with the ISO 24165 standard at the level of granularity specified in the relevant technical standards. ## Technical specifications The RTS concerning order book records entered into force on the 3 rd of April 2025. The JSON schema have been developed by ESMA based on ISO 20022 methodology. Considering the need to ensure an orderly transition to the new standards and format of order book records, NCAs expect to start requesting data in the new JSON file format within 6 months after its official publication on ESMA website at this link. Moreover, to facilitate compliance with Article 6(2)-(3) and 7(2) of the record keeping RTS and to ensure consistency with the order-book RTS, ESMA is making available the related standardised messages based on ISO 20022 methodology at this link. The ITS concerning the form, format and templates to be used for the Crypto-Asset white papers will apply as of 23 rd December 2025. The XBRL taxonomy to be used to comply with these requirements have already been published on ESMA website on 5 th August 2025. To show case generation of an iXBRL white paper, ESMA is also making available an Excelbased example. The example is available on ESMA website at this link. Its use is voluntary and ESMA will not accept any liability concerning its use or its outputs, which need validation and remain under the full responsibility of the issuer/CASP. ## Additional background information ## On the LEI: * How to search for an existing LEI -LEI Search * How to obtain an LEI -Get an LEI: Find LEI Issuing Organizations Organizational Identity -GLEIF * Briefing with additional information on LEI - ## On the DTI: * How to search for an existing DTI - * How to obtain a DTI (or FGG DTI) - * General information on the DTI -FAQs < DTIF ## On XBRL: * XBRL International iXBRL | XBRL --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.mica.wtf/eu-level/soft-law/statement-on-mica-data-standards-format-requirements.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.