How to win a chargeback, a reason code by reason code playbook

How a chargeback is decided

A chargeback starts when a cardholder contacts their bank and the issuer files a dispute through the card network. The issuer picks a reason code that describes the claim, such as fraud, goods not received or a canceled subscription. Your processor notifies you, pulls the funds and gives you a window to respond.

Your response is called representment. Your processor passes it to the acquirer, which forwards it to the issuer. A reviewer at the issuing bank compares your evidence with the claim and decides whether to reverse the chargeback or keep it. If the issuer keeps it and you still disagree, the case can move to pre-arbitration and then to arbitration with the network.

The reviewer is not reading your file for fairness in general. They are checking one question that the reason code defines. A fraud code asks whether the real cardholder made or benefited from the purchase. A not received code asks whether the goods or service arrived. A canceled recurring code asks whether the cardholder canceled before the charge. Evidence that does not answer that question does not help.

The five steps that win most disputes

1. 1 Read the reason code and the network, and write down in one sentence what the cardholder is claiming.
2. 2 Check the deadline your processor shows, not the network deadline. Processors give you less time so they can forward your file.
3. 3 Collect evidence that answers the claim directly, from your order system, payment records, shipping carrier, product logs and support inbox.
4. 4 Write a short rebuttal letter that states the claim, states why it is wrong and points to each exhibit by number.
5. 5 Submit once, as a clean file. Most processors do not let you add documents after submission.

Match your evidence to the reason code

Every network uses different numbers, but the claims fall into the same families. The table below maps the codes merchants see most often to the evidence that tends to answer them. Our full reason codes library has a page for each code with the exact evidence checklist.

Fraud disputes, Visa 10.4 and Mastercard 4837

Fraud claims are the hardest to win with documents alone, because the cardholder says they never made the purchase. Your goal is to show that the same person who owns the card placed the order or benefited from it.

Strong evidence includes a successful 3D Secure authentication, which usually shifts liability to the issuer before the dispute even starts. Without 3D Secure, show AVS and CVV matches, the IP address and device used, and any link between this order and earlier orders on the same card that were never disputed. For Visa 10.4, that link can qualify the dispute for Compelling Evidence 3.0, which shifts liability back to the issuer when the data matches the program rules.

For digital products and SaaS, account activity is the best fraud evidence you have. A login from the same device and IP that placed the order, followed by real use of the product, is hard to reconcile with a claim that the cardholder never authorized the charge.

Not received disputes, Visa 13.1 and Mastercard 4855

For physical goods, the issuer wants carrier proof that the package was delivered to the address on the order. Tracking that only shows shipped is weak. Tracking that shows delivered, with a date, a delivery photo or a signature, is strong. If the delivery address differs from the billing address, add proof the cardholder chose it, such as a saved address in their account.

For services and digital goods, there is no tracking number, so your logs replace it. Show the account creation date, the email used, logins, downloads, or sessions after the purchase date. A timeline with timestamps reads better than a raw log export.

Not as described disputes, Visa 13.3 and Mastercard 4853

Here the issuer asks whether the product matched what you promised. Include a capture of the product page as it looked at the time of sale, the order confirmation, and your return policy. If the cardholder never contacted you or never returned the item, say so and show the empty support history. Many issuers expect the cardholder to have tried to resolve the problem with the merchant first.

Canceled recurring disputes, Visa 13.2

Subscription merchants see this code often. Win it by showing that the cardholder agreed to recurring billing, that you disclosed the price and the renewal date, that you sent the reminders your network rules require, and that there was no cancellation request before the charge. Usage after the renewal date is the most persuasive single exhibit, because it shows the cardholder kept receiving value.

Credit not processed, Visa 13.6

If you already refunded, send the refund record with the date, amount and reference. Issuers usually reverse these quickly. If you did not refund because the item was not eligible, show the policy, where the cardholder saw it, and the event that made the item ineligible.

Write a rebuttal letter the reviewer can read in one minute

Reviewers handle many cases a day. A one page letter with a clear structure beats a long narrative. Start with the merchant name, the transaction date, the amount, the dispute reference and the reason code. Then state the claim in one sentence and your answer in one sentence.

Below that, list each exhibit with a short description of what it proves. Refer to the exhibits by number in the order they appear in the file. Avoid emotional language, avoid blaming the cardholder, and do not include internal notes or unrelated screenshots. Our chargeback rebuttal letter template shows the structure line by line.

• Lead with the evidence that answers the reason code, not with the order history.
• Highlight the data points that match, such as the same IP, the same email or the same address.
• Keep each exhibit readable, with no cropped dates and no images that need zooming.
• Convert everything into one file in the format and size your processor accepts.

Common mistakes that lose winnable disputes

• Sending the full order history instead of the evidence for the reason code that was filed.
• Missing the processor deadline because the dispute notice went to an inbox nobody watches.
• Uploading screenshots with no dates, no order number and no way to tie them to the transaction.
• Issuing a refund after the dispute opened, which can leave you paying twice.
• Arguing about the cardholder's character instead of proving the facts of the order.
• Using a generic letter for every code, so the reviewer has to search for the relevant exhibit.

When to accept a chargeback instead

Not every dispute is worth fighting. Accept when the cardholder is right, when you cannot produce evidence for the specific claim, or when the amount is lower than the time and fees it costs to respond. Accepting fast also closes the case cleanly and keeps your team focused on disputes you can win.

Some disputes are better stopped before they become chargebacks at all. Pre dispute chargeback alerts warn you while the cardholder is still talking to the bank, so you can refund and avoid the dispute, the fee and the hit to your ratio.

Turn dispute response into a repeatable process

Merchants who win more disputes rarely write better letters by hand. They build a process where the evidence is collected automatically when the order happens, so it is ready when the dispute arrives. That means storing IP addresses, device data, AVS and CVV results, delivery confirmations, login events and the exact terms the customer accepted.

With that data in place, every dispute becomes a matching exercise: read the code, pull the evidence for that code, generate the letter and submit before the deadline. That is what automated chargeback management does at scale, and it is the core of a chargeback prevention program that also keeps your dispute ratio under network limits.

Track the results, not just the volume

Measure your win rate per reason code, not as one number. A low win rate on 13.1 usually points to weak carrier evidence. A low win rate on 10.4 usually points to missing authentication or device data. Each pattern has a different fix, and most fixes happen at checkout, not in the dispute response.