How to Win a Chargeback as a Merchant (Step by Step)
· 11 min read · By the rezlo team
What Winning Actually Looks Like
Learning how to win a chargeback as a merchant starts with one uncomfortable fact: you are not the one who decides. The cardholder's bank decides, based on the evidence you submit and the reason code attached to the dispute. Your job is not to argue. Your job is to make the bank's decision easy by handing it a short, factual file that matches the reason code.
Most small stores lose disputes not because the customer lied, but because the rebuttal arrived late, answered the wrong question, or buried three useful facts in four paragraphs of frustration. This guide walks through the process in the order the clock runs: read the code, gather evidence, write the rebuttal, submit on time, then read the outcome honestly.
One thing up front: prevention beats representment. A dispute you never receive costs you nothing to answer. A dispute you answer well still costs you time and often the sale.
The Short Version
Read the reason code first. It tells you exactly what the bank wants to see and what it will ignore.
Gather evidence before writing anything: order record, tracking, delivery confirmation, and the conversation with the customer.
Write a short rebuttal, three to five sentences plus attachments, that answers the reason code directly.
Submit before the deadline. A good file submitted late loses to a weak file submitted on time.
Expect to lose some disputes even with solid evidence. That is normal, not a sign you did something wrong.
After each outcome, fix the one process gap the dispute exposed.
Dispute Types at a Glance
Banks organize disputes by reason code. The code you receive determines what evidence is relevant, so match your file to the row that fits rather than sending everything you have.
Common dispute types and what the bank typically looks for
Dispute type
What the customer claims
Evidence that matters
Often lost because
Item not received (e.g. Visa 13.1)
The order never arrived
Tracking showing delivery to the address on file, delivery confirmation, customer messages
A tracking event alone is not proof of delivery
Not as described
The product differs from the listing
Product page copy, photos, size charts, customer messages before purchase
Store had no clear description to point to
Fraud / unauthorized
The cardholder did not authorize the purchase
AVS and CVV match, delivery to billing address, order history, IP and device data
Hard to rebut; evidence is often thin
Duplicate charge
Charged twice
Payment records showing one capture, refund records if applicable
Merchant cannot produce clean payment logs
Subscription cancelled
Charged after cancelling
Cancellation policy, cancellation confirmation, login and usage records
No record of the cancellation request
Credit not processed
Refund promised but not received
Refund transaction ID, date, and amount
Refund was issued but not documented
Read the table as a checklist, not a script. Your processor's dispute portal will show the exact reason code and its deadline. Shopify's own documentation of the process for Shopify Payments is worth reading once before your first response: Shopify Help Center: chargebacks and inquiries.
Why Disputes Happen More Than They Should
Most chargebacks are not fraud. They are customers who could not get an answer and reached for the bank instead. The bank is free, fast, and does not require the customer to find your contact page.
Silence Looks Like Guilt
A customer emails "where is my order?" and hears nothing for four days. From their side, the store looks like it took the money and vanished. Filing a dispute is the next logical step. A reply within a day, even a boring one, removes most of that motive.
Long Shipping Windows
Dropshipping stores with 15 to 30 day delivery absorb far more item-not-received disputes than domestic stores. If the shipping window on the product page says 7 days and the parcel arrives in 21, the customer has a real grievance regardless of your policy.
Unclear Billing Descriptors
When the charge appears on a statement under a name the customer does not recognize, "I don't know this charge" is an honest reaction. A recognizable descriptor and an order confirmation email prevent a chunk of fraud-coded disputes.
No Record of the Conversation
Many disputes are lost purely because the merchant cannot show what was agreed. If support happens in DMs, personal email, or a phone call nobody logged, you have no evidence to submit. Written, timestamped conversations are the cheapest insurance you can build.
What the Bank Actually Weighs
Bank analysts process disputes in volume. A clear, short file with labeled attachments moves faster than a long narrative. Think of your response as a case file, not a letter.
Does the Evidence Match the Code?
An item-not-received dispute needs delivery evidence. A not-as-described dispute needs the product page. Sending photos of a packed box to answer a "charged twice" claim tells the analyst you did not read the code, and it weakens the whole submission.
Is It Verifiable by a Third Party?
Carrier tracking, a payment gateway record, or a signed delivery confirmation carries more weight than your own statement. Anything you type yourself is a claim. Anything a system generated is evidence.
Did the Customer Have a Chance to Resolve It?
Banks look at whether the customer contacted you first and what you did. A shown attempt to fix the problem, with dates, supports your case even when the fix was imperfect.
Was the Deadline Met?
Miss the response window and the dispute is decided without you. No amount of good evidence survives a late submission, so calendar the deadline the day the dispute lands.
How to Win a Chargeback, Step by Step
The process below is the same whether you handle two disputes a year or twenty a month. Work it in order; skipping ahead is how rebuttals end up answering the wrong question.
Log the dispute and the deadline. The moment a chargeback or inquiry appears in your processor, record the reason code, amount, order number, and response deadline in one place. Inquiries are usually easier to resolve than full chargebacks, so check which one you have before doing anything else.
Read the reason code carefully. Look up what the code means and what evidence the network expects for it. This single step decides the rest of your file. If the code is item not received, our breakdown of the evidence merchants need for Visa 13.1 covers that case in detail.
Pull the order record. Order date, items, amount, shipping address, billing address, payment result, and any fraud signals your gateway captured. Export it as a PDF or screenshot with a visible timestamp rather than retyping the details.
Pull delivery and fulfillment evidence. Tracking number, carrier, scan history, and delivery confirmation if the carrier provides one. Be honest about what it shows: a tracking event is not the same as proof of delivery, and an analyst knows the difference. If the parcel was left at a door, say so plainly and attach whatever the carrier recorded.
Pull the customer conversation. Every message, with timestamps, in order. This is where you show the customer contacted you, what you told them, and what you offered. If support happened on the phone, include your call notes and the date and time.
Write a short factual rebuttal. Three to five sentences: what was ordered, when it shipped, what tracking shows, what the customer said and how you responded. No anger, no accusations, no speculation about the customer's motives. Attach the evidence with clear file names so the analyst can find each point.
Submit before the deadline and keep a copy. Submit through your processor's dispute portal, then save the full submission, including attachments, somewhere you can find it later. If the case escalates to pre-arbitration, you will need it.
Read the outcome and fix one thing. Win or lose, note why. Then change one process: a clearer shipping estimate, a faster first reply, a written record of phone calls. This is where future disputes actually get prevented.
Mistakes That Lose Winnable Disputes
Most lost disputes were winnable on the facts. These are the errors that quietly hand the case to the other side.
Writing an Essay
A two-page letter asking the bank to understand how hard dropshipping is does not answer the reason code. Analysts skim. Put the facts first, keep the narrative short, and let the attachments carry the detail.
Treating Tracking as Proof of Delivery
A "delivered" scan means the carrier believes it delivered. It does not prove the customer received the parcel, and banks weigh it accordingly. Never claim more than the tracking shows, especially in item-not-received cases.
Missing the Deadline
Response windows are short and they do not pause for weekends or busy weeks. If you handle disputes alone, set a reminder the day the case arrives. A missed deadline is the most avoidable loss in the whole process.
Ignoring the Customer First
Sometimes a dispute is still open to a direct fix. If the customer simply wants a refund or a replacement, resolving it directly can end the matter faster than representment. Check whether the dispute can still be withdrawn before you spend hours on a rebuttal.
Expecting to Win Them All
Fraud-coded disputes with thin evidence are usually lost. So are many item-not-received cases where the carrier scan is the only proof. Budget for a share of losses and focus your effort on the cases where evidence is genuinely strong.
Where rezlo Helps
rezlo is a Shopify app that answers customers on a storefront chat widget and a real phone line, using the store's catalog, policies, FAQ, and verified order data. For disputes, the useful part is the record it leaves behind and the disputes it keeps from being filed.
Timestamped Conversations on File
Every chat and phone conversation is logged in the rezlo inbox with a full transcript. When a dispute arrives, you have the customer's own words and yours, in order, ready to attach. No reconstruction from memory.
Verified Order Lookup
Customers can check order status after verifying with their order number plus a detail you choose, ZIP code by default. The verification record is part of the conversation log, which helps show the customer had accurate information about their own order.
A Dispute Evidence Pack
One click per verified order produces a PDF containing the order record, fulfillment and tracking events, and the timestamped conversation log with the verification record, prepared for item-not-received disputes. It is evidence, not an outcome: rezlo does not promise to win disputes, and the pack does not pretend tracking alone proves delivery.
Fewer Disputes to Answer
The agent answers shipping and policy questions instantly, including at night, and escalates refund, cancellation, and chargeback topics to you with a prepared case file. That reduces the silence that pushes customers toward the bank. See how instant answers keep customers from disputing, or watch the product walkthrough.
Frequently Asked Questions
How do I win a chargeback if the customer never contacted me?
Show the bank that the customer had easy ways to reach you and chose not to use them: a visible support page, a chat widget, a phone number, and your policy pages. Attach the order confirmation and shipping notification emails. That does not guarantee a win, but it removes the argument that you were unreachable.
How do I win a chargeback dispute with no tracking number?
It is much harder, and for item-not-received codes you should expect to lose. Submit whatever you have: order confirmation, fulfillment records, customer messages, and proof the item shipped. Then fix the gap so every future order has tracking attached to it before it leaves.
How do I win a credit card dispute as a merchant when the claim is fraud?
Fraud disputes are the hardest to rebut. Relevant evidence includes a matching billing and shipping address, a successful AVS and CVV check, order history from the same customer, and any correspondence. If the signals are weak, weigh the cost of fighting against the amount at stake.
What is the difference between an inquiry and a chargeback?
An inquiry is the bank asking for information before a chargeback is filed. Answering it well can stop the chargeback entirely. A chargeback is a formal withdrawal of funds with a response deadline. Check which one you have, because inquiries are usually cheaper and faster to resolve.
How long do I have to respond?
Deadlines vary by network and processor, and they are short, often measured in days rather than weeks. Your dispute portal shows the exact date for each case. Treat that date as fixed, calendar it immediately, and aim to submit at least a day early in case of upload problems.
Does a tracking number prove the customer received the order?
No. A tracking event shows the carrier recorded a scan, not that the parcel reached the customer's hands. Banks know this. Present tracking accurately and add anything stronger you have, such as a carrier delivery confirmation or a customer message acknowledging receipt.
Should I always fight a chargeback?
No. If the evidence is thin, the amount is small, or the customer has a legitimate complaint, absorbing the loss and fixing the cause is often the cheaper decision. Save your effort for cases where the facts clearly support you.
Can rezlo win disputes for me?
No. rezlo does not file disputes, contact banks, or promise outcomes. It produces a dispute evidence pack as a PDF for item-not-received cases and keeps timestamped conversation logs you can attach to a rebuttal you write and submit yourself.
What should I change to get fewer chargebacks next quarter?
Three things usually move the number most: a realistic shipping estimate on every product page, a first reply to customer questions within a day, and a written record of every support conversation. Each one removes a reason a customer would call the bank instead of you.
Does answering fast really reduce disputes?
It removes the most common trigger: silence. A customer who gets a clear answer about a delayed parcel is far less likely to file. It is not a guarantee, since some disputes come from fraud or genuine dissatisfaction, but speed is the cheapest lever most small stores have.
Keep Reading
Item Not Received Chargebacks (Visa 13.1) A closer look at the evidence banks expect for the most common dispute code. Read the guide
Prevent Chargebacks How instant, accurate answers keep customers from reaching for the bank in the first place. See the approach
Dropshipping Customer Support Handling "where is my order?" at volume when shipping takes weeks. Read more
rezlo on the Shopify App Store Storefront chat plus a real phone line, flat pricing from $7.99/month with a 14-day free trial. View the app listing