Bank Gambling Blocks at Australian Banks

Loading...

Author: Max Cookson Last updated: June 2026 Reading time : 9 min

The toggle that’s now in everyone’s app

Five years ago, the bank-side gambling block was a niche feature that customers had to ring up and request. Today it’s a checkbox in every Big Four banking app, plus most challenger banks, and the take-up has been substantial. The block is the most powerful customer-protection tool in the bank-side toolbox – it sits above bookmaker-level limits, above NCPF deposit caps, and above BetStop in the sense that it doesn’t depend on the bookmaker recognising you. Once the toggle is on, your card simply doesn’t authorise gambling-category transactions, full stop.

The mechanics behind the toggle are genuinely interesting. The bank reads the merchant category code on inbound authorisation requests, and any transaction tagged MCC 7995 – the gambling category – gets refused at the issuer level before your bookmaker even sees the result. The block is precise, it’s instant, and it doesn’t care about anything else in the transaction. But the four major banks implement it slightly differently, and those differences matter for punters who want a finely-tuned protection setup.

This piece compares how the gambling block actually works across CommBank, NAB, ANZ and Westpac in 2026, where the implementations differ, and how to use the toggle as a real protection tool rather than a half-measure.

Navigate bank restrictions via our portal.

How the MCC 7995 block actually works

The gambling block keys off the merchant category code attached to every card transaction. When you tap or enter your Visa Debit at a bookmaker, the operator’s payment system tags the transaction with MCC 7995 – the code that covers betting, lotteries, and casino gaming. Your bank’s authorisation system reads that tag in milliseconds, and if the gambling block is on, the transaction is declined before it reaches any of the bank’s other risk checks.

The block is comprehensive in scope. It catches deposits at licensed Australian bookmakers, deposits at offshore bookmakers (which sometimes use different MCC tagging but usually still resolve to 7995), and any other gambling-coded transaction including lotteries, casino-branded apps, and racing pools. The granularity is at the merchant-category level rather than the merchant level – there’s no “block this bookmaker but allow that one” option in any of the major banks’ implementations.

What this means practically is that the block is an all-or-nothing decision. If you turn it on, every gambling card transaction fails. If you turn it off, none of them do. The simplicity is part of the design – the block is meant to be a clear, unambiguous protection rather than a fine-grained budgeting tool.

CommBank – the longest-running implementation

CommBank had the gambling block earliest of the Big Four and has refined it the most. The toggle sits in the app under “Block Spending Categories” and applies to both their Debit Mastercard and any Visa-branded products they issue. Switching the block on takes effect immediately, and switching it off has a 48-hour cooling-off period – a deliberate friction designed to prevent impulse reversals after a losing session.

CommBank’s implementation also extends beyond MCC 7995 to cover specific identified gambling merchants that may not always tag correctly. The bank maintains its own list of gambling-related merchants alongside the standard MCC filter, which catches edge cases like offshore operators using non-standard category codes or wallet-wrapped transactions where the underlying funding source is gambling-related.

The customer-experience signature of the CommBank block is that the decline message is explicit – the bank’s app shows recent declines tagged “blocked due to gambling category” rather than a generic refusal. This transparency is a significant improvement over the early implementation, where customers sometimes couldn’t tell whether a decline was the gambling block, a fraud flag, or a balance issue.

NAB and Westpac – similar shape, different details

NAB’s gambling block lives in the NAB Mobile app under “Card Controls” and works on the same MCC-7995 logic. The cooling-off period for switching the block off is 24 hours rather than CommBank’s 48, which makes the protection slightly less robust against impulse reversal. Like CommBank, NAB extends the block to certain identified gambling merchants beyond the standard MCC, though their list is somewhat smaller.

Westpac’s implementation, in the Westpac app under “Card Settings”, is the most recently overhauled of the Big Four. It applies a 72-hour cooling-off period when switching the block off, which is the longest of the four major banks. This makes Westpac’s block the most “sticky” – once you’ve turned it on, you’re committed to a longer wait before reversing the decision.

Both NAB and Westpac apply the block to all card products including their commercial and premium cards, which catches situations where a customer might have been planning to use a different card to bypass the block on their primary one. The blocks are account-holder-level, not card-level, so adding a new card doesn’t reset the protection.

ANZ – the implementation that’s caught up

ANZ was the slowest of the Big Four to launch a customer-facing gambling block, but their implementation in 2026 is on par with the others. The toggle in the ANZ Plus app applies the standard MCC 7995 block with a 48-hour cooling-off period, matching CommBank’s design. ANZ’s older legacy app users have a slightly different experience – the block is available but lives in a more buried menu, which has reportedly affected take-up rates.

One detail where ANZ differs is in how the block interacts with their offshore-merchant filtering. ANZ’s implementation is somewhat more permissive on edge cases – offshore gambling sites that miscategorise their MCC sometimes slip through where they’d be caught at CommBank. This has been a known soft spot in the ANZ implementation, and the bank has been gradually tightening it, but it remains an area where the four major banks aren’t perfectly equivalent.

The compliance picture matters here. The credit-card ban – taking effect on 11 June 2024 with operator fines of up to AU$247,500 per breach – pushed banks to invest in MCC-based filtering infrastructure regardless of customer-side blocks, because they need it to enforce the credit-product side of the ban. The customer-facing gambling block on debit cards is a thin layer on top of infrastructure that’s already running for credit-card enforcement.

How the block interacts with PayID and bank transfer

The MCC-based block doesn’t catch PayID transfers or bank transfers, because those rails don’t carry an MCC. A customer with the gambling block on can still send money to a bookmaker’s PayID, and the transfer will clear normally. This is a meaningful gap in the protection model – the block stops one rail but not all of them.

Some banks have started layering name-pattern detection on outbound bank transfers to catch obvious bookmaker recipients, but this is much less reliable than the MCC-based block on cards. A bookmaker registered as “Punt Pty Ltd ATF Trust” might or might not match a name-pattern filter, depending on how the bank has tuned its detection logic.

For punters using the gambling block as a self-control tool, the gap matters. Turning on the card-side block while leaving the bank-transfer rail open isn’t a complete protection – a determined punter can bypass the block by switching to PayID. The complete protection requires combining the card-side block with BetStop, which excludes the customer at the bookmaker level regardless of the funding rail.

Where the gambling block sits in the broader protection stack

The bank-side gambling block is a useful tool but it isn’t a complete answer to gambling-related harm. It’s most effective when combined with bookmaker-level deposit limits, BetStop registration, and any personal protections (separate accounts, locked-down cards, etc) that the customer wants to put in place. The card-payment economy in Australia hit AU$1.1 trillion in 2025 with Visa as the dominant scheme, and the volume that flows through gambling-coded transactions is significant – but the block, used in isolation, only addresses the card-rail slice of that.

Find out how to troubleshoot Visa deposit declines effectively.

For the deeper picture of how BetStop specifically interacts with bank-side blocks, my piece on BetStop and the National Self-Exclusion Register for Australian punters covers the cross-operator self-exclusion mechanics in detail.