Chargeback: what a merchant can actually do about one

A chargeback is a forced reversal of a card payment, initiated by the cardholder’s bank rather than by the merchant. The money is taken back from the merchant’s account, usually with a fee, and the merchant then has a limited window to dispute it by submitting evidence. That process — representment — is where the outcome is decided.

It helps to be clear about what a chargeback is not. It is not a refund: a refund is the merchant returning money voluntarily. It is not a complaint: by the time it arrives, the customer has gone to their bank instead of to you. And it is not usually a judgement about who is right — it is a decision on documents, made by people who were not there.

Why chargebacks arrive

• Genuine fraud: the card was used by someone other than the holder.
• Friendly fraud: the holder made the purchase and disputes it anyway — sometimes deliberately, often because they did not recognise the descriptor on the statement.
• Non-receipt: the goods or services never arrived, or arrived too late.
• Not as described: what arrived differed materially from what was sold.
• Processing errors: duplicate charges, wrong amount, a cancelled subscription that billed again.

The second and last categories are the ones a merchant can reduce without touching fraud tooling: a recognisable billing descriptor, a clear cancellation path, and an obvious support route are cheaper than winning disputes.

The evidence pack decides it

Representment is a documents exercise with a deadline, usually short. What counts depends on the reason code, and submitting the wrong evidence for the code is as bad as submitting none. Typically useful: the order record with date and amount, proof of delivery or of service access, the terms the customer accepted, the refund and cancellation policy as it was shown at purchase, and the communications with the customer.

1. Identify the reason code first, and assemble evidence against that code rather than telling the whole story.
2. Collect the artefacts, not summaries of them — the screenshot of the delivery confirmation, not a sentence saying it was delivered.
3. Redact what should not be shared, particularly other people’s personal data.
4. Assemble one ordered file with a short cover summary, and submit before the deadline.
5. Record the outcome against the order, so patterns become visible.

Watch the ratio, not just the losses. Card schemes run monitoring programmes based on the proportion of transactions disputed; crossing a threshold brings fees, mandatory remediation and, eventually, loss of processing. A merchant can be profitable and still be removed for a chargeback rate.

What reduces them

• A billing descriptor that names your brand as customers know it.
• Immediate order confirmation with what was bought and when it will arrive.
• Delivery tracking retained and retrievable months later.
• Cancellation that works without contacting support, particularly for subscriptions.
• Refunding promptly where the customer is right — a refund costs less than a dispute you may lose.

Ettex is not a payment processor and does not fight disputes: the case is submitted through your acquirer or gateway. What it can do is the part that decides the case — assembling the evidence. Ettex PDF collects the order record, delivery proof, terms and correspondence into a single ordered file with the version that was submitted preserved, so the pack is built from records rather than reconstructed under a deadline. Where the underlying problem is an unpaid or disputed invoice rather than a card dispute, that is a different process.