The 1.5% VAMP Threshold: A 2026 Playbook for Gaming MIDs

For a gaming MID, the VAMP ratio is decided month by month in the operations workflow, long before the acquirer calls.

Visa cut the merchant Excessive VAMP threshold from 2.20% to 1.50% on April 1, 2026, and gaming MIDs absorb that cut on top of a business model underwriters already read closely. Our underwriting team frames it this way for rip and break platforms: the processor is not pricing a label, it is pricing prepaid credit, a randomized outcome and delayed fulfillment, with stored balances and buybacks in the middle. The same lens fits most gaming models, in my view. Each trait can feed the numerator.

The math is unforgiving. VAMP is scored on a calendar month, with no rolling average, no carry-forward and no grace window inside the month. Merchants at Excessive are assessed $8 per event through their acquirer. That fee scales with how many events you log, so volume magnifies every lapse. One widely read 2026 VAMP guide adds that many processors set internal merchant thresholds between 1.0% and 1.2%, so the published line is rarely the one that ends a relationship.

This playbook is written for established operators, not pre-launch startups, because an acquirer boards businesses with real monthly volume and a history it can underwrite. Three controls carry most of the load: pre-authorization fraud scoring, rapid refund routing and dispute deflection. Most published playbooks stop at the thresholds. Each control moves a different part of the ratio, which is why the first job is knowing precisely what Visa counts and what it ignores.

How does Visa calculate the VAMP ratio for a gaming MID?

The VAMP ratio divides TC40 fraud reports plus TC15 disputes by TC05 settled card-not-present transactions. It counts events, not dollars, and ignores card-present volume entirely.

Every control in this playbook depends on one skill: rebuilding the number the way Visa does. A gaming team can reproduce it each month in five steps.

1. Set the denominator. Count settled card-not-present Visa transactions (TC05) for the calendar month, grouped by merchant descriptor.
2. Count every TC40. Include each issuer fraud report, even where no chargeback followed.
3. Count every TC15. Include disputes under all reason codes, not only fraud.
4. Add without netting. A transaction carrying both records counts twice.
5. Close the month. The result belongs to that calendar month alone, with no rolling average to soften a spike.

According to Shawn Kelley's VAMP guide at disputed.ai, "a $12 order and a $1,200 order each count as one transaction," and Visa does not deduplicate, so one fraudulent sale can contribute twice to the same ratio. The guide also shows that the dispute line is wider than most operators expect. TC15 covers fraud (10.4), merchandise not received (13.1), not as described (13.3), authorization (11.x), and processing errors (12.x), and non-fraud disputes count the same as fraud disputes. Domestic and cross-border card-not-present sales both enter the math. Metrics are calculated by merchant descriptor rather than purely by MID, which matters for operators who run several brands through one account.

Samantha Gordon of Glenbrook Partners named the consequence on the firm's 2026 mid-year trends episode: "VAMP is volume-based. That's the change that keeps catching merchants off guard." Because each dispute and fraud report weighs the same regardless of ticket size, she said "high volume, high ticket count, low value merchants are particularly exposed." Gaming deposit flows fit that description closely. Frequent small top-ups mean every disputed one carries full weight.

TC40s are the quieter line. An issuer can file one without any chargeback ever appearing, and on small transactions it may simply credit the cardholder rather than open a dispute. A merchant that never sees its TC40 data cannot see one of the two lines in its own ratio. Conventional wisdom treats the chargeback rate as the figure to manage, yet double-counting is exactly why so many operators find their VAMP ratio running above the chargeback math they trusted.

For a gaming operator, the reading is blunt. A player who does not recognize a deposit descriptor and a fraudster testing a stolen card land in the same pool. Nothing in the formula tells them apart.

Our underwriting team frames risk the same way at onboarding. For card rip and break platforms, the team's view is that a processor is not pricing the product category; it is pricing prepaid credit, a randomized outcome, delayed fulfillment, stored balances, and buybacks. I apply that lens to gaming VAMP exposure too. Map each step of the money flow, from deposit to payout, to the ratio line it can feed, and you end up with the same picture that high-risk underwriters need to approve your application.

