Online gambling payments

Does 3D Secure Protect Gambling Merchants From Chargebacks? Not in the US

Visa's rules switch off 3-D Secure's fraud-dispute protection at the US gambling codes. What the rule says, what authentication still does for an operator, and what answers a fraud dispute instead.

By VyaPayPublished 7 min read

No. In the US, Visa's §5.8.4.6 says 3-D Secure authenticated transactions at MCCs 7801, 7802 and 7995 are not eligible for protection from Dispute Condition 10.4, Other Fraud – Card-Absent, and the acquirer must tell its merchants so. A casino or sportsbook can authenticate every deposit and still lose a fraud dispute it can't answer with evidence.

3-D Secure (3DS) is a protocol that lets the card issuer authenticate the cardholder during an online payment, sometimes with a challenge such as a one-time code. Under card-network rules an authenticated transaction can shift liability for certain fraud disputes from the merchant to the issuer. Visa's US rules remove that shift at the gambling codes.

What Visa's rule says

§5.8.4.6 of the Visa Core Rules (24 October 2026) requires a US acquirer to tell its merchants that Secure Electronic Commerce transactions, Visa's term for 3-D Secure authenticated payments, are not eligible for dispute protection from Condition 10.4 at seven merchant category codes:

  • Gambling: 7801, 7802 and 7995
  • Four others: 4829, 5967, 6051 and 6540

The dispute tables say the same thing from the other side. Table 11-28 confirms that a 10.4 dispute applies to US domestic e-commerce at those codes regardless of the Electronic Commerce Indicator (ECI), the value in the authorization that records how the payment was secured. At a merchant where the shift applies, an ECI showing successful authentication is what moves a fraud dispute to the issuer. On US domestic e-commerce at a casino or sportsbook, the issuer can raise 10.4 whatever the ECI says.

The rule is a notice requirement on the acquirer as well as a liability rule. If your acquirer hasn't told you, that is a gap in its onboarding, not a sign the rule doesn't apply to you.

What 3DS still does for a casino

Authentication still has a job; it just isn't the job of moving fraud liability. Four things remain:

  1. It checks the cardholder at the point of deposit. A stolen card that fails the issuer's challenge never becomes a deposit, a balance or a dispute.
  2. It gives the issuer more to approve on. An issuer looking at a betting code and a quasi-cash indicator also sees that it authenticated its own cardholder, which can matter to an issuer that accepts lawful gambling.
  3. It leaves a record. The authentication result belongs in your evidence file, even though at these codes it doesn't decide the dispute.
  4. It may matter on Mastercard. According to an acquirer notice, Mastercard added a gambling and gaming monitoring element around June 30, 2025 that looks for CVV or 3DS on online authorizations. Ask your acquirer how it applies to you.

Whether 3DS adds friction that costs you deposits is a trade-off each operator has to measure in its own funnel. There is no published figure we'd rely on for it.

What a 10.4 dispute looks like at a casino

It arrives as a cardholder saying they didn't authorize the deposit. Behind that claim are two very different situations, and the right response depends on which one you're in.

Genuine fraud

Someone used a card that wasn't theirs to fund an account. The real cardholder is right, and the operator's job is to find out how the account got past its checks. Our view is that fighting a genuine fraud dispute is a waste of effort and a bad look; the work belongs in prevention.

A player disputing their own deposit

The player deposited, played and lost, and then told the issuer the deposit wasn't theirs. This is friendly fraud, and here the operator holds evidence an issuer can weigh: the verified identity on the account, device and login history, geolocation records, prior undisputed deposits on the same card and the play history showing the funds were used. How to assemble that file, and why the pattern happens, is in our guide to friendly fraud at online casinos and sportsbooks.

What works in place of the liability shift

Prevention, evidence and early resolution. None of them is as tidy as a rule that moves liability, but they are what's available at a gambling code.

