Crypto.com Tax UK: Does It Report to HMRC?

Crypto.com is one of the most widely used crypto platforms in the UK, thanks to its retail app, the CRO ecosystem, and the Crypto.com Visa card. From 1 January 2026, exchanges serving UK customers report your transaction history to HMRC under CARF (the Crypto-Asset Reporting Framework). HMRC will know what you bought, sold, and earned. The question is whether your Self Assessment return matches what they have.

Here is the problem: the export and tax statements you can pull out of Crypto.com are not built around HMRC's rules. UK Capital Gains Tax uses Section 104 pooling — a weighted-average cost basis — not the first-in-first-out method most exchange reports default to. And Crypto.com only ever sees what happened inside Crypto.com. The moment you use another exchange, the Visa card, or any DeFi, those numbers are incomplete.

This guide explains exactly how Crypto.com transactions are taxed under HMRC rules, why its built-in figures fall short, where the hidden disposals hide, and how to file correctly — especially if you also use DeFi.

Does Crypto.com report to HMRC?

Yes. Under CARF, which came into effect on 1 January 2026, crypto platforms with UK customers must collect and report transaction data to HMRC. The first reports are due by 31 May 2027, covering the 2026 calendar year. As a platform that serves UK users, Crypto.com is in scope — the same as Coinbase, Binance, and Kraken.

What HMRC receives includes your name, address, tax identification number, and a full record of acquisitions, disposals, and income events. This is transaction-level data, not a summary. If your Self Assessment does not line up with what the exchange reported, HMRC has the tools to flag the gap. The CARF 2027 readiness page walks through how to reconcile your return before the data lands.

Why Crypto.com's tax report doesn't work for UK investors

Crypto.com can generate transaction statements and a tax summary, but they have two fundamental problems for UK investors.

First, the cost basis method is wrong. Most exchange tax reports — Crypto.com included — lean on first-in-first-out matching, which is correct under US rules but not accepted by HMRC. HMRC requires Section 104 pooling, a weighted average across every unit of a token you hold. The two methods produce different gains — sometimes by thousands of pounds.

Second, Crypto.com only sees Crypto.com. If you also bought ETH on Coinbase, received ETH as staking income from Lido, or swapped USDC for ETH on Uniswap, every one of those acquisitions belongs in the same Section 104 pool. Crypto.com has no visibility into any of it, so its cost basis is structurally incomplete.

Section 104 pools are per-asset, not per-platform

This is the single most important concept for UK crypto tax, and the reason no single exchange can give you the right number on its own.

Under HMRC rules you maintain one Section 104 pool per token. Not per exchange, not per wallet — per token. Every acquisition of ETH, wherever it happened, goes into the same ETH pool with a single weighted-average cost.

The difference grows with every additional source of the same token. A Crypto.com user who also holds the asset on another exchange, stakes it, or earns card cashback in it can see far larger discrepancies than this simple example.

What Crypto.com transaction types mean for HMRC

Crypto.com uses its own labels for transaction types. Here is how each one maps to HMRC tax treatment:

How to export your Crypto.com CSV — App vs Exchange

Crypto.com runs two separate products, and the export path is different for each. Most retail users only have the first.

• The Crypto.com App— the retail mobile app for buying, selling, Earn, and the Visa card. In the app, open Accounts, tap the Transaction History / export icon, choose your date range (use the full history, not just the current tax year), and request the CSV. Crypto.com typically emails the file to you.
• The Crypto.com Exchange— the separate order-book trading platform at crypto.com/exchange. If you traded there, export your trade and transaction history separately from the Exchange interface. The App export will not contain Exchange trades, and vice versa — you need both files if you used both products.

Whichever export you use, do not rely on a built-in tax summary as your filing figure — it does not apply Section 104 pooling across your other platforms. The raw transaction CSV is the file you upload to ChainTax, which rebuilds the pool correctly.

How HMRC taxes Crypto.com Earn (staking) rewards

Crypto.com Earn pays rewards on tokens you deposit — the retail equivalent of staking. Like other staking and reward products, HMRC treats these receipts as miscellaneous income, not capital gains. They are taxed at your income tax rate (20%, 40%, or 45%) based on the GBP market value of the reward on the date it lands in your account.

Income from crypto goes on SA100 (your main Self Assessment return) under "Other income" — not on SA108. This is a common mistake. For the full treatment across providers, see how to report staking rewards to HMRC.

