MiCA vs DAC8: What Changes for EU Crypto Users in 2026?

MiCA and DAC8 are both EU crypto rules, but they answer different questions. MiCA regulates crypto markets: issuers, stablecoins, authorised crypto-asset service providers, disclosures and service conduct. DAC8 is a tax-transparency directive: it requires Reporting Crypto-Asset Service Providers to identify reportable users, collect transaction information and report it to tax authorities for automatic exchange. A platform can therefore be MiCA-authorised and still have separate DAC8 duties. And a transaction can be reportable under DAC8 without the directive itself deciding how much tax you owe.

Quick answer: what is the difference between MiCA and DAC8?

MiCA is primarily a market-regulation framework; DAC8 is a tax-information framework. MiCA asks whether an issuer, token offering or crypto service may operate under EU rules and what safeguards apply. DAC8 asks which service providers must collect user and transaction data, where they report it and how tax authorities exchange that information. Treating them as one law creates false conclusions about licensing, privacy and taxes.

Use the Two-Ledger Test

Run the same crypto activity through two separate ledgers instead of asking whether it is simply 'MiCA compliant'.

• Regulatory ledger: which entity provides the service and does MiCA authorisation or another permitted route apply?
• Asset ledger: do MiCA issuer, offering or stablecoin rules apply to the crypto-asset?
• Tax-information ledger: is the provider an RCASP and is the activity a reportable transaction under DAC8?
• Tax-liability ledger: what does the user's national tax law say about the transaction?

MiCA regulates the market relationship

ESMA describes MiCA as uniform EU market rules covering transparency, disclosure, authorisation and supervision for crypto-assets and market participants. For users, that affects questions such as whether a CASP is authorised, what custody safeguards apply, which stablecoins may be offered and what disclosures accompany an asset or service.

DAC8 regulates tax information flows

The European Commission describes DAC8 as the eighth amendment to the Directive on Administrative Cooperation in Direct Taxation. Its crypto purpose is automatic exchange of information between tax authorities. It adds due diligence and reporting rules for operators handling reportable crypto transactions; it is not a substitute for MiCA licensing.

DAC8 started collecting 2026 activity on January 1, 2026

The Commission states that DAC8 applies from January 1, 2026 and that Reporting Crypto-Asset Service Providers should collect data on reportable transactions of EU-resident users from that date. This makes 2026 the first reporting year. Waiting until a tax authority receives data in 2027 does not mean 2026 transactions are outside the reporting period.

The first cross-border exchange of 2026 data happens in 2027

The reporting path has two stages. Providers submit information according to the domestic implementation and deadline of their reporting jurisdiction. EU tax authorities then exchange relevant information with the user's country of tax residence. The Commission says the exchanges relating to the first reporting year, 2026, will take place by September 30, 2027.

A domestic provider deadline can be earlier than September 30, 2027

September 30 is the EU exchange deadline, not necessarily the provider's local filing deadline. National implementation can require the provider to submit earlier so the authority has time to validate and exchange the data. Users should therefore distinguish the provider filing date, the authority-to-authority exchange date and their own tax-return deadline.

MiCA authorisation and DAC8 reporting are separate tests

A MiCA authorisation answers whether a crypto-asset service provider may provide authorised services in the EU. DAC8 uses its own definition of a Reporting Crypto-Asset Service Provider and its own nexus and transaction rules. The Commission even notes a single-registration route for certain operators active in the EU that are not authorised under MiCA. So 'not MiCA-authorised' does not automatically mean 'invisible to DAC8'.

DAC8 can reach beyond the narrow MiCA product perimeter

The Commission says DAC8 builds on MiCA definitions but has a broad crypto scope that also includes decentralised-issued crypto-assets, stablecoins including e-money tokens and certain NFTs. The directive's reporting design follows tax-transparency objectives, so its perimeter should not be inferred only from whether a token is regulated in the same way under MiCA.

What DAC8 calls a Reporting Crypto-Asset Service Provider

The directive defines an RCASP as a Crypto-Asset Service Provider or Crypto-Asset Operator conducting one or more crypto-asset services that effect exchange transactions for or on behalf of a reportable user. The definition matters because DAC8 is not simply a list of exchanges with MiCA licences; it follows the provider's role, nexus and reportable activity.

DAC8 expressly includes staking and lending in its crypto-service definition

For DAC8, the directive says 'Crypto-Asset Service' means the MiCA Article 3 service definition including staking and lending. That does not mean MiCA and DAC8 regulate those activities identically. It means DAC8 deliberately uses a reporting definition that can capture activity beyond the simple buy-and-sell interface.

What information identifies the user

For a reportable individual, the directive requires information such as name, address, tax-residence Member State or States, tax identification number and date of birth, with place of birth required only in specified circumstances. Providers use self-certification and due-diligence procedures to establish tax residence rather than simply assuming it from an IP address.

