How to Fight a Chargeback: Read the Code, Build the Packet, Write the Rebuttal

How to fight a chargeback in seven steps: read the reason code, check the deadline, decide whether to fight, build a claim-matched evidence packet, and submit a one-page rebuttal early.

Business Fix Kits Team  ·  July 14, 2026  ·  Updated September 24, 2026  ·  13 min read

To fight a chargeback, start with the reason code, deadline, and claim category, then build evidence that directly answers that claim. The direct answer is to submit a labeled packet with the transaction record, fulfillment proof, policy evidence, customer messages, and a short rebuttal letter before the processor deadline.

The weak response is to send everything you can find and hope the bank understands the story. Stripe's dispute documentation groups reason codes by the type of evidence needed, which is the right operating model: match proof to claim.

The Chargeback Evidence + Rebuttal Kit gives you the evidence checklist, rebuttal letters, reason-code map, and dispute tracker.

The email from your processor says a customer disputed a charge. The money has already been pulled back out of your account, often with a dispute fee on top, for an order you packed, shipped, and can prove was delivered. And a response deadline is counting down whether you act or not.

Take a breath. Chargebacks can be contested, but they are decided on evidence and process, not on being right. The bank will not hear your side in person; it decides on the packet you submit. There is no guaranteed result, but a clean, claim-matched packet is the part you control.

First, understand what you are actually in

A chargeback is a forced payment reversal the cardholder starts through their bank. It is not a refund request to you. When you fight it (formally called representment), you are not arguing with the customer. You are presenting evidence to the card-issuing bank that the charge was valid. That reframe tells you what counts:

• Emotion, frustration, and "this customer is a liar": worthless.
• Documents that directly contradict the cardholder's specific claim: everything.

Three parties, three roles: the issuing bank (the customer's bank, which decides), the acquirer or processor (your side's messenger, which sets your deadline and submission process), and you (the evidence builder).

Step 1: Read the reason code before anything else

Every chargeback carries a reason code naming the exact claim you must refute. Codes differ by card network, so read the wording in your processor's dispute notice. Answering a specific claim with generic evidence is a common way to lose a contestable dispute.

Match every piece of evidence to the code. A tracking number answers "not received" and does nothing for "not as described."

Step 2: Respect the clock

Your response window is set by your processor under card-network rules, is usually short, and varies by network and dispute type. Check the exact due date in your processor's dispute notice or dashboard the moment the dispute lands, then work backward: evidence gathered in the first couple of days, packet drafted soon after, submitted with days to spare. A missed deadline generally means the dispute is decided against you no matter how good your evidence is.

If you are enrolled in chargeback alerts, you sometimes get warning before the dispute formalizes, and a fast refund at the alert stage may prevent the chargeback and its fee on orders you would likely lose anyway. Confirm how your alert service and processor handle that. The decision tree for the judgment call is in the chargeback alert response plan.

Step 3: Decide whether to fight or refund

Fighting everything is bad strategy. Every fight costs time, and your dispute ratio matters: card networks and processors monitor chargeback levels, and merchants who stay above their thresholds can face monitoring programs, higher costs, or account termination. Ask your processor what thresholds and programs apply to your account.

• Fight when: you have direct evidence against the specific claim, the amount justifies the effort, or the dispute looks like friendly fraud (the customer got the goods and disputed anyway).
• Refund or accept when: the evidence is weak (for example, no delivery confirmation on a "not received" claim), or a fast refund at the alert stage saves the fee and the ratio hit.

Friendly fraud deserves a note: some disputes come from customers who recognize the charge. They forgot, a family member ordered, or they are gaming the system. These are more contestable if your order process captured evidence.

Step 4: Build the evidence packet

This is the core of your case. The packet has one job: let a bank analyst with a few minutes to review find the contradiction between the claim and the facts immediately. Build the packet before you write a word of the rebuttal; the letter only summarizes what the exhibits already prove. Here is what belongs in it:

Start with a purchase-to-dispute timeline

Before any exhibit, build a one-screen timeline from your records, not from memory. Cite the exhibit letter beside each line; if a line has no document behind it, leave it out.

When nothing ships: digital products, subscriptions, and services

For downloads, software, memberships, and services, fulfillment proof is access and use. Pull the account creation date and email, download or login records with timestamps, activity after the purchase date, the terms or cancellation policy accepted at checkout, and, for services, the signed agreement, completion notes, or dated work photos. The strongest single fact is usually activity after the date the customer says they canceled or never received access.

Assembly order:

1. Rebuttal letter on page one: the summary the analyst reads first.
2. Transaction proof: order record, amount, date, payment authorization, AVS/CVV results.
3. Claim-specific evidence: matched to the reason code from Step 1, strongest item first.
4. Customer identity and history: prior undisputed purchases, account activity, matching contact details.
5. Policies: the return, refund, or cancellation policy the customer accepted at checkout, with proof of acceptance.
6. Correspondence: every email, text, and support ticket with the customer, especially anything where they acknowledge receiving or using the product.

Formatting rules that quietly help:

• Label everything. "Exhibit C: carrier delivery confirmation to billing address, signed [date]."
• Highlight the kill shot. If tracking shows delivery to the cardholder's address the day before they claimed non-receipt, circle it.
• No wall of screenshots. Curated and captioned beats voluminous and raw.

Step 5: Write the rebuttal letter

The rebuttal letter is a one-page cover memo, not an essay. The full version is in the chargeback rebuttal letter template; the structure is:

1. Header: case or dispute ID, transaction date and amount, reason code.
2. One-sentence position: "This dispute should be reversed because [the cardholder received the merchandise at their verified billing address on (date), per Exhibit C]."
3. Three to five numbered facts, each citing an exhibit. Facts only: no adjectives, no frustration.
4. Direct refutation of the specific claim. Name the reason code and state precisely which exhibit contradicts it.
5. Close: "The evidence demonstrates the transaction was valid and properly fulfilled. We respectfully request reversal of this chargeback."

