Digital Goods Chargeback Rate 2026: Check Yours Against the 1.5% Limits

Card networks publish the limits at which they act on a merchant, not a digital goods average. Instant delivery, no tracking number and easy card testing make the category fraud-heavy, and on Visa every fraud report counts toward your ratio. Below: the limits, the formula, a worked example, then the drivers and the evidence for each dispute type.

Sources: Visa VAMP fact sheet (2025), Mastercard Excessive Chargeback Program guide (J.P. Morgan, rev. Dec 2019), Mastercard chargeback research.

1.5%
Visa VAMP Excessive Merchant ratio

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.

1.5%
Mastercard Excessive Chargeback Merchant ratio

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 software download store settles 120,000 Visa card-not-present transactions in May. That month it receives 1,100 TC40 fraud reports and 700 disputes: 1,800 / 120,000 = 1.5%, with more than 1,500 events, so Visa would identify it as an Excessive merchant. Note that the fraud reports, not the disputes, push it over. On Mastercard it ran 30,000 sales in April and received 390 chargebacks in May: 390 / 30,000 = 1.3%, under the limit.

What happens at the threshold

Visa applies VAMP enforcement through your acquirer, and Visa does not publish the fee schedule. Visa also measures each acquirer's whole portfolio (Above Standard from 0.5%, Excessive from 0.7%), so your acquirer has its own reasons to act on a high-ratio merchant before you reach 1.5%. See Visa VAMP thresholds and April 2026 update.

What drives digital goods chargebacks

Four structural drivers:

  • 1.
    No physical delivery proof. There is no tracking number or signature. Your evidence is access logs, downloads and activations, so those need to be captured at the moment of fulfilment.
  • 2.
    Instant fulfilment. No cancellation window between purchase and fulfilment. Cardholders who change their mind cannot stop the order; some file a dispute instead.
  • 3.
    Friendly fraud and card testing. The product is consumed before any dispute is filed. Visa reports that "nearly one in five consumers who have filed a chargeback dispute have committed first party fraud" (Visa, June 2022), and Mastercard puts first-party and third-party fraudulent chargebacks together at around 45% of merchant chargeback volume globally (2025 data). Instantly delivered goods are also a target for stolen-card testing, which generates TC40 fraud reports.
  • 4.
    Limited merchant recourse. The merchant cannot retrieve a downloaded file and often cannot usefully revoke a key. A lost dispute loses the full transaction value.

Fraud reports often lead to disputes: Stripe says about 40% of Visa and Mastercard early fraud warnings become fraud disputes.

Reason codes digital goods merchants see, and the evidence for each

The code tells you what the cardholder claimed and therefore what evidence answers it. The networks do not publish how digital goods disputes split across codes, so check your own processor dashboard for your mix.

Merchandise/Services Not Received (Mastercard: Goods or Services Not Provided)
Visa 13.1 / Mastercard 4855

Evidence: License key activation log, download IP and timestamp, account login records, fulfilment confirmation email with delivery confirmation, machine fingerprint at first activation.

Not as Described or Defective (Mastercard: Cardholder Dispute)
Visa 13.3 / Mastercard 4853

Evidence: Product description at time of purchase (screenshot), terms of service, customer-support communications about the dispute issue, refund offers extended, evidence the customer continued using the product after purchase.

Cardholder Does Not Recognize - Potential Fraud (Mastercard). Visa has no separate code: these arrive as 10.4 fraud
Mastercard 4863 / Visa 10.4

Evidence: Clear billing descriptor showing brand name and URL, signup or purchase confirmation email with timestamp, customer access logs, AVS match, IP address geolocation at purchase.

Other Fraud, Card-Absent Environment (Mastercard: No Cardholder Authorization)
Visa 10.4 / Mastercard 4837

Evidence: 3D Secure authentication record, AVS and CVV match, IP geolocation, device fingerprint, prior undisputed purchase history. For Visa 10.4, prior undisputed transactions from the same account or device can qualify under Visa Compelling Evidence 3.0.

Cancelled Merchandise/Services (Mastercard: Cardholder Dispute)
Visa 13.7 / Mastercard 4853

Evidence: Refund policy URL and screenshot, communications declining a refund where the merchant policy allows it, evidence the customer accessed or used the product after the disputed date.

Prevention playbook

Four moves aimed at the drivers above. Track your own ratio monthly with the formula above to see what each one does for you.

License-key activation telemetry

Log the timestamp, IP address, geolocation, and machine fingerprint of every license-key activation. Treat first activation as the equivalent of physical-goods delivery confirmation and attach it to responses to Visa 13.1 and Mastercard 4855 disputes.

Why it works: It turns a claim of non-delivery into a question of fact you can answer with a log line.

Clear billing descriptor with URL

Set the processor billing descriptor to include the brand name and the product URL (e.g. ACMEAPP-COM-INVOICE). Card statements display this descriptor to the cardholder.

Why it works: A recognisable string cuts does-not-recognise disputes and the fraud reports that come with them.

3D Secure on higher-risk purchases

Enable 3D Secure on transactions your risk rules flag, and on purchases above a value you set for your catalogue. Successful 3DS authentication shifts fraud liability from merchant to issuer under Visa and Mastercard rules.

Why it works: Fraud-coded disputes on authenticated transactions become the issuer's loss, not yours. Stripe notes that about 40% of Visa and Mastercard early fraud warnings become fraud disputes, so stopping fraud at checkout also keeps TC40 reports out of your VAMP ratio. Source: Stripe.

Easy refund and cancellation policy

Offer a clearly documented refund window and a one-click cancellation flow, and make the support route easy to find from the receipt.

Why it works: A refund costs the sale. A chargeback costs the sale plus fees and handling: Mastercard's 2026 research with Javelin puts merchants' average cost at $128 per chargeback ($82 internal, $46 third-party).

Updated November 2026