Regulation

CARF and DAC8 for stablecoin payments: first reports in 2027

CARF and DAC8 make stablecoin providers report users' tax residence, TINs and transaction totals. Dates by country for the first reports on 2026 data.

Caio Barbosa

Founder & CO-CEO

Forbes Under 30. One of the leading voices in Fintech & Crypto in Brazil. Writes weekly about stablecoins, payments, and the future of financial infrastructure in Latin America.

Cover image for Lumx blog article: CARF and DAC8 for stablecoin payments: first reports in 2027
Cover image for Lumx blog article: CARF and DAC8 for stablecoin payments: first reports in 2027

CARF (the OECD's Crypto-Asset Reporting Framework) and DAC8 (its EU law, Directive (EU) 2023/2226) are the tax rules that make a stablecoin provider report each customer's tax residence, taxpayer ID and yearly transaction totals. Collection began January 1, 2026. First reports, covering 2026, fall due between January and July 2027, by country.

Who reports, and who is reported

Under the Directive, the duty falls on a "Reporting Crypto-Asset Service Provider": an entity authorised under MiCA (Regulation (EU) 2023/1114, the EU crypto-asset regulation) or, failing that, a "Crypto-Asset Operator" that provides these services without that authorisation (Annex VI, first section). National laws copy the shape: the UK, Brazil and Colombia each name the provider as the filer.

Your company sits on the other side. If you hold stablecoins or move them through a provider, you are a "Crypto-Asset User" of that provider, which must establish where you are tax resident and, for most companies, who controls you. Your own customers enter in one case: when the provider executes payments for you as a merchant, it must also treat your paying customer as a user, provided anti-money-laundering rules make it verify that customer's identity (Annex VI, Section IV, definition of Crypto-Asset User).

None of this makes you a filer. It makes you a data source on someone else's deadline.

What gets reported about your company and your customers

Annex VI, Section II of the Directive lists the content. Brazil's IN RFB 2.291/2025 (Receita Federal Normative Instruction 2,291 of November 14, 2025) and Colombia's DIAN Resolution 000240 of December 24, 2025 follow it with local additions.

What a provider reports for each reportable user, per Directive (EU) 2023/2226, Annex VI, Section II.

Reported item

Detail

The user

Name, address, country or countries of tax residence, TIN (taxpayer identification number) and, for an individual, date of birth

Controlling persons of a company

Name, address, residence, TIN, date of birth and the role that makes each one a controlling person, when the company is not an excluded person or an active entity

Acquisitions against fiat

Per type of crypto-asset: gross amount paid, number of units, number of transactions

Disposals against fiat

Gross amount received, number of units, number of transactions

Crypto-to-crypto exchanges

Fair market value, number of units, number of transactions, each direction

Retail payments

Same totals for transfers paying for goods or services above USD 50,000

Other transfers in and out

Same totals, split by transfer type where the provider knows it

Transfers to unhosted addresses

Value and units sent to addresses not known to belong to another provider or financial institution

The report is aggregate: yearly totals per asset and category, not a transaction list. Brazil's text says so ("de forma agregada e anual"). It also names the people behind a company: unless the company is an active entity (the OECD guide describes one as having passive income under 50 percent of total income) or an excluded person, its controlling persons are identified.

Listed companies, governments, central banks and most financial institutions are "Excluded Persons". Whether a payments company is itself a financial institution in this sense is a question for its advisers, and it changes what its provider asks for.

The dates, read from each text

Member states had to adopt their laws by December 31, 2025 and apply them from January 1, 2026 (Directive, Article 2). The Directive sets no filing day: Annex VI, Section II says providers report "annually in the calendar year following the year to which the information relates", and Article 8ad(6) gives authorities nine months after year end to exchange the data, which is September 30, 2027 for 2026. The filing day is national.

First report on 2026 data, per the official text or authority page read on November 16, 2026.

Jurisdiction

Collection starts

First report from the provider

Source read

EU level

January 1, 2026

No fixed day. Authorities exchange by September 30, 2027

Directive (EU) 2023/2226, Art. 2, 8ad(6), Annex VI

Netherlands

January 1, 2026

January 31, 2027

Belastingdienst guidance page

Denmark

January 1, 2026

January 31, 2027

skat.dk page on crypto-assets

Ireland

January 1, 2026

May 31, 2027

Revenue guidance and eBrief 121/26

Germany

Calendar year 2026

July 31, 2027

KStTG, sections 9 and 21

United Kingdom

January 1, 2026

May 31, 2027

SI 2025/744 and HMRC guidance

Brazil

January 1, 2026

Last business day of January 2027

IN RFB 2.291/2025, Art. 12(II) and 19

Colombia

Taxable year 2026

Last business day of May 2027

DIAN Resolution 000240, Art. 1.6.11.4

Where the sources do not line up, or a text could not be settled:

  • The EU is not one date. A summary saying "EU reports are due September 30, 2027" describes the exchange between tax authorities. Your provider files on the national day, up to eight months earlier.

  • Brazil's text carries two start dates. Article 19 of IN RFB 2.291/2025 applies Article 8, the OECD-style annual report, from January 1, 2026, and Articles 7, 9 and 18 (which revokes IN RFB 1.888/2019) from July 1, 2026.

  • "Last business day" needs a calendar. January 31, 2027 is a Sunday, so a calendar check puts Brazil's day on January 29, 2027, though no Receita notice states it. Colombia's May 2027 day is left to DIAN's business-day calendar.

  • The UK moved its own dates this month. HMRC's page, updated November 2, 2026, records the removal of a January 1, 2027 start for submitting reports and of a January 31, 2027 registration deadline, because the online service will not be ready. The regulation still sets May 31 after each calendar year.

  • The Dutch status is open. The Belastingdienst page gives January 31, 2027, but final adoption of the Dutch act was not confirmed, and its English portal says reporting functionality is under development.

  • The OECD's own CARF text was unreadable. The OECD site returned an error for the rules, so OECD facts here come from its step-by-step guide (approved October 4, 2024) and its commitments list of September 14, 2026.

The OECD list puts 46 jurisdictions on first exchanges by 2027, among them Brazil, Colombia, the United Kingdom and most EU members. Another 27, including Hong Kong, Singapore and the United Arab Emirates, are on 2028, and four (Argentina, Azerbaijan, Mexico and the United States) on 2029. Local collection dates there are not covered here.

Which stablecoins fall inside the reports

Stablecoins are in scope, with one carve-out. Recital 14 of the Directive says the crypto-asset definition includes stablecoins, "including e-money tokens". The operative text then excludes from "Reportable Crypto-Asset" any Central Bank Digital Currency, any "Electronic Money" and any asset the provider has adequately determined cannot be used for payment or investment. Annex VI defines Electronic Money with five tests: a digital representation of a single fiat currency, issued on receipt of funds for payments, backed by a claim on the issuer in that currency, accepted by someone other than the issuer, and redeemable at par on request.

The authorities lean on the carve-out more than the recital does. Denmark's tax authority says a token issued by an authorised issuer under the e-money directive is reported under the Common Reporting Standard (CRS), not under DAC8 or CARF. HMRC's page excludes assets reportable under CRS as a central bank digital currency or a Specified Electronic Money Product. Colombia's resolution repeats the five tests. Brazil's annex defines a "Criptoativo Declarável Referenciado em Ativo", an asset that aims to hold a stable value against official currencies, and keeps the same two exclusions.

So a USD or EUR stablecoin can land under CARF or under CRS depending on its issuer and structure, and the recital and the operative text do not settle it for you. Ask the provider which regime it applies to each token it handles. Either way a tax authority receives your TIN. For the MiCA side of token classification, see our MiCA explainer for payment companies.

What to hand your provider, and when

Due diligence under the Directive (Annex VI, Section III) is a self-certification. The provider obtains one when the relationship starts, and by January 1, 2027 for existing ones. Germany's KStTG sets the same date for customers onboarded before December 31, 2025 (section 7). For a company, the self-certification states its tax residence or residences, and the provider checks it is reasonable against what it already holds from KYB (know your business, the verification of a company and its owners). The OECD guide says a self-certification that fails that check must be replaced or explained before the provider processes transactions for the user.

The list a payments company should have ready is short:

  • Legal name, registered address and every country of tax residence of the company, plus the TIN issued in each.

  • For each controlling person: name, address, residence, TIN and date of birth, as KYB already collects owners with more than 25 percent.

  • Whether the company claims to be an active entity or an excluded person, and why.

A TIN is the fragile item. The UK page says a provider need not report one when the user's country does not issue TINs. A TIN that exists but was never collected is a different case. Providers must also tell users they will be reported: the Dutch page asks for it by January 31, and the Irish page requires a copy to the user by May 31.

The penalties sit with the provider. HMRC's page says up to £300 per user can follow late, inaccurate, incomplete or unverified reporting, and Colombia's resolution applies Article 651 of the Estatuto Tributario to missing or wrong information. Your exposure is indirect: per the OECD guide, a provider that cannot validate your self-certification must resolve it before processing transactions for you.

I would rather ask a customer for a taxpayer ID once, at onboarding, than chase it later with a payout waiting. The provider has to ask anyway, so the only choice a payments company has is when. Putting the tax-residence question next to the KYB documents costs one extra field and saves a second round of requests.

When CARF is not your problem, and when it is

If your company only pays its own suppliers in stablecoin, you are a user and nothing more: you owe accurate data and a signed self-certification, and the filing belongs to the provider. If you are unsure which side of that line you are on, start with what a VASP is and AML duties for fintechs.

A company that holds, exchanges or transfers stablecoins for its own customers may be a provider itself. Brazil's text reaches a provider that serves Brazil through any of four markers: a .br domain, an agreement to receive local funds from Brazilian residents, a stated Pix (Brazil's instant payment system, run by the Central Bank) route, or advertising aimed at Brazilian residents. Colombia's definition covers anyone providing an exchange service for clients or acting as counterparty or intermediary in exchanges. Whether your company crosses that line is a question for counsel before these dates, not after.

