A customer disputes a payment: what to do, and in what order
A chargeback is not a refund, and the window to respond is short. What to gather, where to respond, and the habits that prevent the next one.

A notice arrives: a customer is disputing a transaction they made with you a few weeks ago. The money has already been pulled back, or is about to be. You did nothing wrong, and yet you are the one who has to prove something.
This catches a lot of merchants off guard, because it doesn't work like an ordinary disagreement. Here is how it actually works, and what to do in the days after the notice.
A chargeback is not a refund
When you refund a customer, you decide, and the money leaves your account on your terms. A chargeback takes a different route entirely. The customer goes to the bank that issued their card, not to you. The bank pulls the funds, and you find out afterward.
That has a practical consequence. Refunding the customer after receiving a dispute notice does not settle anything, and you risk losing the amount twice. If you want to settle informally, do it before a dispute is opened.
Read the reason code first
Every case arrives with a reason code: the grounds the customer gave. Fraud, goods never received, service not rendered, item not as described, duplicate billing, a subscription they say they cancelled.
That code drives everything, because the evidence that counts is different for each one. A fraud dispute is answered with proof the card was physically present and read by the terminal. A goods-not-received dispute is answered with proof of delivery. Answering beside the point loses, no matter how thick the file.
The question is not "am I right?" but "which piece of evidence answers exactly the reason given?"
The deadline is short, and it doesn't move
You get a limited window to respond, stated in the notice itself. It is counted in days, not weeks, and no response is treated as a concession: the funds stay with the customer and the file closes.
This is the number one cause of lost cases, well ahead of weak evidence. A notice landing in an inbox nobody reads, a manager on vacation, a busy season, and the window passes. Decide right now who in your business receives these notices and handles them.
What to gather
Your payment system keeps more information than you think: the transaction timestamp, the payment method used, the electronic signature, and the technical data attached to online orders. That is the backbone of the file.
Depending on the reason code, add whatever applies:
- A copy of the receipt, showing how the card was read: inserted, tapped or keyed in.
- Proof of delivery or pickup, with the date and the name of whoever signed.
- Your correspondence with the customer: emails, messages, appointment notes.
- Your cancellation or refund policy, as it was displayed at the time of sale.
- The signed contract or work order, if there is one.
Write a short, factual explanation: what was sold, when, how the customer paid, and why the attached evidence answers the reason code. No emotion, no history of the relationship. Whoever reads your file has a few minutes to give it.
Where to track the case
On a Clover account, disputes and transaction inquiries live under the Finances section of the web dashboard, in Disputes. Each case shows its status: action required when the ball is in your court, in progress once your response has been submitted.
Get in the habit of opening that section once a week, even when nothing seems to be happening. An inquiry sometimes arrives before a formal dispute, and answering it properly can stop the file from going further.
Preventing the next one
Most avoidable disputes come from ordinary causes. The commonest: the customer doesn't recognize the name on their statement. If your business trades under a different name than its legal one, get the name shown on statements corrected.
Next comes the invisible refund policy. A policy posted at the counter and printed at the bottom of the receipt gives you something to attach to the file.
Then there are keyed-in transactions. A card inserted or tapped in front of you leaves a far stronger trail than a number typed on a keypad. Whenever you can have the chip read, have it read.
Settle one simple thing today: who opens the notices, how often, and where receipts and delivery proofs are filed. Cases are won with documents you can find, not documents that exist somewhere.