Double Refund Chargeback

What a double refund chargeback is

A double refund chargeback is one card purchase paid back twice: first through a refund you issue, then through a chargeback granted by the customer’s card issuer. A refund is handled by your business; a chargeback moves through the issuer and card network. The two processes can run at the same time, so a refund does not automatically stop an open dispute.

The customer might ask you for a refund and separately contact their bank, or dispute the charge first and then ask you to refund it. A delayed refund posting can also prompt a customer to dispute the payment. Receiving both credits does not by itself prove the customer acted intentionally.

Before paying a customer back, check whether the same transaction already has a refund or an open dispute.

How the two processes collide

Your support team, refund system, and dispute or alert system can each handle the same transaction without sharing an up-to-date status. For example, an agent refunds an order while a dispute alert is already being resolved. The issuer then grants the chargeback, and the refund has already left your account.

Timing matters. A refund issued before a customer disputes a charge can prevent a chargeback from proceeding, but refunding after a dispute is filed does not cancel it. As of 2026, cardholders generally have 120 calendar days from the transaction or expected delivery date to dispute under Visa and Mastercard rules. Your response window is much shorter, often 20 to 30 days as set by your processor.

One $100 sale, two payouts

Illustrative example excludes any dispute fee or staff time.

What it costs your business

You lose the sale amount through the refund and the same amount again when the chargeback is taken from your account. You can also be charged a dispute fee, even when the underlying problem is a duplicate payout. For an illustrative $100 sale, issuing a $100 refund and then losing a $100 chargeback means $200 leaves your business, before any fee or staff time.

The duplicate can be hard to spot because the refund and chargeback appear as separate events in different records. A growing number of disputes also adds operational work and can affect your chargeback ratio, which card networks monitor. A refund receipt alone does not show whether a separate dispute remains open.

Where the process breaks down

The common failure is approving a refund without checking the transaction’s dispute status and refund history. A second is treating an alert as resolved before recording the outcome against the original transaction. If you refund after a dispute begins, preserve the refund confirmation and submit it with your response rather than assuming the dispute will disappear.

Reconcile each refund and chargeback against the same order or transaction ID. Compare the amount, transaction date, refund date, dispute status, and final outcome in your payment records. That gives your team evidence to identify a duplicate quickly and prevents another agent from paying out on the same sale.

What you can actually change

1. 01
   Check before refunding. Search the transaction for an open dispute, alert, or existing refund before issuing another payment. Record the check with the order or transaction ID.
2. 02
   Log every outcome. Keep the refund confirmation and dispute status together in your transaction records. Update the record when the issuer decides the dispute.
3. 03
   Explain refund timing. Tell customers when to expect a refund to appear in their account. A clear timeline can reduce disputes filed while a refund is still processing.
4. 04
   Respond with proof. If a dispute arrives after you refunded the purchase, submit the refund confirmation within your processor’s response window. As of 2026, response windows are often 20 to 30 days, but the exact deadline is set by your processor.

Frequently asked questions