Mon–Sat 8:00 AM–6:00 PM IST · Sunday Closed +91 977 447 2022 business@integratedchargebackmanagement.com

Visa & Mastercard Chargeback Rules, Explained for Merchants

Reason code categories, response deadlines, and what Visa's VAMP program actually measures — the practical version, not the 40-page operating regulations.

A note on accuracy: card network rules, thresholds, and fees change frequently and can vary by region and acquirer. This page reflects publicly available program information as of 2026. Always confirm current figures with your acquirer or processor before making business decisions.
VISA

Visa Dispute Categories

Visa organizes disputes into four numbered categories. The first digit of the reason code tells you immediately which category you're dealing with — and which kind of evidence will actually matter.

CategoryCode RangeCoversExample Codes
Fraud10.xTransactions the cardholder says they never authorized10.1 Counterfeit fraud · 10.4 Card-absent fraud
Authorization11.xTransactions processed without proper authorization11.2 Declined authorization · 11.3 No authorization
Processing Errors12.xMerchant-side processing mistakes12.1 Late presentment · 12.5 Incorrect amount · 12.6 Duplicate processing
Consumer Disputes13.xDisputes over the goods, service, or transaction itself13.1 Merchandise not received · 13.3 Not as described · 13.6 Credit not processed

Response deadlines

Merchants get a uniform 30 days to respond at each phase of a Visa dispute, starting the day after Visa initiates that phase. Cardholders, on the other hand, typically have up to 120 days from the transaction or expected delivery date to file — and up to 540 days for certain reason codes.

The Visa Acquirer Monitoring Program (VAMP)

Visa retired its older Visa Dispute Monitoring Program (VDMP) and Visa Fraud Monitoring Program (VFMP) in favor of VAMP, a single combined risk score. VAMP enforcement began October 1, 2025, and shifts the emphasis from flagging individual merchants toward monitoring risk at the acquirer-portfolio level — meaning your bank or processor now has direct visibility into your dispute activity as part of their own risk exposure.

ClassificationThresholdMinimum Volume
Merchant — Excessive (most regions)1.5%1,500 combined TC40/TC15 records
Merchant — Excessive (CEMEA region)2.2%1,500 combined TC40/TC15 records
Acquirer — Above Standard0.5%–0.7%1,500 combined TC40/TC15 records
Acquirer — Excessive≥0.7%1,500 combined TC40/TC15 records

Thresholds shown reflect the revised figures effective April 2026. The VAMP ratio is calculated as (fraud reports + disputes) ÷ total transaction count; a related "enumeration ratio" separately tracks card-testing style attacks.


MASTERCARD

Mastercard Dispute Categories

Mastercard groups its reason codes into four functional categories, simplified in its 2016 reason-code overhaul.

CategoryFocusExample Codes
Authorization-RelatedErrors in the authorization request4808
Point-of-Interaction ErrorProcessing errors during the transaction4834
Cardholder DisputeChallenges to goods, services, or transaction terms4853, 4854
Fraud-RelatedUnauthorized or fraudulent activity4837, 4849, 4870, 4871

Response deadlines

Mastercard gives merchants a consistent 45 calendar days to submit representment documentation through their acquirer's dispute platform. Issuers and cardholders generally have 90–120 days to file the original dispute, depending on the specific reason code.

The practical takeaway for small merchants: the exact code matters less than the category. Authorization and processing-error disputes are usually about your systems and paperwork; fraud and cardholder disputes are usually about evidence — proof of delivery, agreed terms, and communication history. Knowing which bucket you're in tells you what to gather first.

Not sure which reason code you're looking at?

Send it our way — we'll tell you what it actually means and what evidence gives you the best shot at winning.