What Is a Chargeback? Meaning, Process, Costs and How Merchants Respond

A chargeback is a card payment that the cardholder’s bank reverses after the cardholder disputes it. The merchant does not agree to it. The issuing bank takes the money back through the card network, the merchant’s account is debited, a fee is usually added, and the merchant gets a fixed window to prove the charge was valid.

Chargebacks were designed as consumer protection. They let a cardholder recover money from a merchant who never delivered, overcharged, or ran a card without permission. Today a large share of them come from customers who did receive what they ordered. That is why merchants treat chargebacks as a cost to manage, not only a fraud problem.

This guide is the starting point for everything else on our blog. It covers the definition, the parties involved, how the process runs, how chargebacks differ from refunds and inquiries, why they happen, what they cost, the deadlines, and how merchants fight and prevent them.

Chargeback meaning, in one paragraph

The word is literal: the bank charges back the transaction to the merchant. The term mostly applies to credit and debit cards on the four major networks (Visa, Mastercard, American Express and Discover). Wallets and payment platforms such as PayPal run similar processes under their own rules. Every chargeback carries a reason code, a short code from the network that says why the cardholder disputed (for example Visa 13.1, “Merchandise/Services Not Received”). The reason code decides what evidence the merchant needs to win.

Who is involved in a chargeback

Five parties take part in every card chargeback. Knowing who does what explains why the process feels slow and why the merchant hears about it last.

American Express and Discover often act as both issuer and network, which makes their disputes a little more direct. The principle is the same.

How a chargeback works, step by step

The full path from purchase to final ruling looks like this.

1. The cardholder disputes the charge. They call their bank or tap “dispute” in a banking app. They do not have to contact the merchant first, and many don’t.
2. The issuer opens the chargeback. The bank checks that the dispute qualifies, assigns a reason code and usually gives the cardholder a provisional credit.
3. The funds are pulled from the merchant. The chargeback travels through the network to the acquirer, which debits the disputed amount from the merchant’s account. The processor typically adds a chargeback fee.
4. The merchant is notified. The processor sends the reason code, amount, transaction details and a response deadline.
5. The merchant accepts or fights. Accepting closes the case. Fighting means submitting evidence through representment before the deadline.
6. The issuer decides. If the evidence shows the charge was valid, the funds return to the merchant. If not, the cardholder keeps the credit.
7. The case can escalate. If either side still disagrees, the case can move to pre-arbitration and then arbitration, where the card network makes a binding ruling.

For a closer look at each step from the merchant’s side, read what happens when a customer disputes a charge. For each stage and the decisions at each one, see the chargeback dispute lifecycle.

Chargeback vs refund vs dispute vs inquiry vs retrieval request

These words are often used as if they mean the same thing. They don’t, and each one calls for a different response.

Two practical points follow. First, an inquiry or retrieval request is a chance to stop a chargeback: answer it quickly and fully, and many never escalate. Second, a refund issued after a chargeback has been filed can cost you twice, once for the refund and once for the chargeback. The comparison is covered in full in chargeback vs refund, and the double-loss scenario in chargeback after a refund. PayPal adds its own layers (dispute, claim, chargeback), explained in PayPal disputes vs chargebacks.

Why customers file chargebacks

Every chargeback falls into one of three causes. The reason code tells you which one the cardholder claimed. Your evidence decides which one it really was.

1. True fraud

A criminal used a stolen card or card number, and the real cardholder disputes a charge they never made. These arrive under fraud codes such as Visa 10.4 (Other Fraud, Card-Absent Environment), Mastercard 4837 (No Cardholder Authorization), Amex F29 and Discover UA02. Card-testing attacks can produce them in bulk; see card testing fraud.

2. Friendly fraud (first-party misuse)

The cardholder made the purchase, received the order and disputes it anyway. They might not recognize the billing descriptor, forget a subscription renewal, regret the purchase, or simply find the bank easier than a return. Friendly fraud often comes in under fraud codes, or under consumer codes such as Visa 13.1 (Merchandise Not Received), Visa 13.2 (Cancelled Recurring Transaction) and Visa 13.3 (Not as Described). Learn to spot it in friendly fraud and first-party vs friendly vs true fraud.

3. Merchant error

Sometimes the merchant really did get it wrong: a duplicate charge, a refund that was promised and never processed, a charge after cancellation, or an order that never shipped. Typical codes include Visa 12.6.1 (Duplicate Processing), Visa 13.6 (Credit Not Processed) and Mastercard 4853 (Cardholder Dispute). These are the cases to accept and fix at the source.

Each network has dozens of codes. Browse them all in our reason code library, or start with the guides to Visa, Mastercard and PayPal codes.

What a chargeback costs a merchant

A chargeback costs much more than the sale. Look at four layers:

