What is iXBRL?
iXBRL stands for Inline eXtensible Business Reporting Language. It is a format that combines the visual presentation of an HTML document with machine-readable data tags embedded directly into the content. When you open an iXBRL file in a web browser, it looks like a normal web page. But underneath, every key data point (e.g., numbers, dates, entity names, risk disclosures) is tagged with a structured label that computers can read and process automatically.
The "inline" part of iXBRL is what sets it apart from traditional XBRL. In regular XBRL, the machine-readable data and the human-readable document are separate files. With iXBRL, both are combined into a single file. This means regulators, investors, and automated systems can all consume the same document: humans see the formatted whitepaper, machines extract the tagged data.
Why Does MiCAR Require iXBRL for Crypto-Asset Whitepapers?
The Markets in Crypto-Assets Regulation (MiCAR, EU 2023/1114) requires all crypto-asset whitepapers to be submitted in iXBRL format. This is not optional. If your whitepaper is not formatted in iXBRL, it will be rejected by the national competent authority (NCA).
The rationale behind this requirement is straightforward. The European Securities and Markets Authority (ESMA) needs to process thousands of crypto-asset whitepapers from across 27 EU Member States. Doing this manually would be impossible. By requiring iXBRL, ESMA ensures that every whitepaper can be automatically parsed, compared, and stored in the central ESMA register. Regulators can instantly extract specific data points (the issuer's identity, the consensus mechanism used, energy consumption figures, risk disclosures) without reading the entire document.
This is the same logic behind the European Single Electronic Format (ESEF), which requires all listed companies in the EU to file their annual financial reports in iXBRL. ESMA has now extended this approach to the crypto-asset market through MiCAR.
How iXBRL Works: Tags, Taxonomies, and Structure
An iXBRL document consists of three core components:
- HTML content: The visible whitepaper that humans read. This includes all text, tables, images, and formatting.
- XBRL tags: Invisible data markers embedded in the HTML. Each tag identifies a specific data point and links it to a concept in the taxonomy. For example, the issuer's legal name might be tagged as
micar:IssuerLegalName. - Taxonomy reference: A link to the ESMA 2025 taxonomy, which defines all the valid tags and their relationships. The taxonomy acts as a shared dictionary that ensures every whitepaper uses the same labels for the same concepts.
When a regulator or automated system processes an iXBRL whitepaper, it reads the tags and maps them to the taxonomy. This allows for structured extraction of data across all submitted whitepapers, enabling cross-comparison and automated validation.
iXBRL vs PDF vs HTML: What Are the Differences?
Most crypto projects currently publish their whitepapers as PDFs or HTML web pages. Neither of these formats meets MiCAR's requirements. Here is how they compare:
| Feature | HTML | iXBRL | |
|---|---|---|---|
| Human-readable | Yes | Yes | Yes |
| Machine-readable data tags | No | No | Yes |
| Structured data extraction | No | No | Yes |
| MiCAR compliant | No | No | Yes |
| Opens in browser | Requires reader | Yes | Yes |
| Supports branding/styling | Yes | Yes | Yes |
The key takeaway: iXBRL gives you the best of both worlds. It looks like an HTML page but contains structured data that regulators can process automatically. PDFs and plain HTML cannot do this.
The ESMA 2025 Taxonomy for MiCAR Whitepapers
The taxonomy is the backbone of iXBRL. For MiCAR whitepapers, ESMA has developed a specific taxonomy that defines every data point that must be tagged. This taxonomy was finalized in 2025 and covers the requirements set out in the Implementing Technical Standards (ITS 2024/2984).
The taxonomy assigns a unique identifier and data type (text, number, date, boolean, etc.) to each disclosure required by the ITS. This means every piece of information in your whitepaper, from the issuer's legal name to the energy consumption of the consensus mechanism, has a corresponding tag that regulators can read and process automatically. When we convert or draft a whitepaper in iXBRL, each required data point is mapped to the correct taxonomy tag and validated against the schema.
We wrote a dedicated article on the ESMA 2025 taxonomy that covers its structure, data types, and validation rules in detail.
Who Needs an iXBRL Whitepaper?
Under MiCAR, the following entities need to submit a whitepaper in iXBRL format:
- Token issuers offering crypto-assets to the public in the EU
- Token issuers seeking admission to trading on a MiCAR-licensed exchange
- Crypto-Asset Service Providers (CASPs) listing tokens that require a whitepaper
If you are issuing a token and want it traded on EU-based exchanges like Kraken, Bitvavo, or Coinbase (operating under MiCAR), you need an iXBRL whitepaper. There is no workaround.
How to Get Your Whitepaper in iXBRL Format
There are two paths depending on your starting point:
- Starting from scratch: If you do not have a whitepaper yet, you need a MiCAR whitepaper drafting service that produces the document directly in iXBRL format, fully tagged with the ESMA 2025 taxonomy.
- Converting an existing whitepaper: If you already have a whitepaper in PDF, HTML, or Word format, you can use an iXBRL conversion service to transform it into the required format. The content is preserved, restructured to match MiCAR's ITS requirements, and tagged with the correct taxonomy.
In both cases, the final deliverable is a validated iXBRL file that can be submitted to any EU national competent authority.
Get your iXBRL whitepaper
Without a properly tagged iXBRL whitepaper, your token cannot be offered or traded in the EU. Whether you need a whitepaper drafted from scratch or an existing document converted to iXBRL, the end goal is the same: a validated, ESMA-taxonomy-compliant file ready for your national competent authority.
