Crypto Exchanges Face 2027 Tax Deadline: What Changes

Anyone who opened a crypto account before 2026 will hear from their exchange over the coming months. What it asks for is a tax self-certification: your country of tax residence, your tax identification number, and a confirmation that the details are correct. Ignore it and you do not lose your balance, but you do lose the ability to trade with it. That is what the German Crypto Asset Tax Transparency Act, the KStTG for short, lays down, and the cut-off date is 1 January 2027.

German coverage of the new reporting duty is almost entirely about what the tax office will learn about you. That is one half of it. The other half asks something of you, and the consequence is not a query from the tax office but an account you can no longer trade on.

The KStTG transposes the EU directive DAC8 and the OECD's CARF standard into German law. It obliges crypto-asset service providers to identify their users for tax purposes and to report certain transactions once a year to the Federal Central Tax Office. Sections 4 to 6 set out how that identification works: the provider has to obtain a self-certification, check it for plausibility, and document it.

In practice the self-certification comes down to a handful of details. You are asked for the country or countries in which you are tax resident, the corresponding tax identification number, and an explicit confirmation that the information is accurate. Some providers also ask for your place of birth. The effort involved runs to a few minutes in the app. The problem is not the effort but that many people take the request for marketing and click it away.

The statutory wording is brief and unambiguous here. Section 7(2) reads: "In the case of a crypto-asset user who entered into a business relationship with the provider by 31 December 2025, the provider shall complete the measures under sections 4 to 6 by 1 January 2027."

What matters is whose deadline this is: the provider's, not yours. The exchange has to be finished by that day. From this follows a calculation that does not appear in the statute but does follow from the deadlines. If the block under section 8 takes effect at the earliest 60 and at the latest 90 days after the initial request, and if a reminder and a formal notice come before that, then the requests have to go out by autumn 2026 at the latest. That is an inference from two deadlines and not an announcement by any provider; nobody has named a mailing date. Only the direction is solid: the post arrives before the cut-off, not after it.

The law knows two groups of people with differently strict rules. For everyone who began their business relationship by 31 December 2025, the transitional deadline quoted above applies, running to 1 January 2027. For everyone after that, section 7(1) applies, and it is stricter: there, identification has to be complete before a reportable transaction is carried out at all.

The Federal Central Tax Office describes the same sequence in its procedural guidance and puts it this way for new customers: "As a rule, obtaining the self-certification and confirming its plausibility are required before reportable transactions are carried out." For existing customers the authority names the same cut-off date as the statute. So anyone who has opened an account since January 2026 will already know the query; anyone who has held their account for years often still has it ahead of them.

Enforcement is staged. First the provider requests the details. If no answer comes, a reminder follows, then a formal notice. Only when nothing comes of that either does the final stage take effect. The decisive sentence in section 8(3) is that the provider must then, "at the latest after 90 days have elapsed, but not before 60 days have elapsed since the original request, prevent the crypto-asset user from carrying out reportable transactions through the provider."

Two details here are easily skipped. First, the block is not a matter of discretion for the provider but a duty. It cannot be waived as a goodwill gesture. Second, the clock runs from the original request, not from the formal notice. Anyone who ignores the first email and only pays attention at the notice stage has already used up part of the window.

The span is deliberately framed as a corridor. Before 60 days have elapsed the provider may not block; after 90 days it must. What happens inside that span depends on each provider's internal procedure. That fixes a window of roughly two to three months between the first request and the point at which trading ends.

For your planning that means this: once the first request arrives, you have plenty of time, but not unlimited time. Deal with it the same evening and the matter is closed. Leave it lying around and you need to remember when it came.

Precision pays off here, because the shorthand "the exchange freezes your money" is misleading. The law speaks of preventing the user from carrying out reportable transactions. What is meant are the operations that fall under the reporting duty, essentially exchange and trading activity. Withdrawing your own balance to your own bank account is not automatically part of that.

One provider describes exactly this distinction in its public help centre: users who do not supply their tax details first receive reminders; after that the account can be restricted so that trading ends while withdrawing the balance remains possible. How an individual provider implements that technically is its own decision, and the law only prescribes the lower limit. You should not rely on it: an account you can only empty is not a working account.

Unlike a supervisory measure, this is not a permanent state. The law expressly provides for the way back: the business relationship can be resumed as soon as the user supplies the information requested. So anyone who only takes notice once the block hits has to submit the details afterwards and is then able to trade again.

That takes the drama out of the process that some quarters attach to it, but it changes nothing about the practical nuisance. Between the block and reactivation lies a processing time nobody guarantees. Anyone who wants to react to a price move during that time cannot.

How well prepared are investors for this process? Rather than estimate, we measured it. On 17 August 2026 we queried the publicly searchable help centres of six crypto providers whose help interface is openly accessible, and evaluated every article that names DAC8, CARF, the self-certification, the tax identification number, or the Crypto-Asset Reporting Framework in its title or body. We checked Bitvavo, Bitpanda, BISON, Gemini, Luno and Bybit; every request returned HTTP 200. cryptoticker.io carried out this survey itself on 17 August 2026.

The result in numbers: five of the six providers carry a relevant help article at all, 24 in total. At one provider the search found none. The distribution is uneven: Bitpanda alone accounts for eleven articles, mostly explaining where to find the tax number in the respective country, including separate texts for Germany, Austria and Switzerland. BISON, the provider run by Boerse Stuttgart, carries four, Bitvavo four, Gemini three, Luno two.