Existing users have a tax-residence self-certification deadline

For pre-existing individual users, the directive requires the RCASP to obtain a valid self-certification allowing it to determine tax residence by January 1, 2027. New relationships are handled when the relationship is established. A provider may therefore ask an existing customer for tax-residence or TIN information during 2026 even if ordinary identity verification was completed years earlier.

What transaction data DAC8 reports

The directive is more specific than the phrase 'your full transaction history'. For each reportable crypto-asset, the reporting fields include aggregate amounts, units and transaction counts for acquisitions and disposals against fiat, acquisitions and disposals against other reportable crypto-assets, reportable retail payments and transfers to or from the user. The report is structured by asset and transaction category.

Crypto-to-crypto exchanges are inside the reporting map

DAC8 defines an exchange transaction to include exchanges between reportable crypto-assets and fiat currencies and exchanges between one or more forms of reportable crypto-assets. A user should therefore not assume that only cashing out to euros creates reportable information. Reporting scope and taxable treatment still remain separate questions.

Transfers can be reportable even when they are not trades

The directive separately defines a transfer as movement of a reportable crypto-asset to or from a user's address or account where the provider cannot determine that the movement is an exchange transaction. This is why an exchange withdrawal or deposit can appear in the DAC8 reporting framework even when the user says 'I did not sell anything'.

Self-custody is not automatically invisible to DAC8

A self-custody wallet does not become an RCASP merely because it holds a user's keys, but the regulated or reporting service at the boundary can still record the transfer. DAC8 includes an aggregate reporting field for transfers made by the RCASP to distributed-ledger addresses not known to be associated with a virtual asset service provider or financial institution.

DAC8 does not say that every external wallet address is a separate tax record

The directive's specific field for transfers to addresses not known to belong to a VASP or financial institution requires aggregate fair market value and aggregate units. That wording is important: it is more precise than claims that DAC8 automatically sends tax authorities a complete labelled map of every private wallet address. Other legal or investigative data sources can exist, but they should not be confused with this particular DAC8 field.

Reported does not mean taxable

A DAC8 reportable transaction and a taxable event are not synonyms. DAC8 creates a tax-transparency and information-exchange system; national tax law still determines whether a disposal, exchange, income receipt, staking reward, transfer or other event creates tax, how the taxable base is calculated and which exemptions or accounting rules apply.

MiCA-compliant does not mean tax-free

A token or provider can satisfy MiCA rules and the user's transaction can still fall within national tax law and DAC8 reporting. MiCA authorisation is not a tax exemption. The reverse is also true: the fact that data is reportable under DAC8 does not certify that the asset, platform or service is authorised under MiCA.

A practical four-question check for any EU crypto transaction

Before drawing a compliance or tax conclusion, write down four answers.

• Who is the legal entity providing the service?
• What exact service is being used and what does MiCA require of that provider or asset?
• Is the provider an RCASP for this activity and which DAC8 transaction category applies?
• What does the user's country of tax residence treat as a taxable event?

Why this distinction matters for small rewards and microwallets

A tiny faucet reward can move through several legal layers: the reward source, a custodial microwallet, a conversion and finally an exchange or self-custody withdrawal. The value being small does not by itself answer whether an RCASP reports a transaction. Equally, a reported transfer does not establish that the transfer itself creates tax. Keep records of the source, asset, date, amount, conversion and destination so later reporting can be reconciled.

The practical rule to remember

Use MiCA to answer 'may this issuer or provider offer this crypto service in the EU, and under what safeguards?' Use DAC8 to answer 'who collects and reports which crypto tax information, and where does it go?' Then use national tax law to answer 'what do I owe?'. Those are three different questions, even when the same transaction appears in all three.

Primary sources checked on August 20, 2026

EU legislation and European Commission material were prioritised. National tax-authority material was used only to illustrate that domestic filing deadlines can differ from the EU authority-to-authority exchange deadline.

• European Commission - DAC8: https://taxation-customs.ec.europa.eu/taxation/tax-transparency-cooperation/administrative-co-operation-and-mutual-assistance/directive-administrative-cooperation-dac/dac8_en
• Council Directive (EU) 2023/2226: https://eur-lex.europa.eu/eli/dir/2023/2226/oj/eng
• ESMA - Markets in Crypto-Assets Regulation (MiCA): https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica
• Netherlands Tax Administration - DAC8/CARF information: https://odb.belastingdienst.nl/en/carf-dac8/information-on-dac8-carf/
• Irish Revenue - CARF/DAC8 registration obligations: https://www.revenue.ie/en/companies-and-charities/international-tax/aeoi/dac8/registration.aspx

FAQ