• The transaction amount. It is debited as soon as the chargeback is filed.
• The goods or service. If it shipped, it is almost never returned.
• The chargeback fee. This is typically $15 to $50 per case from your processor, and it is usually kept even if you win. Fees vary by processor and risk profile; see chargeback fees.
• Ratio and monitoring risk. Every chargeback counts toward your chargeback ratio. Card networks run monitoring programs that add fines and conditions above set thresholds. Visa’s VAMP combines fraud and disputes into one ratio, with a merchant threshold of 1.5% in most regions as of 2026. Mastercard’s Excessive Chargeback Merchant program is commonly cited at 1.5% and 100 chargebacks per month. Sustained breaches can lead to account termination and placement on the Mastercard MATCH list.

Add staff time and the all-in cost usually comes to around two to three times the transaction amount. The full math is in how much does a chargeback cost. Ratio benchmarks are in what is a good chargeback ratio, and the Visa program is covered in VAMP explained. Thresholds change and vary by region and acquirer, so confirm the current numbers with your acquirer.

Chargeback time limits

There are two clocks, and they are very different lengths.

• The cardholder’s window to file is generally around 120 days from the transaction or expected delivery date. Some reason codes and situations allow longer, up to 540 days in certain cases.
• The merchant’s window to respond is short, typically 7 to 21 days from notification, depending on the network, the reason code and your processor. Your processor’s deadline is usually earlier than the network’s, because it needs time to package and forward your evidence. Treat the processor’s date as the real one.

Miss the response deadline and the case is lost automatically, however strong the evidence. The details by network are in chargeback time limits. For how long the whole process takes from start to finish (often 30 to 90 days, longer with escalation), see how long does a chargeback take.

How merchants respond: representment

Representment (Mastercard calls it the second presentment) is how a merchant contests a chargeback. You send the transaction back to the issuer with evidence that it was valid. A winning response has three parts:

1. A short rebuttal letter that names the reason code and explains, point by point, why the cardholder’s claim fails. Templates are in chargeback rebuttal letter template.
2. Evidence matched to the reason code. For “not received,” that means carrier tracking showing delivery to the billing or shipping address. For “fraud,” it means AVS and CVV results, IP and device data, account login history and prior undisputed orders. For “not as described,” it means the product page, photos and the policies the customer agreed to. For subscriptions, it means the signup terms, renewal notices and usage records.
3. On-time submission through your processor, before its deadline.

For Visa card-absent fraud disputes, Visa Compelling Evidence 3.0 lets merchants show that the same cardholder made earlier undisputed purchases using matching identifiers. A qualifying case moves liability back to the issuer. See compelling evidence.

The issuer then decides. If you win, the funds come back. If the cardholder’s bank still disagrees, it can escalate to pre-arbitration, and from there to network arbitration, where filing fees raise the stakes for both sides.

Not every chargeback is worth fighting. Clear merchant errors should be accepted. Very small disputes may cost more in time than they recover, unless the work is automated; see should you fight small chargebacks. For the full method, read how to win a chargeback dispute. Processor-specific steps are in our guides for Stripe, PayPal, Braintree, Adyen, Square, Checkout.com and Klarna.

How to prevent chargebacks

Prevention works in layers, starting at checkout and ending just before a dispute becomes a chargeback.

• Make the charge recognizable. Use a billing descriptor that matches your store name, and add a support URL or phone number.
• Make refunds easier than disputes. Customers who can reach you and get an answer quickly rarely call their bank.
• Be clear about subscriptions. State the terms at checkout, send a renewal reminder, and offer a one-click cancellation.
• Screen for fraud at checkout. Use AVS, CVV, 3-D Secure where it fits, and velocity rules to stop card testing. See prevent disputes at checkout.
• Ship with tracking and confirm delivery. Delivery confirmation prevents “not received” claims and wins them when they do arrive.
• Catch disputes before they become chargebacks. Alert networks (Ethoca, Verifi CDRN) and Visa Rapid Dispute Resolution let you refund before a chargeback is recorded. Compare them in Ethoca vs Verifi vs RDR.
• Flag repeat disputers. Customers who have disputed before are much more likely to do it again. See how to stop repeat disputers.

The full playbook is in how to prevent chargebacks. Industry guides cover subscriptions, supplements, beauty, electronics and DTC brands.

Chargeback glossary

For more definitions tied to specific codes, see our chargeback reason codes overview.

Where automation fits

The work on each chargeback is mostly the same every time: notice the case, read the reason code, pull the order, tracking, customer and fraud data, write a rebuttal that fits the code, and submit before the deadline. DisputeDash does that work for a flat monthly fee. It connects to your processors, checkout platform, shipping and support tools, builds the evidence package for each reason code, and submits on time. It runs at an 87% win rate across 15 brands in production. If you are comparing options, see chargeback representment services and the best chargeback management software, or check pricing.

The short version

A chargeback is a bank-forced reversal of a card payment. The cardholder disputes, the issuer pulls the money back through the network and the acquirer, and the merchant pays a fee and has days to respond. Chargebacks come from true fraud, friendly fraud or merchant error. They cost about two to three times the sale and push up your ratio. Merchants who prevent what they can and fight the rest with evidence matched to the reason code keep most of that money.