Crucially, each reward also enters your Section 104 pool as an acquisition at that same fair market value. That increases your pool's total cost basis, which reduces the capital gain when you eventually sell. If your tax tool ignores the reward or records it at zero, you will declare income you did pay tax on and overpay CGT later. Both halves need to be captured.

Crypto.com Visa card cashback and CRO rewards

The Crypto.com Visa card pays cashback in CRO, and historically the cashback rate depended on how much CRO you staked to unlock a card tier. However it is earned, the cashback arrives as a new crypto asset — and that is where the tax treatment gets subtle.

Cashback you earn on your own spending is most defensibly a non-taxable rebate, not income — you did nothing for it but buy your own goods, which HMRC's long-standing cashback practice (SP 4/97; BIM100210) treats as a discount, not a recognisable service. So there is no Income Tax when it lands. But the CRO is now an asset you hold, so a later sale, swap or spend is a Capital Gains event — and it sits in your Section 104 pool until you dispose of it.

Here the treatment is genuinely contested. HMRC's default rule for an asset acquired for no consideration (TCGA 1992 s.17(2); CG14550) points to a nil cost basis— so the full sterling proceeds are taxed when you dispose — while a minority of advisers argue the CRO should enter your pool at its market value on receipt. There is no crypto-specific HMRC guidance on card cashback, so this is a reasoned position by analogy; confirm with a qualified adviser before you file.

Keep card cashback separate from Crypto.com Earn and CRO staking rewards: those are earned for locking up or providing capital, so they are miscellaneous income at market value on receipt (CRYPTO21200), and that value becomes their cost basis. And if you trade crypto as a financial trader, even spend-cashback can be a taxable trading receipt (BIM100210).

The hidden disposals most Crypto.com users miss

The disposals that trip people up are the ones that do not feel like selling. On Crypto.com, three patterns account for most of them:

1. In-app Swap and Convert.When you swap one token for another — say CRO for ETH, or USDC for BTC — HMRC sees two events: a disposal of the outgoing token at its GBP market value, and an acquisition of the incoming token at the same value. No GBP changes hands, but the disposal is still taxable. This is identical to how HMRC treats DeFi token swaps.
2. Card spending. As above, every crypto-funded card purchase disposes of the crypto used. Frequent card users often have the most disposals and the least awareness of them.
3. Spending Earn or cashback rewards.Rewards you received as income still sit in your pool. The day you swap or spend them is a fresh disposal, measured against the cost basis they entered at — not against zero.

Each of these is a real CGT event. Miss them and your declared disposals will not match the holdings HMRC can infer from the exchange's CARF report. You can calculate your Crypto.com gains across all of these event types automatically rather than reconstructing them by hand.

What if I also use DeFi? — and how ChainTax handles it

This is where most crypto tax tools break. If you buy ETH on Crypto.com and then deposit it into Aave, swap it on Uniswap, or bridge it to Arbitrum, your Section 104 pool needs to reflect all of that activity — not just what happened inside the Crypto.com app.

The same-day and Bed & Breakfast rules also operate across platforms. Sell ETH on Crypto.com on Monday and buy ETH via a Uniswap swap on Wednesday, and the B&B rule matches those transactions — even though they happened on different platforms. No single-platform tool can detect this.

ChainTax is built for exactly this scenario:

1. Import your Crypto.com CSV. Upload your App (and, if you used it, Exchange) transaction history. Buys, sells, swaps, Earn rewards, and card activity are each categorised for HMRC. Classified as Disposal, Income, or Transfer as appropriate.
2. Import your other exchanges too. Add Coinbase, Binance, or Kraken CSVs. Every exchange feeds the same tax engine.
3. Connect your DeFi wallets. Add your Ethereum, Arbitrum, Optimism, Base, or Polygon addresses. ChainTax scans your full on-chain history and categorises every transaction using 32 protocol-specific classifiers.
4. Unified Section 104 calculation.Crypto.com activity, other exchange trades, and DeFi are merged into a single S104 pool per token. Same-day and B&B matching applies across every source.
5. SA108 boxes auto-filled.Boxes 13.1–13.8 are computed directly from the unified calculation. Every disposal shows the matching rule used and the full gain working.

Crypto.com sits firmly in the centralised-exchange camp, but the moment you touch DeFi the two worlds meet in one pool — see centralised exchange vs DeFi tax treatment for the full picture.

Weighing up your options first? See how ChainTax compares to Koinly, CoinTracker, and Recap.