The core paragraph you can copy:

Tone check before submitting: if any sentence sounds angry, delete it. The analyst does not care that this hurts. They care whether Exhibit C contradicts the claim.

The four rules for a cleaner rebuttal

Step 6: Submit early, then log the outcome

Submit through your processor's dispute portal with days to spare, keep a complete copy, and record the outcome either way. Decisions can take weeks; ask your processor for its timeline. If you prevail, the funds return, but whether the fee does depends on your processor's terms. If you lose a case you believe was decided wrongly, some networks allow pre-arbitration or arbitration, which can carry significant added fees. Confirm costs with your processor first; for high-stakes disputes, consider professional guidance.

Either way, the loop is not closed until you have asked: what would have prevented this dispute?

Small business example

In this hypothetical, an online parts seller receives a product-not-received dispute for a $286 order. The deadline in the processor's dispute notice is eight days away. The seller pulls the order, tracking scan, delivery address, support thread, and policy page. The rebuttal opens with the delivered-to-address proof, not a complaint about the customer. The packet is submitted on day three, and the owner logs the outcome plus one prevention step: signature confirmation on orders over a defined threshold.

Step 7: Make the next chargeback less likely

Much of the chargeback fight is won or lost at order time, not dispute time:

• Clear billing descriptor. Some "fraud" disputes are customers not recognizing your name on their statement. Make the descriptor match your customer-facing brand.
• Confirmation that doubles as evidence. An itemized, policy-linked, descriptor-named order confirmation can pre-empt disputes and becomes an exhibit when one lands. Blueprint: chargeback prevention order confirmation.
• Screen risky orders before shipping. Mismatched AVS, rush shipping to a new address, unusually large first orders: run the high-risk order verification checklist before the label prints, because after it ships your leverage is gone.
• Answer duplicate-charge complaints fast. A same-day, well-handled response to a billing question can stop a dispute before it starts. Script: duplicate charge customer response.
• Delivery confirmation on everything that matters. Signature confirmation on high-value orders is inexpensive insurance against "not received" claims.

The chargeback response checklist

• Read the exact reason code and identify the claim you must answer.
• Confirm the response deadline in the processor's dispute notice or dashboard.
• Decide whether to fight, refund, or accept based on evidence strength.
• Pull transaction, authorization, and AVS/CVV records.
• Gather claim-specific evidence: tracking, access or download logs, correspondence, policy acceptance.
• Build the purchase-to-dispute timeline and cite an exhibit on every line.
• Organize proof in timeline order, grouped by type, as labeled and captioned exhibits with the kill shot highlighted.
• Write a one-page rebuttal that cites each exhibit.
• Remove insults, guesses, emotion, and unsupported claims.
• Submit early and save a full copy of the packet.
• Log the outcome and apply one prevention fix.

Want this pre-built? The Chargeback Evidence + Rebuttal Kit has the packet checklist, rebuttal letters for six claim types, and the evidence-matching table for each major claim category, ready to run. Not a course. A response system.

Free version vs. full kit

This article gives you the free version: the reason-code table, evidence packet structure, timeline exhibit, rebuttal paragraph, response rules, and pre-submit checklist. The full Chargeback Evidence + Rebuttal Kit adds the reason-code worksheet, rebuttal letter, packet builder, tracker, and prevention review.

View the Chargeback Evidence + Rebuttal Kit

If chargebacks connect to cash flow pressure, the cash flow crisis playbook helps protect payroll and vendors while disputes run.

FAQ

How long do I have to respond to a chargeback?

Your processor sets the exact window based on card-network rules, and it varies by network, processor, and dispute type. Check the due date in your processor's dispute notice or dashboard the day the dispute arrives and submit early; a missed deadline generally means the dispute is decided against you.

What are the odds of winning a chargeback dispute?

There is no reliable single number, and no outcome is guaranteed. Odds depend on evidence fit: delivery confirmation against a "not received" claim, or documented policy acceptance against a cancellation claim, is far stronger than generic evidence. Track your own results by claim category.

Is every chargeback worth fighting?

No. Fight when the amount and evidence justify it, especially when proof directly contradicts the reason code. Accept or refund weak-evidence cases when the cost, time, and dispute ratio risk outweigh the likely result. Processor, card-network, and legal rules vary, so use the dashboard deadline and get professional guidance for high-stakes disputes.

Is it worth fighting a small chargeback?

Weigh the amount against your time and evidence strength. A strong-evidence case can be worth contesting even when small, since customers who dispute freely may repeat. A weak case is usually better refunded at the alert stage, before it counts toward your ratio.

Should I contact the customer after a chargeback is filed?

You can, politely. Some cardholders filed by mistake or forgot the purchase, and a customer can ask their bank to withdraw the dispute. Never pressure or offer inducements to drop it, and keep building your evidence packet in parallel; withdrawal is never guaranteed and your deadline does not pause.

What is friendly fraud and can I fight it?

Friendly fraud is a cardholder disputing a legitimate charge they actually made and received, sometimes by honest confusion, sometimes deliberately. It is contestable, and your odds improve if your process captured evidence: delivery confirmation, account usage after delivery, prior purchase history, and policy acceptance at checkout.

Do chargebacks hurt my business even if I win?

They can. Fees may not be returned even on a win, depending on your processor's terms, and your dispute ratio typically counts filed chargebacks regardless of outcome. Sustained high levels can mean monitoring programs or account termination; ask your processor how the ratio is calculated for your account. Prevention matters as much as the fights you take on.

Educational and operational guidance only. No guaranteed outcome. Not legal, tax, or financial advice.