DAC8 and NFTs

The most common misconception about DAC8 and NFTs is that NFTs are exempt because they are "non-fungible." They are not exempt. DAC8 applies a function test: an NFT is a reportable crypto-asset when it can be used for payment or investment purposes, assessed case by case. For an NFT marketplace or a treasury holding NFTs, that turns a one-line assumption into a per-collection classification problem.

This article explains where the line sits and how to operationalize it.

TL;DR

• No blanket NFT exemption under DAC8. Reportable status is assessed case by case on the NFT's nature and function.
• Function test: can the NFT be used for payment or investment? If yes, it is in scope.
• Likely in scope: fractionalized NFTs, large non-unique series (big PFP collections), NFTs used as payment.
• Likely out of scope: genuine one-of-a-kind art NFTs functioning like traditional art.
• Assessment is per collection, not per marketplace — mixed inventory needs a documented classification process.
• DAC8 aligns with MiCA's fungibility logic; expect granularity at least matching CARF.

The function test, not the "non-fungible" label

The decisive question under DAC8 is not whether a token is technically non-fungible. It is whether the token, in practice, can be used for payment or investment purposes. The OECD's reasoning, which DAC8 follows, is explicit: NFTs are often marketed as collectibles, but that marketing does not prevent an NFT from being used for payment or investment. So each NFT is evaluated on its nature and its function in practice.

This produces a spectrum, not a binary:

The label "NFT" tells you almost nothing about scope. The function does.

Why fractionalized and series NFTs are the exposure

Fractionalized NFTs and NFTs issued in large, non-unique series are the highest-exposure categories. The reason is functional: a 10,000-piece PFP collection trades much more like a fungible investment asset than like a unique artwork, and a fractionalized NFT is, by construction, an investment instrument split into tradeable units. Under MiCA's logic — which DAC8 aligns with — these are increasingly treated as financial instruments or other crypto-assets rather than unique collectibles.

For a marketplace, this means the risk concentrates exactly where volume concentrates: the big collections, not the rare 1/1s.

Operationalizing a case-by-case test

A case-by-case test sounds unworkable at marketplace scale. It is workable if you assess per collection, not per token or per platform:

1. Inventory your collections and classify each: genuine 1/1 art, large series, fractionalized, payment-utility.
2. Apply the function test per collection, documenting the reasoning (series size, fungibility, observed trading behaviour, payment use).
3. Feed the classification into the reporting pipeline so in-scope collections flow into DAC8 aggregation and out-of-scope ones are excluded with a documented basis.
4. Keep the classification auditable. A tax authority reviewing your DAC8 filing will ask why a collection was excluded — "it's an NFT" is not an answer; the documented function assessment is.

A marketplace dealing only in genuine 1/1 art has a light obligation. A marketplace with mixed inventory has a real classification process to build — and getting it wrong in either direction (excluding an in-scope series, or over-reporting unique art) is a data-integrity exposure (see DAC8 penalties).

For treasuries and creators holding NFTs

The function test also applies to entities holding NFTs:

• A treasury holding NFTs as investment positions should expect the activity to be within a serving CASP's reportable scope.
• A creator minting and selling a large series is, functionally, closer to issuing an investment instrument than selling unique art — the series side of the catalogue is the exposure.
• Genuine unique commissioned art held or displayed is the lowest-risk category.

The practical action is the same as for marketplaces: classify by function and collection, document the basis, reconcile to what a serving CASP will report.

Where vendors fit

• Cryptio normalizes NFT transaction data so collections can be classified and the in-scope ones aggregated.
• TaxBit produces the reporting output once the in/out-of-scope classification is decided.
• Sumsub handles the user-side due diligence underneath the reporting.

The per-collection classification itself is a judgement layer no tool fully automates — it has to be documented and owned.

How Wag3s helps

Wag3s Ledger supports the NFT side of DAC8:

• NFT transaction normalization across chains and marketplaces (see multi-chain reconciliation)
• Per-collection tagging so in-scope vs out-of-scope classification feeds the reporting pipeline cleanly
• Retained lineage so any excluded-collection decision is auditable
• Aggregation of in-scope NFT activity per reportable user

See the Wag3s Ledger product page for module details.

Further reading

• DAC8 Compliance Guide 2026
• DAC8 Data Collected
• DAC8 vs CARF Difference
• DAC8 and Stablecoins
• DAC8 CASP Penalties
• MiCA ART vs EMT Stablecoins

Sources

• Council Directive (EU) 2023/2226 (DAC8) — EUR-Lex
• OECD Crypto-Asset Reporting Framework — model rules and commentary
• Regulation (EU) 2023/1114 (MiCA) — EUR-Lex
• European Commission — DAC8 overview