Chargeback guide

A customer says they were charged twice — what now?

You must show the two charges are not the same sale.

What this dispute type means

A duplicate charge claim says the customer was billed twice for one purchase. Sometimes that is a genuine double submission; often it's two real orders that look similar on a bank statement.

The processor is asking whether the two charges are the same sale. Your answer is either 'here is what each charge was for' or 'you're right, one was an error'.

What evidence typically helps

  • Two distinct invoices, order numbers, or receipts — one per chargeSend one document per charge, each with its own order number, so the two are visibly not copies of each other.
  • Settlement or processing records showing what each charge coveredYour processor's transaction records show what each charge actually covered, and that is the version the processor itself can verify.
  • Timestamps showing the two transactionsGive the time and date of each transaction: two charges minutes apart look like a double submission, two charges a week apart usually don't.
  • Any customer communication acknowledging both ordersIf the customer wrote to you about both orders, that message is often the simplest proof that they knew about both.

What weak evidence looks like

The one thing to get right: If one charge was an error, refunding it before responding usually resolves the case faster than disputing it.

  • Sending the same invoice twice, or two invoices showing the same line items, doesn't prove two sales.
  • Arguing only about the first charge leaves half the dispute unanswered — address the second charge explicitly.

How the respond-by deadline works

If you conclude that one charge really was an error, refund it before you respond and say so in the response. That is faster than arguing, and it usually closes the case.

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. Say how many separate orders the customer placed, and identify each one by number.
  2. Attach the matching invoice or receipt to each charge.
  3. If you refunded one of them, lead with that and give the refund date and reference.

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.