Combining 5 sources points to one practical conclusion: the numerator is broader, noisier, and less visible than a dashboard built around chargebacks will ever show. Which raises the harder question of whose limit that number is really measured against, and for many gaming MIDs the answer is not Visa's own line.

What will matter most for gaming MIDs over the next 12-24 months?

Acquirer contracts, dispute mix and event counts will matter more than Visa's published threshold, so gaming MIDs should plan against the bank's number and raw event volume, not the percentage alone.

The network rule sets the outer wall. Inside it, each acquirer draws its own line, and gaming MIDs sit near the edge of most high-risk portfolios. My bet is that those internal lines tighten before Visa's does, because the bank answers for its whole portfolio while a single operator answers only for itself.

Contrary to the usual framing, I think the fraud half of the ratio will be the easier half for most gaming operators. Fraud models are improving, and industry fraud losses dipped in 2024. The harder half is different. It is the customer who disputes a charge, whatever the reason code, and no fraud score stops that at authorization.

Three developments could change this forecast. Visa could raise or pause the merchant line. Visa could revise the acquirer tiers, which have not moved since the program launched. Or agent-driven purchases could become a real dispute source: one payments consultancy reported dispute data showing customers contesting charges an AI agent made, yet agentic payment volume was close to nil as of June 2026.

I hold the first two predictions with more confidence than the third. The evidence shows where acquirer and dispute pressure is heading, but it has no vertical breakdown of VAMP ratios and no measured improvement from specific controls on gaming MIDs. The figure worth building is your own: the ratio in the month before each control goes live and in each month after, starting with pre-authorization scoring.

Why is your acquirer's limit the real VAMP ceiling, not 1.5%?

For an established gaming operator processing $25,000 or more a month, the binding limit is the acquirer's internal VAMP target, which often sits well below Visa's 1.50% merchant line.

Visa measures two parties with two rulers. The merchant line applies to one descriptor. The acquirer line applies to the bank's whole card-not-present portfolio, and it is far tighter: Early Warning at 0.40%, Above Standard at 0.50%, and Excessive at 0.70%. The two upper acquirer tiers have stood since VAMP launched on 1 April 2025, and Visa did not revise them when the merchant line dropped in 2026.

That gap is the whole story.

An acquirer whose portfolio drifts toward 0.70% faces its own remediation plans and fines, and that pressure travels downstream to whichever merchants move its numbers. Industry reports say some acquirers already require merchants to stay below a 0.40% VAMP ratio, a small fraction of the published merchant threshold. Sellers of high-risk processing, writing in public payment forums, go further: acquirers fined at the portfolio level will drop merchants faster, and a merchant can be caught even when its own ratio sits under Visa's line. Their advice is to keep disputes under 1%, and ideally under 0.7%, because a single bad month can bring fines, an account review, or removal mid-campaign.

Visa's 1.50% is a line a gaming MID should never approach. Plan against the acquirer's number instead.

The count floor offers less shelter than it looks. A descriptor below 1,500 combined fraud reports and disputes a month falls outside formal network monitoring, yet most acquirers apply stricter internal limits well below that floor. For gaming, that math is unforgiving. One promotional weekend that spikes unrecognized-deposit disputes can push a MID past its acquirer's internal limit while the network itself sees nothing at all.

Waiting for a warning is no safer. Posts in merchant forums describe an aggregator's dispute-rate flag arriving only after the merchant was already inside a monitoring program, with fines accumulating in the background. Some free ratio calculators shared in those same threads still quote tiers of 0.9% and 1.8%, which do not match Visa's published VAMP merchant thresholds. An operator who trusts those figures is measuring against the wrong ruler.

In practice, the working target is whatever your processing agreement says. Ask for it in writing. Fees and reserves can follow from that number too, which is why it pays to understand what a high-risk merchant account should really cost before the first month closes. I would put one question to any processor, including us, before a single deposit settles: what VAMP ratio will you actually hold this MID to, and what happens at each step above it?

