Merchant Chargeback Dispute Playbook

To dispute a chargeback, respond through your processor before the deadline on the case notice with evidence matched to the reason code: proof the cardholder authorized the sale, received what was promised, and agreed to your terms. That response is called representment. Miss the deadline and you lose automatically.

Everything else on this page is detail underneath that sentence. Which evidence counts depends entirely on what the cardholder claimed, the deadline is unforgiving in a way that most business deadlines are not, and a meaningful share of the disputes a small business receives are not worth fighting at all. Knowing which is which is the actual skill.

What you need before you start

Pull the chargeback case notice from your processor’s portal or the notice you were emailed, the original transaction record, and whatever customer communication exists for that order. Note two dates from the notice: the date the case was opened and the date your response is due. Write the due date somewhere you will see it. It is the only date on the page that can cost you the money by itself.

---

Chargeback, refund, and retrieval request: three different things

These three get used interchangeably in conversation and they are not the same event. They start in different places, they move money differently, and only one of them puts your funds in someone else’s hands while you argue.

	Refund	Retrieval request	Chargeback
Who starts it	You do, at the customer’s request or on your own initiative.	The card issuer, usually on behalf of a cardholder who does not recognize a charge.	The card issuer, after the cardholder formally disputes the transaction.
What it is	A new transaction that returns money to the card.	A request for a copy of the transaction record. An information request, not yet a dispute.	A forced reversal of the original transaction.
Who controls the outcome	You.	You, by answering it well and quickly.	The card issuer first, then potentially the card network.
Effect on your funds	You give the money back deliberately.	None yet.	The disputed amount is debited from your account while the case is open.
Counts against your dispute activity	No.	Generally no, though an unanswered one often becomes a chargeback.	Yes. Card networks monitor merchant dispute activity.

The practical consequence: a retrieval request is the cheapest problem on this page and the easiest to make worse by ignoring. Answer it the day it arrives. A refund is the only one of the three where you keep control of the outcome, which is why refunding a reasonable customer before they call their bank is almost always the better trade.

---

The five phase chargeback dispute process

Phase 1: Read the case notice and find the two dates

Open the case in your processor’s portal rather than working from the email summary. The notice tells you the transaction being disputed, the reason code the issuer assigned, the disputed amount, and your response deadline. The reason code is the most important field on the notice, because it defines what you have to prove. Do not start assembling evidence before you have read it.

Phase 2: Decide whether to fight

Fighting a dispute you cannot win is not neutral. It costs staff time, it delays the point where you write the loss off, and it does not improve your dispute activity record. Run the decision aid further down this page before you build anything. If the transaction was a genuine duplicate, a service you did not deliver, or a card-present sale that was keyed in manually with nothing to tie the card to the person, accept it and move on.

Phase 3: Build the evidence package for that reason code family

Assemble only evidence that answers the specific question the issuer asked. A package that answers a different question reads as a non-response even when it is thick. Write a short cover summary in plain language, put the strongest document first, and label every attachment so a reviewer who spends two minutes on your file can find the proof without searching. Redact what does not need to be there.

Phase 4: Submit the representment through your processor

Representment means re-presenting the transaction to the issuer with your evidence. You submit it through your processor or acquirer, never directly to the issuing bank or the cardholder. Submit before the deadline, not on it, and keep a copy of exactly what you sent and the confirmation that it was received. Late is the same as no response.

Phase 5: Handle the outcome

The issuer reviews your evidence and either reverses the chargeback, which returns the funds to you, or upholds it, which makes the reversal final for that round. If the issuer upholds it, the next step is pre-arbitration, and that is a decision to make deliberately rather than reflexively. See the pre-arbitration section below for when it is worth it.

---

The chargeback lifecycle and who holds the money

The single most disorienting part of a first chargeback is that the money leaves before anyone has decided anything. That is normal and it is not a judgment against you. Here is where the funds sit at each stage.

