Most high-street banks now let you switch on a gambling block in a few taps, and most players assume that switch is absolute. It is not. The block is usually applied at the card and merchant-category level, which means it catches a direct card payment to a casino or betting site but can miss a deposit that arrives through an e-wallet or a mobile wallet such as Apple Pay. If you want to know whether your block actually covers what you think it covers, you have to test the route, not just the merchant.
What a gambling block actually intercepts
A bank gambling block is a transaction filter. When you switch it on, your bank flags gambling merchant category codes and declines card payments that carry them. That works well for a straightforward deposit: you type your debit card details into a casino cashier, the payment is tagged as gambling, and the block stops it. The same logic applies to direct debits and some recurring card payments to bookmakers.
The filter gets weaker the moment an intermediary sits between your bank and the casino. An e-wallet such as PayPal or Skrill receives your money as a transfer, then pays the casino from its own balance. From your bank’s point of view, the transaction is a payment to a wallet provider, not to a gambling operator. The merchant code belongs to the wallet, so the block has nothing to match against. Some banks have started flagging known wallet-to-gambling patterns, but coverage is patchy and varies by provider and account type.
Mobile wallets add another layer. When you fund a deposit through Apple Pay, the card network generates a device account number and the payment is tokenised. Your bank sees a wallet transaction, and whether the underlying gambling category survives that tokenisation depends on how the bank and the wallet have configured the flow. Plenty of players have found that a direct card deposit is declined while an Apple Pay deposit to the same casino goes through untouched.
Why Apple Pay and e-wallets slip past the filter
The core problem is that the block is looking for a gambling merchant, and the wallet is not one. A deposit routed through Apple Pay can present as a payment to the wallet service, which sits outside the gambling category the bank is screening for. The same applies to e-wallets that act as a funding source rather than a pass-through. The casino receives the money, but the trail your bank inspects never touches the casino’s merchant code.
This is not a loophole anyone should rely on, but it is a real gap you need to understand if a block is part of your self-control strategy. A block that only covers direct card payments gives you a false sense of security. If your goal is to keep gambling spend out of reach, you have to verify whether wallet-funded deposits are caught or whether they sail straight through.
How to test whether your block catches wallet deposits
You can check your coverage without gambling a penny, and you should. The method is to compare how your bank treats a direct card payment to a gambling merchant against how it treats a wallet-funded payment to the same merchant. If the first is declined and the second is not, your block is partial.
- Confirm the block is active. Open your banking app, find the gambling controls section and check the block is switched on for the card you actually use. Some banks apply it per card, so a second card or a virtual card may be unprotected.
- Test a direct card deposit at a small amount. Go to a licensed UK online casino cashier and attempt a deposit of the minimum, often £5. You do not need to complete it. If the bank declines before the payment authorises, the direct card route is covered.
- Test the same deposit through Apple Pay. Choose Apple Pay at the cashier and attempt the same £5. If the payment authorises when the card route was blocked, your bank is not catching wallet transactions.
- Repeat with an e-wallet if you use one. Fund a wallet such as PayPal from your blocked card, then try a casino deposit from the wallet balance. Watch whether the card-to-wallet transfer is declined or allowed.
- Check your statement and app notifications. Look at how each attempted transaction is described. A payment labelled with the wallet provider’s name rather than the casino’s tells you the merchant code the bank saw, which explains why the block behaved as it did.
Run the test on the specific operator you use, because cashier setups differ. A site like BestOdds, which provides sports betting markets and a mobile casino experience, will route deposits through its own payment processor, and the wallet options it accepts may behave differently from a rival’s. The result at one casino does not guarantee the result at another.
If you want a reason to test in the first place, remember that a £10 free bet or 250 free spins is exactly the kind of promotion that pulls a lapsed player back in. BestOdds UK offers a £10 free bet and 250 free spins, with the promo code bop20x10fb unlocking the free bet and bop5x50fs unlocking the spins. A block that fails on wallet deposits will not stop you claiming either. The operator holds a UKGC licence, 66479, accepts Apple Pay, requires a £5 minimum deposit and promotes responsible gambling via GamCare and BeGambleAware, but none of that changes how your own bank screens the payment.
What to do when the block has gaps
If your test shows the block only stops direct card payments, treat it as one layer rather than the whole defence. The most reliable fix is to remove the wallet from the equation. Delete your saved cards from Apple Pay, remove stored payment methods from any e-wallet tied to your bank account, and ask your bank whether it can block wallet transfers as a category. Some banks will, some will not, and a few will only do it over the phone.
Strengthen the setup with controls the bank cannot bypass. Register with GamCare and BeGambleAware for advice and self-exclusion tools, and use GAMSTOP if you want a single block across UK-licensed operators. Set deposit limits at the casino itself, which apply regardless of payment method, and consider a software blocker on your devices. If gambling has already become a problem, Gamblers Anonymous runs meetings and a helpline that do not depend on your bank cooperating.
The practical takeaway is simple: a gambling block is only as good as the payment routes it screens, and wallet and Apple Pay deposits are the usual blind spot. Test your own setup with a £5 attempt on each route before you trust it. If the wallet route gets through, close it at the source by removing stored cards and wallet funding, then back that up with operator-level limits and a self-exclusion tool. Your bank’s block is a useful first line, not a guarantee, and the only way to know is to check.