UK Crypto Reporting Rules Started in 2026: What Casino Depositors Should Record

What changed in 2026?

The UK's Cryptoasset Reporting Framework, or CARF, began on 1 January 2026. In-scope cryptoasset service providers must now carry out due diligence, retain transaction records and report required information to HM Revenue & Customs.

The first reporting period runs from 1 January to 31 December 2026. Reports covering that period are due by 31 May 2027.

For someone who buys crypto through an exchange and sends it to a casino address, the central point is simple: transferring funds to an external wallet does not necessarily place the activity outside the reporting system.

CARF is a tax-transparency framework. It is not a casino-licensing rule, and a reported transfer does not automatically mean that tax is due.

Who may be asked for information?

HMRC says an individual using a cryptoasset service may be required to provide:

• full name
• date of birth
• normal home address and country
• country of tax residence
• a tax identification number, such as a National Insurance number or Unique Taxpayer Reference for an eligible UK resident

Cryptoasset service providers can include businesses that allow customers to buy, sell, transfer or exchange cryptoassets. Whether a particular wallet application falls within the rules depends on the service it performs; the word “wallet” alone does not decide the issue.

HMRC says a UK resident using a UK reporting provider will have the information linked to their UK tax record. If a UK resident uses a provider in another participating country, that country's tax authority may share the information with HMRC. Information can also move in the other direction for a non-UK resident using a UK provider.

The framework covers more than Bitcoin. HMRC's consumer guidance lists stablecoins, exchange tokens, utility tokens, security tokens and NFTs among the types of cryptoasset that can fall within the rules.

What transaction information is collected?

HMRC's guidance tells reporting providers to collect the following for cryptoasset transactions:

• transaction value
• cryptoasset type
• transaction type
• number of units

The annual reporting rules distinguish acquisitions and disposals against fiat, crypto-to-crypto exchanges and transfers.

CARF reporting is generally aggregated by cryptoasset and transaction category. The annual submission is therefore not necessarily a line-by-line explanation of why a customer made every transfer.

That distinction should not be mistaken for anonymity.

How are external-wallet transfers treated?

HMRC's June 2026 technical guidance addresses external wallet transfers directly.

When a reporting provider transfers crypto on behalf of a reportable user to a wallet that is not known to be associated with a virtual-asset service provider or financial institution, the provider must report that category distinctly. The report includes the cryptoasset type, aggregate number of units and aggregate fair-market value in fiat currency.

If the provider is unsure whether the destination belongs to another regulated provider, HMRC says it should still be treated as an external-wallet transfer for this purpose. If it knows that the destination belongs to a VASP or financial institution, the transaction is reported in the applicable transfer-by-user category instead.

The actual external wallet address is not included in the routine CARF submission. The reporting provider must nevertheless collect and retain that address or equivalent identifier for at least five years after the end of the reporting period. A tax authority can request it later if needed.

An exchange withdrawal to a casino-controlled address could therefore be classified as an external-wallet transfer, depending on what the exchange knows about the destination. HMRC's reporting category describes the destination relationship, not necessarily the transfer's gambling purpose.

It would be inaccurate to say that the annual file automatically labels every such transfer with a casino name. It would be equally inaccurate to say that the destination address leaves no record.

What records should a casino user retain?

CARF places reporting duties on providers, but users still need records that explain their own activity. An exchange's aggregate report may not preserve the context required to reconcile a casino deposit, returned funds and a later crypto disposal.

A practical record for each casino deposit or withdrawal should include:

• date and time
• asset and blockchain network
• number of units
• transaction hash
• sending and receiving addresses
• exchange or wallet used
• fiat value and the price source used at the time
• network and platform fees
• casino account transaction receipt
• whether the transfer was a deposit, refund or withdrawal
• any related conversion between assets

This is a practical recordkeeping checklist, not a quotation of an individual-user duty under CARF.

Download exchange and casino statements periodically rather than assuming they will remain available indefinitely. A transaction hash proves that a blockchain transfer occurred, but it does not by itself explain ownership, purpose, cost basis or how the casino credited it.

Keep records for both directions. A casino withdrawal returning to an exchange may be categorised differently from the original outward transfer. CryptoHut's withdrawal guide explains the payment records worth retaining.

Does CARF make a casino deposit taxable?

CARF does not decide the tax result. It changes collection and reporting, not the underlying rules used to calculate liability.

HMRC says selling, giving away, exchanging or making a purchase with cryptoassets may create a Capital Gains Tax question. Whether a casino-related transfer constitutes a disposal, and how any later receipt is treated, depends on the facts and applicable tax law.

Do not infer “tax due” merely because a transfer is reportable. Conversely, do not infer “not taxable” merely because funds moved to an external address or because the annual submission is aggregated.

Our crypto casino tax guide provides a general recordkeeping framework. Anyone with material gains, losses or cross-border activity should obtain advice based on their circumstances.

CARF does not verify a casino

The reporting framework says nothing about whether a casino is licensed, safe or legally available in a user's location. It also does not make an offshore operator compliant with UK gambling law.

Data collection by an exchange should not be presented as a casino endorsement. Licence verification, payment due diligence and bonus-term checks remain separate.

Moving funds through a self-custody wallet also does not erase the original exchange record. HMRC specifically requires providers to retain external destination addresses even though those addresses are not part of the routine annual submission. Our wallet guide explains the practical distinction between exchange custody and self-custody.

Collection is active; the first deadline is later

The live obligation in 2026 is data collection, due diligence and recordkeeping by in-scope providers.

The first reports have not already been filed for the complete 2026 year. They are due by 31 May 2027. Collection is active now; the first annual reporting deadline remains in the future.

The UK is also part of a wider international reporting system. HMRC's guidance states that participating countries can exchange information about users resident elsewhere. Using a foreign exchange is therefore not a reliable reason to assume that UK-resident activity will remain outside HMRC reporting.

The bottom line

From 2026, UK crypto reporting reaches beyond simple purchases and sales on an exchange. It includes transfers, including aggregate reporting of withdrawals to wallets not known to belong to another regulated provider.

The standard CARF report does not routinely include the actual external wallet address, but the provider must retain that address for at least five years. For casino users, the sensible response is accurate recordkeeping—not an assumption that every transfer creates tax or that an external wallet makes the transaction invisible.