What Is a Chargeback? A Merchant’s Guide
Learn how chargebacks differ from refunds, how the dispute process works, and which evidence and prevention controls protect merchants.
A chargeback is a forced payment reversal initiated by a cardholder through their issuing bank instead of through the merchant. The bank pulls funds from the merchant account first and investigates second. The merchant loses the sale, often the product, and a separate fee on top.
How Is a Chargeback Different From a Refund?
A refund is voluntary and merchant-controlled, while a chargeback is compulsory and bank-controlled. Three differences matter operationally:
- Control: refunds are approved by the merchant, chargebacks are ordered by the issuer.
- Cost: refunds return only the sale amount, chargebacks add a separate chargeback fee.
- Record: refunds carry no network penalty, chargebacks count against your dispute ratio.
What Are the 5 Stages of the Chargeback Process?
Every dispute moves through 5 defined stages before it closes.
- Cardholder contacts the issuing bank and disputes the transaction.
- Issuer credits the cardholder provisionally and debits the acquiring bank.
- Acquirer debits the merchant account and forwards a numbered reason code.
- Merchant accepts the loss or submits representment evidence within the deadline.
- Issuer rules on the evidence, or the case escalates to network arbitration.
How Long Does a Chargeback Take to Resolve?
Most disputes resolve in 30 to 90 days from the initial filing. Representment deadlines are far shorter, commonly 20 to 45 days depending on the card network, and a missed deadline forfeits the case automatically.
What Are the 4 Chargeback Reason Code Families?
Card networks group reason codes into 4 families that describe what the cardholder claimed.
- Fraud: card-not-present transactions the cardholder says they never authorized.
- Authorization: transactions captured after a decline, an expiration, or a stale approval.
- Processing errors: duplicate charges, incorrect amounts, or currency mismatches.
- Consumer disputes: goods not received, goods not as described, or canceled subscriptions still billing.
Fraud and consumer dispute codes account for the majority of merchant losses, and both are heavily represented in friendly fraud filings.
When Does Chargeback Activity Put a Merchant Account at Risk?
Visa now evaluates fraud and dispute activity through its Visa Acquirer Monitoring Program at both acquirer and merchant levels. The current framework uses a combined fraud-plus-dispute measure and a minimum count of 1,500 events before program thresholds apply. Network rules and regional enforcement can change, so merchants should review their current VAMP ratio and Mastercard monitoring status with their acquirer instead of relying on an old static benchmark.
Which Metrics Should You Track Monthly?
Track dispute count, dispute ratio, win rate, and average dispute value. Reviewing all 4 together separates a seasonal spike from a structural problem in fulfillment or billing descriptors.
What Evidence Wins a Representment?
Compelling evidence is the documentation that proves the cardholder authorized and received what they paid for. Issuers weigh 5 exhibits most heavily.
- Signed proof of delivery or a tracking record showing the delivery address matched.
- AVS and CVV match results captured at authorization.
- IP address, device fingerprint, or login history tied to the cardholder account.
- Written terms the customer accepted, including refund and cancellation policy.
- Prior email or chat history showing the customer used the product or service.
Assemble the packet in the order the reason code requires, since issuers review against the specific claim rather than the overall story. The complete workflow appears in how to dispute a chargeback as a merchant.
Reducing Disputes Before They Are Filed
Prevention outperforms representment at every volume. Clear billing descriptors, delivery confirmation, and responsive support resolve most complaints before they reach an issuer. Our guide to how to prevent chargebacks covers 9 controls merchants can deploy in a single billing cycle.
Declines and disputes also share root causes in gateway configuration. See chargebacks, declines, and operational problems for the operational view of both.
Frequently Asked Questions
Can a merchant win a chargeback dispute?
Yes. Merchants who submit compelling evidence, including signed delivery confirmation, AVS matches, and prior customer communication, win a meaningful share of cases. Documentation quality determines the outcome more than dispute volume does.
Who pays the chargeback fee?
The merchant pays the chargeback fee, and the fee is assessed whether or not the merchant later wins the dispute. Fees are set by the acquirer and vary by risk profile.
Does a chargeback remove the customer’s product?
No. A chargeback reverses the payment only. Recovering shipped goods is a separate collections matter the card networks do not handle.
Table of Contents
Subscribe to our newsletter
Get the latest insights and updates delivered to your inbox.
What Is a Payment Gateway? An Explainer From the Team That Configures Them Every Day
Learn what a payment gateway does during checkout, how it protects data, routes transactions, stores tokens, and adds cost.
What Is a Hosted Payment Gateway? When We Recommend One Over an Integrated Checkout
Learn how hosted payment gateways work, when they reduce PCI scope, and how they compare with integrated checkout experiences.
Payment Gateway vs Payment Processor: How We Explain the Difference to Every New Merchant
Understand the difference between a payment gateway and payment processor, including responsibilities, fees, reporting, and support.