UK Crypto Transfer Complaints: 10,092 in 90 Days
UK crypto transfer complaints reached 10,092 in 90 days. See which banks drew the most, what the figures show, and what the coming FCA regime could change.

Why UK Customers Filed 10,092 Complaints About Crypto Transfers
A bank transfer to a crypto exchange can look like a normal payment. But for some UK customers, it's the start of a problem - an unexpected decline, a transfer limit, or a block that doesn't line up neatly with what the bank says in its published policy. That mismatch has become a flashpoint in the UK's debate over fraud prevention, customer choice, and what crypto regulation should (and shouldn't) require.
A report from the advocacy group Stand With Crypto says it collected 10,092 complaints about restricted or blocked transfers over 90 days, from 9,803 people. Lloyds Banking Group reported the highest number of complaints, even though it does not publish a crypto-transfer policy restricting such transfers, according to the report. The headline numbers are attention-grabbing - but they need context. These are complaints submitted through the group's online tool, not a market-share-adjusted measure of how often each bank blocks payments.
This article breaks down what the report says, what the figures can and cannot show, why banks put these controls in place, and where things could go as the UK's crypto regime moves toward 2027. The core question isn't whether banks should prevent fraud. It's whether customers can understand, anticipate, and challenge restrictions when they make legitimate transfers.
What the report says
Stand With Crypto's report, Blocked: Britain's Crypto Access Problem, says 9,803 people submitted 10,092 complaints between May and August 2026. The submissions were about transfers to crypto platforms registered with the Financial Conduct Authority (FCA), according to the report. The group says the complaints came from all 650 UK parliamentary constituencies.
The banks with the highest reported totals were:
- Lloyds Banking Group: 2,297 complaints. The group includes Lloyds, Halifax and Bank of Scotland.
- Barclays: 1,569 complaints.
- NatWest Group: 1,278 complaints. The group includes Royal Bank of Scotland.
- HSBC UK: more than 1,000 complaints; the report did not provide an exact figure.
Virgin Money and the Co-operative Bank had the lowest reported totals, with 103 and 76 respectively. These counts reflect submissions linked to each bank, not a ranked measure of how likely any individual customer's payment is to be blocked.
Lloyds' position stands out. The report says Lloyds accounted for more than 22% of all complaints even though it does not publish a policy restricting crypto transfers. But that alone doesn't explain what went wrong for customers. A transfer can be stopped by fraud controls, an account review, or another internal process that isn't presented publicly as a crypto-specific rule. In other words, the report lists complaint totals, not transaction-level evidence showing why each decision was made.
The report also points to a split in public approaches. It says six banks publish limits on crypto transfers. Barclays sets a limit of £2,500 per transaction and £10,000 over 30 days. NatWest's stated limits are £1,000 per day and £5,000 over 30 days. Santander UK sets limits of £1,000 per transaction and £3,000 over 30 days.
Other banks named in the report - Starling, TSB, Chase UK, Metro Bank, Virgin Money and the Co-operative Bank - block crypto transfers entirely. The report describes Lloyds and Revolut as having no published crypto-transfer policy. A lack of a published restriction doesn't mean every payment will go through; banks can still apply account-level checks and payment controls.
Barclays told Decrypt that its limits are meant to protect customers from crypto-related scams and losses. NatWest said its approach blocks or limits certain payments to crypto exchanges to address fraud risk. Those explanations matter, because the real dispute is whether broad blocks and caps are a proportionate way to manage that risk - and whether customers get clear information when payments are stopped.
How to read the complaint figures
The report is useful as a snapshot of customer frustration. It isn't a complete picture of bank behaviour across the UK.
First, the complaint totals are not weighted by the number of current accounts each bank has. The report says those account figures aren't publicly available for its analysis. A bigger bank may attract more complaints simply because it serves more people. Without a denominator - customers, attempted exchange payments, or declined transfers - it's not possible to compare the chance of a block from one bank to another.
Second, one person may submit more than one complaint, including complaints about more than one bank. The report records 10,092 complaints from 9,803 people. That matters: the total complaints isn't the same thing as unique customers, and it isn't automatically the same thing as a count of distinct failed transactions.
Third, the complaints were collected through an online tool run by an advocacy group. They shouldn't automatically be treated as the same as formal bank complaints processed through each bank's own system, and they aren't independently verified records of payment decisions. The submissions describe reported experiences. To determine how often a bank blocks legitimate payments, you'd need more detailed, comparable data from banks, payment providers, and customers.
The report groups complaints based on the type of bank policy it says is published. Banks with limits accounted for 6,198 complaints. Lloyds and Revolut, described as having no published policy, accounted for 2,842. Banks with outright bans accounted for 989. Stand With Crypto suggests the lower figure for outright bans may reflect customers deciding not to attempt transfers in the first place. That's a plausible idea - but the totals alone can't prove it.
There also seems to be a gap between categories and the overall total. The report's summary doesn't spell out how every complaint was classified in detail, so the category numbers shouldn't be treated as a perfect reconciliation of all submissions. That's another reason to treat the figures as a broad signal, not a precise league table.
What the report does support is a narrower conclusion: customers are reporting real uncertainty about whether they can access crypto platforms, and that uncertainty isn't limited to banks that explicitly publish a ban. The most important operational point the report makes is simple: customers can't reliably use what a bank publishes to predict whether a transfer will be accepted.
That's a transparency problem even before you get into whether any particular control is justified. If customers can't tell whether a limit applies, what evidence they'd need, or how to appeal a decision, they end up learning the rules only by trying a payment. That's a bad experience for customers, and it makes planning difficult for any business that depends on predictable payment access.
Why banks restrict crypto transfers
Banks aren't making up the fraud concerns. Crypto transfers can be hard to reverse, and scammers often pressure people into sending money to a platform or wallet they don't control. A customer might think they're making an investment, when they're actually following instructions from a fraudster. From a bank's perspective, stopping a payment before it leaves an account can reduce potential losses and protect customers.
The hard part is separating a risky payment from a legitimate one. A blanket restriction is easier to administer than a detailed, case-by-case review. It may reduce exposure to scams - but it also blocks customers who are transferring money to a platform they chose. A strict cap can be simpler than investigating every payment, but it can still feel confusing when the cap isn't prominent or when customers don't understand how it works across payment types like cards, online banking, and faster payments.
In practice, bank controls can also be more complicated than a single public rule. A payment might be affected by the amount, the payment method, the customer's account history, or an internal fraud alert. A publicly stated limit covers only one part of the policy; it doesn't necessarily describe every check applied to a particular transaction. That's why a customer-facing message can feel arbitrary, even if the bank has a legitimate risk rationale.
So there's a trade-off. If a bank offers no friction, customers may be left more exposed to scams. If it blocks too broadly, it can stop legitimate use of a customer's own money and harm confidence in the banking relationship. The goal shouldn't be "zero checks." It should be controls that match the level of risk, explained in plain language, with a real route for review.
Stand With Crypto recommends that banks move away from blanket restrictions toward risk-based, case-by-case checks. It also calls for clearer published policies and a way for customers to challenge restrictions or opt out of controls for transfers to FCA-registered providers. Of course, those ideas come with constraints. Case-by-case review takes time and can still produce tough decisions. An opt-out can't mean banks ignore suspected fraud or other legal obligations. Still, those constraints don't erase the argument for clearer transparency.
A practical standard would be straightforward: tell customers what types of transfer may be restricted, explain why a payment was stopped when it's appropriate to do so, and provide a clear process to review a decision. The details matter because an unexplained decline can push customers to retry through another route - sometimes increasing confusion rather than reducing risk.
What regulation could change
The dispute is unfolding as the UK prepares a crypto regime scheduled to take effect in 2027, according to the report. Stand With Crypto argues that firms authorized under the new regime shouldn't then face blanket barriers from other regulated firms. It has asked the FCA and HM Treasury to say publicly that sector-wide blocks and hard caps on transfers to registered or authorized crypto firms are unlikely to be justified by anti-fraud or financial-crime rules.
That's a proposal from an advocacy group, not a settled regulatory rule. The report does not claim the FCA has told banks to accept crypto-related payments, nor does it say authorization will force banks to process every transfer. Banks will still have to assess risk and meet their obligations. The question under debate is whether those obligations justify restrictions applied across a whole sector, including payments to firms that meet relevant regulatory requirements.
It's also worth not blurring FCA registration and authorization. The report describes the platforms involved in the complaints as FCA-registered, and it separately discusses firms seeking authorization under the forthcoming regime. For customers, the practical takeaway is to check a provider's status through the FCA's own information, rather than assuming "registered" means blanket approval or that a bank must accept payments to it. The FCA's information on cryptoasset firms is a good place to start.
The wider political and parliamentary conversation reflects the same access problem, just from different angles. In July, Parliament's Crypto and Digital Assets All-Party Parliamentary Group launched an inquiry into crypto firms' access to banking services, including transaction limits and payment blocks. In August, its co-chairs wrote to major UK banks asking how they treat crypto firms and what limits they apply. As reported, their concern was that banking access could become a major barrier to growth for UK crypto businesses.
Stand With Crypto's report also points to earlier evidence of friction. A 2025 FCA and YouGov survey found that 13% of UK crypto users said they'd had problems withdrawing crypto to a bank account; the report describes this as the most common negative experience in that survey. A January survey by the UK Cryptoasset Business Council estimated that banks blocked or delayed around 40% of transfers to the country's ten largest exchanges. Those are separate surveys with different methods, not direct confirmation of the 2026 complaint totals. Still, together they suggest payment access has been a recurring concern.
For the market, what happens next may depend less on whether crypto is "allowed" in general, and more on how the rules get implemented. If legitimate providers can obtain authorization but customers still face opaque and inconsistent payment controls, the operational barrier will remain. And if banks are expected to accept every payment without meaningful risk checks, the cost could show up as increased exposure to fraud. Regulation has to address both sides instead of assuming one solves the other.
Conclusion: clarity matters as much as access
The 10,092 submissions don't prove that one UK bank is more likely than another to block a legitimate crypto payment. What they do show is that a lot of customers are reporting friction, alongside policies that range from published limits to outright bans and no public crypto-specific rule.
For banks, the challenge is managing fraud without making payment access unpredictable. For regulators, it's about preserving risk controls while making sure lawful, regulated crypto activity isn't shut out by default. For customers, the immediate move is to check both your bank's current policy and the provider's regulatory status before transferring funds - and to use the bank's formal complaints process if a restriction is unclear or disputed.
The next useful milestone isn't another headline number. It's clearer, comparable information about what banks restrict, why they do it, and how customers can challenge a decision. Read the original report coverage, then check the relevant bank and FCA guidance before making a transfer.