Why Did My Bank Block My Crypto Purchase?

The price quote said three minutes, so it was card number in, expiry in, pay. Then the screen nobody screenshots for fun: payment declined by your bank, please try another method. Twenty seconds later your phone buzzes, and it is the bank, asking whether you really just tried to send £200 to a crypto company.

The card works everywhere else and the balance is fine, yet the payment died all the same. Your bank answered a question before the crypto platform ever saw the order, and the answer was no. This is a guide, not financial advice. It sorts out which kind of no you got, because one kind clears with a tap in your banking app and the other will not move for anyone.

The decline happened before anyone sold you anything

Press pay and the request travels through the card network to the bank that issued your card, which approves or declines in under a second. A decline means no money moved: nothing left your account, nothing arrived anywhere, and the on-ramp at the far end, the service that would have turned your pounds into coins, never saw a thing. Banxa has run that conversion plumbing since 2014, across more than 100 payment methods, and on a bank-side decline none of that machinery even gets a look in.

Separate one lookalike first. If the purchase died inside a verification popup, the one asking for a code or an app approval, that was 3D Secure failing, a different problem with different fixes and an article of its own. This piece is about the bank itself deciding no.

MCC 6051, the four digits your bank reads first

Every card payment carries a merchant category code, a four-digit label that tells your bank what kind of business is asking. Crypto purchases are coded 6051, a bucket called quasi-cash that also holds things like money orders. Banks write rules against whole categories rather than individual shops, so one line of policy can cover every crypto merchant at once.

The expensive version of this catches people on credit cards. Some issuers treat quasi-cash on a credit card as a cash advance: a higher fee, interest running from day one with no interest-free grace period, sometimes a lower limit than the card normally has. A debit card from the same bank often sails through while the credit card takes the surcharge. Same bank, same person, different rulebook per card. The sting is that the extra cost surfaces on the statement weeks later, when the coins are long since bought.

Policy blocks

Some banks have taken crypto off the menu entirely. Chase UK stopped its customers making crypto payments in October 2023 and cited fraud when it announced the change. Starling Bank has blocked both card payments and transfers to crypto platforms since November 2022. Positions like these are published, dated, and applied to every customer the bank has.

That is what makes them unmovable from your side. The agent on the phone cannot override a policy block, however reasonable you sound, because nothing about you triggered it. It lifts when the bank changes its policy and on no other schedule, and no phone call moves a wall.

Fraud flags, the kind a call can clear

Most banks allow crypto and run it through tighter fraud scoring instead. Picture your first purchase the way the scoring model sees it: a merchant type this card has never paid before, online, for a round amount, £200 or £500 on the nose. That combination sits close to a textbook fraud pattern, so the model declines first and asks questions second.

The asking is the good news. A notification lands in your banking app, or a text arrives, wanting to know whether the payment was genuinely you. Confirm it, retry, and the payment usually goes through. Your original quote will have lapsed by then, since locked prices only hold for around three minutes, so take the fresh one and carry on. Card orders typically complete within about 10 minutes of issuer approval, so a cleared flag costs you minutes rather than days. Ignore the notification, though, and the card tends to stay twitchy on the next attempt too.

One call, three questions

If the app shows nothing, ring the bank and ask these in order.

Did the bank decline the payment at all? If no request ever reached it, the failure happened upstream, in the card details or the checkout itself, and that is a different problem entirely.

Was it policy or security? The wording matters: security means confirm it and retry, and policy means stop retrying, because the no applies to everyone.

Is crypto restricted on this card type specifically? Ask about quasi-cash, MCC 6051, on credit versus debit. Plenty of banks refuse or surcharge one card type and wave the other through.

The workarounds that hold up, and the one that backfires

The clean fix is changing rails. A bank transfer leaves your account as an ordinary transfer rather than a card payment coded 6051, so card-category rules never come near it. It runs at roughly 1% all-in against 3 to 5% for cards, which is why buying bitcoin by transfer is the standard fallback rather than the consolation prize. A card from a second bank with no crypto policy also works, where you have one.

The one to refuse: describing the payment as something else, or routing the money through a friend so its purpose is hidden. Lying to your bank about what a payment is for is a bad idea, stated plainly, and it usually breaches the account terms you signed. One blocked purchase is a nuisance, but souring the relationship with your own bank over it is a rotten trade.

Look before you pay next time

Banks publish their crypto stance in their help pages, and the big blockers announce it publicly, the way Chase UK did in October 2023. So run the check before the next attempt, in this order: search your bank's help pages for crypto, confirm which card types any restriction covers, and pick your rail before you pick your coin. If all three come back clear and the payment still dies, then contact support, carrying the one question that matters: was that policy, or security?