A punter sits down on a Saturday afternoon, opens their banking app and flicks to the card controls section. A toggle marked “gambling block” sits alongside switches for contactless payments and online spending limits. One tap turns it on, and from that moment the card will decline any transaction the bank’s system flags as a gambling payment. This feature is now standard across most UK current accounts, though the way it interacts with different gambling operators varies, particularly when players compare it with options like UK casinos not on GamStop or other sites outside the usual regulatory framework.

The mechanics behind that moment are more layered than a simple on/off switch. Most high-street banks now offer gambling transaction blocks as a standard feature inside their mobile apps, and they work through a combination of merchant category codes, real-time risk scoring and transaction monitoring. These tools sit at the intersection of personal finance and harm prevention, and while they sound straightforward, the reality of how they function varies from bank to bank and from one gambling site to another.

How the bank’s system actually identifies a gambling payment

Every card transaction carries a four-digit merchant category code (MCC) that tells the bank what kind of business is receiving the money. Gambling operators generally fall under MCC 7995, which covers betting, casino transactions and lottery sales. When a customer enables the gambling block, the bank’s authorisation system checks the MCC on every attempted payment in real time. If the code matches the blocked category, the transaction is declined before funds leave the account.

Some banks layer additional signals on top of the MCC check. The merchant name string, the transaction amount and the geographical location of the payment gateway can all feed into the decision. A payment to a corner shop that also operates a lottery terminal might trigger a false positive, while a cryptocurrency exchange with a gambling-like interface might slip through if its MCC is registered as something else. A quirk that catches some punters off guard is that gambling blocks typically apply only to the specific card on which they are activated, not to the entire account.

Claire, a casual bingo player with a £20 weekly budget

Claire plays online bingo twice a week and tops up her account by debit card. She set a gambling block through her banking app last year after a friend mentioned it, mostly as a precaution. The block works without any fuss until the bingo site she uses changes its payment processor. The new processor’s MCC falls outside the standard gambling code because the company also handles transactions for a large retail chain.

Her next deposit clears without the block catching it. Claire only notices three weeks later, when she checks her statement and realises the block had stopped triggering. She contacts her bank, which explains that MCC assignments can lag behind a merchant’s actual business activity. The bank updates its classification manually, and the block resumes.

David, a football accumulator fan who switched banks

David moves his current account from one high-street bank to another, drawn by a switching bonus. He had a gambling block turned on with his old bank, and he assumes the new bank will either migrate the setting or prompt him to set it up. Neither happens. The new bank’s app has a gambling block toggle buried inside a “manage cards” submenu, and it defaults to off.

On a Friday evening he places a few accumulator bets and the payments go through without issue. He realises a month later, when he reads an article about bank gambling blocks, that his new account has no such restriction in place. David activates the block immediately, but the gap has already allowed a handful of deposits he would have preferred to prevent. Gambling blocks are not portable between financial institutions, and anyone moving banks should check all security and spending settings within the first week.

Priya, a slots player who tried a site outside the UK licensing system

Priya plays slots on a UK-licensed site and has a gambling block active on her debit card. A friend mentions an offshore operator with a different game selection, and Priya decides to try a small deposit. The payment clears, despite the block. The offshore site’s payment gateway uses an MCC associated with general entertainment services rather than gambling, so the bank’s filter does not flag it.

Priya later learns that many operators based outside the UK do not use MCC 7995, either because their payment processor bundles multiple merchant types under a single code or because the acquiring bank is in a jurisdiction where gambling classification rules differ. Her bank’s support team confirms that the gambling block applies only to transactions coded under the gambling MCCs in the bank’s internal list. Priya decides to stick with UK-licensed sites where the coding is more predictable.

Lewis, who used the block after a self-exclusion period

Lewis completed a six-month self-exclusion through GAMSTOP and wanted an additional safeguard when the exclusion ended. He activated his bank’s gambling block on both his debit and credit cards the day after his GAMSTOP period expired. The block gave him a second layer of friction: even if he visited a gambling site and attempted a deposit, the transaction would fail.

During the first month he tested the block inadvertently. A targeted email from a casino he used years earlier offered free spins, and he clicked through and tried to deposit £10. The payment was declined. Lewis appreciated the ambiguity; it removed the temptation to argue with himself about whether to override it. He keeps the block on indefinitely, treating it as a permanent fixture rather than a temporary measure.

The following table summarises key differences in how UK banks apply gambling blocks, based on publicly available information from current account terms and app descriptions.

What the gambling block can and cannot catch

The gambling block is a blunt instrument built on a fragile classification system. It works reliably for UK-licensed operators using standard merchant codes and for punters who pay by debit or credit card. It does not cover bank transfers, e-wallet funding that routes through a non-gambling MCC, or cryptocurrency purchases where the exchange does not identify as a gambling business.

False positives occur too. Purchases at newsagents that sell lottery tickets, or payments to entertainment venues with gambling machines on the premises, can sometimes trigger a decline. The block’s strength is its simplicity, but that simplicity also defines its limits. It stops the obvious transactions; it does not block intent. For someone who wants a blanket restriction, combining the bank block with other tools such as website blocking software and self-exclusion schemes creates a more comprehensive net.