How to Respond to a Chargeback: Step-by-Step Guide for Merchants (+ Free Template)

Chargeback Shield team · Updated August 28, 2026 · 8 min read

A chargeback lands in your dashboard, the money is already gone from your balance, and you have a deadline counting down. What you do next decides whether that revenue comes back. This guide walks through the representment process step by step — what to check first, what evidence actually persuades an issuing bank, and how to structure the rebuttal letter — with a template you can adapt at the end.

1. What actually happens when a chargeback is filed

When a cardholder disputes a charge, their issuing bank pulls the funds back from your acquiring bank, which passes the debit — plus a fee — on to you. At that moment the cardholder has, in effect, won by default. Representment is your formal right to contest it: you "re-present" the transaction to the issuer with evidence that the charge was legitimate.

The issuer's analyst then reviews your response against the card network's rules for that specific dispute category. They don't know your business and won't give you the benefit of the doubt — your response has to stand entirely on the documents you attach and how clearly they map to the claim being made.

2. Know your deadline — it's shorter than you think

Response windows are set by the network and enforced by your processor, and the processor's own cutoff is usually a few days earlier than the network's so they have time to forward your case. Typical windows from the date the chargeback is raised:

• Visa: 30 days
• Mastercard: 45 days
• American Express / Discover: typically 20 days

Treat the date shown in your processor's dashboard as the real deadline. A perfect response submitted late is a guaranteed loss — if you're short on time, a good response today beats a great one after the cutoff.

3. Read the reason code before you write a word

Every chargeback carries a reason code — Visa 13.1, Mastercard 4853, Amex C08, Discover RG — that defines exactly what the cardholder is alleging. The code dictates what you must prove. A response that proves the wrong thing loses even when the charge was completely legitimate.

The classic example: the code says "merchandise not received" and the merchant responds with signature-match evidence proving the cardholder authorized the purchase. Irrelevant — authorization was never in question. The issuer needed proof of delivery, didn't get it, and upholds the chargeback.

4. The evidence that wins, by dispute type

"I never received it" (Visa 13.1, Mastercard 4855, Amex C08, Discover RG)

• Carrier tracking showing delivered status to the address on the order
• Proof of delivery with signature, if you have it
• The order confirmation showing the shipping address the customer entered
• For digital goods: server logs showing download, access, or usage after purchase

"I didn't authorize this" (Visa 10.4, Mastercard 4837, Amex F24)

• AVS and CVV match results from the transaction
• 3-D Secure authentication results if used
• IP address / device data consistent with the cardholder's billing address
• History of prior undisputed orders from the same customer

"Not as described / defective" (Visa 13.3, Mastercard 4853, Amex C31/C32, Discover RM)

• The product listing or service description the customer saw at purchase
• Photos, specs, or the signed statement of work
• Any customer-service correspondence — especially if they never reported a problem or refused a remedy you offered
• Your return policy and evidence it was presented at checkout

"I cancelled" (Visa 13.2, Mastercard 4841, Amex C18, Discover AP)

• Your cancellation terms and where the customer agreed to them
• Logs showing no cancellation request before the billing date — or that service was used after the alleged cancellation

5. Structuring the rebuttal letter

Issuer analysts work through stacks of these. A response they can grasp in sixty seconds gets a fairer read than ten unstructured paragraphs. Use four labeled sections:

1. Summary of case — one short paragraph: order number, amount, date, reason code, and your position in a single sentence.
2. Merchant position — directly rebut the specific allegation the reason code makes. Nothing else.
3. Supporting evidence — a numbered list, each item saying what the document proves, matching the attachments in order.
4. Conclusion — a respectful, one-sentence request for reversal.

6. Free chargeback response template

Skip the blank page. Chargeback Shield asks for your case details, matches the reason code, and drafts this letter for you — your first draft is free.

7. Five mistakes that lose winnable disputes

1. Answering the wrong question. Proving authorization on a non-receipt claim, or delivery on a fraud claim. Match your rebuttal to the code.
2. Missing the processor's deadline. It is earlier than the network's. Late equals lost, regardless of merit.
3. Dumping raw files with no narrative. Twelve unlabeled attachments force the analyst to build your argument for you. They won't.
4. Emotion instead of evidence. Frustration is understandable; it persuades no one. Keep it factual and professional.
5. Refunding after the chargeback. Once a chargeback is open, a refund doesn't close it — you can lose both the money and the dispute. Respond through the process instead.

Fighting disputes is partly a numbers game: the faster you can produce a quality response, the more of them you'll contest instead of writing off. That's the entire point of Chargeback Shield — structured, professional drafts in minutes, matched to the right reason code, exported as a submission-ready PDF.