QWIT
How bank gambling blocks actually work — and where they fall short
A growing number of banks let you flip a switch in the app and block gambling transactions on your debit or credit card. It sounds like a simple, complete fix, and it's genuinely useful — but it's a narrower tool than most people assume, and understanding exactly what it does and doesn't cover matters if you're relying on it as part of a financial recovery plan.
What the block actually does
Behind the toggle, the bank flags transactions using a merchant category code that identifies gambling operators — betting shops, online casinos, lottery retailers, and similar. When a payment comes through tagged with that code, it's declined at the point of sale before it settles. It's a genuinely useful layer: it works even in a moment of impulse, because the decision was made in advance, by a calmer version of you, and the bank enforces it automatically without needing willpower in the moment.
Where it sits next to self-exclusion
A card block and a self-exclusion scheme solve different halves of the same problem. Self-exclusion stops an operator from accepting you as a customer at all. A bank-level block stops the payment from your account regardless of which operator you try, which matters because self-exclusion schemes are typically opt-in per operator or per country scheme, and new sites appear faster than any registry can track. The two are complementary, not interchangeable — a card block catches gambling sites a self-exclusion list hasn't caught up with yet, and self-exclusion stops you being marketed to in the first place, which a card block can't do.
The gaps a card block doesn't cover
Merchant category codes aren't perfectly applied everywhere; some smaller or newer gambling sites, peer-to-peer betting, or platforms based in jurisdictions with looser reporting can slip through miscoded. Cash withdrawn from an ATM and then used to gamble in person isn't stopped by a card block at all — the block only sees card transactions, not what cash gets spent on afterwards. Cryptocurrency purchases used to fund gambling on crypto-friendly platforms are another common gap, since the crypto purchase itself may not be coded as gambling. None of this means the block isn't worth having; it means it shouldn't be treated as a complete solution on its own.
Setting it up so it isn't a five-minute undo
Some banks let you disable a gambling block instantly from the same app that set it up, which defeats much of the point during a genuine urge. Ask specifically whether your bank offers a cooling-off period — some require 24 to 72 hours' notice before a block can be lifted, which builds in exactly the kind of delay that a decision made in the heat of an urge needs. If your bank doesn't offer a delay, consider setting the block on an account you don't have instant self-service access to, or asking a trusted person to hold the ability to remove it.
Pairing it with something that isn't a bank
A card block that lives entirely inside your banking app is still, in the end, something only you control. Combining it with self-exclusion registries, uninstalling gambling apps, and telling one trusted person the block exists — so removing it isn't a private, silent decision — closes most of the remaining gap. None of these tools individually stop a determined workaround, but stacked together they add enough friction that most urges pass before a workaround gets found.
Sources: GambleAware, financial tools for gambling harm; UK Finance, banking industry guidance on gambling blocking tools; National Council on Problem Gambling.