The answer resets the whole plan, because every control that follows is built to hold a gaming MID under the acquirer's figure rather than Visa's.

What monthly routine keeps a gaming MID's VAMP ratio under control?

Measure the ratio yourself, score fraud before authorization, resolve refunds and alerts inside the same calendar month, and fight only the disputes that evidence can remove.

High-risk merchants often ask how to cut chargebacks with their processor's help. Under VAMP, the sharper question is which levers change the numerator, which change the denominator, and which only feel productive. Here is the order I would work in.

1. Build your own ratio. Aggregator dashboards rarely surface a VAMP figure, and merchants describe digging through several reports to calculate it by hand. Get monthly TC40 and TC15 counts from your acquirer in writing, and know that a purchased TC40 feed may not capture every fraud report filed against you.
2. Score fraud before authorization. Stop card-testing attempts before they ever reach the authorization layer, and capture device ID and IP on every deposit. Block too hard, though, and good settled deposits vanish from the denominator while the fraud reports stay put, so the ratio rises instead of falling.
3. Route refunds inside the calendar month. Disputes resolved through RDR or CDRN drop out of the dispute line, and the evidence-based exclusions only count when resolution lands in the same calendar month as the dispute.
4. Deflect with evidence that removes events. Save your fights for fraud claims you can rebut with prior-transaction matches under Compelling Evidence 3.0, where qualifying cases leave the ratio entirely.

Visibility comes first. Without it, every other step is guesswork.

The pre-authorization step carries a second payoff. CE3.0 exclusions depend on device ID and IP captured on prior transactions and on 120 days of matching history, so that readiness cannot be bolted on after a bad month. The old habit of low-value first charges, anything between $0 and $5 ahead of a membership, now backfires too: a single fraud claim on one of them produces two fraud notifications.

Refund routing is where many gaming teams leave the ratio exposed. Alerts cost a fee per alert whether or not a refund goes out, and refunding every alert by reflex gives away disputes that a strong evidence file would have won. My rule is to let the actual risk position decide: auto-resolve where the ratio is tight, fight where there is room. No published benchmark says how fast a gaming refund must move. The calendar-month cutoff is the only hard deadline, so track two things from day one, the time from alert to refund and the share of cases resolved before month end, until your own pattern becomes visible.

Multi-MID operators face one more wrinkle. Ratios are judged per acquirer, so a merchant over the line at several acquirers can collect fines from each, and one high-risk payment provider reports acquirers passing on penalties at anywhere from $10 to $25 per case. I'd ask every acquirer for its enforced ratio separately rather than assume one answer covers all of them.

Each step protects settlement, not just compliance. Skip them and the path runs from fines to reserves to settlement pauses, and at the far end toward termination and a TMF/MATCH listing. Those settlement pauses can freeze funds for three to 14+ days before any formal notice arrives.

Where does VAMP pressure on gaming MIDs go from here?

Acquirers, not Visa's published 1.5% line, will set the working limit for gaming MIDs, and operators who score fraud early, refund fast and deflect disputes should hold their accounts.

The Merchant Risk Council flagged the direction early. In a January 2025 impact assessment, Keith Briscoe, the council's VP of Member Advocacy, wrote that acquirers might rationalize their merchant base before tighter thresholds arrived. He also expected fee exposure to reshape processing strategies, "particularly in higher risk merchant segments." Gaming sits squarely inside that group. I would pin his line that "fraud and dispute mitigation decisions are revenue decisions" above every operator's desk.

The common assumption is that a VAMP problem is a fraud problem. I disagree. Card fraud as a share of volume is edging down by a few basis points, yet every customer dispute still lands in the same numerator as a fraud report. A gaming MID with clean fraud numbers can breach on disputes alone.

Underwriters price the shape of a gaming business, not its name, and the monthly ratio is now part of that shape. For established operators with real volume behind them, the next move is practical: get the acquirer's internal number in writing, then plan every calendar month to sit well below it, beginning with the fraud score that runs before the first authorization.