LeverWhat it involvesWhat it addresses
Identity before moneyVerify the player before the first deposit; match the cardholder name to the verified accountGenuine fraud with stolen cards
Device and velocity controlsFlag new devices, several cards on one account or one card across accountsAccount takeover and card testing
A recognizable descriptorUse the name players know, as Visa's §1.5.1.12 requiresDisputes from players who don't recognize the charge
Purchase-inquiry data sharingAnswer the issuer's question about a transaction before it becomes a disputeFriendly fraud and confusion
Representment with evidenceRespond to the dispute with identity, device, location and play recordsFriendly fraud that reaches a chargeback

VyaShield, VyaPay's chargeback automation, works on the last two rows: automated dispute responses, and purchase-inquiry data sharing so more disputes stop before they become chargebacks. We don't publish win rates for it, and no one should promise you one at a gambling code.

How fraud disputes feed into VAMP

They count toward the ratio Visa uses to monitor you and your acquirer. As acquirers and chargeback vendors report Visa's published thresholds, the Visa Acquirer Monitoring Program divides TC40 fraud reports plus TC15 disputes by settled card-not-present transactions, and the US merchant "Excessive" threshold fell from 2.2% to 1.5% on April 1, 2026.

Our reading of how that combines with §5.8.4.6: because 10.4 disputes stay available against authenticated gambling deposits, authentication alone won't keep the dispute side of the ratio down. Prevention and pre-dispute resolution have to do more of that work. The counting rules, and what 1.5% means at casino volumes, are in our guide to Visa VAMP for gambling merchants.

Should you still use 3DS?

For the reasons in the list above, it is worth testing, as long as nobody on your team believes it is insurance. Treat it as an authentication tool with some fraud-prevention value and a record for your file, and budget for fraud disputes as if it weren't there.

If you do use it, decide where it earns its friction. Our suggestion is to apply it at the points where a stolen card would show up rather than on every deposit: a player's first deposit, a new card on an existing account, a new device, or a deposit far above the player's own pattern. A challenge at those moments costs less goodwill than one on a regular player's routine top-up. Record the result either way. A successful authentication on a deposit later disputed as fraud is a fact worth putting in front of the issuer, even though at these codes it doesn't decide the case.

One conclusion to avoid: that the fix is to get out from under the gambling codes. 3DS protection exists at other codes, but Visa's §5.8.18.1 requires online gambling to carry 7995 and, in the US, the quasi-cash/online gambling indicator. A deposit coded as something else to regain the liability shift is miscoded, and it trades a dispute problem for a compliance one that can end the account.

VyaPay runs its own processor and underwrites risk in-house, so the team that approves an account is the team that reviews its dispute controls afterwards. If you're a licensed operator working through your dispute exposure, talk to us about your program.

Frequently asked questions

Does the 3DS rule apply to non-US transactions at gambling merchants?

§5.8.4.6 is a US-region rule, and Table 11-28 describes US domestic e-commerce. For cross-border or non-US transactions, ask your acquirer which rules apply.

What is the ECI, and why doesn't it matter here?

The Electronic Commerce Indicator is a value in the authorization showing how an online payment was secured or authenticated. At US gambling codes, Visa's dispute table lets a 10.4 dispute proceed whatever the ECI shows.

Does 3DS help with non-fraud disputes such as 13.1?

No. The liability shift concerns fraud disputes. A claim under 13.1 Merchandise/Services Not Received turns on whether the player got what they paid for, which your play records can answer.

Which MCCs lose 3DS fraud-dispute protection in the US?

Seven: 4829, 5967, 6051, 6540, 7801, 7802 and 7995, under §5.8.4.6 of the Visa Core Rules (24 October 2026).

Sources

Talk to the team that underwrites you

Tell us about your licenses, your markets and your volume. You'll be talking to the people who run VyaPay's processor and make its risk decisions.

or call 833-4-VYAPAY

Let’s meet up!

Tell us about your business and someone from our team will reach out.