DAC8 vs MiCA

DAC8 and MiCA are mentioned in the same breath so often that many crypto businesses treat them as one regulatory event. They are not. One is market regulation. The other is a tax-transparency directive. They interlock — DAC8 borrows MiCA's definition of a crypto-asset service provider — but they impose different obligations, on different timelines, enforced by different authorities.

This guide separates the two cleanly and shows what a crypto business actually has to do under each in 2026.

TL;DR

• MiCA = market regulation. Regulation (EU) 2023/1114. Governs licensing, conduct, custody, issuer disclosure, and stablecoin structure. Stablecoin titles applied from 30 June 2024.
• DAC8 = tax transparency. Council Directive (EU) 2023/2226. Expands automatic exchange of tax information from CASPs. Reporting effective 1 January 2026; first exchange by 30 September 2027.
• They interlock: DAC8 uses MiCA's CASP definition but has a broader reporting scope (reaches non-EU providers serving EU-resident users).
• Being MiCA-authorized does not make you DAC8-compliant — they are separate workstreams.
• Different authorities: MiCA is supervised by financial regulators (ESMA, EBA, national authorities like the AMF). DAC8 is enforced by tax authorities.

What MiCA does

MiCA (the Markets in Crypto-Assets Regulation) is the EU's market framework for crypto. It answers the question: who is allowed to do what in the crypto market, and under what rules?

• Crypto-asset service providers (CASPs) must be authorized and supervised. Custody, exchange, brokerage, placement, and advice all fall in scope.
• Issuers must publish whitepapers and meet disclosure obligations.
• Stablecoins are split into two regulated categories — e-money tokens (EMTs) and asset-referenced tokens (ARTs) — with reserve, redemption, and governance requirements (see MiCA ART vs EMT).
• Market abuse rules apply (insider dealing, manipulation).

MiCA is prudential and conduct regulation. Its enforcement question is "should this entity be allowed to operate, and is it operating safely?"

What DAC8 does

DAC8 is the eighth amendment to the EU Directive on Administrative Cooperation. It answers a different question: what tax-relevant data must crypto platforms report, and to whom?

• CASPs collect tax residency, TIN, and identity data for their users (see DAC8 data collected).
• CASPs report annual aggregate transaction data per reportable user to their home Member State tax authority.
• Authorities exchange that data automatically with other Member States and CARF partner jurisdictions (see DAC8 vs CARF).
• Penalties for non-reporting, data-integrity failures, and due-diligence failures are set nationally within an EU-mandated minimum severity (see DAC8 CASP penalties).

DAC8 is tax transparency. Its enforcement question is "did this platform report its users' activity accurately to the tax authority?"

How they interlock

The connection point is the CASP definition. DAC8 reuses MiCA's definition of a crypto-asset service provider as its starting point for who must report. But the scopes are not identical:

The practical consequence: a platform can be fully MiCA-authorized and still be non-compliant with DAC8 if it never built the tax-data reporting pipeline. The two are sequential workstreams, not one.

What a crypto business actually has to do

For a platform operating in or into the EU in 2026, the two tracks run in parallel:

MiCA track

1. Obtain CASP authorization (or operate under the national transitional regime until its deadline — in France, see PSAN to CASP migration).
2. Meet custody, conduct, and disclosure obligations.
3. If issuing a stablecoin, comply with the EMT or ART regime.

DAC8 track

1. Collect tax-residency self-certifications and TINs from users.
2. Run due diligence to verify the certifications.
3. Aggregate annual transaction data per reportable user.
4. File in the required format with the home Member State authority within the national deadline (the EU exchange deadline is 30 September following the reporting year).

Neither track substitutes for the other.

Where vendors fit

The vendor landscape splits along the same MiCA/DAC8 line:

• Sumsub sits on the DAC8 due-diligence layer — KYC, tax-residency self-certification capture, TIN verification. It does not handle MiCA authorization or produce the tax report itself.
• TaxBit generates DAC8/CARF-shaped tax outputs from transaction data. It assumes you bring your own KYC and your own MiCA posture.
• Cryptio is the transaction-data and accounting layer that feeds both: clean normalized data is the prerequisite for accurate DAC8 reporting and for the financial records a MiCA-authorized CASP must keep.

Most platforms end up with a stack rather than one tool, because no single product spans market regulation and tax transparency.

How Wag3s helps

Wag3s Ledger sits on the data layer that both tracks depend on:

• Multi-chain reconciliation so the transaction data feeding DAC8 reporting is complete (see multi-chain reconciliation)
• Per-user aggregation aligned with DAC8 reportable-data fields
• Stablecoin tagging at issuer + chain level, which matters for the EMT scope distinction
• Audit-ready records that support the financial-recordkeeping side of MiCA authorization

See the Wag3s Ledger product page for module details.

Further reading

• DAC8 Compliance Guide 2026 — the umbrella DAC8 article
• DAC8 vs CARF Difference — the tax-framework comparison
• DAC8 Data Collected — the exact reportable fields
• DAC8 CASP Penalties
• MiCA Regulation — the MiCA pillar
• MiCA ART vs EMT Stablecoins
• PSAN to CASP Migration (France)
• MiCA Implementation Checklist

Sources

• Council Directive (EU) 2023/2226 (DAC8) — EUR-Lex
• Regulation (EU) 2023/1114 (MiCA) — EUR-Lex
• European Commission — DAC8 overview
• EBA — Asset-referenced and e-money tokens (MiCA)
• ESMA — Markets in Crypto-Assets Regulation (MiCA)