Tax outside the reporting duty, such as IOF, sits in our Brazil stablecoin tax guide. Colombia's wider rules are in the Colombia regulation guide, the UK's in the UK rules for GBP payments, and the general footing in are blockchain payments legal.

What this looks like with Lumx

Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.

The data a reporting provider needs starts at onboarding, and the Lumx docs list what is collected. Every customer accepts the terms of service before verification. An individual submits name, tax ID, date of birth, country, address and an identity document with a liveness check. A business submits country, company name, tax ID, incorporation date and address, company formation documents, and documents from the representative and from each UBO (ultimate beneficial owner) and shareholder above 25 percent. The docs say the tax ID must be the local identifier for the customer's country of residence, and the tax IDs by country page lists what is accepted. The KYB flow guide and the KYB explainer cover the process.

On the Brazilian leg, Lumx SPSAV Ltda, the Brazilian entity, filed its application for a virtual asset service provider authorization with the Central Bank of Brazil (BCB), operates under the transition regime and reports customer operations to the Receita Federal under IN RFB 2.291/2025, the DeCripto instrument above. A Brazilian company that also needs a USD account contracts Lumx US OP LLC for that leg. See global payments, the coverage map and the supported countries page for where onboarding applies.

Methodology and sources

Read on November 16, 2026, in full or in the relevant part: Directive (EU) 2023/2226 on EUR-Lex (Articles 1 and 2, recital 14, the four sections of Annex VI); SI 2025/744 and HMRC's three CARF pages; the Belastingdienst, skat.dk and Irish Revenue pages and eBrief 121/26; KStTG sections 7, 9, 17 and 21; IN RFB 2.291/2025 and the Receita's DeCripto page; DIAN Resolution 000240, from a scanned copy hosted by the Colombian Cijuf, not from dian.gov.co; the OECD's CARF step-by-step guide and commitments list; and the Lumx docs on identity verification, business verification and tax IDs.

