MCC 7995 is a payment-card merchant category for gambling transactions, not a gambling licence or a universal decline rule. Acquirers apply the code under card-network standards; issuers and regulators add separate controls. Great Britain, Australia and Brazil restrict credit-funded gambling in different ways.
This guide is for operator payment and compliance teams, acquirers, payment providers, analysts and journalists. It explains how merchant coding interacts with authorisation and law. It is not legal advice, an acquiring application manual or evidence that any particular gambling transaction is permitted.
What MCC 7995 means
The Visa Merchant Data Standards Manual describes MCC 7995 as betting, including lottery tickets, casino gaming chips, off-track betting, race-track wagers and games of chance for monetary prizes. Mastercard describes it as gambling transactions involving wagers, lottery tickets, spread betting, in-flight gaming or chips and other value used for gambling.
Those descriptions establish a transaction category. They do not establish the operator's licence, the customer's location, the legality of the product or the card issuer's willingness to approve it. The gambling licence guide explains why permission must be checked against a named entity, product and jurisdiction. The operator guide separates that legal entity from its brand and suppliers.
Classification also follows the actual transaction. Mastercard says non-gambling purchases at the same establishment, such as food or lodging, should use the MCC that best describes those purchases. Visa says that if a merchant cannot distinguish betting transactions from its other transactions, all of those transactions must be identified with MCC 7995. Accurate product and merchant setup therefore matters before an authorisation request reaches the issuer.
Who assigns the code and who decides the payment
A card payment passes through several control layers. Treating MCC 7995 as the whole decision hides where a problem actually occurred.
| Role | What it means | Where to verify |
|---|---|---|
| Merchant and product | Presents the gambling deposit or purchase and supplies transaction data | Legal entity, product, channel, customer location and funding method |
| Acquirer or payment facilitator | Onboards and classifies the merchant under network rules | Contract, assigned MCC, merchant registration and permitted territories |
| Card network | Carries the transaction and applies scheme standards | MCC, transaction type, registration status and regional rules |
| Card issuer | Authorises or declines the individual payment | Response code, account controls, balance, authentication and risk policy |
| Regulator and operator controls | Decide whether that payment method can be offered in the market | Licence conditions, statute, wallet funding source and safer-gambling controls |
Mastercard requires an acquirer to register a merchant before acquiring its non-face-to-face gambling transactions. Its manual also pairs MCC 7995 with different transaction category codes for gaming payments and purchases of gambling chips or value. These are network implementation details, not a substitute for local permission.
The practical consequence is that the operator, gateway, acquirer and issuer should preserve the original response data. A statement line showing MCC 7995 cannot explain by itself why the payment succeeded or failed.
MCC 7995 versus 7800, 7801 and 7802
Both Visa and Mastercard publish more specific gambling-related codes for the US region. Their manuals should be checked separately because descriptions and registration requirements are network-specific.
| Role | What it means | Where to verify |
|---|---|---|
| 7995 | Gambling transactions not placed in a more specific applicable category | Product, channel, region and whether other purchases are separated |
| 7800 | Government-owned lotteries in the US region | Ownership, lottery product and network registration |
| 7801 | Government-licensed online or internet gambling in the US region | Licence, online channel, state scope and network registration |
| 7802 | Government-licensed horse or dog racing in the US region | Racing product, licence, channel and network registration |
The existence of 7800–7802 does not mean every licensed US operator should choose its own code. The acquirer must apply the relevant network standard and registration process. Nor should a code used in the US be copied into another country without checking that network's regional rules.
Why an MCC 7995 card payment can decline
Only the payment participants can identify the actual reason for a specific decline. Common control points include:
- The merchant or acquirer is not registered for the required gambling programme or region.
- The issuer blocks gambling transactions across all cards or on the customer's account.
- The card is credit-funded in a market that permits only debit or prepaid funding for the product.
- The operator's licence, product or customer location does not support the attempted payment method.
- The account lacks funds, authentication fails or the issuer applies an ordinary fraud or velocity rule.
- A customer-set gambling block, deposit limit or safer-gambling restriction applies.
- Merchant, product, transaction-type or wallet-funding data is incomplete or inconsistent.
Do not translate every generic decline into “gambling is illegal” or “MCC 7995 is blocked.” Ask for the acquirer or gateway response code, determine who produced it and map it to the correct layer. The transaction-monitoring guide shows how payment events should lead to alerts, review and recorded decisions without treating every alert as proof of wrongdoing.
Credit-card gambling bans compared
Credit restrictions are jurisdictional. The same wallet or card can be treated differently according to the regulated product, customer location and source of funds.
| Role | What it means | Where to verify |
|---|---|---|
| Great Britain | Licensed operators must not accept gambling payment by credit card, including through a money service business unless it prevents credit-card-funded gambling | Covers remote gambling and non-remote betting; specified non-remote lottery purchases and postal payments are outside the general ban |
| Australia | Online and telephone wagering operators must not accept credit cards, linked credit wallets or digital currency | Applies to wagering, including on-course bookmakers taking online or phone bets; lotteries are outside this measure |
| Brazil | Federally authorised fixed-odds betting can use prepaid methods such as debit, but not post-paid credit or credit supplied through partners | The rule concerns federal fixed-odds betting; do not generalise it to every Brazilian payment or lottery product |
| United States | Federal law and Regulation GG target payments connected to unlawful internet gambling rather than imposing one national ban on all lawful gambling card use | State law, product legality, network registration, acquirer policy and issuer controls still vary |
Great Britain
The Gambling Commission's licence condition 6.1.2 prohibits relevant licensees from accepting gambling payments by credit card. The Commission says the ban took effect on 14 April 2020 and applies to remote betting, casino and bingo, remote and telephone lotteries, and betting in shops or at tracks. Non-remote lottery tickets bought in shops and qualifying postal payments are treated differently.
The rule reaches indirect funding. An operator may accept payment through a money service business only when that business prevents credit-card-funded balances from being used for gambling. The Commission's land-based guidance also says credit-funded cashback and mobile-wallet payments must not become a route around the ban. The Great Britain market profile provides the wider licence context.
Australia
Australia's online wagering credit ban took effect on 11 June 2024. The Australian Communications and Media Authority says online and telephone wagering providers, including on-course bookmakers taking those bets, cannot accept credit cards, credit-linked digital wallets or digital currency. The ACMA also states that the measure does not apply to other gambling products such as lotteries.
The legal categories appear in Part 2B of the Interactive Gambling Act 2001. A payment review should therefore identify the product and channel before assuming that a card rule covering wagering applies to every gambling transaction.
Brazil
Brazil's Ministry of Finance says federally authorised fixed-odds operators may accept prepaid forms such as debit cards but not post-paid credit cards. Operators also cannot provide credit directly or through partners. The payment rule sits within Brazil's federal fixed-odds framework, so entity authorisation and account ownership still need separate checks.
The Brazil authorisation guide explains the federal operator record, while the Brazil market profile provides the market context. Neither page turns a permitted payment method into proof that a particular website is authorised.
United States
The Unlawful Internet Gambling Enforcement Act and Federal Reserve Regulation GG focus on restricted transactions connected to unlawful internet gambling. Regulation GG gives non-exclusive examples of policies that use transaction codes and merchant category codes to identify payments that may need to be denied. It also contemplates evidence such as a state or tribal licence or a reasoned legal opinion.
That framework is not a nationwide statement that every MCC 7995 transaction is unlawful. The underlying federal, state and tribal law matters, as do the product, location and participants. The specific US codes 7800–7802 add classification detail but do not replace that legal analysis.
MCC is not proof of legality or a licence
Merchant coding is designed to describe transaction activity for the payment system. A licence answers a different question: whether a named entity may offer a defined gambling product in a jurisdiction. An authorisation approval answers another: whether the issuer accepted one transaction at one moment.
These facts can coexist in several ways. A properly coded payment can still be declined. A technically approved payment can still breach an operator rule if the product or funding source is not permitted. An operator can hold a licence while a particular card type remains unavailable. Conversely, seeing a gambling MCC on a statement does not confirm that the merchant held the required licence.
Use the licence-verification process for legal permission. Use card and gateway records for transaction routing. Keep the two evidence chains linked but distinct.
Operator and acquirer implementation checklist
- Identify the contracting merchant entity, product, channel and every customer territory before assigning a code.
- Confirm the applicable Visa and Mastercard MCC, regional variation and gambling registration requirement with the acquirer.
- Separate gambling from hotel, food, retail or other non-gambling purchases where the network rules require separate classification.
- Map each jurisdiction's rule by product and funding source rather than maintaining one global “credit cards allowed” flag.
- Trace indirect funding through wallets and money service businesses where the rule looks through to the original card.
- Preserve MCC, transaction type, authentication result, gateway response and issuer response without rewriting them into one generic decline.
- Test debit, prepaid, credit, linked-wallet, refund and withdrawal paths separately before launch and after processor changes.
- Join payment controls to account limits, self-exclusion and safer-gambling restrictions in the Player Account Management system.
- Recheck the setup when a licence, product, acquiring bank, payment provider, network standard or law changes.
What a player or analyst can infer from MCC 7995
MCC 7995 on a statement is reasonable evidence that the merchant or payment flow was classified as gambling by the acquiring side. It is not enough to identify the exact gambling product, the operator's regulator or the reason for a decline. Statement descriptors can also differ from consumer-facing brand names.
For a disputed payment, preserve the date, amount, currency, descriptor and any bank response. The card issuer can explain its own account policy; the operator or payment provider can trace the acquiring path. Licence status should be checked independently against the regulator's current register.
Refresh policy
BETTIMES reviewed the cited network manuals and regulator materials on 22 September 2026. Card-network standards, merchant-registration programmes and gambling payment laws can change independently. This guide should be reviewed when Visa or Mastercard revises the relevant codes, or when any named jurisdiction changes the permitted product, channel or funding source.
Frequently asked questions
What is MCC 7995?
MCC 7995 is a merchant category code used for gambling transactions under card-network standards. It can cover betting, lottery tickets, casino chips and other games of chance, subject to network and regional rules. It classifies payment activity; it does not prove that the merchant is licensed.
Is MCC 7995 used for every gambling transaction?
No. Visa and Mastercard publish US-region codes 7800, 7801 and 7802 for specified lottery, licensed online-gambling and racing activity. Network rules, region, product and registration determine the correct code. Non-gambling purchases at the same establishment may also require a different merchant category.
Why was an MCC 7995 card payment declined?
The code alone does not reveal the reason. The issuer may block gambling, a credit restriction may apply, registration or transaction data may be incomplete, or normal balance, authentication, fraud and velocity controls may intervene. The gateway or acquirer response code is the starting point for diagnosis.
Is it illegal to gamble with a credit card?
There is no single global rule. Great Britain prohibits credit-card gambling across the covered remote and betting sectors, Australia prohibits credit for online and telephone wagering, and Brazil prohibits post-paid funding for federal fixed-odds betting. US rules depend on product, state, legality and provider controls.
Can an e-wallet bypass a credit-card gambling ban?
Not where the law or licence condition looks through to the wallet's funding source. Great Britain's rules require money service businesses to prevent credit-card-funded balances from being used for gambling, and Australia's restriction includes credit-linked digital wallets. Operators must verify the original funding method, not only the wallet brand.