While a refund costs you a sale, a chargeback costs you the sale, a fee, a hit to your chargeback ratio, and often goods or services already delivered. We’ll explain how to minimize these costs and master chargeback management.
It’s tempting to treat chargebacks as an unavoidable cost of doing business. However, in reality, a fair number of disputes that get written off are winnable, and a fair number of chargebacks could have been prevented earlier.
This guide covers the whole picture, including what a chargeback is, how the dispute process works, why ratio thresholds matter, and to leverage prevention and representment for a successful strategy.
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
First, a breakdown of the terminology:
- A refund is merchant-initiated and voluntary. You decide to return the customer’s money. It costs you the sale, full stop.
- 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: the issuer is asking for transaction details. Often a precursor to a full chargeback.
- A dispute is the umbrella term, and the formal name of the network process that a chargeback runs through.
A refund is almost always cheaper than a chargeback. If a customer is going to get their money back either way, it’s better to give it as a refund than to have it taken as a chargeback. That idea drives a lot of prevention strategy.
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 just 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
Take a $100 order. You lose the $100 (reversed), you pay a chargeback fee (typically between $15 and $50), and if you shipped physical goods, you lose those too. Mastercard estimates the all-in cost of a chargeback can reach 2.5x the transaction value, and that it takes around 17 successful sales to recover the loss from one.2 That’s before you count the ratio damage, the cost that can put your account at risk.
Prevention and representment
A chargeback program runs on two fronts:
- 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 and comes first as a prevented chargeback carries no fees or ratio impact. Representment is the backstop, by the time you reach it you’re already paying some cost.
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.
Aside from the above, a large and fast-growing category is friendly fraud which is your own customers disputing legitimate purchases. 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.
The landscape is acronym soup, but it reduces to two companies owned by the two networks. Verifi (owned by Visa) runs RDR, Order Insight, and CDRN. Ethoca (owned by Mastercard) runs Ethoca Alerts and Consumer Clarity.
The one most worth knowing is RDR (Rapid Dispute Resolution), which is fully automated. It resolves qualifying disputes against your preset rules with no manual work. Order Insight and Consumer Clarity sit one step earlier, defusing confusion before it becomes a dispute at all. CDRN and Ethoca Alerts are more manual tools where you decide what to refund.
The trade-off, covered in the alerts guide, is that you pay a per-alert fee and refund the sale to avoid the chargeback. Near a ratio threshold that’s usually the cheaper outcome, since a chargeback’s fee and ratio damage cost more than a refunded sale plus the alert fee. 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.
This is a common place to lose recoverable revenue. Merchants win roughly 45% of the disputes they fight but recover revenue on only about 18% of chargebacks overall,4 in part because so many disputes go unfought or get fought with generic evidence that doesn’t address the actual claim. Our representment playbook has details on what evidence to provide for each reason code as well as information on how to write a strong rebuttal.
On chargeback management software
Manual chargeback management can work at low volume. Spreadsheets become less effective once your dispute volume rises due to the human capital required to respond to every dispute.
It’s at that point when software starts to pay off. Tools handle alerts and deflection, evidence assembly, automated representment, ratio monitoring, and reporting. The bigger question is less which tool than which model: a standalone bolt-on to your processor, a managed service that fights disputes for a cut of recoveries, or a payments platform with disputes built in. The software buyer’s guide walks through these options.
Bias takes the native approach: disputes are part of the platform, managed through the in the dashboard or through the disputes API resource. We pull relevant data like customer IPs, invoices and receipts automatically. If you’re evaluating tooling, consider demoing our platform.
Building a chargeback management program
A chargeback program tends to come together in stages:
- Measure your baseline ratio and reason-code mix. This gives you a baseline to compare against as you make improvements. It also tells you where to focus your attention, whether that be on fraud prevention, better customer service, or other areas.
- Address prevention gaps. Start with high-ROI prevention fixes: billing descriptor, simple refunds, recurring billing clarity, etc.
- 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. Past a certain volume, the deadline tracking and evidence assembly are better handled by software than a person. AI representment and API-based evidence submission help you keep up without growing headcount.
To conclude: prevention shrinks the problem, deflection catches what prevention misses, and representment recovers what lands. Automation lets it scale.