Stage	What happens	Who is holding the disputed funds	Your clock
1. Retrieval request	The issuer asks for a copy of the transaction record. No dispute has been filed.	You do. Nothing has moved.	Short. An unanswered retrieval request frequently becomes a chargeback.
2. Chargeback filed	The issuer reverses the transaction and your account is debited for the disputed amount.	The cardholder, provisionally. The money is out of your account.	The response deadline printed on the case notice. This is the deadline that matters.
3. Representment	You submit evidence through your processor and the issuer reviews it.	Still out of your account.	None on you once submitted. Review time is set by the issuer.
4. Issuer decision	The issuer either accepts your evidence and reverses the chargeback, or upholds it.	If accepted, the funds are credited back to you and will appear on a future settlement.	None. Watch your statement to confirm the credit actually posted.
5. Pre-arbitration and arbitration	Either side escalates. If neither concedes, the card network can be asked to rule.	Depends on the escalation stage and who conceded what.	Short, and escalation carries costs. Ask your processor what those are before agreeing.

Stage names and timing vary by card network and by processor, and network rules change. Confirm the current stage names, deadlines, and escalation costs for your account with your processor rather than assuming this table is current for your situation.

---

Reason code families in plain English

Every card network publishes its own numbered reason codes, they differ between networks, and they get revised. Rather than reproduce anyone’s code table, here are the five families those codes sort into. Find the family your case belongs to, then use the matching row of the evidence checklist below.

Fraud and unauthorized use: The cardholder says they did not authorize the transaction, so the issuer wants proof that the real cardholder was in control of the card at the time of the sale.

Product or service not received: The cardholder says they paid and nothing arrived or no service was performed, so the issuer wants proof of delivery or completion, with a date.

Not as described or defective: The cardholder received something but says it was not what was represented or did not work, so the issuer wants proof of what was promised at the point of sale and what was actually provided.

Duplicate or processing error: The cardholder says they were billed twice, billed the wrong amount, billed in the wrong currency, or that a promised credit was never issued, so the issuer wants your settlement records.

Subscription and recurring billing: The cardholder says they cancelled, or never knowingly signed up for a recurring charge, so the issuer wants proof of the enrollment, the terms disclosed at signup, and how cancellation was supposed to work.

There is a sixth situation that gets miscategorized constantly: credit not processed, where you agreed to refund the customer and the refund never landed. It usually sorts into the processing error family. If this is your case, check your own settlement records first, because the refund frequently was issued and simply has not posted yet, and that is a document you can produce in about five minutes.

Reason code numbering, family names, and the evidence each one requires are set by the card networks and change over time. Confirm the current code and its requirements with your processor before you build a response around this page.

---

Deadlines, and why they are unforgiving

The deadline is not a target, it is a gate: A response filed after the deadline is generally treated as no response at all, and the chargeback stands regardless of how strong your evidence was.

Your deadline is shorter than the network deadline: Your processor needs time to package and transmit your response inside the network’s window, so the date they give you is earlier than the network’s date. Work to the processor’s date.

Weekends and holidays do not extend it: Calendar days, not business days, is the safe assumption unless your processor tells you otherwise in writing.

Notification failure is the most common cause of a preventable loss: Case notices go to the contact email and portal on file with the processor, and small businesses routinely lose disputes because that address belongs to someone who left. Verify the notification address on your account today, not the day a case opens.

One submission is the practical rule: Treat the first submission as your only one. Portals vary in whether they let you add documents afterward, and a reviewer is under no obligation to wait for your second thought.

---

Evidence checklist by reason code family

This is the working table. Find your family, gather what is in the third column, and skip what is in the fourth.

