Your real deadline is the processor’s, not the network’s. Visa allows 30 days and Mastercard 45, but processor response windows can be as short as 9 days.
The reason code decides your evidence. Fraud, authorization, processing error, and consumer dispute claims each demand a different package, and answering the wrong question is an automatic loss.
Friendly fraud has a fast lane. Visa Compelling Evidence 3.0 and Mastercard First-Party Trust shift liability back to the issuer when your data matching qualifies.
Winning does not fix your ratio. A won representment recovers the money, but the dispute already counted toward VAMP and your Mastercard counts. Fight to recover, prevent to survive.
A chargeback is not a verdict. It is an opening claim, and you are allowed to answer it. The process for answering is called representment: you send evidence back through your acquirer arguing the transaction was legitimate, and the cardholder’s bank rules on it. Merchants who fight win roughly half the time. Most merchants never fight at all, which is why the average business recovers only about one in eight chargebacks issued against it.
For a high-risk merchant the stakes are doubled. Every dispute you lose is revenue gone. Every dispute you receive, won or lost, counts toward the network ratios that decide whether you keep your merchant account at all. This guide covers both sides: how to win the fight, and how to know when fighting is the wrong move.
- REPRESENTMENT
- The formal process of contesting a chargeback: the merchant submits evidence through their acquirer that the disputed transaction was valid, literally “re-presenting” it to the issuing bank for a second decision.
Your real deadline is about a third of the official one
The rulebooks look generous. Visa gives the acquiring side 30 days to respond to a dispute, and Mastercard allows 45 days at each cycle. But that window belongs to your acquirer, not to you. Your processor needs time to review your evidence, format it, and submit it upstream, so it carves its own internal deadline out of the network one.
In practice that internal deadline is brutal. Adyen, for example, gives merchants 9 days to respond in the US and Canada and 18 days elsewhere. Other processors land in a similar range. Add the lag between the issuer filing the dispute and you actually seeing it, and many merchants have a single working week to assemble a case.
The operational fix is simple and unglamorous: find the response window in your processor’s dispute documentation today, not when the first chargeback arrives, and build your evidence pipeline so a complete package can ship in 48 hours. If you cannot pull order data, delivery confirmation, and customer communication for any transaction within two days, that is the first thing to fix.
The reason code decides your evidence, not your story
Every chargeback carries a reason code, and the code is effectively the question the issuer is asking. Answer a different question and you lose, regardless of how legitimate the sale was. The codes group into four families.
| Family | Typical codes | The issuer is asking | Evidence that wins |
|---|---|---|---|
| Fraud | Visa 10.x, MC 4837/4849 | Did the real cardholder participate? | Device fingerprint, IP history, login records, prior undisputed purchases |
| Authorization | Visa 11.x | Was there a valid approval? | The authorization record itself; without it, nearly unwinnable |
| Processing error | Visa 12.x, MC 4834 | Was the charge technically correct? | Processing records showing correct amount, currency, and no duplicate |
| Consumer dispute | Visa 13.x, MC 4853 | Did the customer get what they paid for? | Delivery confirmation, access logs, displayed cancellation policy, correspondence |
Source: Chargebacks911, Visa dispute rules and time limits
Fraud codes say the cardholder claims they never made the purchase, so the issuer wants proof the real customer participated. Authorization codes are nearly unwinnable if the approval record is genuinely missing: screen them out fast rather than burning hours on them. Processing error codes turn on your own records. Consumer dispute codes turn on delivery proof and what your checkout actually displayed.
Match your package to the family before you write a word. A beautiful rebuttal aimed at the wrong question is an automatic loss.
Fraud claims have a fast lane: CE 3.0 and First-Party Trust
Fraud reason codes dominate high-risk verticals, and most of them are not real fraud. They are friendly fraud: the cardholder made the purchase, then disputed it anyway. Both networks now run structured evidence programs that decide these cases on data matching rather than narrative.
Visa’s Compelling Evidence 3.0 applies to reason code 10.4, card-absent fraud. You qualify by producing two undisputed transactions from the same customer, each between 120 and 365 days older than the disputed one, where at least two data elements match across all three transactions, and one of the two must be the IP address or the device ID or fingerprint. Hit that standard and liability shifts back to the issuer.
Mastercard’s First-Party Trust program takes a different approach. Instead of demanding prior history, it asks for one data element from each of three categories: device (IP address, device ID or fingerprint), delivery (shipping address, email, phone), and identity (account login, billing address, device location). Because no prior transactions are required, it can protect even a first-time customer, which CE 3.0 cannot.
| Visa CE 3.0 | Mastercard First-Party Trust | |
|---|---|---|
| Applies to | Reason code 10.4 (card-absent fraud) | First-party (friendly) fraud disputes |
| Core evidence | 2 undisputed prior transactions, 120 to 365 days old, 2+ matching data elements | 1 element each from device, delivery, and identity categories |
| Mandatory element | IP address or device ID/fingerprint must be one of the matches | No single mandatory element; one per category |
| First-time customers | Not covered (history required) | Covered (no history required) |
| Result when qualified | Liability shifts to the issuer | Liability protection on the transaction |
Sources: Visa, CE 3.0 Merchant Readiness · Mastercard, First-Party Trust
The common thread: these programs reward merchants who capture rich session data at checkout. If you are not logging device fingerprints, IPs, and login identifiers against every order today, you are locked out of both fast lanes.
Build the package the way the issuer analyst reads it
The person deciding your case reviews stacks of these files. You win by making the decision easy.
- Confirm the code and the clock. Pull the reason code and your processor’s internal deadline the day the dispute lands. Everything else is scoped by these two facts.
- Check for a refund first. If the customer was already refunded, say so on page one with the refund reference. A chargeback filed after a refund is one of the cleanest wins available.
- Write a one-page rebuttal letter. The reason code, one sentence stating why the claim fails, then a numbered list of the evidence attached and what each item proves.
- Order exhibits strongest first. For a “merchandise not received” claim, the first attachment is the signed delivery confirmation, not your terms of service. Label everything; highlight the disputed transaction in logs; keep timestamps visible.
- Submit early, never at the wire. Ship the package at least two days inside your processor’s window so a formatting rejection still leaves time to fix and resubmit.
Never pad the file: analysts skim, and ten pages of boilerplate bury the two pages that win.
Winning the dispute does not fix your ratio
Here is the part most dispute guides skip, and it is the part that terminates high-risk accounts. Network monitoring programs count disputes when they are filed, not when they are resolved. A chargeback you later win at representment still counts toward your VAMP ratio with Visa and your Mastercard chargeback counts. You can win 90 percent of your representments and still breach the threshold that costs you the account.
Warning
A won representment still counts against you. VAMP and Mastercard’s monitoring programs tally disputes at filing. Representment recovers revenue; only prevention protects the account.
Chargeback disputes
Fighting works, but only if you actually fight
US merchant outcomes, share of chargebacks, percent
That means representment is a revenue-recovery tool, not a compliance tool. The decision rule looks like this: fight the disputes where the evidence is strong and the amount justifies the effort, refund proactively when a dispute alert (Verifi, Ethoca) gives you the chance to intercept before the chargeback posts, and put the real investment into stopping fraud before it becomes a chargeback so fewer disputes exist to fight.
Merchants who fight everything on principle lose twice: they burn team hours on unwinnable authorization codes, and the ratio damage accrues anyway. Merchants who fight nothing quietly donate half their disputed revenue back to friendly fraudsters. The playbook is selective aggression: fast, evidence-rich responses on winnable codes, immediate refunds where an alert lets you keep the dispute off your count, and prevention as the main line of defence. If you run recurring billing, start with our subscription chargeback prevention guide.
At a glance
- Visa response window
- 30 days (acquirer level)
- Mastercard response window
- 45 days per cycle
- Processor internal deadline
- As short as 9 days
- Win rate when contested
- ~54% (US average)
- CE 3.0 scope
- Visa reason code 10.4 only
- After representment
- Pre-arbitration, then arbitration (loser pays fees)
FAQ
How long do I have to dispute a chargeback?
Formally 30 days on Visa and 45 on Mastercard, but your processor’s internal deadline is shorter, sometimes under 10 days. Check your processor’s documentation and treat that date as the real one.
What win rate should I expect?
US merchants who contest disputes win a little over half on average. Rates run higher with strong data capture and lower in verticals where evidence is thin, like digital goods.
Does winning a representment remove the chargeback from my VAMP ratio?
No. The dispute counted the moment it was filed. Winning recovers the money, not the ratio.
Should I fight friendly fraud from a repeat customer?
Yes, and these are your strongest cases: prior purchase history is exactly what Visa CE 3.0 is built to use. Then block the customer from future purchases.
What happens if the issuer rejects my representment?
The next stage is pre-arbitration and then arbitration, where the network itself rules and the loser pays fees that often exceed the transaction. Reserve it for high-value disputes with airtight evidence.
- Visa, “Compelling Evidence 3.0 Merchant Readiness,” usa.visa.com merchant readiness PDF, March 2023.
- Mastercard, “Scaling efforts to combat friendly fraud” (First-Party Trust), mastercard.com press release, June 2025.
- Chargebacks911, “Visa Chargeback Time Limits: The 2026 Guide,” chargebacks911.com, 2026.
- Chargebacks911, “Mastercard Chargeback Time Limits: The 2026 Guide,” chargebacks911.com, 2026.
- Chargeflow, “Visa Chargeback Dispute Rules, Fees and Time Limits (2026),” chargeflow.io, 2026.
- Chargeback.io, “Chargeback Statistics 2026,” chargeback.io, 2026.
- Chargebacks911, “Chargeback Win Rate Complete Guide for Merchants,” chargebacks911.com, 2026.
