CryptaCount
EN
EnglishENDeutschDEEspañolESFrançaisFRItalianoIT日本語JA한국어KONederlandsNLPolskiPLPortuguêsPT
Log in Start Free

UK Banks Face Over 10,000 Crypto Transfer Complaints

CryptaCount Editorial · · 10 min read
AML / KYC / LICENSING UK Banks Face Over 10,000 CryptoTransfer Complaints

More than 10,000 complaints were filed against UK banks in a single 90-day window over restrictions on transfers to crypto platforms, according to data published by advocacy group Stand With Crypto. The figures, covering May to August 2026 and reviewed by Cointelegraph, reveal a banking access problem that is already affecting thousands of retail customers and crypto businesses alike — and one that the UK's incoming 2027 regulatory regime may do little to fix.

UK Banks Face Over 10,000 Crypto Transfer Complaints

What the Complaint Data Shows

Stand With Crypto reported that 9,803 individuals submitted 10,092 complaints through the group's dedicated online tool during the 90-day period. The complaints were directed at UK-based banks over restrictions placed on outbound transfers to cryptocurrency platforms.

Which Banks Received the Most Complaints

Lloyds Banking Group received the highest number of complaints at 2,297, followed by Barclays with 1,569 and NatWest Group with 1,278. The data does not necessarily reflect the strictness of each bank's policy: Lloyds was separately classified as having no published crypto transfer restrictions, which suggests that even the absence of a formal policy does not prevent customers from running into practical difficulties.

Transaction Limits and Outright Bans

Barclays and HSBC UK were identified as capping crypto-related transfers at £2,500 per transaction and £10,000 over any rolling 30-day period. Six banks — including Starling Bank, TSB, and Chase UK — were listed as banning crypto transfers entirely. Revolut, despite also receiving complaints, carries a note on its official support page that transfers to certain cryptocurrency exchanges are unsupported; Stand With Crypto characterised this as a technical constraint rather than a deliberate policy position.

The table below sets out the reported restriction categories for the banks named in the complaint data.

Bank Reported Restriction Complaints Received
Lloyds Banking Group No published restriction 2,297
Barclays £2,500/tx; £10,000/30 days 1,569
NatWest Group Not specified in report 1,278
HSBC UK £2,500/tx; £10,000/30 days Not specified
Starling Bank Full ban on crypto transfers Not specified
TSB Full ban on crypto transfers Not specified
Chase UK Full ban on crypto transfers Not specified
Revolut Some exchanges unsupported (technical) Not specified

Why Banks Are Restricting Crypto Transfers

UK banks have long pointed to anti-money laundering obligations and fraud risk as the rationale for limiting or blocking payments to crypto platforms. The FCA's existing requirements under the Money Laundering Regulations mean that banks must assess the risk profile of the counterparties their customers transact with. Where a crypto exchange or wallet provider is not on the FCA's registered or authorised list, banks may treat transfers to it as higher risk by default.

The AML and Fraud Argument

Banks are not acting without precedent. The Payment Systems Regulator has previously addressed how firms should handle authorised push payment fraud, some of which involves crypto-related scam networks. The concern is that a customer who transfers funds to a crypto platform may, in certain cases, be the victim of a scam rather than a willing investor. From a bank's liability perspective, a blanket restriction or low cap can appear easier to defend than a case-by-case assessment.

The difficulty is that this logic treats every crypto transfer as inherently suspicious, regardless of whether the destination platform is a properly registered UK crypto asset business. That is a position that sits uneasily with the government's stated ambition to make the UK a global hub for digital assets.

The Regulatory Gap Banks Are Exploiting

There is currently no specific rule in the FCA's handbook that requires banks to treat transfers to FCA-registered crypto asset firms the same way they would treat transfers to other regulated financial services firms. The incoming 2027 crypto authorisation regime under the Financial Services and Markets Act 2000 will require crypto firms to obtain full FCA approval, but it does not compel banks to change their payment policies in parallel. Nick Jones, CEO of Zumo, made exactly this point: a crypto firm could clear every hurdle to obtain FCA authorisation in October 2027 and still find itself unable to open or maintain a UK business bank account.

What the 2027 FCA Regime Does and Does Not Cover

The UK's incoming crypto regulatory framework, expected to take effect in October 2027, will require firms offering crypto asset services to UK customers to be fully authorised by the FCA. This covers activities such as operating a crypto exchange, providing custody services, and facilitating crypto lending. It is a significant step toward bringing crypto businesses within the same supervisory perimeter as other regulated financial services.

Banking Access Falls Outside the Authorisation Perimeter

What the regime does not address is the relationship between banks and their crypto-related customers. Banking access is governed by separate conduct rules, contract law, and the FCA's banking conduct of business requirements — none of which currently oblige a bank to serve a crypto firm or to process a customer's transfer to a crypto platform. The complaint data therefore points to a structural gap: licensing and authorisation reform will not, on its own, resolve the payment access problem that thousands of customers and businesses are already experiencing.

For accounting firms and CFOs advising clients who operate in the crypto space, or who hold digital assets on their balance sheets, this distinction matters enormously. A client may be fully compliant, properly registered, and operationally ready for the 2027 regime, yet still face disruption if their primary bank decides to restrict or exit the relationship. Tracking those banking dependencies now is a practical step that belongs in any crypto-focused client risk review.

Understanding the broader supervisory direction the FCA is taking is also useful context here. Our analysis of FCA and AI-driven crypto supervision signals sets out how the regulator is evolving its monitoring approach, which has direct implications for how compliant firms can demonstrate their risk controls to banking partners.

