Crypto Tax Data Sharing: What France’s New Bill Means
Learn what France’s Senate-approved crypto tax data bill would change, how CARF differs from DAC8, and what the proposal means for privacy and taxpayers.

France's Crypto Tax Data Bill: What Changes - and What Doesn't
Crypto tax reporting in France is headed toward less "what you choose to disclose" and more "what providers report to tax authorities." The French Senate has adopted a bill that would allow tax authorities to automatically exchange crypto-asset tax information with other countries.
But it's still early in the process. This vote is not the final law.
That distinction matters. France already has crypto reporting obligations under EU rules. The Senate bill would add an international agreement based on an OECD framework. And because this kind of data-sharing involves sensitive financial details, the debate isn't just technical - it also comes down to privacy, security, and who gets access to taxpayer information.
This article breaks down what the Senate approved, how the proposed framework relates to DAC8, what "automatic exchange" could mean in practice, and why data security is a core part of the discussion. It also covers what you can do now - without treating a proposal as if it's already in force.
What the French Senate approved
The French Senate passed the bill at first reading and sent it to the National Assembly for consideration as Bill no. 3421. The proposal covers:
- an agreement for exchanging crypto-asset tax information
- an update to an existing agreement covering financial account information
A Senate vote is not the same thing as an enacted law. The bill still has to complete the legislative process. Until then, it's more accurate to call it a proposed authorization for information exchange than a new reporting system already operating under this agreement.
What the bill is designed to do
The crypto agreement is based on the OECD's Crypto-Asset Reporting Framework (CARF). CARF aims to set common standards for participating jurisdictions to collect and automatically exchange information about crypto transactions. The goal is to make cross-border tax reporting more consistent, instead of forcing each country to build its own approach from scratch.
The proposed agreement sits alongside France's existing EU-based rules rather than replacing them. The Senate bill also updates an agreement for exchanging financial-account information, so the legislation covers more than crypto alone.
What is still unresolved
The remaining uncertainty is straightforward: the National Assembly still has to consider the bill, and the final wording and timing depend on what lawmakers do next. The Senate vote is meaningful, but it doesn't lock in the final implementation details by itself.
For crypto businesses and users, it helps to separate three things that often get mixed together:
- A proposal: the Senate approved the bill at first reading.
- Existing obligations: EU crypto reporting rules are already in place in France.
- Future implementation: the international exchange agreement depends on the legislative process finishing and the next implementation steps.
That separation isn't about legal fine print. It helps companies avoid building compliance workflows around a rule that isn't finalized yet - while still planning around the reporting duties that already apply.
How CARF differs from DAC8
CARF and DAC8 solve related problems, but they're not just different names for the same system.
- CARF is an OECD-developed framework for collecting and exchanging crypto tax information between participating jurisdictions.
- DAC8 is an EU directive that extends tax cooperation and reporting requirements to crypto-assets and crypto service providers within the EU framework.
France has already introduced crypto reporting obligations through its 2025 Finance Act, which implements the crypto reporting amendment to the EU's Directive on Administrative Cooperation (DAC8). Under those rules, crypto service providers report customer identities and transaction data to tax authorities. Authorities then share relevant information with other EU countries where users are tax residents.
A useful way to distinguish the two
A practical way to think about it is:
- DAC8 is the EU reporting and information-sharing regime.
- CARF is the broader international framework that can support exchanges beyond the EU.
They may overlap in the kinds of information they handle, but they sit in different legal and geographic contexts.
| Framework | Main context | What it covers in this case |
|---|---|---|
| DAC8 | European Union | Crypto service provider reporting and exchange of information among EU tax authorities |
| CARF | International, OECD-backed | Common standards for participating jurisdictions to collect and exchange crypto tax information |
Why the overlap matters operationally
For a provider, overlapping frameworks can translate into real work: figuring out which customers and transactions fall under which reporting rule, validating identity and tax-residency information, and building a process that can be defended when reporting happens.
If a system only records a wallet address and a transaction amount, that may not be enough when the applicable reporting rules also require customer identity details.
For an individual, the takeaway is simpler: reporting obligations can be triggered through a service provider, not only through a tax return you file. That said, provider reporting doesn't automatically answer every question about how a specific transaction is taxed. Reporting information and calculating tax liability are related - but they're not the same task.
What automatic exchange means for taxpayers
Automatic exchange means tax authorities can receive and share relevant information through established reporting arrangements, rather than relying only on a specific request inside an investigation.
In this case, the Senate-backed bill would authorize an agreement for international exchange of crypto tax information, assuming it completes the legislative process.
That doesn't mean every crypto transaction becomes visible to every government, or that every transfer is automatically taxable. The bill is about exchanging tax information under an agreement. What information is covered, which jurisdictions participate, who reports it, and how it's handled depends on the rules of the system once it's finalized.
Reporting is not the same as tax owed
If you're trying to interpret headlines about crypto reporting, this distinction is the one to keep in mind. Information a provider reports can help an authority compare activity against a taxpayer's filings. It doesn't, by itself, determine whether someone owes tax, what rate applies, or whether a transaction qualifies for an exemption.
Tax treatment still depends on national rules and the taxpayer's situation. Reporting makes it easier for authorities to compare what's been reported with what's been filed - it doesn't replace the underlying rules that define taxable events and how gains or income should be calculated.
Do not confuse the proposal with the stablecoin budget debate
France is also debating possible crypto tax changes as part of its 2027 budget. On Oct. 16, the National Assembly adopted an amendment that would make gains from conversions into certain fiat-pegged stablecoins taxable from Jan. 1, 2027. That amendment is not law yet.
This budget amendment is separate from the Senate bill on information exchange. One is about changing the tax treatment of certain conversions; the other is about authorizing cross-border information exchange. Treating them as the same policy shift can lead to incorrect assumptions about what a taxpayer must report or pay right now.
Lawmakers resumed debate on the budget's revenue section on Tuesday, with a vote scheduled for Nov. 3. That outcome should be treated as separate from the legislative progress of Bill no. 3421.
Why data security is part of the debate
Cross-border reporting can make it easier for tax authorities to administer rules. It also increases the amount of sensitive personal and financial data that has to be protected.
This isn't abstract. Reporting under DAC8 can involve sharing names, addresses, tax identification numbers, and transaction volumes between EU tax authorities.
Faustine Fleuret, global head of public affairs at lending protocol Morpho, told Cointelegraph that collecting and exchanging this information raises data security concerns. She warned that a centralized repository could become a single point of failure for sensitive crypto transaction data.
The exposure is more than a privacy question
A leak of financial data can cause harm beyond the relationship between a person and a tax authority. In France, concern about physical attacks targeting crypto holders has made the consequences of exposure feel especially real.
These incidents - often referred to as wrench attacks - typically involve criminals using threats or violence to force someone to hand over crypto or to access it.
Blockchain security company CertiK reported that France accounted for 33 of 52 verified wrench attacks worldwide during the first half of 2026. In a March incident cited in the source reporting, criminals posing as police officers robbed a French couple in their late 50s of about $1 million worth of Bitcoin.
These figures don't prove that tax reporting caused any attack. They do help explain why some industry participants treat identity-linked financial data security as both a privacy issue and a physical safety issue.
Centralization has a real trade-off
The European Commission plans to create a central repository for crypto reports by the end of 2026, with each member state's tax authorities able to access information about their tax residents. Centralization can make access more manageable - authorities may have one consistent mechanism for retrieving relevant reports instead of relying on fragmented systems.
The trade-off is concentration. A centralized system can also be a more attractive target. If there's an access-control failure or a breach, the scale of exposure could be much harder to contain.
For users, it's fair to ask what protections will actually be in place. It's not reasonable to assume that a proposed reporting framework automatically guarantees perfect security or unrestricted access. The available source information points to planned exchange and security concerns, but it doesn't establish that all data will be publicly accessible.
What crypto users and businesses should do now
The best response here is preparation, not panic. Reporting obligations are expanding, but a proposed international agreement isn't the same as a final rule.
The most useful steps are the ones that help you understand your records and meet obligations that already apply - without treating unfinished legislation like it's already settled.
If you are an individual crypto user
Keep a clear record of activity on exchanges and other crypto service providers. Depending on your situation, this can include transaction dates, amounts, asset types, fees, transfers between accounts, and whatever you need to identify where funds came from and where they went.
A clean history is often more useful than trying to reconstruct years of activity when a tax filing or authority question arrives.
A practical checklist:
- Keep account statements and transaction exports from the services you use.
- Track transfers between wallets you control so they don't get mistaken for separate trading activity.
- Reconcile exchange records with your own wallet history and tax calculations.
- Separate the reporting requirement from whether a transaction creates a tax liability.
- Check the status of proposed French tax changes before reacting to a headline.
- Use appropriate security practices for accounts and personal information; don't share access credentials in response to unsolicited requests.
These steps don't replace advice tailored to your tax residence and activity. They can reduce avoidable uncertainty when records are reviewed or reporting rules change.
If you operate a crypto business
Start by mapping what applies now, including DAC8-related reporting, before you design processes around a proposed CARF-based exchange agreement. Keep customer identity and tax-residency information accurate, document how transaction records are assembled, and clearly assign who is responsible for validating and submitting data.
Alongside that, treat security as part of compliance, not just an engineering afterthought. Limit access to sensitive data, define retention and deletion practices, log access where appropriate, and plan how you'd respond to an incident. The more systems that store identity-linked transaction details, the more important it is to understand where the data sits and who can retrieve it.
A decision rule for the next few months
Use this simple sequence:
- Confirm what applies now. Identify current French and EU reporting obligations relevant to your role.
- Track what is still a proposal. Monitor Bill no. 3421 and the separate 2027 budget discussion without treating either as enacted law.
- Prepare reusable records and controls. Improve data quality and security in ways that will still help even if implementation details shift.
That approach keeps you out of two traps: ignoring a direction of travel that's already visible, and overreacting to a bill that hasn't finished the legislative process.
Conclusion
The French Senate has taken a step toward international crypto tax information exchange, but the bill still needs to complete the legislative process. It's based on CARF and would sit alongside France's existing DAC8-related reporting obligations - and it shouldn't be confused with the separate, still-pending stablecoin tax amendment.
For individuals, the most useful preparation is accurate transaction records. For businesses, the priority is understanding current reporting duties while building secure, auditable data processes that can adjust as the rules develop. The direction is toward more cross-border visibility, but the safeguards around sensitive data still matter.