A chargeback is a transaction reversal initiated by the customer's bank rather than the merchant, typically in response to a customer dispute. Where a refund is voluntary and merchant-initiated, a chargeback is forced — the bank pulls funds from the merchant's account regardless of the merchant's view of the dispute, and the merchant has to actively contest it to recover the funds. For ecommerce brands, chargebacks are an unavoidable cost of card payments and a significant operational risk if rates climb.
How chargebacks happen
- Customer disputes a charge with their card-issuing bank — claiming fraud, non-delivery, item not as described, duplicate charge, or other issue.
- The bank temporarily reverses the charge, debiting the merchant's account and crediting the customer.
- The bank notifies the merchant of the dispute and the reason code.
- The merchant has a defined window (typically 7–30 days) to respond with evidence — proof of delivery, signed receipts, communication logs, terms of service.
- The bank reviews evidence and rules in favour of either party. If the merchant wins, funds are returned; if not, the reversal stands.
- Win or lose, the merchant typically pays a chargeback fee ($15–100 depending on the processor) for each disputed transaction.
Common chargeback reason codes
- Fraud / unauthorised transaction. The customer claims they didn't make the purchase. Often genuine fraud; sometimes "friendly fraud" where the customer made the purchase but disputes it anyway.
- Item not received. Customer says the order never arrived. Tracking data and delivery confirmation are the main evidence.
- Item not as described. Customer claims the product differs from what was advertised. Product page accuracy and customer service records matter.
- Duplicate charge. Customer says they were charged twice. Usually resolved with refund records.
- Subscription / recurring billing dispute. Common in subscription ecommerce when customers don't realise they're on a recurring plan or struggle to cancel.
- Refund not issued. Customer requested a refund the merchant agreed to, but the refund wasn't processed.
Chargeback vs. refund
Both move funds back to the customer, but the mechanics differ significantly:
- Refund: merchant-initiated, voluntary, customer's bank not involved. Typically no fee.
- Chargeback: bank-initiated, forced reversal, merchant must contest to keep funds. Always carries a fee, win or lose.
Issuing a refund preemptively when a customer is unhappy is almost always preferable to letting it become a chargeback — refunds cost less, preserve the relationship, and don't damage the merchant's chargeback ratio.
Why chargeback rates matter
Card networks (Visa, Mastercard) monitor merchant chargeback ratios. Sustained chargeback rates above 0.9–1% trigger monitoring programs that increase fees and processor scrutiny; rates above 1.5–2% can lead to processor account termination, which is a significant operational disruption — finding new processing infrastructure under termination conditions is harder and more expensive than maintaining low chargeback rates in the first place.
Reducing chargebacks
- Clear product descriptions and photography. "Item not as described" disputes drop sharply when customers know what they're buying.
- Visible billing descriptors. The merchant name on the credit card statement should match the brand the customer thinks they bought from.
- Easy refund and cancellation flows. Customers who can self-serve a refund don't escalate to their bank. Subscription brands especially benefit from frictionless cancellation.
- Responsive customer service. Most chargebacks could have been refunds if customer service responded faster.
- Fraud prevention tools. Address verification, 3D Secure, and fraud-scoring services (Signifyd, Riskified, Stripe Radar) catch fraudulent transactions before they ship.
- Tracking and delivery confirmation. "Item not received" is straightforward to defend with tracking; impossible to defend without it.
.png)
.png)
