What Happens When a Customer Disputes a Charge? A Merchant's Guide
When a customer disputes a charge, their bank pulls the funds from your account, issues them a provisional credit, and charges you a fee. You're notified with a reason code and given a short window to respond with evidence (representment). The issuer then decides, and either side can escalate to arbitration.
The first sign is usually a notification and a missing deposit: money you already counted as revenue is suddenly gone. A dispute has been filed, and the clock is now running on your chance to get it back. Here’s exactly what’s happening behind the scenes and what’s expected of you at each step.
Step 1: The cardholder files the dispute
It starts when the customer contacts their issuing bank — the bank that gave them the card — and disputes a transaction. They might claim fraud (“I didn’t make this purchase”), non-delivery (“I never got it”), a product problem (“it wasn’t as described”), or simply not recognize the charge.
Critically, this happens without you. The customer doesn’t have to contact you first, and often doesn’t. The bank takes the claim, assigns it a reason code that categorizes the dispute, and initiates the chargeback.
Step 2: Provisional credit and the debit hit
The issuing bank immediately gives the cardholder a provisional credit — they get their money back right away, pending the outcome. To fund that, the network pulls the disputed amount straight out of your account through your acquirer.
At the same time, your processor charges you a chargeback fee, typically $15 to $50, which is usually non-refundable even if you go on to win. So before you’ve done anything or even been notified, you’re already down the transaction amount plus the fee. This is why a chargeback costs so much more than the sale itself — the full math is in how much a chargeback costs.
Step 3: You get notified
Your processor or acquirer notifies you that a dispute exists. The notification includes:
- The reason code (why the customer disputed)
- The disputed amount
- The transaction details (date, order reference)
- Your response deadline
This is the moment your window opens — and it’s short. Depending on the network and reason code, you typically have 7 to 21 calendar days to respond; some processors and PayPal give as little as 10. Miss it and you lose automatically. Because notifications can slip through busy inboxes, a missed deadline is one of the most common and most avoidable ways merchants lose winnable cases. The exact clocks are broken down in chargeback time limits.
Step 4: Representment — your chance to fight
If the charge was legitimate, you respond through a process called representment — literally “re-presenting” the transaction to the issuing bank with evidence that it was valid.
What counts as good evidence depends entirely on the reason code:
- “Item not received” → tracking number, carrier delivery confirmation, delivery address matching the order.
- “Fraud / unauthorized” → AVS and CVV match, device/IP data, login history, prior order history with the same card.
- “Not as described” → product photos, listing description, your policies the customer agreed to.
- “Duplicate / already refunded” → the refund transaction ID and date, or proof there were two distinct orders.
You compile this into a rebuttal and submit it before the deadline. The stronger and more specific the evidence, the better your odds — see how to win a chargeback dispute.
Step 5: The issuer decides
Your evidence goes back to the issuing bank, which reviews it and rules. If your case is convincing, the provisional credit to the cardholder is reversed and the funds return to your account (the fee usually stays lost). If it isn’t, the customer keeps the credit and you keep the loss.
This review takes time — often several weeks — which is why the full timeline from first dispute to final answer commonly runs 30 to 90 days. See how long a chargeback takes.
Step 6: Escalation — pre-arbitration and arbitration
A decision isn’t always final. If the cardholder (via their bank) still disagrees after you win, the case can move to pre-arbitration, where each side makes a final case. If that doesn’t resolve it, it goes to arbitration, where the card network itself makes a binding ruling — and the losing party typically pays an arbitration fee that can run into the hundreds of dollars.
Because arbitration fees are steep, both sides weigh whether a low-value dispute is worth escalating. For most everyday transactions, the case ends at the issuer’s decision in Step 5.
The lifecycle at a glance
| Stage | What happens | Who acts |
|---|---|---|
| Dispute filed | Cardholder disputes with their bank | Customer |
| Provisional credit | Funds debited from you, fee charged | Issuing bank |
| Notification | You receive reason code and deadline | Processor |
| Representment | You submit evidence | You |
| Decision | Issuer rules for you or the customer | Issuing bank |
| Escalation | Pre-arbitration → arbitration | Either side |
What this means for you
Two things decide most outcomes: speed and evidence. You lose the money the instant the dispute is filed, so every day of the response window matters, and the quality of your reason-code-specific evidence determines whether you get it back. Merchants who track disputes in a spreadsheet and respond by hand routinely miss deadlines and submit thin evidence on cases they should win.
That’s the gap DisputeDash closes: it detects the dispute the moment your processor reports it, pulls the exact evidence the reason code calls for — order data, tracking, AVS/CVV, IP, customer messages — builds the rebuttal, and submits it before the deadline, either fully automatically or after your review. Across 12,000+ production disputes that approach has held an average win rate near 87%, which is what happens when no case slips and every response is complete.
Win more chargebacks, automatically.
DisputeDash gathers the evidence, builds the rebuttal, and submits before the deadline — across Stripe, PayPal, Braintree, PayArc and more. Flat fee, no commission.
Start free — keep 100%