A chargeback costs more than a refund because you lose the sale, pay a fee, and take a hit to your chargeback ratio. You may also lose goods or services that have already been delivered. This guide explains how merchants can reduce those costs and manage disputes.
Some chargebacks are unavoidable, but merchants also write off disputes they could have won and receive chargebacks that could have been prevented.
This guide explains what a chargeback is, how the dispute process works, why ratio thresholds matter, and how to use prevention and representment in a chargeback management program.
What is a chargeback?
A chargeback, or dispute, is a forced reversal of a card transaction, initiated by the cardholder through their issuing bank. The cardholder complains to their bank, the bank pulls funds back from the processor, and you’re left to accept the loss or try to fight it.
Chargebacks exist because of consumer-protection law. In the US, the Fair Credit Billing Act of 1974 gave cardholders the right to dispute charges with their issuer. The bill was originally designed to protect consumers from fraud and non-delivery issues.
This origin explains why the system is biased toward the cardholder. When a dispute is filed, the cardholder is provisionally credited and the merchant carries the burden of proving the charge was valid.
Five parties are involved in every chargeback:
- The cardholder, who disputes the charge.
- The issuer, the cardholder’s bank, which files the chargeback and assigns the reason code.
- The card network, Visa or Mastercard, which sets the rules and arbitrates.
- The acquirer, your bank or payment processor, which gets debited.
- The merchant, you, who accepts or fights it.
Chargebacks vs. refunds, inquiries, and disputes
These terms describe different parts of the payment dispute process:
- A refund is merchant-initiated and voluntary. You decide to return the customer’s money, and the cost is limited to the refunded sale.
- A chargeback is issuer-forced. The bank reverses the charge whether you agree or not, and it brings a fee and a ratio impact a refund never does.
- An inquiry (also called a retrieval request) comes before a chargeback and asks the merchant for transaction details. It can lead to a full chargeback.
- A dispute is the umbrella term, and the formal name of the network process that a chargeback runs through.
If a customer is going to get their money back either way, issuing a refund is almost always cheaper than waiting for a chargeback. Many prevention strategies are based on that calculation.
The chargeback lifecycle
A chargeback moves through a defined sequence, from the original sale through the dispute, representment, and (if it gets that far) arbitration:
The first sale is known as the first presentment; the merchant’s evidence-backed rebuttal is the second presentment. Most disputes resolve at the issuer’s review, but either side can push an unfavorable outcome into pre-arbitration and, finally, network arbitration, where Visa or Mastercard decides and the loser pays the fees.
As of July 2025, Visa gives merchants 9 days in the US and Canada to respond to a chargeback.1 Mastercard allows up to 45 days. Some processors can take two or three days to notify you of the chargeback, further shortening the window. Both networks run the same broad lifecycle (Visa through its Visa Claims Resolution framework, Mastercard through its own); the differences that matter are the ratio thresholds and response windows each sets separately.
The true cost of a chargeback
On a $100 order, the merchant loses the $100 payment, pays a chargeback fee that is typically between $15 and $50, and may also lose any physical goods already shipped. Mastercard estimates that the total cost can reach 2.5x the transaction value and that it takes around 17 successful sales to recover the loss from one chargeback.2 The damage to the merchant’s chargeback ratio can also put the account at risk.
Prevention and representment
A chargeback program combines two types of work:
- Prevention stops chargebacks before they happen: clear descriptors, easy refunds, fraud detection, deflection via alerts.
- Representment fights the ones that get through by assembling evidence and contesting the dispute to recover funds.
Prevention is generally cheaper because a chargeback that never gets filed carries no fee or ratio impact. Representment deals with disputes that have already been filed, so the merchant has incurred at least some cost by that point.
Where most chargebacks come from
Common causes include the use of stolen cards, merchant errors like double-charges or forgotten refunds, and disputes over goods that never arrived or weren’t as described.
Another large and fast-growing category is friendly fraud, in which a customer disputes a legitimate purchase. First-party fraud was an estimated 45% of all chargebacks and made up 36% of reported global fraud in 2024, up from 15% the year before (LexisNexis Cybercrime Report 2025).3
If a lot of your chargebacks come from real customers, typical fraud filters won’t stop them. Read more about mitigation strategies in our friendly-fraud guide.
Chargeback alerts and network deflection (Verifi, Ethoca, RDR)
Pre-dispute deflection sits between prevention and representment. Alerts let you refund or resolve a disputed transaction before it becomes a chargeback, so it never counts against your ratio.
Most of these services come from two companies owned by the card networks. Verifi (owned by Visa) runs RDR, Order Insight, and CDRN. Ethoca (owned by Mastercard) runs Ethoca Alerts and Consumer Clarity.
RDR (Rapid Dispute Resolution) is fully automated and resolves qualifying disputes according to rules you set in advance. Order Insight and Consumer Clarity provide transaction information earlier, which can clear up a cardholder’s confusion before a dispute is filed. CDRN and Ethoca Alerts require more manual involvement because the merchant decides which transactions to refund.
Using these services means paying a per-alert fee and refunding the sale to avoid the chargeback, as explained in the alerts guide. For a merchant near a ratio threshold, that is usually cheaper than paying a chargeback fee and taking further ratio damage. Bias offers Visa RDR opt-in at wholesale cost.
How to win a chargeback (representment basics)
Representment is your formal re-presentation of the transaction with evidence, the second presentment, to rebut the chargeback. You win by matching the right evidence to the specific reason code, before the deadline, in the format the issuer expects.
Reason codes explained
Every chargeback carries a reason code, the issuer’s categorization of why the cardholder is disputing. The code drives your evidence strategy, since each one has its own set of evidence requirements. Bias walks you through the requirements for each code.
Reason codes group into four families:
| Family | What it means | Typical cardholder claim |
|---|---|---|
| Fraud | The cardholder says they didn’t authorize the charge | ”I didn’t make this purchase” |
| Authorization | The transaction wasn’t properly authorized | ”This was declined / not approved” |
| Processing errors | A technical or procedural mistake | ”I was charged twice / wrong amount” |
| Consumer disputes | The cardholder is unhappy with what they got | ”It never arrived / wasn’t as described / I canceled” |
Within each family, the networks use specific numbered codes. Here are a few of the most common:
| Code | Network | Meaning |
|---|---|---|
| 10.4 | Visa | Fraud, card-absent (basis for Compelling Evidence 3.0) |
| 13.1 | Visa | Merchandise or services not received |
| 13.2 | Visa | Canceled recurring transaction |
| 13.3 | Visa | Not as described or defective |
| 4837 | Mastercard | No cardholder authorization (fraud) |
| 4853 | Mastercard | Cardholder dispute, not as described |
| 4855 | Mastercard | Goods or services not provided |
The code tells you which claim you’re rebutting, and therefore which evidence to gather. The representment playbook maps each family to the specific evidence that rebuts it.
To combat friendly fraud, Visa’s Compelling Evidence 3.0 lets merchants show two prior undisputed transactions on the same credentials, sharing data points like IP address or device ID, and Visa shifts liability for friendly-fraud disputes to the issuer.
Merchants lose recoverable revenue when they do not contest a dispute or submit generic evidence that does not address the cardholder’s claim. Merchants win roughly 45% of the disputes they fight but recover revenue on only about 18% of chargebacks overall.4 Our representment playbook explains what evidence to provide for each reason code and how to write a rebuttal.
On chargeback management software
Manual chargeback management can work at low volume. As dispute volume rises, spreadsheets become less practical because someone still has to track deadlines and prepare a response for each case.
Software can help once that work takes up too much staff time. Available tools handle alerts and deflection, evidence assembly, automated representment, ratio monitoring, and reporting. Merchants can choose a standalone tool connected to their processor, a managed service that fights disputes for a share of recoveries, or a payments platform with dispute management built in. The software buyer’s guide walks through these options.
Bias includes dispute management in the payments platform. Merchants can manage disputes in the dashboard or through the disputes API resource, and Bias automatically pulls relevant data such as customer IPs, invoices, and receipts. Merchants evaluating chargeback software can also request a demo of the platform.
Building a chargeback management program
A merchant can build a chargeback program in stages:
- Measure your baseline ratio and reason-code mix. Use the results as a baseline for later improvements and to decide whether fraud prevention, customer service, or another area needs attention first.
- Address prevention gaps. Start with practical prevention fixes, such as a recognizable billing descriptor, simple refunds, and clear recurring-billing terms.
- Enroll in alerts and RDR. Turn on deflection to stop disputes before they count against your ratio.
- Standardize representment. Build a reason-code-to-evidence process so every winnable dispute gets the right evidence.
- Automate where the volume justifies it. Software can track deadlines and assemble evidence when doing this work manually would require more staff time. Automated representment and API-based evidence submission can also help a team handle more disputes without adding headcount.
As dispute volume and the mix of reason codes change, merchants should review the program and adjust it. That may mean changing a fraud rule or refund policy, enrolling in more alerts, or improving the evidence collected for a common reason code. When staff can no longer keep up with deadlines and evidence collection, those are sensible parts of the process to automate.