Reason code family	The question the issuer is actually asking	Evidence that carries weight	Evidence that rarely helps	The most common reason merchants lose this one
Fraud and unauthorized use	Was the genuine cardholder in control of this transaction?	Chip or contactless read data for a card-present sale. Signed receipt. AVS and CVV results captured at authorization. Delivery to the address that matched AVS, with signature or photo. Device, IP, and account login records consistent with the customer. A history of prior undisputed purchases on the same card or account.	Your opinion that the customer is lying. An order confirmation screenshot with no verification data attached. A receipt with no signature, no chip data, and no address verification result.	The sale was keyed in manually with no address verification and no signature, so nothing in the record ties the card to a person.
Product or service not received	Did the cardholder get what they paid for, and on what date?	Carrier tracking showing delivery confirmed, ideally with signature or delivery photo, to the address on the order. Service completion records with a date and a customer acknowledgment. Appointment or job logs. Messages where the customer refers to having received the item or the work.	A shipping label with no carrier scan. A “shipped” status with no delivery event. Internal notes with no external corroboration.	Delivery is confirmed to an address different from the one on the order, most often because the customer asked for a change by phone and nobody recorded it.
Not as described or defective	Did the goods or service match what was represented at the point of sale?	The product page, menu, quote, or listing exactly as it appeared on the transaction date, including photos and specifications. Your return and refund policy shown as it was presented at checkout, with evidence the customer accepted it and when. Communication logs showing you offered a remedy. Repair, inspection, or return records.	A policy page that exists on your site now but cannot be tied to the date of sale. An argument that the customer used the item for a while, offered on its own.	The refund and return policy cannot be proven to have been presented and accepted before payment, so it reads as a policy invented after the dispute.
Duplicate or processing error	Was this cardholder billed twice, billed incorrectly, or denied a credit you agreed to?	Settlement and batch reports showing the two charges are separate sales, with distinct authorization codes, timestamps, and items. Both signed receipts. For a credit-not-processed case, the credit transaction record with its date and reference number.	An assertion that the charges are different without the settlement detail that proves it. A verbal account of what happened at the register.	It is a genuine duplicate. When it is, accept it, refund promptly, and fix the terminal or checkout behavior that produced it.
Subscription and recurring billing	Did the cardholder knowingly agree to recurring billing, and was a cancellation honored?	The enrollment record with a timestamp and the terms as displayed at signup, including the billing amount and frequency. The cancellation instructions as shown at signup. Records of every channel the customer could cancel through and whether they used one. Usage or login activity after the disputed billing date. Renewal notices you sent.	Current terms of service with no link to the signup date. A cancellation policy the customer was never shown.	The customer cancelled through a channel nobody monitors, such as a reply to a no-reply address or a message to a social account, and billing continued.

Two rules cut across every row. Documents beat narrative. A one-paragraph summary pointing at four labeled attachments outperforms four pages of explanation with nothing attached. And never build an evidence file out of full card numbers or security codes. Storing that data to win a dispute creates a much larger problem than the dispute, and it is exactly what PCI compliance requirements exist to prevent. Redact the card number to the last four digits.

---

Should you fight this one: a decision aid

Work down this table. It is weighted, not scored: any single item in the “stop here” column is usually enough on its own.

Question	Points toward fighting it	Stop here and accept it
Do you have the specific evidence this reason code family requires?	Yes, and you could attach it in under an hour.	No, and no amount of searching will produce it. This is the whole decision.
Is the customer’s claim actually true?	No, and you can show why with a document rather than an argument.	Yes. A duplicate charge, an undelivered order, or a missed cancellation is a loss you already took.
Is the disputed amount worth the staff hours?	The amount is meaningful to your week and the evidence is already assembled.	The time to assemble a real package costs more than the transaction, and the evidence is thin.
Was the transaction card-present and processed correctly?	Chip or contactless, receipt retained, terminal settled on time.	Keyed in manually with no address verification, no signature, and no imprint.
Is this a repeat customer with a clean history?	Yes, with prior undisputed orders on the same card or account.	First transaction, shipping address that does not match billing, and no verification data.
Can you still resolve it directly with the customer?	Sometimes. A customer who got what they wanted may withdraw a dispute with their bank.	Never refund a transaction that is already under dispute without confirming the process with your processor first. See the warning below.
Is this one case, or a pattern?	An isolated case with a specific, explainable cause.	A pattern. Then the case is not the problem, and fixing the pattern is worth more than winning this one.

The refund trap. Refunding a transaction that is already in dispute can leave you out the money twice, because the chargeback debit and your refund are two separate movements of funds and the chargeback does not cancel itself when you issue a credit. If you want to resolve a live dispute by making the customer whole, call your processor first and ask what the correct sequence is for your account. This is one of the few places on this page where acting fast makes things worse.

When it is a pattern, not a case. If disputes are arriving steadily rather than occasionally, the useful work is upstream: the billing descriptor, the delivery process, the cancellation flow, the way cards are accepted at the counter. Card networks operate programs that monitor merchant dispute activity, and merchants whose activity runs persistently high can end up in remediation programs or find their account underwriting reviewed. How that is measured, and what follows, is set by each network and by your acquirer, and it changes. Ask your processor directly where your account stands rather than reading a threshold off a web page. If your business is in a category where elevated disputes are structural rather than fixable, that is a high-risk processing conversation, not a per-case one.

---

Representment, and what happens after

Representment is the formal act of re-presenting the disputed transaction to the issuer with evidence attached. You do not send it to the cardholder and you do not send it to the issuing bank. It goes through your processor, in the format your processor requires, before the date your processor gave you.

