Chargeback guide

A customer says they don't recognise the charge — what now?

For a fraud claim, the processor is asking: did the real cardholder authorise this sale?

What this dispute type means

In a fraud claim the cardholder tells their bank they don't recognise the charge. It might be a stolen card, a family member's purchase, or a real purchase the cardholder later disowned.

The processor is asking one question: did the real cardholder authorise this sale? Your records either connect the order to the person who owns the card, or they don't.

What evidence typically helps

  • Order records showing the customer's details, IP/device data, and any past orders from the same customerAn order placed from the same device, address and email as earlier successful purchases is far stronger than a one-off transaction with no history behind it.
  • AVS/CVV match results from your processor, if availableIf your processor passed the address and security-code checks on this sale, attach those results rather than describing them.
  • Proof of delivery to the address on file — tracking with a signature or confirmed delivery is the strongest formDelivery to the address the cardholder has on file with their bank, with a signature, is the single most persuasive item in a fraud case.
  • Any messages where the customer acknowledges the orderA reply to an order confirmation, a delivery question, or a review all tie the person to the purchase.

What weak evidence looks like

The one thing to get right: Consistency matters most here: the details on your order should line up with what your processor has on file.

  • A delivery to an address that has nothing to do with the cardholder weakens an otherwise strong file — check before you send it, and explain any difference yourself.
  • Screenshots of your own admin panel prove what your system says, not that the cardholder ordered. Pair them with processor-side data wherever you have it.

How the respond-by deadline works

Fraud disputes are often decided quickly, so a short file with your three strongest documents beats a long one sent late.

The respond-by date comes from the chargeback notice your processor sent you. That date is the one that matters, and meeting it is yours to do — nothing on this site files a response for you or buys you more time.

You respond through your processor's own portal, dashboard or process, using the case reference they gave you. If the notice doesn't state a deadline, or you can't find it, ask your processor before the window closes.

Build the response early enough that you aren't choosing between sending it late and sending it thin. If you're close to the deadline, send your strongest evidence first rather than waiting for a complete file.

What a good response letter contains

  1. State the order date, the amount, and the email or device used, in the first lines.
  2. Report the AVS/CVV result and the delivery address exactly as recorded — including anything that didn't match.
  3. Close with the evidence that ties this order to earlier orders from the same customer.

Whichever dispute type it is, the letter also needs:

  • The case reference and the disputed amount in the first two lines, so the reader knows which case this is.
  • One short paragraph on what was sold and when — facts only, no adjectives.
  • The evidence listed in the order it supports your account, each item named and dated.
  • A closing line stating what you're asking for, without predicting the outcome.
  • Your business details and a contact for follow-up questions.

Fighting one right now? Log your case in about ten minutes.

Chargeback Combat writes your side of the case down as one organised record — the reference, the dates, the respond-by deadline and the evidence you hold — and drafts a response letter you review, edit and send yourself.

We organise and draft. We don't file your response with your processor or the card network, and nobody here can promise a particular outcome — that decision is between you, your customer and the network.

General guidance only — networks and processors differ, and your processor's own instructions always take precedence.

Other dispute types

Not sure which one fits? Start from all dispute guides.