What Happens After a Chargeback: A Step-by-Step Guide for Merchants
You open your processor portal one morning and discover a chargeback notification. A customer has disputed a transaction you are certain was legitimate. The purchase happened, the product was delivered, you have records of everything. Now you have a limited window to respond, and if you miss it, you lose automatically.
Chargebacks are among the most frustrating aspects of accepting card payments. They put the burden of proof on the merchant, impose fees regardless of the outcome, and can happen months after the original transaction. Understanding the process—what happens, in what order, and what your responsibilities are at each step—significantly improves your ability to handle them effectively.
The Chargeback Timeline
When a customer contacts their bank to dispute a charge, the bank initiates a chargeback. The card network (Visa, Mastercard, etc.) notifies your processor, who forwards the dispute to you. From the moment you receive that notification, your response window begins.
Response deadlines vary by card network and reason code. Visa and Mastercard typically give merchants 20 to 45 calendar days to respond. Missing that window is an automatic loss—the funds are returned to the customer and you receive a chargeback fee with no recourse.
Once you respond, the issuing bank reviews your documentation and makes a determination. If they find in your favor, the funds are returned. If they find for the customer, you can escalate to pre-arbitration (depending on the card network) and ultimately arbitration, though arbitration is expensive and rarely worth pursuing for small transaction amounts.
Understanding Reason Codes
Every chargeback carries a reason code that tells you why the customer is disputing the charge. These codes vary by card network but fall into a few categories: fraud (the customer claims they did not make the purchase), item not received, item not as described, processing errors, and authorization issues.
The reason code tells you what evidence to gather. A fraud claim requires proof the legitimate cardholder authorized the purchase. An item not received claim requires proof of delivery. A not as described claim requires evidence the product or service matched its description. Sending the wrong documentation for the reason code weakens your response even if you have compelling evidence elsewhere.
Building a Winning Response
The strongest chargeback responses tell a complete story. They start with a clear, brief summary: when the transaction occurred, what was purchased, what you delivered, and why the dispute is incorrect. Then they present supporting documentation in a logical order.
For in-person transactions: your transaction receipt (signed if available), proof of delivery or service completion, and any communication from the customer that acknowledges the purchase.
For online transactions: the order confirmation with IP address, shipping tracking confirmation showing delivery, any correspondence with the customer, and your clearly stated return policy as it appeared on your website at the time of purchase.
For service businesses: a signed service agreement, invoices, photos of completed work, and communication history showing the customer accepted the work.
The Documents That Make the Biggest Difference
Processors who work with high chargeback volumes consistently report that two types of evidence win disputes most often: delivery confirmation and customer communication. A tracked package that shows delivery to the correct address is extremely difficult for a customer to overcome. A text or email from the customer referencing the purchase—especially one sent after delivery—is almost conclusive.
Signed card receipts still matter for in-person disputes. If you have EMV chip transaction records showing the physical card was present and authenticated, that evidence is particularly strong for fraud claims.
Reason Codes That Merchants Cannot Win
Some chargebacks are effectively impossible to reverse, and recognizing them quickly prevents wasted effort. Card-absent fraud on transactions where you processed as card-not-present without proper authentication will generally not support a reversal under card network rules.
Processing errors—charging the wrong amount, duplicate transactions—should result in issuing a refund rather than fighting the chargeback. These are correct from the customer perspective.
After the Dispute
Whether you win or lose a specific dispute, analyze what it tells you about your business. A pattern of fraud chargebacks on online orders suggests your authentication needs strengthening. A pattern of customer service disputes suggests your communication or fulfillment process has gaps. Chargebacks are expensive data points—let them inform how you operate.
Tracking your win rate over time is also valuable. If you are responding to disputes but consistently losing, your documentation package needs review. Processors and third-party chargeback management services can help identify what is missing from your evidence.