What a strong submission looks like in practice:

A short cover summary in plain language: Three or four sentences stating what was sold, when, to whom, and which attached document answers the cardholder’s specific claim.

The strongest document first: A reviewer working through a queue should hit your best proof immediately, not on page six.

Labeled attachments: “Delivery confirmation, signed, March 14” is a filename that helps you. “IMG_4471” is not.

Only the relevant transaction: Do not attach the customer’s entire order history unless prior purchases are themselves the argument, as they can be in a fraud case.

Redacted personal and card data: Last four digits only, and nothing you would not want stored on someone else’s system.

After you submit, the issuer reviews and rules. If the issuer accepts your evidence, the chargeback is reversed and the funds are credited back to you, typically appearing on a later settlement rather than instantly. Watch for that credit rather than assuming it posted. If the credit does not appear and your case shows as won, that gap is worth raising with your processor promptly, and it is the same class of problem as any other mismatch between your sales and your deposits.

If the issuer rejects your evidence, the reversal stands for that round, and the next question is whether to escalate.

---

Pre-arbitration, and when to stop fighting

Pre-arbitration is the round after representment, where the issuer pushes back on your evidence or you push back on their ruling, before either side asks the card network to decide. Arbitration is the final step, where the network itself rules and assigns the outcome.

Three things worth understanding before you escalate:

Escalation carries costs that the original dispute did not: Arbitration involves fees set by the card networks and the losing side generally bears them. Ask your processor exactly what escalating will cost on your account, in writing, before you agree to it. Do not escalate a small transaction without that number in front of you.

New evidence is the only good reason to escalate: If the issuer rejected your package and you have nothing to add, resubmitting the same argument is unlikely to change the outcome. If you have a document you did not have before, that is different.

Stopping is a legitimate decision: Writing off a disputed transaction, fixing whatever produced it, and moving on is often the correct business call. The point of this page is not to fight everything. It is to fight the cases where you have proof and let go of the ones where you do not.

---

Preventing chargebacks in the first place

Prevention here means ordinary operational hygiene, not software. Every item below is something a small business can do this month with no new vendor.

Fix your billing descriptor first: The name that appears on a customer’s bank statement should be the name on your door or your website, plus a phone number if the format allows it, because “did not recognize the charge” is the most preventable dispute there is.

Make it easy to reach a human: A customer who can get you on the phone in one try calls you instead of their bank, and a dispute avoided is worth more than a dispute won.

Keep delivery proof for every shipment: Tracking with delivery confirmation to the order address, and signature or photo confirmation on higher-value orders, is the single document that decides the not-received family.

Follow card-present procedures exactly: Dip or tap the chip rather than keying the number, keep the signed receipt where you can find it by date, and settle your batches on time. Manual key entry without address verification is how card-present merchants lose fraud disputes they should have won.

Show your terms before payment, and save the proof: The refund policy, the delivery window, and the recurring billing schedule need to be visible at checkout and captured with a timestamp, because a policy you cannot prove was shown is a policy that does not exist during a dispute.

Make cancellation genuinely easy: A subscription that is harder to cancel than it was to start converts frustrated customers into disputes, and a cancellation flow that works in one channel while customers try three others produces the most winnable-looking disputes that merchants nevertheless lose.

Refund quickly when the customer is right: A refund is a transaction you control. A chargeback is not.

Confirm who receives dispute notices on your account: Check the email address and portal login your processor has on file, today, and make sure a person who still works there monitors it.

---

When a second opinion on your account is worth having

Chargebacks are a support problem, not a pricing problem, and most of what is on this page is work you do yourself with your existing processor. But if you are working through disputes and finding that nobody at your provider will explain the process, or you cannot get a straight answer about what escalation costs on your account, that is worth noticing. Responsiveness is part of what you are paying for.

PayPoint Systems is an independent merchant services provider based in Northwest Indiana. We are not the card processor. If you want an outside look at what your current arrangement includes, the free rate analysis is a review of your statement with no obligation.

---

Frequently Asked Questions

Related guides

• Why Your Card Deposits Do Not Match Your Sales
• Merchant Statement Fee Dictionary: What Every Line Item Means
• How to Read a Merchant Services Statement

This article is general information for business owners, not legal, tax, or accounting advice. Card brand rules, interchange schedules, and processor agreements change; confirm specifics against your own statement and your own signed agreement.