The Double Dip: When a Refunded Customer Files a Chargeback Too
Direct answer: The double dip is simple: a customer gets a refund from you, then files a chargeback with their bank for the same order, and ends up with the money twice. It slips through because refunds and chargebacks live in different systems watched by different people. The fix is reconciliation: match every chargeback against refund records, submit the refund proof in the dispute, and flag accounts that attempt it, because one successful double dip almost always predicts another.
Most return fraud takes planning. The double dip takes only impatience and a banking app. A customer asks for a refund, receives it, and then, days or weeks later, tells their bank they never got their money. The bank pulls the funds from your account while your refund receipt sits in a different system, seen by nobody who handles disputes.
It is one of the most fixable losses in ecommerce, and one of the most common, precisely because it is an organizational bug wearing a fraud costume. The money is not lost to clever criminals. It is lost between two desks.
How the double dip actually happens
The innocent version is confusion. Refunds take days to post, the customer checks their statement too early, sees the charge and no refund, and calls the bank in genuine frustration. The bank opens a dispute, the refund lands, and now both processes run to completion because nobody tells the bank the matter is settled. This version resolves if you respond to the dispute with the refund evidence.
The deliberate version is a business model. Rings teach it openly: always take the merchant refund first, then dispute anyway, because a large share of merchants never respond to chargebacks or respond without the refund proof attached. The expected value is high, the risk is near zero, and the whole scheme depends on your paperwork being slower than their script.
Why your own systems let it through
Refunds are usually issued by support or the warehouse in the commerce platform. Chargebacks are handled by finance or a payments tool. If those two records are never joined, the dispute response becomes a generic we shipped the product letter, which is true and completely beside the point. The bank needed one document: proof the customer was already made whole.
There is also a timing trap. Chargeback windows run long, sometimes months after the order. Staff who handled the original refund have moved on, notes are thin, and the dispute arrives as an unexplained debit. Companies that treat chargeback response as archaeology lose cases that were winnable on the day the refund posted.
The reconciliation habit that kills it
Build one weekly report: every chargeback, matched by order and transaction identifier against every refund. The match rate will surprise you the first time you run it. Each match gets the same response package: the refund confirmation, the amount, the date, the destination account details your processor provides, and a statement that the cardholder has already received the funds.
Automate what you can. Most payment processors can attach refund records to dispute evidence with the order link intact, and some offer alerts when a dispute opens on an already refunded transaction. The goal is boring reliability: no chargeback answered by a human reconstructing history from three dashboards under a deadline.
What to do about the customer afterward
Handle the two versions differently. The confused customer deserves a short, kind explanation and no penalty; their bank created the overlap as much as they did. You will often keep them for years once someone explains what happened.
The deliberate double dipper gets a closed account and a documented file. Attempting to collect twice for one order is fraud by any reasonable reading, and it predicts future attempts with near certainty. Keep the evidence, share it with your payment provider where their rules allow, and do not let a high lifetime value number talk you out of what the record shows.
Frequently asked questions
What is a double dip chargeback?
It is when a customer receives a refund from the merchant and also wins a chargeback from their bank for the same transaction, collecting the money twice. It happens through genuine confusion about refund timing and through deliberate fraud that banks on merchants not responding with refund proof.
How do you win a double dip dispute?
Submit the refund evidence: confirmation, date, amount, and processor reference showing the funds returned to the same card. Banks close these disputes when the documentation is clear, because the cardholder has already been made whole. Generic shipping proof without the refund record usually loses.
How common is refund and chargeback overlap?
Common enough that every mid sized store should reconcile weekly. The first audit typically finds a meaningful share of chargebacks sitting on already refunded orders, especially after holiday peaks when refund delays and impatient statement checks both spike.
Should you ban a customer who double dips?
If the evidence shows intent, yes. A customer who disputes after a completed, documented refund and cannot explain it has shown you their model. Confused first timers who cooperate when contacted are a different case and should be treated as such.