British crypto buyers have a problem, and it usually starts at their own bank. Stand With Crypto UK says it collected 10,092 complaints about blocked or restricted transfers to crypto platforms over a 90-day stretch.
The most surprising name at the top of the list is Lloyds Banking Group. It drew more complaints than any other lender, even though it has no published policy restricting crypto transfers.
Inside the complaint data
The report is titled “Blocked: Britain’s Crypto Access Problem.” It covers submissions made between May and August 2026 through the group’s online complaint tool.
A total of 9,803 people filed the 10,092 complaints. That gap suggests some users hit a wall more than once and decided to say so again.
Every complaint concerned moving ordinary money, or fiat, to platforms registered with the Financial Conduct Authority (FCA). These are exchanges the UK regulator has already approved to operate, not offshore venues of uncertain origin.
Lloyds Banking Group, which also owns Halifax and Bank of Scotland, led the count with 2,297 complaints. That works out to over 22% of all submissions.
Barclays came second with 1,569 complaints. NatWest Group followed with 1,278.
Together, those three banking groups accounted for approximately 51% of everything the campaign received.
The geographic spread is just as notable. Complaints came in from all 650 UK parliamentary constituencies, which means no member of Parliament can claim this is somebody else’s local issue.
A patchwork of bans and caps
The report sorts UK banks into rough categories based on how they treat crypto payments. Six banks, including Starling Bank, TSB and Chase UK, are listed as banning crypto-related transfers outright.
Others allow transfers but cap them. Barclays and HSBC UK apply limits of £2,500 per transaction and £10,000 per 30 days, according to the report.
NatWest is described as using stricter daily or rolling caps.
Lloyds sits in an awkward spot. Without a published policy, customers have no rulebook explaining why a payment might fail, which may help explain the volume of complaints.
The report does carry a caveat. The figures count submissions to the Stand With Crypto tool, and the group does not verify that every complaint reached the bank named or confirm the exact reason behind each restriction.
How we got here
In June 2026, an earlier Stand With Crypto UK push cited industry data showing that around 40% of attempted transactions from banks to crypto exchanges were blocked or delayed.
During that same period, one exchange reported almost £1 billion in cancelled transactions.
The new report, published in October 2026, puts names and constituency-level reach behind those earlier figures. It arrives as the UK prepares a planned digital asset regulatory framework for 2027.
Stand With Crypto UK wants regulators, the FCA included, to issue clearer guidance. Specifically, the group argues that blanket restrictions are not a proportionate way for banks to meet their regulatory obligations.
Its preferred alternative is a risk-sensitive approach that assesses customers individually.
What this means for UK crypto users and the industry
For retail investors, the immediate effect is friction. A cap of £2,500 per transaction and £10,000 per 30 days can be workable for casual buyers, but it constrains anyone trying to rebalance a portfolio or move larger sums quickly.
Outright bans are a harder stop. Customers of banks in that camp may need a second account elsewhere just to fund an exchange, which adds cost and hassle to activity that is legal.
For FCA-registered exchanges, registration is supposed to signal legitimacy, yet the onboarding funnel can break at the bank transfer step, before a customer ever places a trade.
The caveat about unverified submissions will likely be the banks’ first line of defense. But 9,803 people taking the time to file is a signal that access, not just regulation, may be the bigger obstacle facing crypto adoption in Britain.
Disclosure: This article was edited by John Chen. For more information on how we create and review content, see our Editorial Policy.
