How do you fight a chargeback?

What is actually being judged

Not whether you are right. Whether the evidence you submitted matches what the reason code requires.

Every chargeback arrives with a code that states the grounds: the customer did not recognise the transaction, the goods never arrived, the service was not as described, the transaction was fraudulent. Each code has an associated list of what would rebut it, and that list is published.

A response that ignores the list and explains the situation in prose will lose, however true it is. A response that attaches the delivery confirmation with a signature, the IP and device match, the terms the customer accepted at checkout, and the record of the customer using the service, will often win, with almost no prose at all.

The four things that decide most cases

The right document for the right code. A friendly-fraud claim wants evidence the cardholder made the purchase and received the benefit. A non-delivery claim wants proof of delivery to the billing address. Sending the wrong one is sending nothing.

The deadline. Windows are short and counted in days. A missed deadline is an automatic loss regardless of merit, and this is a routine cause of loss at businesses where disputes land in an inbox nobody owns.

Legibility. Submissions go through systems and reviewers with very little time. A single compiled document, clearly labelled, ordered to mirror the code's requirements, beats a bundle of screenshots.

Whether it was authenticated. A transaction that passed 3D Secure has usually already shifted fraud liability to the issuer, which means the chargeback should not have reached you at all and saying so is often sufficient.

When not to fight

This is the part most guidance omits.

Representment costs staff time and a fee, and it does not reduce your chargeback count even when you win, because the ratio that scheme monitoring programmes watch counts disputes received rather than disputes lost. So a merchant that wins every case can still enter a monitoring programme.

Fight where the amount justifies the effort and the evidence is strong. Do not fight low-value cases with weak evidence, and do not fight a customer who is plainly right, because the refund is cheaper than the process and much cheaper than the relationship.

The higher-return work sits earlier: a clear billing descriptor so people recognise the charge, an easy cancellation path so leaving does not require a bank, responsive support so the customer calls you first, and pre-dispute alerts that let you refund before a case is formally raised and counted.

Appealing a parking ticket. Writing a paragraph about how unfair it was achieves nothing. Attaching the permit, photographed, with the date visible, on the form they specified, before the date they specified, works. The council is not weighing your argument. It is checking whether the required thing is present.

Where you meet it

Every dispute notification with a code nobody in the business understands. Every merchant portal with a deadline counter. Every won case that did not improve the ratio.