Skip to main content
FHAVI

Research · Operations

Chargebacks: what actually causes them, and what reduces them

A chargeback is usually a support failure that became a bank dispute. The four causes worth fixing, the evidence that wins a dispute, and the ratio that tells you it is becoming structural.

2 min read

In brief

  • Most chargebacks follow an unanswered or unsatisfying support contact — the customer disputes because they gave up, not because they planned to.
  • Delivery time is the strongest predictor: a promise missed by a week produces disputes that a correct product never would.
  • The cheapest intervention is a proactive message when a parcel is late, before the customer has to ask.

The four causes

  • Never arrived, or arrived far later than promised. The customer's card issuer sees a merchant who did not deliver.
  • Arrived and did not match the listing — wrong item, wrong size, materially different from the photographs.
  • Unrecognisable statement descriptor, so the charge looks fraudulent to the customer themselves.
  • Refund promised and not received, which converts an ordinary refund into a dispute.

Only one of those four involves a dishonest customer. The rest are process failures that a store creates and then pays for twice — once in the refund, once in the fee.

Prevention that is cheaper than the dispute

  1. 1

    Publish a delivery window you can meet, then beat it

    The window is the promise a dispute is measured against. An optimistic promise is a liability.

  2. 2

    Message late parcels before the customer asks

    One email with a new date and a tracking link removes most of the anger that becomes a dispute.

  3. 3

    Make the statement descriptor recognisable

    If the customer cannot match the charge to your store, they dispute it to find out.

  4. 4

    Refund fast on the clear cases

    A refund issued in 24 hours costs the order. A dispute over the same order costs the order plus a fee plus a ratio.

When you do dispute

  • Evidence that wins: delivery confirmation with address, tracking showing delivery, the customer's own order confirmation, and any support thread.
  • Evidence that loses: policy screenshots with no order context, and arguments about the customer's intent.
  • Track the ratio monthly — disputes as a share of orders. A rising ratio is a product or delivery problem, not a payments problem, and processors will treat it as yours.

Chargebacks are a support and delivery metric that arrives as a financial one. Fix the promise, message the delay, refund the clear cases quickly — and keep the evidence for the ones worth disputing.

Questions

Asked about this directly

Does a refund prevent a chargeback?
If it is issued before the customer contacts their bank, usually yes. After the dispute is filed, the refund does not withdraw it.
How many chargebacks are too many?
The thresholds are set by your processor and card networks and vary by market and volume. Track the ratio monthly and treat any sustained rise as a signal, before a threshold is reached.
Should I fight every dispute?
No. Fight the ones with delivery evidence. Fighting a case you will lose spends time and does not improve the ratio.

Keep reading

Other pieces in the library

All research

Numbers first, promises second

Send your store and we will tell you which of these failure modes is already happening — before you pay for a fix.

Prefer email? Write to md@fhavi.com