A customer sees a charge on their card statement they do not recognize, or a purchase that never arrived, and instead of contacting the merchant they call their bank and ask for their money back. A few days later the merchant finds the sale reversed, the goods gone, and a fee deducted on top. That reversal is a chargeback, and the sequence of events that produced it, from the cardholder’s call to the final resolution, is a defined process with fixed stages, deadlines, and rules set by the card networks.
Most explanations of chargebacks jump straight to how to prevent them. This one does something different: it walks through what a chargeback actually is and how the dispute moves through the system from start to finish, because understanding the mechanism is what makes everything else, the reason codes, the deadlines, the decision of whether to fight one, make sense.
What is a chargeback?
A chargeback is a forced reversal of a card payment, initiated by the cardholder’s bank rather than by the merchant. When a cardholder disputes a transaction with the bank that issued their card, the bank can reverse the payment, pull the funds back from the merchant, and return them to the cardholder, while the dispute is investigated under the card network’s rules.
The mechanism exists for consumer protection. In the United States its legal foundation is the Fair Credit Billing Act of 1974, which gave cardholders the right to dispute billing errors and unauthorized charges. The card networks (Visa, Mastercard, American Express, and Discover) built their own dispute frameworks on top of that principle, and those frameworks are what govern how a chargeback plays out today.
The essential thing to grasp is who initiates it. A chargeback comes from the issuing bank, at the cardholder’s request, and it happens whether or not the merchant agrees. That single fact, that the reversal is imposed from outside rather than granted by the merchant, is what separates a chargeback from a refund and what makes it costly and adversarial in a way a refund is not.
What is the difference between a chargeback and a refund?
A refund and a chargeback both return money to the customer, but they travel opposite paths. A refund is voluntary and merchant-led: the customer contacts the business, the business agrees, and it returns the money directly. The process is cooperative, there is no penalty, and no third party is involved.
A chargeback is involuntary and bank-led: the customer bypasses the merchant, goes to their issuing bank, and the bank forces the reversal. The merchant usually pays a chargeback fee on top of losing the sale, the transaction counts against the merchant’s chargeback ratio, and the card networks are directly involved. A refund is a customer-service outcome; a chargeback is a dispute with financial and reputational consequences for the merchant. Because the two are so often confused, Gr4vy covers the distinction in more detail in its guide on refunds versus chargebacks.
How the chargeback process works, stage by stage
A chargeback is not a single event but a sequence, and the sequence matters because each stage has its own actors, deadlines, and decisions. Here is how a typical card dispute moves from the cardholder’s first complaint to a final resolution.
Stage 1: The cardholder disputes the transaction
The process begins when a cardholder contacts their issuing bank to dispute a charge. They might claim the transaction was fraudulent, that the goods never arrived, that the product was not as described, that they were charged twice, or that a subscription they thought they had cancelled was billed again. The cardholder does not need the merchant’s involvement or agreement to start this; they simply tell the bank they want the charge reversed.
Stage 2: The issuing bank reviews and assigns a reason code
The issuing bank examines the cardholder’s claim and, if it decides the dispute is valid enough to proceed, provisionally credits the cardholder and assigns a reason code that categorizes the dispute. This code (more on the categories below) is the bank’s shorthand for why the chargeback is being raised, and it determines what evidence the merchant will need if they choose to fight it. At this point the funds are pulled from the merchant’s account through the acquiring bank.
Stage 3: The acquirer notifies the merchant
The dispute travels from the issuing bank, through the card network, to the merchant’s acquiring bank, which notifies the merchant of the chargeback along with its reason code and the amount reversed. The merchant now learns that a sale has been pulled back, why the cardholder says it should be reversed, and how long they have to respond. This is usually the first moment the merchant knows a dispute exists.
Stage 4: The merchant accepts or represents the chargeback
The merchant now faces a decision. They can accept the chargeback, absorbing the loss and the fee, which is often the rational choice for a low-value transaction or one the merchant knows it cannot win. Or they can contest it through a process called representment, submitting evidence to the issuing bank that the charge was legitimate. That evidence depends entirely on the reason code: proof of delivery for a “goods not received” claim, proof of authentication for a fraud claim, records of a cancellation policy for a subscription dispute. Representment has to be built to answer the specific claim the reason code describes, under a tight deadline.
Stage 5: Arbitration by the card network
If the merchant represents and the issuing bank rejects the evidence, the dispute can escalate. The cardholder’s bank may file a second chargeback, and if the two banks still disagree, the case can go to arbitration, where the card network itself reviews the evidence and makes a binding decision. Arbitration carries fees and risk for whichever side loses, so it is usually reserved for higher-value disputes where the amount justifies the cost. Most disputes resolve before this stage, but it is the backstop that settles the ones that do not.
Chargeback reason codes explained
The reason code assigned in Stage 2 is the pivot the whole dispute turns on, so it is worth understanding what these codes are. A chargeback reason code is a standardized identifier that the issuing bank attaches to a dispute to describe why the cardholder says the charge should be reversed. Each card network maintains its own set of codes with its own format: Visa uses codes under its Visa Claims Resolution framework, Mastercard uses four-digit numeric codes, and American Express and Discover each have their own systems.
Despite the different formats, the codes across all networks fall into roughly four categories:
The first is fraud, where the cardholder claims they did not authorize the transaction. The second is authorization, covering transactions that should not have been approved, such as a charge on a card that was already declined or over its limit. The third is processing errors, operational mistakes like charging the wrong amount, billing twice, or failing to process a credit. The fourth is consumer disputes, where the cardholder acknowledges the purchase but has a complaint, such as goods not received, a product not as described, or a cancelled service still being billed.
One caution that experienced merchants learn quickly: the reason code reflects what the cardholder told their bank rather than a verified fact. A cardholder may select or be assigned a code that does not match what really happened, sometimes out of confusion and sometimes deliberately. The code tells the merchant what claim they have to rebut and what evidence will count, which is why reading it carefully before responding matters more than the label suggests.
How long does the chargeback process take?
Chargebacks operate on the card networks’ deadlines instead of the merchant’s, and the full cycle can stretch over weeks or months. A cardholder generally has a set window after the transaction or statement to raise a dispute, often up to 120 days depending on the network and the reason, though for some claim types it can be longer. Once a chargeback is filed, the merchant typically has a limited response window, frequently around 20 to 45 days depending on the network, to submit representment evidence.
From there, the issuing bank takes time to review any evidence, and if the dispute escalates to a second chargeback or arbitration, additional weeks are added. In practice, a straightforward chargeback that the merchant accepts closes quickly, while a contested one can take two to three months or more to fully resolve. The precise deadlines vary by card network and reason code, which is one reason cross-border merchants dealing with multiple networks find dispute management complex to run.
Who pays for a chargeback, and what does it cost?
When a chargeback succeeds, the merchant bears the cost, and that cost is larger than the sale itself. The merchant loses the transaction amount, which is returned to the cardholder. On top of that, the acquirer typically charges a chargeback fee for processing the dispute, which the merchant pays regardless of whether they win or lose the case. If physical goods were shipped, the merchant has usually lost those too.
Beyond the direct costs, every chargeback counts toward the merchant’s chargeback ratio, the proportion of its transactions that end in disputes. Card networks monitor this ratio, and merchants who exceed the networks’ thresholds can face monitoring programs, additional fines, higher processing costs, and in severe cases the loss of their ability to accept card payments. This is why chargebacks are treated as a serious operational risk rather than an occasional cost of doing business: the fees and lost goods are visible, but the threat to the merchant’s processing standing is often the more consequential exposure.
What is friendly fraud, and why is it rising?
A growing share of chargebacks are not fraud in the traditional sense at all. Friendly fraud, also called first-party misuse, happens when a legitimate customer disputes a charge for a purchase they actually made and received, to get their money back while keeping the goods or service. Sometimes it is deliberate abuse; sometimes it is genuine confusion, such as not recognizing a merchant’s billing name on a statement or forgetting about a subscription.
Friendly fraud is difficult for merchants because it arrives disguised as a legitimate dispute, often under a fraud reason code, even though the transaction was valid. Industry research points to this category growing: the Merchant Risk Council’s 2026 Global eCommerce Payments and Fraud Report, a survey of 1,278 merchants across 37 countries, found that around 64% of merchants reported increasing first-party misuse. Because the transaction really did happen, the merchant’s defense in representment rests on evidence that the cardholder received what they paid for, which is why records like delivery confirmation, usage logs, and authentication data matter so much. Gr4vy’s guide on payment fraud prevention strategies covers how merchants detect and respond to this pattern.
Frequently asked questions
What is a chargeback in simple terms?
A chargeback is a forced reversal of a card payment that the cardholder’s bank initiates after the cardholder disputes the charge. The bank pulls the funds back from the merchant and returns them to the cardholder while the dispute is investigated under the card network’s rules. Unlike a refund, it happens without the merchant’s agreement and usually comes with a fee and a mark against the merchant’s chargeback ratio.
What is the difference between a chargeback and a refund?
A refund is voluntary and handled directly between the customer and the merchant, with no penalty and no third party. A chargeback is involuntary: the customer goes to their issuing bank, which forces the reversal. The merchant typically pays a fee, loses the sale, and has the transaction counted against its chargeback ratio. A refund is a customer-service outcome; a chargeback is a formal dispute with financial consequences.
How does the chargeback process work?
It moves through stages. The cardholder disputes a charge with their issuing bank; the bank reviews the claim, assigns a reason code, and provisionally reverses the funds; the merchant’s acquiring bank notifies the merchant; the merchant either accepts the chargeback or contests it through representment by submitting evidence; and if the banks still disagree, the dispute can escalate to arbitration, where the card network makes a binding decision.
What are chargeback reason codes?
Reason codes are standardized identifiers that the issuing bank attaches to a dispute to describe why the cardholder says the charge should be reversed. Each card network has its own format (Visa, Mastercard, American Express, and Discover all differ), but the codes generally fall into four categories: fraud, authorization issues, processing errors, and consumer disputes. The code determines what evidence a merchant needs to contest the dispute.
How long does a merchant have to respond to a chargeback?
The response window depends on the card network and reason code but is commonly in the range of 20 to 45 days from notification. Merchants have to submit their representment evidence within that window, which is why having documentation organized in advance matters. Missing the deadline generally means the chargeback stands regardless of the merits.
Can a merchant fight a chargeback?
Yes, through a process called representment, where the merchant submits evidence to the issuing bank that the transaction was legitimate. The evidence has to answer the specific claim behind the reason code, such as proof of delivery for a “goods not received” dispute or authentication records for a fraud claim. Whether it is worth fighting depends on the transaction value, the reason code, and the strength of the available evidence.
How much does a chargeback cost a merchant?
A merchant that loses a chargeback loses the transaction amount, typically pays a chargeback fee to its acquirer regardless of outcome, and often loses any goods that were shipped. Each chargeback also counts toward the merchant’s chargeback ratio, and exceeding the card networks’ thresholds can lead to fines, monitoring programs, higher costs, and in serious cases losing the ability to accept cards.
What is friendly fraud?
Friendly fraud, or first-party misuse, is when a legitimate customer disputes a charge for something they actually bought and received, keeping the goods or service while recovering their money. It can be deliberate or the result of genuine confusion, such as not recognizing a billing descriptor. It is hard to counter because it looks like a legitimate dispute, and research indicates it is rising, with most merchants reporting increases.
What happens if a merchant gets too many chargebacks?
Card networks track each merchant’s chargeback ratio. Merchants who exceed the networks’ thresholds can be placed into chargeback monitoring programs, charged additional fines, moved to higher processing costs, and, in severe or sustained cases, lose their ability to accept card payments. This is why keeping the chargeback ratio low is a priority even beyond the cost of individual disputes.
Do chargebacks apply to digital wallets and other payment methods?
Card-based digital wallet transactions (a card loaded into Apple Pay or Google Pay, for example) are still subject to the card networks’ chargeback rules, because the underlying payment is a card payment. Other payment methods, such as bank transfers or certain local payment methods, have their own dispute mechanisms that differ from the card chargeback process, which is one more reason merchants operating many payment methods find dispute handling complex.
Where chargebacks fit in a merchant’s payment strategy
Understanding the chargeback process end to end changes how a merchant treats it. A chargeback is not a random misfortune but a defined procedure with predictable stages, actors, and deadlines, which means it can be prepared for: documentation kept ready for representment, billing descriptors made clear to reduce confusion-driven disputes, delivery and authentication records retained, and reason-code patterns watched for the operational problems they reveal.
The deeper point is that chargebacks sit at the intersection of fraud, customer experience, and payment operations. Some are genuine fraud, some are friendly fraud, and many trace back to preventable friction like an unclear billing name or a confusing cancellation flow. Reducing them is less about fighting each dispute and more about addressing what causes them, which is the subject of Gr4vy’s guides on avoiding and controlling chargebacks and, for European merchants specifically, reducing chargebacks and protecting revenue.
Gr4vy is a cloud-native payment orchestration platform that gives merchants centralized visibility over disputes across every connected provider, along with the fraud tooling, authentication controls, and unified reporting that help keep chargeback ratios in check. To see how consolidated dispute visibility would work across your payment stack, talk to our team.