Implications for Accounting Firms and CFOs

The complaint data is not just a consumer story. For professional service firms and corporate finance functions, it raises several practical concerns that need to be addressed before the 2027 deadline arrives.

Client Banking Relationship Risk

If your firm acts for crypto businesses or for companies that hold digital assets, the banking restrictions described above represent a counterparty operational risk. A client that cannot process fiat on-ramps or off-ramps smoothly will face cash flow disruption, potential settlement failures, and in extreme cases the need to restructure their banking arrangements entirely. That has direct consequences for your audit, accounting, and tax advisory work: going concern assessments, liquidity disclosures under FRS 102 or IFRS, and the treatment of pending transfers in the accounts all become more complex when banking access is uncertain.

Transaction Records and Crypto Bookkeeping Software

When a bank blocks or delays a transfer to a crypto platform, it creates a reconciliation problem. The client's bank statement will show a blocked or returned payment, while the crypto platform may show no corresponding receipt. For firms using digital asset accounting software to maintain the books of crypto-active clients, these mismatches need to be identified and documented promptly. The cost basis of any intended acquisition is also affected if a transfer is blocked mid-process and the client subsequently re-executes at a different price.

Maintaining clean, timestamped records of every attempted and completed transfer is essential — both for tax reporting purposes and for any future compliance review by the FCA or HMRC. Speaking of HMRC, the penalty framework for digital platform operators is already tightening; our breakdown of HMRC penalties for digital platform operators explains what firms need to have in order before those rules bite.

Due Diligence on Banking Partners

CFOs and finance directors at crypto firms should carry out a structured review of their banking relationships, specifically asking which of their banks have published restrictions on crypto-related transfers, and whether those restrictions apply to business accounts as well as retail customers. The Stand With Crypto data focuses on retail-level complaints, but the same banks are likely applying analogous risk-based policies to their business banking divisions. Knowing your bank's position before you need to act on it is basic treasury risk management.

The Broader Policy Tension

The UK government has positioned itself as a destination for crypto and digital asset businesses, with the Treasury and the FCA both investing in the regulatory architecture needed to attract firms that might otherwise choose the EU's MiCA framework, Singapore's MAS regime, or Dubai's VARA regime. The Stand With Crypto complaint data cuts against that narrative. If customers and businesses cannot reliably move money between their bank accounts and crypto platforms, the practical utility of a UK regulatory licence is reduced.

Jones's point about a level playing field is worth taking seriously in that context. Regulatory clarity from the FCA helps, but it only reaches the parts of the financial system the FCA directly supervises. The payment infrastructure that connects banks to crypto platforms sits in a different part of the regulatory architecture, and closing that gap may require coordinated action between the FCA, the Payment Systems Regulator, and the banks themselves — none of which is currently mandated by the 2027 framework as it stands.

For firms building compliance programmes now, the practical takeaway is straightforward: do not assume that FCA authorisation will resolve banking access. Treat the two as separate workstreams and plan accordingly.

UK Banks Face Over 10,000 Crypto Transfer Complaints

Frequently Asked Questions

Can a UK bank legally block a transfer to a crypto platform?

Yes. Banks have broad contractual discretion to restrict or refuse payments they consider high risk, subject to giving reasonable notice under their terms and conditions. There is currently no FCA rule that specifically prevents a bank from blocking transfers to crypto platforms, even those that are FCA-registered. Customers who believe a restriction is being applied unfairly can complain to the Financial Ombudsman Service.

Will the FCA's 2027 crypto regime change how banks treat crypto transfers?

Not directly. The 2027 authorisation regime applies to firms providing crypto asset services, not to the banks that process payments. Banks will continue to set their own payment policies under existing conduct rules. It is possible that a larger pool of FCA-authorised crypto firms will make banks more comfortable over time, but no regulatory obligation currently compels that outcome.

What should a CFO do if their bank restricts crypto-related payments?

Start by documenting the restriction in writing and obtaining the bank's stated rationale. Review your treasury policy to identify whether an alternative banking relationship is needed. Notify your accounting and tax advisers so that any disruption to transfer timelines is captured in the accounts and cost basis records are adjusted if any intended acquisitions were delayed or cancelled.

How do banking restrictions affect crypto tax reporting?

A blocked transfer that is subsequently retried at a different date and price will affect the cost basis of the asset acquired. Under HMRC's rules for pooling and same-day and 30-day matching, the timing of an acquisition matters. Firms and individuals should ensure that their crypto bookkeeping software records not just completed transactions but also attempted transactions and the circumstances of any delay or failure.

Is this problem unique to the UK?

No, but the UK context is particularly pointed given the government's stated ambition to be a global crypto hub. Other jurisdictions have seen similar tensions between bank risk policies and digital asset activity. The Stand With Crypto complaint data is UK-specific, but the underlying regulatory gap between banking supervision and crypto asset supervision exists in multiple markets.

Source: Cointelegraph

UKGeneralEffectiveAML/KYC & Licensing

Related articles

AML/KYC & Licensing
HMRC Updates MLR Fee Payment Guidance: What Crypto Firms Must Know
AML/KYC & Licensing
HMRC Publishes Penalty Factsheet for Digital Platform Operators
AML/KYC & Licensing
ACCA's 2026/27 AML Return: Document Upload Raises the Bar
AML/KYC & Licensing
What a High-Quality Crypto SAR Looks Like in 2026