How to Win a Chargeback as a Merchant: The Representment Playbook

You Don't Have to Eat Every Chargeback

When a chargeback lands, the money is already gone. The issuing bank has pulled the funds from your account, your processor has charged you a fee, and the notice in your portal reads like a verdict.

It isn't. It's an accusation — and you get to answer it.

The process for answering is called representment: you literally re-present the transaction to the cardholder's bank, this time with evidence. Merchants who do it well win a meaningful share of the disputes they fight. Merchants who do it badly — late responses, generic evidence, angry letters — lose almost all of them.

This guide covers the fighting side: how representment works, which disputes are worth contesting, exactly what evidence wins each dispute type, and what the published win-rate data actually says. If you're looking to stop chargebacks before they happen, that's a different discipline — start with our chargeback prevention guide. And if you're not yet sure how disputes work at all, read what is a chargeback first.

The Representment Process in Plain English

Strip away the jargon and the flow is simple:

1. The cardholder disputes the charge. They call their bank (the issuer), not you. The issuer assigns a reason code — a short code that says why the money is being clawed back: fraud, product not received, not as described, credit not processed, and so on.
2. The money is reversed provisionally. The funds leave your merchant account, and your processor notifies you of the dispute, the reason code, and your response deadline.
3. You build an evidence package. Documents that rebut the specific claim behind the reason code — not a general defense of your business.
4. You submit through your processor. Your processor forwards the package to the issuer. This is the representment.
5. The issuer re-reviews. A bank analyst compares your evidence against the cardholder's claim and decides. Win, and the funds come back (the chargeback fee usually doesn't). Lose, and the reversal stands — with a possible pre-arbitration round after that.

Two things about this process surprise most merchants. First, the reviewer is a stranger at a bank who will spend minutes, not hours, on your case — clarity beats volume. Second, the whole thing runs on deadlines that are shorter than they look, which we'll get to below.

Decide Fast: Is This One Worth Fighting?

Not every chargeback deserves a fight. The first move — ideally the same day the notice arrives — is triage:

Dispute situation	Usually fight?	Why
Friendly fraud (customer got the goods, disputes anyway)	Yes	You have delivery and usage evidence; this is the most winnable category
Quality / "not as described" complaints	Yes	Your listing, photos, and correspondence usually tell a better story than the claim
Subscription "I cancelled" disputes	Yes	Signup and cancellation logs are hard evidence
True fraud on a card-not-present order (stolen card, no AVS/CVV match)	Usually accept	If the card really was stolen, you will lose; save the fee and fix your fraud screening
Tiny amounts	Do the math	If the transaction is $18 and fighting costs you an hour plus a possible fee, acceptance can be the rational call

Two caveats on the "accept" rows. Even chargebacks you accept still count against your chargeback ratio, so a policy of always folding is not free — it just moves the cost. And if you're in a high-risk category where your ratio is under a microscope, preventing the dispute from becoming a chargeback at all (via alert services) matters more than winning it afterward. Our high-risk program includes free chargeback alerts (Verifi, Ethoca) and representment guidance for exactly this reason — see high-risk merchant account fees for how those accounts are structured.

The Evidence Playbook, by Dispute Type

Representment is won or lost on fit: the evidence must answer the specific claim, not vouch for your character. Here's what wins each common dispute type.

Product Not Received

The claim: "I never got it." The rebuttal: proof it arrived.

• Carrier tracking number with a delivered status
• Delivery confirmation showing the address matches the order's shipping address
• Signature confirmation if you have it — this is close to a trump card
• For digital goods or services: download logs, license activations, or appointment records showing fulfillment

Fraud / "I Didn't Authorize This"

The claim: "That wasn't me." The rebuttal: evidence the real cardholder placed the order.

• AVS and CVV match records from the original authorization — a full match undercuts the stolen-card story
• IP address and device data tying the order to the cardholder's usual location or a device used on prior orders
• Order history: prior undisputed purchases from the same customer, same card, same address
• Any communication where the customer references the order (emails, support tickets)

If none of that exists — mismatched AVS, new customer, shipping address you can't connect to the cardholder — revisit the triage table. This is the accept column, and the real fix is upstream in your fraud prevention setup.

Not as Described / Defective

The claim: "It wasn't what I ordered." The rebuttal: what you promised versus what shipped.

• The listing copy and photos as they appeared at purchase
• Correspondence with the customer — especially if they never mentioned a problem, or you offered a fix and they went straight to their bank
• Your return policy, with proof it was displayed at checkout and whether the customer used it
• Quality-control or shipment records for the specific item, if you have them

Subscription / "I Cancelled"

The claim: "I cancelled and you kept billing." The rebuttal: the paper trail.

