Visa VAMP for Gambling Merchants: How the Ratio Is Counted and What 1.5% Means
Visa's Acquirer Monitoring Program weighs fraud reports and disputes against card-not-present sales, for merchants and for their acquirers. How the numbers work as reported, and what they mean for a casino or sportsbook.
As acquirers and chargeback vendors report it, Visa's Acquirer Monitoring Program divides a merchant's fraud reports and disputes by its settled card-not-present transactions. The same sources report that the US merchant "Excessive" threshold fell from 2.2% to 1.5% on April 1, 2026, with a floor of 1,500 fraud reports and disputes a month. For an online gambling merchant, every card deposit sits inside that ratio.
The Visa Acquirer Monitoring Program (VAMP) is Visa's program for monitoring card-not-present fraud and disputes at both the merchant and the acquirer level. As acquirers and chargeback vendors describe it, the program launched in 2025 and combines fraud reports and disputes into a single ratio, with thresholds that trigger fees charged through the acquirer.
How is the VAMP ratio counted?
Fraud reports plus disputes, over settled card-not-present transactions. Visa publishes the program's thresholds, and the figures below are as acquirers and chargeback vendors report them; we haven't worked from a Visa program document for this section, so treat every number as reported.
| Element | As reported by acquirers and vendors |
|---|---|
| Numerator | TC40 fraud reports (the issuer's report that a transaction was fraudulent) plus TC15 disputes |
| Denominator | Settled card-not-present transactions |
| Merchant "Excessive" threshold, US | 1.5% since April 1, 2026 (previously 2.2%); the change also applied in other regions |
| Minimum count | 1,500 fraud reports plus disputes in a month |
| Fee | $8 per fraud report or dispute, charged through the acquirer |
| Acquirer thresholds | 0.5% (above standard) and 0.7% (excessive) |
Two features of that formula matter more for a casino than for a retailer with stores. The denominator is card-not-present only, and every online casino card deposit is card-not-present, so the whole business is in scope. And fraud reports and disputes sit together in the numerator, so a fraud claim that also becomes a dispute can count in both parts.
What 1.5% means at casino volumes
It depends on your size, because the 1,500 floor and the 1.5% ratio work together. If a merchant has to meet both to reach "Excessive", which is how a minimum count reads, then below 100,000 settled card-not-present transactions a month the floor is what binds, and above it the ratio is. Here is our arithmetic on the reported figures:
| Settled CNP transactions per month | Fraud reports + disputes at 1.5% | Count needed to reach "Excessive" | Ratio that count represents |
|---|---|---|---|
| 20,000 | 300 | 1,500 | 7.5% |
| 50,000 | 750 | 1,500 | 3.0% |
| 100,000 | 1,500 | 1,500 | 1.5% |
| 500,000 | 7,500 | 7,500 | 1.5% |
The table is easy to misread. A smaller operator can look at the 20,000 row and conclude that VAMP doesn't reach it. It does, in two ways. Its fraud reports and disputes still count toward its acquirer's portfolio ratio, which vendors report is judged against thresholds of 0.5% and 0.7%, well below the merchant line. And Visa's rules for high-integrity risk merchants, which include gambling, require the acquirer to monitor your disputes daily from the 31st day after your first deposit of transactions (§10.4.5.2), whatever VAMP's merchant floor says. Why that acquirer-level pressure lands on merchants is covered in why online casinos get cut off by processors they've never met.
Why gambling merchants sit close to the line
Because three features of the business push the numerator up. The reasoning below is ours; there's no published dispute rate for gambling we'd rely on.
- 3-D Secure doesn't protect the deposit. Under §5.8.4.6 of the Visa Core Rules (24 October 2026), authenticated transactions at MCCs 7801, 7802 and 7995 in the US get no protection from Dispute Condition 10.4. Fraud claims on authenticated deposits, which would be the issuer's problem at a merchant where the shift applies, stay yours. The detail is in our piece on 3D Secure and gambling chargebacks.
- Deposits invite second thoughts. A player who deposits and loses can dispute the deposit, and that claim lands in the numerator whether or not it's genuine. How to answer it is in our guide to friendly fraud at online casinos and sportsbooks.
- Money draws stolen cards. A deposit that can be played or withdrawn is worth more to a fraudster than a pair of shoes, and each fraudulent deposit that clears can become a fraud report.
What Visa can do beyond the fee
A fee per dispute is the mild end. Visa's rules give it heavier tools when a high-integrity risk merchant's disputes run high, and the October 2026 edition names VAMP directly in two of them.
| Rule | What Visa may do |
|---|---|
| §10.4.5.4 | Disqualify a high-integrity risk merchant that reaches a critical level of disputes, acts to circumvent Visa's programs or harms the Visa system |
| §10.4.6.2 | Require the acquirer to contract directly with a sponsored merchant that generates excessive exception items in 12 months, or that takes action to evade responsibility for compliance with the Visa Rules; disqualify a high-integrity risk PayFac or sponsored merchant under VAMP |
| §1.9.1.4 | Permanently prohibit a merchant, PayFac or sponsored merchant, or its principals, for grounds including non-compliance with VAMP |
The §10.4.6.2 power is aimed at platforms. A casino boarded as a sponsored merchant under a payment facilitator can find itself pulled out from under the PayFac and into a direct contract with the acquirer, or out of the system altogether.
Splitting volume across accounts is evasion, not strategy
Spreading volume or disputes across several merchant accounts (MIDs) so each stays under a threshold doesn't change your dispute rate. It changes only what each account reports, and Visa's rules have language for that. §10.4.6.2 speaks of a merchant that "takes action to evade responsibility for compliance with the Visa Rules". §10.4.5.4 covers a merchant that acts to circumvent Visa's programs. §1.9.1.4 adds laundering, meaning transactions presented through a merchant that isn't the one the cardholder dealt with, and signing a new merchant agreement under a new name to get around the rules.
The accounts in such a scheme share owners, a product, a website and players. Our reading is that this makes the arrangement easy for an acquirer or Visa to connect, and once connected it turns a dispute problem, which can be fixed, into a circumvention finding, which can end the business's access to card payments and follow its principals.
Keeping the ratio down without gaming it
Lower the numerator honestly and watch it as closely as your acquirer does. In practice:
- Measure it yourself. Ask your acquirer what fraud-report and dispute data it can share, and track your ratio at least weekly, using the same formula vendors describe.
- Stop fraud before the deposit. Identity checks before first deposit, device and velocity controls, and card-to-account name matching cut fraud reports at the source.
- Resolve disputes early. Purchase-inquiry data sharing answers the issuer before a dispute is filed. VyaShield, VyaPay's chargeback automation, does that alongside automated dispute responses, so more disputes stop before they become chargebacks.
- Make the charge recognizable. Use the merchant name players know, as §1.5.1.12 requires, and disclose refund restrictions at checkout under §5.4.2.5.
- Accept genuine fraud quickly. Fighting a stolen-card claim adds cost without changing the count.
- Talk to your acquirer before a spike, not after. A launch, a promotion or a new market can move the ratio. An acquirer that hears about it in advance has context when its daily monitoring flags the change.
There is no reseller between a VyaPay merchant and the people who read its ratio: VyaPay runs its own processor and underwrites risk in-house. Licensed operators who want to go through a dispute profile can talk to us about their program.
Frequently asked questions
When did Visa lower the VAMP merchant threshold to 1.5%?
On April 1, 2026, according to acquirers and chargeback vendors, down from 2.2%. The reported minimum of 1,500 fraud reports and disputes a month still applies.
Who pays the VAMP fee?
Vendors report a fee of $8 per fraud report or dispute, charged through the acquirer. Whether and how your acquirer passes it on is set by your merchant agreement.
Do card-present sales count toward the VAMP ratio?
Not as the formula is reported: the denominator is settled card-not-present transactions only. For an online casino, whose card deposits are all card-not-present, the distinction changes little.
Is VAMP the only dispute monitoring a gambling merchant faces?
No. Visa's high-integrity risk rules require your acquirer to monitor your daily volume, average ticket and disputes against a baseline, and Visa can disqualify a high-integrity risk merchant that reaches a critical level of disputes.
Sources
- Visa, Visa Core Rules and Visa Product and Service Rules, 24 October 2026 (sections 1.5.1.12, 1.9.1.4, 5.4.2.5, 5.8.4.6, 10.4.5.2, 10.4.5.4, 10.4.6.2)
- Visa Acquirer Monitoring Program thresholds and fees, as reported by acquirers and chargeback vendors, 2025–2026
- Visa, Visa Merchant Data Standards Manual, October 2026 (MCCs 7801, 7802, 7995)
