
When a customer files a chargeback, the merchant is not simply dealing with a customer asking for a refund. The transaction enters a formal payment dispute process involving the customer’s issuing bank, the card network, and the merchant’s payment-processing side.
For an online business, that can mean the disputed amount is debited, evidence must be gathered, and a response may need to be submitted within a specific timeframe. The exact process varies by card network, dispute type, country, processor, and merchant agreement. But the basic flow is similar across many card-payment disputes. If you are starting with the basics, understanding what a chargeback is and how it works makes the steps below easier to follow.
The process usually starts with the cardholder contacting the bank that issued their card. The customer explains why they believe the transaction is incorrect, unauthorized, or otherwise should not have been charged. Common claims include:
The issuing bank reviews the customer’s claim and determines how to proceed under the applicable dispute rules. Importantly, a customer filing a dispute does not automatically mean the merchant did something wrong. Some claims are legitimate, while others may result from misunderstandings or friendly fraud.
Once the issuing bank accepts the dispute for processing, it moves through the relevant card-network process. The card network acts as the framework connecting the issuing side of the transaction with the merchant’s acquiring side. The merchant’s acquirer or payment processor then receives information about the dispute.
At this point, the merchant may learn the reason for the dispute and the amount being challenged. The terminology and exact sequence can differ between networks, but the merchant generally needs to review the dispute and decide how to respond.
A chargeback can affect the merchant’s funds before the dispute is finally resolved. Depending on the merchant’s payment arrangement and the stage of the dispute, the disputed transaction amount may be debited from the merchant’s account or otherwise withheld while the case is being handled.
For example, an online retailer receives a $250 chargeback after a customer claims an order was never delivered. The merchant may see the $250 removed from its available funds while the dispute is processed. That does not necessarily mean the merchant has permanently lost the $250. The outcome depends on how the dispute is resolved.
There may also be a chargeback fee, depending on the processor and merchant agreement. This is one reason understanding the true cost of a chargeback matters. The financial impact can include more than the original transaction.
The merchant should examine the dispute as soon as possible. The reason for the chargeback matters because it determines what evidence may be relevant.
Suppose a customer claims that a $400 order was never received. The merchant might check the order record, shipping information, tracking number, delivery confirmation, and customer communications. If the customer claims that the transaction was unauthorized, the merchant may need to review authentication information, transaction details, account activity, and other relevant records.
This is also where good recordkeeping becomes valuable. A merchant that keeps transaction and fulfillment information organized can investigate a dispute much faster than one that has to reconstruct what happened from scattered systems.
After reviewing the claim, the merchant may decide to accept the chargeback or challenge it where the applicable process allows. If the merchant accepts the dispute, the case generally ends without the merchant attempting to recover the transaction. If the merchant believes the claim is incorrect, it can submit evidence through the applicable dispute process. This is commonly known as representment.
The evidence should address the customer’s specific claim rather than simply demonstrate that a payment occurred.
For example, if the customer says a physical product was never delivered, a copy of the original receipt by itself may not be very persuasive. Shipping and delivery records are more directly relevant. The same principle applies to digital businesses. If a customer disputes a software subscription, records showing account access or service usage may help establish what happened.
When challenging an eligible dispute, the merchant typically provides supporting documentation through its processor, acquirer, or relevant payment system. Evidence might include:
The evidence needed depends on the dispute category.
For example, a claim involving why customers file chargebacks and the common reasons behind them can require very different evidence depending on whether the issue involves fraud, non-delivery, duplicate billing, or a subscription cancellation. Merchants should also pay close attention to submission deadlines. Missing the applicable deadline can affect the merchant’s ability to challenge the dispute.
Once the merchant submits its response, the evidence is reviewed through the applicable dispute process. The customer may also have an opportunity to respond in some dispute processes.
The outcome is not necessarily based on which side simply provides more information. The evidence needs to address the dispute and satisfy the applicable rules.
If the merchant provides sufficient evidence, the disputed transaction may be returned; otherwise, the chargeback may remain in place. The exact terminology and stages can vary by network and dispute type.
Eventually, the dispute reaches a final outcome. If the merchant wins, the disputed amount may be returned or any provisional debit may be reversed, depending on the applicable process. If the customer wins, the merchant generally bears the disputed amount. In certain cases, additional review or escalation may be available, depending on the circumstances and applicable network rules. The merchant should retain the final outcome as part of its transaction records.
The first priority is to understand why the customer disputed the transaction. Do not treat every chargeback in exactly the same way. A practical review can include:
The merchant should also look beyond the individual transaction. If several disputes involve the same product, billing process, or customer complaint, there may be an underlying business problem.
For example, repeated subscription disputes could indicate unclear renewal terms or a difficult cancellation process. Repeated fraud disputes may indicate weaknesses in transaction screening. That is where how to prevent chargebacks through better billing, fraud controls, fulfillment, and customer service becomes relevant. Prevention is usually more valuable than trying to win every dispute after it occurs.
When a customer files a chargeback, the transaction moves into a formal dispute process rather than simply becoming a normal refund.
The issuing bank reviews the customer’s claim, the dispute moves through the applicable payment network and merchant-processing channels, and the merchant gets an opportunity to review the claim and provide evidence where appropriate. For merchants, the most important steps are straightforward: understand the dispute reason, protect the relevant records, meet the response deadline, and look for patterns across disputes.
A chargeback should not only answer the question, “Can we win this dispute?” It should also prompt a second question: “Why did this happen, and what can we change so it happens less often?”