Chargeback
A forced reversal of a card payment initiated by the cardholder's bank — the customer's escape hatch when the merchant's own one is worse.
A chargeback reverses a settled payment at the cardholder's request, through their bank rather than through the merchant. The merchant loses the money and a fee, and can contest it with evidence — a process weighted towards the cardholder. Sustained rates above roughly 1% put a merchant into card-network monitoring programmes with fines attached, so it is a commercial risk long before it is a support metric.
A large share of chargebacks are not fraud. They are “friendly fraud” — the customer did not recognise the descriptor, could not find how to cancel, or gave up on a refund request. Every one of those is a product failure with a cheaper fix: a recognisable billing descriptor, a self-serve cancellation that actually cancels, a visible refund path, and a receipt that names what was bought. Disputing after the fact costs more than preventing it.
In practice
A subscription product used its legal entity name as the card descriptor. 38% of chargebacks cited an unrecognised charge. Changing the descriptor to the brand plus a support number, and emailing a receipt on every renewal, cut total chargebacks by roughly half in a quarter.
Where teams get it wrong
- A billing descriptor nobody recognises, which generates disputes from satisfied customers.
- Cancellation that is harder to find than the dispute button in a banking app.
- No renewal notice, so charges arrive unannounced.
- Treating chargebacks as a finance problem rather than a product signal.
- Contesting disputes without the evidence the networks require, which wastes the effort entirely.
( Learn more )
Related terms
All terms- Payment GatewayThe service that takes payment details from a checkout, passes them for authorisation, and returns the result.
- ChurnThe rate at which customers stop paying or stop using a product over a given period — the mirror image of retention.
- 3-D SecureThe card-network authentication step that shifts fraud liability from the merchant to the issuer — at a measurable cost in completed checkouts.
- Error StateWhat an interface shows when something failed — which system failed, whether the user's work survived, and what they can do next.