UK crypto exchanges operate under a bifurcated regulatory framework that splits anti-money laundering oversight (enforced) from prudential and conduct regulation (pending). This creates specific operational constraints around customer onboarding, asset custody, and liquidity management that differ from both EU MiCA venues and offshore platforms. Understanding these mechanics matters for anyone evaluating execution quality, counterparty risk, or regulatory arbitrage opportunities across jurisdictions.
This article covers the UK registration regime, custody and segregation requirements, fiat gateway constraints, and the practical implications of operating without full prudential oversight.
Registration and AML Supervision
The Financial Conduct Authority requires all UK crypto exchanges to register under the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017. Registration requires demonstrating adequate systems and controls for customer due diligence, transaction monitoring, and suspicious activity reporting.
The FCA has maintained a restrictive registration posture. It does not publish formal rejection rates, but the register lists fewer than 50 approved crypto asset businesses as of recent counts, while many applications remain pending or withdrawn. Registration does not confer passporting rights into the EU post-Brexit, forcing firms to establish separate entities for cross-border service.
The registration process examines beneficial ownership structures, AML policies, senior management fitness, and technology controls. The FCA expects real-time transaction monitoring calibrated to risk typologies specific to crypto (structuring via multiple small deposits, rapid conversion chains, mixer exposure). Generic AML tooling built for traditional payments often fails these assessments.
Once registered, exchanges face ongoing supervision including thematic reviews, transaction data requests, and compliance attestations. The FCA has used Section 55J powers to impose restrictions on registered firms where controls degrade, including customer onboarding freezes and asset type limitations.
Custody Models and Client Asset Safeguarding
UK crypto exchanges typically custody client assets in one of three configurations: omnibus hot wallets, segregated cold storage, or third party qualified custodians. The FCA does not mandate specific custody arrangements under the current AML-only regime, creating significant variance in protection levels.
Exchanges holding client assets directly must implement operational controls around key management, withdrawal authorization, and disaster recovery. The absence of formal custody regulation means no statutory segregation requirement exists. Client assets may be commingled with exchange operational funds, creating exposure to exchange insolvency not present in FCA-regulated investment firms.
Some platforms adopt voluntary segregation, holding client crypto in separately identified wallets with independent attestation. This provides operational separation but not legal ring-fencing in UK insolvency proceedings. Crypto assets are intangible property under English law, subject to standard insolvency priority (unsecured creditors rank behind secured and preferential creditors).
Third party custody through a qualified custodian domiciled in a jurisdiction with explicit crypto custody regulation (Switzerland, Germany post-MiCA) offers stronger protection. The custodian’s insolvency remoteness from the exchange matters more than the exchange’s own financial health. Verify whether custody is actually segregated at the custodian level or merely sub-accounts within omnibus structures.
Fiat Payment Rails and Banking Access
UK exchanges rely on Faster Payments, CHAPS, and increasingly, embedded banking services for GBP on and off-ramps. Banking access has tightened considerably. Major UK clearing banks restrict crypto exchange accounts or impose enhanced monitoring, driving platforms toward challenger banks and payment institutions willing to serve the sector.
The Faster Payments rail supports instant GBP settlement up to £1 million per transaction, but banks apply their own limits. Exchange users commonly encounter per-transaction caps in the £10,000 to £50,000 range, with daily and monthly aggregate limits. These are bank risk controls, not Faster Payments protocol limits.
Delays occur when banks flag deposits to crypto exchanges for additional verification. The exchange has no visibility into this hold, creating user confusion. Withdrawals face similar scrutiny. Banks may request source of funds documentation from the exchange or the end user, particularly for first-time large withdrawals.
Some exchanges have obtained e-money licenses or embedded banking-as-a-service arrangements to reduce friction. These models internalize payment processing but introduce different risks (e-money insolvency priority, BaaS provider concentration).
Tax Reporting and HMRC Coordination
UK exchanges must maintain records suitable for HMRC transaction reporting, though no automatic reporting obligation currently exists equivalent to DAC8 in the EU. HMRC can and does issue information notices to exchanges requesting user transaction histories during investigations.
Exchanges typically provide users with transaction export tools but do not calculate tax liabilities. UK users remain responsible for calculating gains under the share pooling rules for fungible tokens and reporting on self-assessment returns. Same day and 30 day matching rules apply, complicating basis calculation for active traders.
Some exchanges have implemented voluntary sharing arrangements with HMRC for large or suspicious transactions. The legal basis for these disclosures is the Proceeds of Crime Act 2002 suspicious activity reporting framework, not tax-specific information sharing.
Worked Example: GBP Deposit to BTC Purchase
A user initiates a £25,000 Faster Payments transfer from a Barclays current account to a registered UK exchange at 09:00 on a weekday.
The exchange’s partner bank (a challenger institution) receives the payment at 09:02. Automated screening flags the payment for manual review due to the amount and crypto destination. The bank holds the funds pending review, which completes at 14:30. The exchange credits the user’s GBP balance at 14:45.
The user places a market order for BTC. The exchange matches this against its internal order book or routes to external liquidity providers. The spread is 0.15% wider than Binance International spot due to lower UK platform liquidity. The exchange charges a 0.5% taker fee. Settlement is immediate in the user’s exchange wallet.
The user requests withdrawal to a personal hardware wallet. The exchange batches BTC withdrawals every four hours to minimize network fees. The transaction is broadcast at 16:00, paying a moderate fee rate. It confirms in the next block. The exchange records the user’s cost basis in GBP terms at the execution price for export to tax software.
Common Mistakes and Misconfigurations
- Assuming FCA registration confers investor protection equivalent to authorized investment firms. Registration is AML-only oversight. No compensation scheme, conduct rules, or prudential capital requirements apply.
- Relying on exchange-provided cost basis data without verification. Exchanges export transaction history but do not apply HMRC’s same day and 30 day matching rules. Most export tools use average cost or FIFO, which is incorrect for UK tax.
- Treating exchange GBP balances as protected deposits. These are unsecured exchange liabilities, not FSCS-protected bank deposits, even when the exchange uses an e-money license or banking partner.
- Ignoring custody model differences across UK platforms. “FCA registered” does not imply custodial standards. Some platforms custody client assets in hot wallets without segregation.
- Overlooking payment limit fragmentation. The £1 million Faster Payments limit is theoretical. Actual limits depend on the exchange’s bank relationship and that bank’s risk appetite.
- Assuming instant GBP deposits. Bank-side AML holds are invisible to users and can delay deposits by hours or days, particularly for new accounts or large amounts.
What to Verify Before You Rely on This
- Current FCA registration status on the Financial Services Register. Registration can be suspended or varied with conditions restricting activities.
- Custody arrangements: omnibus vs segregated, hot vs cold, self-custody vs third party. Request attestation reports if available.
- Identity and domicile of the banking partner or e-money provider. Some exchanges rotate partners, changing risk profiles.
- Payment limits specific to your bank and the exchange’s receiving bank. These are bilateral arrangements, not published standards.
- Fee schedules for deposits, withdrawals, and trading. Structure varies (maker/taker, flat, percentage) and changes frequently.
- Supported asset list and whether assets are available for withdrawal or trading only. Some platforms restrict withdrawals for certain tokens.
- Insurance coverage specifics. Generic “insurance” claims often cover only hot wallet hacks, not insolvency, fraud, or cold storage loss.
- Tax export functionality and whether it includes all trade types (spot, staking, referral bonuses). Many tools omit non-trading events.
- Withdrawal batching schedules and minimum/maximum withdrawal amounts. These affect liquidity access during volatile periods.
- Current GBP deposit and withdrawal processing times based on recent user reports, not marketing materials.
Next Steps
- Cross-reference at least two UK registered exchanges’ fee structures and custody models for your use case. Liquidity and protection vary substantially across registered platforms.
- Test small GBP deposits and withdrawals with your specific bank to identify holds or limits before committing large amounts. Document typical processing times.
- Set up independent tax tracking using software that implements HMRC’s share pooling rules. Do not rely solely on exchange exports for tax reporting.
Category: Crypto Exchanges