Not read: the OECD's CARF rules and commentary, the final Dutch act, other member states' texts, and the laws of the 2028 and 2029 jurisdictions. No figure here comes from a secondary summary.

Directive (EU) 2023/2226 checked against eur-lex.europa.eu on November 16, 2026. IN RFB 2.291/2025 checked against the Receita Federal DeCripto page on November 16, 2026.

Verified on November 16, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: laura adai on Unsplash.

  • When are the first CARF and DAC8 reports due?

    The filing day is national: January 31, 2027 in the Netherlands and Denmark, May 31, 2027 in Ireland and the UK, July 31, 2027 in Germany, and the last business day of January 2027 in Brazil and of May 2027 in Colombia. The Directive itself sets no filing day, only that tax authorities exchange the data within nine months of year end, which is September 30, 2027. Lumx collects each customer's country and tax ID at onboarding, per its docs.

  • Does CARF or DAC8 cover stablecoins?

    Yes, with a carve-out. The Directive's recital says stablecoins, including e-money tokens, are in scope, but its operative text excludes products that meet the e-money definition, and Denmark's tax authority sends tokens from authorised e-money issuers to the Common Reporting Standard instead. A stablecoin can therefore be reported under either regime depending on issuer and structure. Lumx pays out in USDC and USDT, and your Lumx contact can say how a given token is classified.

  • What does a payments company need to give a stablecoin provider?

    A signed self-certification with the company's tax residence or residences and the TIN for each, plus the name, address, residence, TIN and date of birth of each controlling person, unless the company is an active entity or an excluded person. Customers that existed before 2026 need it on file by January 1, 2027. Lumx KYB already collects the company's tax ID, address, incorporation date and documents for owners above 25 percent.

  • Who is responsible for filing, the provider or your company?

    The provider files, and the penalties in the UK and Colombian texts fall on the provider. Your company is a reported user, and it is exposed to delays if its data is missing or fails the provider's reasonableness check. A company that handles stablecoins for its own customers may be a reporting provider itself, a question for counsel. Lumx SPSAV Ltda reports Brazilian customer operations to the Receita under IN RFB 2.291/2025.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

carf-dac8-stablecoin-payment-providers-2027

A

carf-dac8-stablecoin-payment-providers-2027

CARF and DAC8 for stablecoin payments: first reports in 2027

Copy link

Copied!

carf-dac8-stablecoin-payment-providers-2027

TALK TO OUR TEAM

Ready to transform your business with stablecoins?

Discover how our infrastructure can seamlessly integrate stablecoins into your financial operations quickly, securely, and efficiently.

Regulation

In this page

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.