Is returns fraud the same as chargeback fraud?

Returns fraud and chargeback fraud are different problems. Returns fraud arrives at your dock, like a box of bricks in place of a laptop, and is fought with inspection at receipt; chargeback fraud happens at the bank, where the customer keeps the goods, and is answered with proof of delivery.

What does the 9% returns fraud figure measure?

That figure counts returns, and it says nothing about disputes. NRF and Happy Returns project that US shoppers will send back $849.9 billion of merchandise for 2025, that online sales come back at a rate of 19.3%, and that 9% of all returns are fraudulent. The 9% still gets quoted in chargeback meetings as though it described disputes.

A chargeback fraud claim never reaches your dock. The customer keeps the goods and tells the bank that the charge was not theirs, or that nothing arrived, and the bank takes the money back. Check which of the two problems your fraud budget pays for, because merchants who fold them into one budget tend to spend it on the wrong one.

How should you defend against each one?

Returns abuse is fought at your warehouse, and a chargeback fraud claim is fought with proof of delivery. The person deciding a chargeback is a bank analyst who will never see your warehouse. Give the person who opens returns a written standard for what counts as a bad return, and let them refuse on that basis.

Then give whoever handles disputes read access to the return record, so the inspection photo that justified a refusal can be shown to the bank. Keep inspection notes, delivery proof and refund confirmations in one folder per order.

A customer who receives $60 back on a $100 order and then disputes the full $100 has not cancelled the dispute by accepting the credit. Stripe's guidance is to respond anyway and show the amount and date of the refund.

When should you refund instead of fighting?

Draw the line by order value and by what you hold. An early fraud warning is an alert that a cardholder has reported a charge as fraud, and Stripe reports that about 40% of Visa and Mastercard warnings turn into fraud disputes if the charge is not refunded. A refund only stops the report from counting when it is processed as a reversal, usually within about 2 hours of capture.

Stripe suggests refunding warning charges at or below roughly the dispute fee, and the $15 received fee it charges in the US is never returned. That advice suits a $12 order. It is a poor habit for a $400 one, because a merchant who refunds every suspicious order on request has built the very policy a returns abuser looks for.

Above the fee, the refund decision belongs with whoever can see the customer history, the carrier scan and the login record together. How to weigh those against each other is set out in the chargeback versus refund cost rule.

Why do December returns turn into chargebacks?

December returns turn into chargebacks when refunds are slow in the week after Christmas, which is when returns bunch up. Adobe counts 2025 holiday returns down 1.2% on the previous season, yet returns from December 26 to 31 rose 4.7%, and 1 in 7 holiday returns fell inside that window. A customer whose refund has not appeared by the time the statement closes has a quick route to getting it from the bank.

US law adds a clock of its own. Under Regulation Z, once a merchant accepts a return it has 7 business days to send the credit statement to the issuer, and the issuer then credits the cardholder within 3 business days of receiving it. The same section does not oblige a merchant to take returns, but you must move quickly on the ones you accept.

Takeaway: what to do this week

1. Write a bad-return standard. Give the person who opens returns written criteria and the authority to refuse on them.
2. Share the return record with disputes. Let whoever handles disputes see inspection photos, delivery proof and refund confirmations for each order.
3. Staff the refund queue for December 26 to 31. That week held 1 in 7 holiday returns in 2025, and Regulation Z gives you 7 business days to send the credit to the issuer once a return is accepted.
4. Answer partial-refund disputes. If a customer disputes the full amount after a partial refund, respond and show the refund amount and date.

Sources: NRF, "2025 Retail Returns Landscape" (15 October 2025); Adobe, 2025 holiday shopping season release (7 January 2026); Stripe Docs, "How disputes work"; Stripe Support, "June 2025 pricing updates for disputes"; CFPB, Regulation Z, 12 CFR 1026.12(e); Stripe Docs, "Dispute best practices". All checked 24 October 2026.