Skip to content

HMRC Disclosure & Compliance

Can HMRC Track My Crypto Wallets? What They Can and Cannot See

8 min read

HMRC can see more crypto activity each year through KYC exchange data, the CARF reporting framework (collecting from 1 January 2026) and public blockchains anyone can read, though it's data-matching, not omniscience.

Can HMRC actually see what you're doing with your crypto, or is it still mostly invisible? It sees more than it used to, and from 2027 it'll see a lot more. But it's data-matching and investigation, not a live feed of your wallet.

The short answer: yes, increasingly, and here is how

HMRC can see crypto activity through three overlapping channels: KYC data from exchanges, systematic reporting under the Cryptoasset Reporting Framework (CARF) from 2026, and the public blockchains themselves, which anyone can read. None of these channels gives HMRC a complete, real-time view of every wallet; collectively they give HMRC meaningful and growing data-matching capability. The key phrase is data-matching: HMRC uses data to flag discrepancies between what exchanges report and what appears (or does not appear) in your Self Assessment return, then decides whether to write to you or open an enquiry.

Three things HMRC cannot do automatically: it cannot see the private keys to your wallet, it cannot read your intentions from on-chain data, and data-matching alone does not produce a tax assessment. A discrepancy triggers a process. You are not assessed until the facts are established.

What HMRC can and cannot see Status Notes
Your identity at a UK exchange (KYC) Can see Exchanges hold this under AML rules; HMRC can require disclosure
Your exchange transaction history (from 2026) Can see (systematic from 2027 report) CARF: platforms collect from 1 Jan 2026; first report due by 31 May 2027
On-chain flows on public blockchains Publicly visible Bitcoin, Ethereum and most chains are transparent ledgers
Linking on-chain addresses to your identity Possible at the on/off-ramp Harder for purely self-custodied activity with no exchange contact
Transactions on privacy chains or mixers Harder to trace Not invisible: in an enquiry you'll still need records showing where the coins came from and went
Your intentions or reasons for a trade Cannot see directly Established through correspondence and records in an enquiry

Channel one: exchange data and KYC

Every UK-regulated crypto exchange and many major international ones operating in the UK must carry out Know Your Customer (KYC) checks under anti-money-laundering rules. This means the exchange holds your name, address, date of birth, and often a copy of your identity documents. It also holds a record of every trade, deposit, and withdrawal on your account. The same goes for a crypto debit card, including one sold as "no KYC": paying with crypto is a disposal for Capital Gains Tax, and under CARF you have to give your name, date of birth, address and tax number to every crypto service you use, wherever it's based (gov.uk).

