How merchant category codes shape what your bank statement and budgeting app show

A bank statement looks simple because almost all of the complexity has already been stripped out by the time it reaches you. You see a merchant name, a date and an amount, and that is the end of it. Behind each of those tidy lines sits a payment message carrying considerably more detail, including a four-digit code that tells the banking system what kind of business took the money.

That code matters more for some purchases than others. A sandwich shop and a shoe retailer sit in different buckets, but nobody much cares which. Gambling is different, because banks, regulators and consumers all have reasons to want those payments identified separately. Whether the transaction is a bet with a high street bookmaker, a lottery ticket or a deposit at an online casino, the payment travels through the network with a tag that lets the card issuer recognise the merchant's line of business before the charge is ever approved, let alone displayed on a phone screen.

The four digits attached to every card payment

Merchant Category Codes, usually shortened to MCCs, are four-digit identifiers assigned to businesses according to the goods or services they sell. The international classification framework comes from ISO 18245, while Visa, Mastercard and the other card schemes publish their own more detailed rules about which category applies in which circumstances. The result is a shared vocabulary that works across borders and across banks.

The code is not something your bank invents when the transaction lands. It is set much earlier in the chain. A merchant signs up with an acquirer or payment processor, which assesses the nature of the business and assigns a category. When a customer pays, the authorisation request travels from the merchant to the acquirer, across the relevant card network, and on to the issuing bank, which decides in a fraction of a second whether to approve it. By that point the merchant category has normally already been supplied as part of the message.

The main category used for gambling is 7995. Payment specialists describe this as the code covering betting, lottery tickets, casino chips and wagers placed at race tracks, and Mastercard maintains a comparable classification. For operators, the code carries real commercial weight rather than being a piece of back-office housekeeping. Businesses categorised under 7995 are treated as higher risk by many acquirers, which affects pricing, reserve requirements and the willingness of banks to offer accounts at all.

It is worth being precise about what the code actually conveys. MCC 7995 identifies the type of merchant requesting payment. It says nothing about which game was played, how much was staked on any individual bet, whether the customer was winning or losing, or whether the operator holds a licence in the customer's country. It answers one narrow question, and it answers it consistently, which is precisely why it is useful.

What the code looks like across different markets

Most UK cardholders will only ever encounter 7995, but the classification is not uniform worldwide. Visa operates additional US-specific codes for particular regulated activities, which occasionally causes confusion when people compare notes across markets.

The American split reflects a regulatory landscape where gambling is legalised state by state and card issuers sometimes need to distinguish between categories that are lawful in one jurisdiction and not in another. Great Britain took a different route, regulating the sector through a single national licensing regime, so a single code does most of the work. The practical consequence is that a UK gambling block built around 7995 will catch the overwhelming majority of relevant merchants, whereas an equivalent control in the United States has to account for several codes at once.

When a code becomes a rule

Once the issuer receives the authorisation request, the merchant category becomes one input among many. Banks use it to sort account histories, to trigger notifications, to apply product restrictions and, increasingly, to honour controls that customers have switched on themselves. Most major UK banks and app-based providers now offer a gambling block of some kind, and these typically include a cooling-off period so the block cannot be lifted on impulse. Where such a feature is active, a transaction arriving with a recognised gambling code can be declined before authorisation completes.

Regulation sits alongside those voluntary tools rather than replacing them. The most significant intervention came in April 2020, when the Gambling Commission prohibited licensed operators from accepting credit card payments for gambling, covering online betting, casino and bingo alongside the non-remote sector. The ban was not absolute, and the Commission has been open about its scope, exceptions and the difficulty of evaluating its effects, including the treatment of lottery tickets bought in person and payments routed through e-wallets that might themselves be funded by credit.

The direction of travel since has been towards more granular oversight. The 2023 white paper set out a programme of reform, and the exchanges between ministers and the Culture, Media and Sport Committee on the pace and design of gambling regulation illustrate how contested the detail has been. Several of those measures have since taken effect, including financial vulnerability checks based on net deposit thresholds, stake limits on online slots, and a statutory levy on operator revenue to fund research, prevention and treatment.

None of this makes MCC 7995 a universal stop signal. Two banks can receive an identical merchant category and treat it entirely differently, because card products, customer settings and internal risk policies vary.

Why your budgeting app and your bank disagree

Here is where the neat picture starts to fray. The category shown in a budgeting app is not necessarily the MCC translated into plain English. Some apps receive enriched transaction data through bank feeds or open banking connections, arriving with a merchant name, amount, date and a pre-assigned label. Others run their own classification engines, matching merchant name strings against proprietary databases and only using the MCC as a fallback.

The result is inconsistency at the surface. One app files a payment under gambling, another under entertainment, a third under a broad discretionary spending heading. That divergence usually has nothing to do with how the card network classified the merchant and everything to do with what happened after the data reached the bank or the budgeting platform.

There is a more meaningful gap, though. Card controls only work on card payments. A bank transfer, an open banking payment initiation, a top-up through a third-party wallet or a purchase of cryptocurrency that is later used elsewhere may never carry a gambling code at all. That last route is worth particular attention, given how many crypto-based gambling platforms operate outside recognised consumer protections and how little recourse users have when something goes wrong. Someone relying on a gambling block as a complete barrier may find it considerably more porous than expected.

Data quality is the other weak point. If a merchant is miscoded, whether through administrative error or deliberate evasion, a control that depends solely on that field will not catch it. Acquirers and networks police this, and penalties exist, but enforcement is reactive by nature.

What the code is genuinely good for

Structured merchant data lets banks separate gambling expenditure from everything else without a human reading each line. That supports spending analysis, category-based limits, affordability assessments by lenders and the kind of aggregate research that informs policy. For anyone trying to understand their own finances, it means the raw material for an honest picture is already sitting in the account.

For the individual, the useful framing is straightforward. Gambling is discretionary entertainment, sitting in the same part of a monthly budget as eating out or a concert ticket, and money spent on it should be money you can lose without consequence. UK players do not pay income tax or capital gains tax on winnings, since duty falls on the operator rather than the customer, which occasionally encourages people to think of gambling in returns-based terms. That framing does not hold up. The mathematics run against the player over time, which is what distinguishes it from saving or investing.

Bank-level controls are worth using, but they work best treated as friction rather than fences. Alongside a gambling block, GAMSTOP allows self-exclusion from all online operators licensed in Great Britain in one registration, GamCare runs the National Gambling Helpline, and NHS gambling clinics take referrals across England. Gambling is restricted to adults aged 18 and over.

A four-digit number can tell a bank what sort of business is asking for money. Everything that happens after the payment clears is still a matter of judgement, and no classification system has ever been designed to supply that.