- The advocacy group Stand With Crypto says thousands of UK customers have complained about banks limiting or refusing payments to crypto exchanges. The figures are the group’s own and we have not seen the underlying data.
- Lloyds and Barclays are among the banks named. Both have published crypto payment restrictions for some time.
- None of this is an FCA instruction. Banks set these limits themselves, which is why they vary so much from one bank to the next.
A lot of UK holders have had the same afternoon: a transfer to an exchange bounces back, the app offers no reason, and there’s nobody obvious to ask. An advocacy group now says it has collected thousands of those complaints, and it’s pointing them at the banks.
If your bank refuses a payment to a crypto exchange, that’s the bank’s decision, not a rule imposed on it by the regulator. You can complain, and if you get nowhere you can take it to the Financial Ombudsman Service for free. It also matters that a blocked payment is not frozen money: the funds stay in your account, they simply don’t go where you sent them.
What’s actually been reported
Cointelegraph reports that Stand With Crypto, a campaign group funded by the crypto industry, has gathered complaints from UK customers about transfer caps and outright bans on sending money to crypto platforms, with Lloyds and Barclays among the banks named. We could not find a primary source for the complaint totals, and the number comes from a group whose purpose is to argue for lighter restrictions on crypto. Treat it as a claim with a direction of travel behind it rather than a verified count.
The underlying behaviour is not in dispute, though, because the banks publish it. Several UK banks have for years applied daily or monthly caps on card and transfer payments to crypto exchanges, and some block certain platforms entirely. The stated reason is almost always fraud: investment scams run through crypto rails more often than through any other payment channel, and banks carry reimbursement liability when a customer is tricked into sending money away.
Where the line sits

Here is the distinction that gets lost in most coverage of this. A bank choosing not to process a payment to a particular merchant is making a commercial and risk decision. The Financial Conduct Authority has not told banks to stop crypto payments, and it has no rule requiring them to allow them either. That’s why one bank will send £5,000 to an exchange without blinking and another refuses £50.
It also means the remedy is the ordinary one. You complain to the bank, you wait for its final response, and if you’re unhappy you escalate to the Ombudsman, which will look at whether the bank treated you fairly and applied its own terms properly. Our guide to UK banks and crypto payments sets out which banks currently restrict what.
What the Ombudsman won’t do is force a bank to do business it doesn’t want to do. De-banking cases generally turn on process and fairness rather than on a right to make a particular payment.
The timing, against the FCA gateway
The complaints land in an awkward month. The FCA has just opened its authorisation gateway, the point at which crypto firms operating in the UK can apply to be regulated directly, ahead of the full regime due in 2027. The regulator called it a step towards the UK becoming “one of the most trusted places in the world to build and invest in cryptoasset businesses”.
Applications are not approvals, and an open gateway is not a functioning regime. But it does create a question the industry will keep asking: if an exchange is authorised by the FCA, on what basis does a bank refuse to pay money into it? Nothing obliges the bank to change its mind. The argument simply gets harder to make.
It isn’t a European norm
Germany offers a useful comparison here. Sparkassen, the network of regional savings banks that most ordinary German customers use, has begun offering bitcoin and ether trading inside its own banking app, built through its asset manager DekaBank. Same continent, same fraud risks, roughly the same regulatory direction under the EU’s MiCA rules, and a very different answer from the banks.
That doesn’t make the UK position wrong. Fraud losses are real and British banks have been under heavy political pressure over reimbursement. It does mean the position is a choice rather than something forced on them from above, which is worth remembering when a bank’s app tells you a payment “cannot be completed”.
What to watch
Whether any major UK bank revises its limits once exchanges start coming out of the FCA gateway with authorisation in hand. That’s the first real test of whether the restrictions were about regulatory uncertainty or about fraud exposure, and the two have very different timelines.
Also worth watching: whether Stand With Crypto publishes the complaint data in a form that can be checked, or submits it to the FCA or the Treasury. A number in a press release and a number in a regulatory submission carry different weight, and only one of them tends to produce a response.
If your own payment has been blocked, the practical steps are in our UK banks guide, and if the problem is at the exchange end rather than the bank end, our withdrawals guide covers that instead.