Gaming Chargeback Rate 2026: Measure Yours Against the 1.5% Limits
Card networks publish the limits at which they act on a merchant, not a gaming average. What they do count is every fraud report and dispute on your own merchant account, which for a game means your direct-to-consumer sales. Below: the limits, the formula, a worked example, then the parental-dispute driver, the evidence for each dispute type, and how app stores and consoles change who carries the dispute.
Sources: Visa VAMP fact sheet (2025), Mastercard Excessive Chargeback Program guide (J.P. Morgan, rev. Dec 2019), Mastercard chargeback research.
From 1 April 2026 in the US, Canada, EU and Asia Pacific, with at least 1,500 fraud reports plus disputes in the month. It was 2.2% from 1 June 2025 until then. Visa fact sheet.
With at least 100 chargebacks in the calendar month. The High Excessive tier starts at 3% and 300 chargebacks. Mastercard program guide.
Visa VAMP ratio = (card-not-present fraud reports, TC40 + disputes, TC15) / settled transactions, TC05, for the month. Disputes resolved through pre-dispute tools such as Visa RDR and alerts are excluded, as are fraud reports that qualify under Compelling Evidence 3.0.
Mastercard ratio = chargebacks this month / sales transactions in the preceding month.
Worked example (illustrative inputs). A game sells currency packs through its own web shop and settles 250,000 Visa card-not-present transactions in November. That month it receives 2,400 TC40 fraud reports and 900 disputes: 3,300 / 250,000 = 1.32%. The count is over 1,500 but the ratio is under 1.5%, so Visa would not flag it; at the same volume, 3,750 events would. On Mastercard it ran 80,000 sales in October and received 1,000 chargebacks in November: 1,000 / 80,000 = 1.25%, under the limit.
Mastercard puts the average chargeback in gambling, gaming and crypto exchanges at $99 in 2025, against $110 for the US overall (Mastercard).
Which sales count toward your ratio
Only transactions on your own merchant account count toward your VAMP and Mastercard ratios. App Store, Google Play and console purchases are processed by the platform, so they do not. Direct-to-consumer revenue counts in full, and Visa applies VAMP enforcement through your acquirer without publishing the fee schedule. See Visa VAMP thresholds.
What drives gaming chargebacks
- 1.Parental disputes. A minor uses a parent's saved card to make in-game purchases. When the parent sees the statement, they report the charges as unauthorised, which creates a fraud report and a fraud-coded dispute.
- 2.Many small transactions. In-game purchases are small and frequent, and each one is a separate charge that can be disputed. One unhappy cardholder can generate several disputes and fraud reports at once, which moves both the ratio and the count.
- 3.Regret on virtual goods. In-game items are subjective in value. A customer who regrets a spend and cannot get a refund from the developer may go to the card issuer instead.
- 4.Card-not-present environment. Like other digital goods, there is no physical delivery evidence. Defence rests on access logs and item-grant timestamps.
Mastercard's research with Datos Insights finds first-party ("friendly") and third-party fraudulent chargebacks together make up around 45% of merchant chargeback volume globally (2025 data). Mastercard.
Reason codes game sellers see, and the evidence for each
Parental claims are filed as unauthorised transactions, so fraud codes matter most for direct-to-consumer game sellers. The networks do not publish how gaming disputes split across codes, so check your own processor dashboard for your mix.
Evidence: 3D Secure authentication record, age-verification logs, parental-control confirmation, IP geolocation, device fingerprint, customer-account historical purchase pattern, email confirmation sent to the cardholder's verified email address. For Visa 10.4, prior undisputed transactions from the same account or device can qualify under Visa Compelling Evidence 3.0.
Evidence: Clear billing descriptor with brand name, signup confirmation email, prior undisputed purchase history, customer-account login records, AVS match.
Evidence: In-game receipt log showing item delivered to account, account-access logs showing customer played the game after purchase, item-grant timestamp, customer's IP and device at the moment of purchase and immediately after.
Evidence: Subscription terms agreed at signup, billing-descriptor screenshot, in-product cancellation flow link, cancellation-policy URL, evidence of game launches after the disputed charge date.
Evidence: Refund policy URL, communications declining the refund, evidence the customer accessed or used the in-game item after the disputed date.
Platform-specific patterns
Who carries a dispute depends on who took the payment. Store and console developers lose the revenue on a refund or lost dispute; direct-to-consumer developers carry the whole dispute, fee and ratio impact.
Handling: Apple processes the payment for in-app purchases and handles disputes and refunds with the customer. The developer does not deal with the card dispute, but refunded purchases come out of the developer's proceeds.
Defense: Apple's Family Sharing and Screen Time controls provide parental controls. Design the in-app purchase flow to require explicit confirmation rather than one-tap purchase to reduce accidental-purchase refunds.
Handling: Similar to Apple. Google handles disputes and refunds through Google Play, and the developer sees the refund outcome rather than the underlying chargeback workflow.
Defense: Google Play parental controls and family payment settings. Require confirmation for new purchases while keeping friction low for repeat legitimate buyers.
Handling: When the storefront takes the payment, it handles the card dispute; the publisher sees the outcome in its revenue share.
Defense: Use the storefront's own refund and family-account tools, and keep in-game purchase confirmation explicit.
Handling: The developer is the merchant. Every dispute, fee and fraud report lands on its own merchant account and counts toward its VAMP and Mastercard ratios.
Defense: Account-based purchases, login confirmation, billing-descriptor clarity, post-purchase email to the verified account email, and 3D Secure on purchases your risk rules flag.
Handling: The platform holder takes the payment and handles disputes on the developer's behalf. Developer revenue is reduced by refunds and lost disputes, but the dispute process is managed by the platform.
Defense: Platform-level parental controls and family-account settings. Developer-side defence is limited to clear in-game purchase confirmation prompts and avoiding one-tap purchase patterns for high-value items.
Gaming-specific prevention patterns
- 1.Age verification at signup. Require date of birth at account creation. Send a parental confirmation email for accounts indicating under-18 status. This does not stop minors from lying, but it creates evidence that the merchant took reasonable steps.
- 2.Confirmation for purchases above a threshold. Require an additional confirmation step (PIN entry, password re-entry, biometric) for any single purchase above a value you set for your game. This targets accidental and child purchases.
- 3.Email receipts to the account holder. Send every purchase receipt to the verified account email, so the paying adult has contemporaneous notice of each charge and you have a record that it was sent.
- 4.3D Secure on higher-risk purchases. Activate 3D Secure on purchases your risk rules flag or above a value you set. Successful authentication shifts fraud liability from merchant to issuer under Visa and Mastercard rules.
- 5.Parental-control toggle. Expose a parental-control setting that requires PIN entry for in-app purchases. Placing it prominently (not buried in settings) creates merchant-side evidence of reasonable steps to prevent unauthorised purchases by minors.