• Signup logs showing the customer's acceptance of recurring terms (timestamp, IP)
• Cancellation policy acknowledgment at enrollment
• Usage logs showing the customer logged in or used the service after the alleged cancellation date
• Your cancellation records — or the absence of any cancellation request

Credit Not Processed

The claim: "They promised a refund that never came." The rebuttal is short: your refund records. If you issued the credit, show the transaction ID and date. If you didn't because the return never arrived or fell outside policy, show the policy and the correspondence. If you simply forgot to process a promised refund — issue it and accept the dispute; you will not win this one.

Deadlines Matter More Than Eloquence

A perfect evidence package submitted a day late loses to a mediocre one submitted on time. There is no appeal for missing the window.

Response windows are short and vary by card network and processor. Under network rules, merchant response windows commonly run in the 20–45 day range — roughly 30 days for Visa, 45 for Mastercard, 20 for American Express, and 30 for Discover, per Chargeback Gurus' guide to chargeback time limits (see Sources). But treat those as ceilings, not promises:

• Your processor's dispute notice states your exact deadline — use that number, always. Processors often set internal deadlines shorter than the network's so they have time to format and forward your package.
• The clock can start before you find out. Response windows may begin when the dispute is filed, not when you're notified, so days can be gone before you ever see the notice.

The operational fix is boring and effective: check your dispute queue every business day, and start pulling evidence the day a notice arrives — not the week the deadline approaches.

How to Write the Rebuttal Letter

The rebuttal letter is the cover page of your evidence package. One page. Its only job is to make the analyst's decision easy.

• Lead with the reason code. First line: the dispute reference number, the reason code, and one sentence stating why the dispute is invalid.
• Map each evidence item to the claim. Number your exhibits and connect each one to the specific assertion it rebuts: "Exhibit 2: carrier confirmation showing delivery to the cardholder's verified address on March 4."
• State facts, not feelings. No adjectives about the customer, no complaints about the process, no story of your business's hardships. The analyst is a neutral party scoring evidence against a claim; emotion reads as a substitute for proof.
• Keep the package lean. Include what rebuts the claim and nothing else. Twenty pages of unlabeled screenshots is how strong cases lose.

How Often Do Merchants Win Chargeback Disputes?

Honest answer: it depends heavily on who's counting, and published figures vary widely by industry, dispute type, and how selectively merchants fight.

The most-cited recent dataset is Mastercard's 2025 State of Chargebacks report, which found that merchants challenge a little over half of the chargebacks they receive — and of those contested cases, issuers win about 75%, merchants win about 20%, with roughly 5% escalating to pre-arbitration or arbitration. The same report shows how much strategy matters: 52% of large enterprises reported win rates above 50%, versus 36% of mid-market merchants.

Read those numbers carefully. The 20% aggregate includes every merchant who fights unwinnable true-fraud disputes with weak evidence. Merchants who triage ruthlessly — fighting only the disputes where they hold delivery proof, match data, or logs — report dramatically better outcomes, which is exactly what the large-enterprise numbers suggest. No single published win rate is reliable as a benchmark for your business; your own tracked results over a few months are the only number that matters.

After the Verdict

If you win: the funds return to your account. Log what evidence carried the case — that's your template for next time.

If you lose, there's one more round. The issuer (or you, depending on direction) can escalate to pre-arbitration, a second review where new evidence or a rules argument gets one more look. Past that lies formal network arbitration, where filing fees typically run to hundreds of dollars and the loser pays. Practical translation: pre-arbitration is worth engaging only when the amount is substantial and your evidence is genuinely strong. For a routine $60 dispute, a pre-arb loss costs far more than letting go.

Either way, close the loop. Every dispute is a diagnostic. A cluster of "not received" disputes says add signature confirmation. Repeated "didn't authorize" disputes say your billing descriptor is unrecognizable or your fraud screening is porous. Subscription disputes say your cancellation flow is too hard to find. Feeding each verdict back into your operations is how the fight column gets smaller — and that upstream work is the whole subject of our chargeback prevention guide, which pairs with this one: prevention shrinks the number of disputes you face, representment recovers the ones that get through anyway.

Fight Smarter — and Pay Less While You're At It

Winning disputes protects revenue you've already earned. But if you're paying $35 per chargeback and an inflated rate on every clean transaction, the fee side of your statement is leaking money too. Send us a statement through our free statement review and we'll show you exactly where.

Sources

• Chargeback Gurus, "A Merchant's Guide to Chargeback Time Limits" — https://www.chargebackgurus.com/blog/dont-run-out-the-clock-understanding-chargeback-time-limits (observed September 2026)
• Chargeback Gurus, "Chargeback Stats and Insights from Mastercard's State of Chargebacks Report" (summarizing Mastercard, 2025 State of Chargebacks) — https://www.chargebackgurus.com/blog/chargeback-stats-and-insights-from-mastercards-state-of-chargebacks-report (observed September 2026)