HMRC also has powers, separate from CARF and older than it, to ask a business for information (Schedule 36 to the Finance Act 2008). And the government has announced that it'll extend one of them, the Financial Institution Notice, to cryptoasset service providers from Royal Assent of Finance Bill 2026-27; it isn't law yet (HMRC's note on the change). So if you used an exchange, HMRC may already be able to get data about your account. People tend to think crypto is anonymous, when the exchange they use has already linked their real identity to every transaction.

Do Coinbase or Binance report to HMRC? Under CARF it depends where the platform is based, not on its name. A UK-based platform reports to HMRC directly. If you live in the UK but use a platform based in another country that follows the same rules, that country's tax authority will share your information with HMRC. That information sharing is how HMRC can track crypto on non-UK exchanges.

Channel two: CARF makes exchange reporting systematic

The Cryptoasset Reporting Framework (CARF) is an OECD-designed international standard that the UK has adopted. It moves exchange data reporting from ad-hoc HMRC requests to an annual systematic obligation. Under HMRC's CARF collection rules, UK cryptoasset platforms must collect user and transaction data from 1 January 2026 (CRYPTO10410). The first report to HMRC covers the 2026 calendar year (1 January to 31 December 2026) and must be submitted by 31 May 2027. Annual reports follow by 31 May each year thereafter.

This is what the "HMRC cannot see my exchange" era ending means in practice: your 2026 exchange activity will land with HMRC by 31 May 2027, automatically, without any individual request. The calendar year straddles two tax years, so it's checked against your Self Assessment returns for 2025/26 (due 31 January 2027) and 2026/27 (due 31 January 2028). If they don't match what the exchange reports, that discrepancy can be flagged through data-matching. CARF does not reach back to collect data from years before 2026 under this framework, though those years remain open to investigation under existing powers.

The full timeline is in our CARF reporting rules explainer.

Channel three: on-chain analytics

Public blockchains such as Bitcoin and Ethereum record every transaction on a transparent, permanent ledger. Anyone, HMRC included, can see every address, every transaction amount, and every movement of funds. The blockchain doesn't know your name, but it knows every address that has ever held or moved those tokens.

HMRC's own manual puts it plainly: crypto transactions "usually occur on a public blockchain" and "can be viewed digitally and checked using records obtained from a wallet" (CRYPTO10400). So in an enquiry, HMRC can line your wallet records up against the chain. The link to your identity comes at the on/off-ramp: the point where your funds moved from or to a KYC exchange, whose records say who you are.

HMRC's published guidance and reports don't name any tracing tools. It describes its crypto work as combining education, targeted communications, specialist compliance work and "improved use of data and intelligence" (HMRC, October 2026), and its annual report for 2025 to 2026 credits AI and advanced analytic tools across its compliance work generally, not crypto in particular. So treat the chain as something HMRC can read and check, not something it watches in real time. There are real limits too: cross-chain bridges and wrapped tokens make a trail harder to follow, and purely self-custodied activity with no exchange contact is harder to put a name to.

The "self-custody wallet they cannot see" belief

A common assumption is that funds held in a self-custody wallet (a hardware wallet or a non-custodial software wallet) are invisible to HMRC because there is no exchange in the middle. This is weaker than it sounds for anyone who has ever used an exchange.

If you ever moved funds between a self-custody wallet and a KYC exchange, that on/off-ramp transaction is on the public blockchain. The exchange knows your identity. Anyone reading the chain, HMRC included, can follow the flow between your exchange deposit address and your self-custody wallet. The connection exists; it takes effort to trace, not impossibility.

Can your bank see where the money came from? When crypto proceeds land in your account, that's the off-ramp, and HMRC expects you to keep your bank statements and wallet addresses in case of an enquiry (CRYPTO10400). If you've never touched a KYC exchange and bought crypto peer-to-peer in cash, the identity link is much weaker. Even then, turning crypto into money you can spend in the UK without it eventually hitting a payment system is difficult in practice.

The honest conclusion: self-custody is not invisibility. It reduces the directness of HMRC's data access, particularly for amounts that never touched an exchange. It does not eliminate it.

What HMRC can do with this data

HMRC uses exchange data, and from 2027 CARF data, for data-matching: comparing what platforms report about your activity against what appears in your Self Assessment return. Where there is a gap, a discrepancy, or no return at all for a year with apparent taxable activity, HMRC's compliance teams can decide to act.

Often the first step is a nudge letter: a letter saying HMRC has information suggesting you may have crypto gains to declare, inviting you to review and correct your return. Nudge letters are not assessments and are not enquiries. They are a prompt. Responding is always the right move; ignoring a nudge letter is not.

Had one? Here's what to do when an HMRC crypto nudge letter arrives.

Where data-matching reveals more significant discrepancies, HMRC can open a formal enquiry under section 9A of the Taxes Management Act 1970, or make a discovery assessment. Where the underpayment was deliberate, HMRC can go back 20 years. For careless behaviour the window is 6 years; for cases where reasonable care was taken it is 4 years. These year counts are from HMRC's cryptoasset disclosure guidance, and the 4 and 6 apply if you're in Self Assessment. If you never told HMRC you needed to file, it can go back up to 20 years however careful you were otherwise, unless you had a reasonable excuse (Taxes Management Act 1970, section 36(1A)). Penalties vary by behaviour and by whether the disclosure is unprompted or prompted; one made before HMRC has reason to look at you gets the lowest penalty for your behaviour.

What HMRC's data-matching cannot do automatically is produce a tax bill. Tax due on crypto must be calculated on the actual facts: which disposals were made, at what prices, with what allowable costs under the s104 pooling rules, applying the same-day and 30-day override rules. Data-matching flags the gap; you or an accountant fill in the facts.

Calculator

Crypto Disclosure Scope Estimator

Pick the behaviour that fits, say whether you ever told HMRC you had tax to pay, and enter a rough figure for the tax you think went unpaid each year. You'll see how many years HMRC can go back and the total tax at stake. Penalties come on top as a percentage of that tax, so the tool gives you HMRC's ranges rather than one figure.

HMRC sorts underpaid tax into reasonable care, careless or deliberate. Where you filed returns, the band sets how far back HMRC can go: 4, 6 or 20 years.

If you never told HMRC you had income or gains to pay tax on, it can go back up to 20 years however careful you were otherwise, unless you had a reasonable excuse.

£

A rough estimate of the tax underpaid each year. Used to illustrate the total exposure.

Your result

Your answer's ready. Press below to see it.

If your history is untidy: the window to act

The first CARF report is due with HMRC by 31 May 2027. That's the most concrete near-term date in the timeline. A disclosure made through HMRC's cryptoasset disclosure service is unprompted if you'd no reason to believe HMRC had found the problem or was about to, and that carries the lowest penalty range for your behaviour band. That gets harder to show once you know your details have gone to HMRC, and once HMRC has told you it's checking your return, a disclosure about the same thing is prompted and the penalty range rises.

If you have unreported gains or income from crypto, whether from sales, crypto-to-crypto swaps, staking rewards, or mining, the practical window to get ahead of the data is now. The crypto disclosure estimator gives you a rough sense of what tax exposure and penalty exposure might look like based on the facts you input. It's an estimate, not a filing-ready figure.

For the wider picture of how many UK adults hold cryptoassets and when CARF data starts reaching HMRC, see the UK Crypto Tax Compliance Index. HMRC publishes no crypto-specific tax gap, so the index states none; it sets out the verified ownership and reporting timeline instead.

If you want to understand the scope of disclosure required and get the calculation right, the HMRC disclosure service is the right starting point. The aim's an accurate disclosure, made before HMRC has reason to look, that claims every allowable cost and loss and keeps the penalty as low as your facts allow.

Want this checked against your specific situation?

Leave your details and a one-line summary. A specialist will come back to you, with no obligation.

We'll only use your details to respond to your enquiry. We don't pass them to any other firm. See our Privacy Policy.

Common questions

Can HMRC track my crypto wallet?
Increasingly, yes. HMRC has three channels: KYC exchange data (your exchange knows who you are and can be required to share it), the CARF framework (systematic collection from 1 January 2026), and the public blockchain itself, which anyone can read and HMRC can check against your wallet records in an enquiry. It's data-matching capability, not real-time omniscience.
Does HMRC know about my crypto?
If you used an exchange, HMRC may already hold information about you, because it has powers to ask businesses for information. From 2027 onwards, HMRC will receive systematic CARF reports covering 2026 activity, with the first due by 31 May 2027. Earlier years remain open to investigation using existing powers.
Can HMRC see a self-custody or hardware wallet?
The blockchain itself is public, so on-chain flows are visible to anyone. A self-custody wallet has no direct KYC link, but if you ever moved funds to or from a KYC exchange, that on/off-ramp creates an identity link that anyone reading the chain can follow.
How does HMRC get crypto data?
Three routes: (1) exchange KYC data under HMRC information powers, (2) systematic CARF reporting from UK platforms from 2027 covering 2026 activity, with platforms in other CARF countries reporting to their own tax authority, which will share UK users' details with HMRC, and (3) the public blockchain, which HMRC can check against your wallet records in an enquiry.
Does CARF mean HMRC can see everything now?
CARF makes exchange data systematic from 2026, not retroactively comprehensive. It does not give HMRC instant access to all historic years under this framework, though earlier years remain open to investigation under existing powers.
Will HMRC automatically investigate me?
No. Data-matching can flag a discrepancy and lead to a nudge letter or open an enquiry; it does not produce an automatic tax assessment. If you receive a nudge letter, responding is always better than ignoring it.
What should I do if I have unreported crypto?
Use HMRC's dedicated cryptoasset disclosure service at gov.uk/guidance/tell-hmrc-about-unpaid-tax-on-cryptoassets. An unprompted voluntary disclosure, made before HMRC has any reason to be looking at you, typically secures a lower penalty than a prompted one. The window before the first CARF report lands is the best time to act.

Need help with your crypto tax position?

Tell us about your situation and we will explain what is involved.

Step 1 of 2 · About you

Optional: a bit more detail (helps us prepare)