Chargeback Ratio Thresholds Can Cut Off Your Payments

Visa's threshold for what it classifies as an "excessive" dispute ratio dropped to 1.5% effective April 1, 2026. Mastercard's equivalent program triggers at the same 1.5% ratio, but only needs 100 disputes in a single month to enroll a merchant, a bar that a mid-size studio running its own web shop can clear faster than the Visa number suggests. Neither of these thresholds cares why the disputes happened. They only count the ratio.

This isn't the platform fee shift, it's a card network cutting off processing

Studios that have been reading up on chargebacks recently have mostly been tracking Google Play's move to stop absorbing chargeback fees, which turns disputes into a direct cost on the platform side. That's a real and separate issue. What Visa and Mastercard are doing operates one layer down, at the payment network itself, and it applies regardless of which platform or payment processor sits on top of it — including a studio's own direct-to-consumer web shop running Stripe, Braintree, or a similar processor.

Visa's VAMP program measures a combined fraud-plus-dispute ratio against your settled transaction volume. Cross 1.5% and you're in a monitoring tier with intervention requirements. Cross 1.8% and Visa expects immediate remediation. Mastercard's Excessive Chargeback Merchant program enrolls at 1.5% combined with 100+ disputes in a month, and its higher-severity tier kicks in at 3% and 300+ disputes with steeper penalties attached. For comparison, most payment processors themselves cap acceptable merchant chargeback rates well below that: Stripe's own threshold sits around 0.5%, with PayPal, Shopify, and Authorize.net closer to 1%. A studio that's fine by its processor's own rules can still be closer to a network-level enrollment than it thinks, because the processor threshold and the network threshold aren't the same number and aren't measured the same way.

Why a mobile game crosses this line without anyone noticing

A studio running an active live-ops calendar generates chargebacks from more sources than outright fraud. A player disputes a purchase they made and simply changed their mind about, which their bank often processes as fraud regardless of the real reason. A limited-time bundle triggers confusion about what was actually purchased. A subscription renewal surprises a player who forgot they'd signed up. None of these are criminal fraud, but every one of them counts identically toward the same ratio a card network is watching.

The ratio also moves against a shrinking denominator during a slow month. If your total transaction volume dips — a seasonal lull, a slower content cadence — the same absolute number of disputes represents a higher percentage of a smaller pool. A studio that was comfortably under 1% during a strong month can drift toward 1.5% during a quiet one without a single additional dispute actually happening.

What actually gets a studio flagged, and what to do before it happens

The mechanism that gets you enrolled isn't a single bad month, it's a sustained ratio measured over a rolling window, which means the fix has to be structural rather than reactive. Three things move the needle before enforcement, not after:

Instrument the reason code on every dispute you receive, not just the count. Visa and Mastercard both provide dispute reason codes that distinguish fraud from "product not as described" from "duplicate charge" — and a studio that can see its disputes clustering under one reason code has a specific product or purchase-flow problem to fix, not an abstract fraud number to worry about.

Fix the purchase flow issues that generate confusion-driven disputes before they become chargebacks. A limited-time offer that isn't clear about what it grants, a subscription renewal notice that arrives too late for a player to cancel first, an accidental double-tap on a bundle purchase — all of these produce disputes that a clearer purchase flow prevents at the source, which is cheaper than winning the dispute after the fact.

Watch the ratio, not just the count. A dashboard that tracks disputes as a percentage of settled transactions, updated on the same rolling basis the card networks use, is the only way to see a threshold approaching before a network notice arrives. Waiting for that notice means you're already enrolled in a monitoring program with intervention requirements attached.

The cost of getting flagged is bigger than the fees

Enrollment in one of these programs isn't just an extra fee per disputed transaction, though Visa's own estimate puts that cost around $8 per dispute above the threshold. The real risk is what happens if the ratio doesn't come back down: sustained non-compliance can lead to a merchant account being terminated by the acquiring bank, which for a studio running a direct-to-consumer web shop means losing the ability to take payments outside the app stores entirely, at exactly the moment more studios are building external payment paths to reduce platform fee exposure. A studio that treats this as a bookkeeping line rather than an operational risk is the one most likely to find that out the hard way.