Return abuse and chargebacks: how the two fraud types feed each other
Returns fraud and chargeback fraud are usually owned by different teams, tracked in different systems, and discussed in different meetings. The fraudsters do not respect that org chart. The same accounts cycle between the two channels, picking whichever one is easier that week.
Treat them as one problem with two doors and the patterns get much clearer. A customer whose return was denied on Monday filing a chargeback on Friday is not two incidents. It is one dispute wearing two hats.
The denied return becomes a chargeback
This is the most common crossover. A customer requests a return outside policy, gets denied, and disputes the original charge with their bank instead. From the bank's perspective it looks like a legitimate "merchandise not as described" claim; from your perspective it is policy enforcement being relitigated in a forum where you usually lose.
The defense is documentation. Every denial should generate a timestamped record: the policy clause cited, the condition of the item if inspected, the communication history. Chargeback representment win rates climb sharply when you can show the bank a clean, consistent paper trail instead of a bare denial.
The double dip: refund then dispute
The reverse direction is more damaging. The customer gets a return refund, then files a chargeback on the same order, collecting twice. This works because refunds and disputes live in different systems that reconcile slowly, if at all. By the time anyone notices, the money is gone twice.
Close the loop with a simple control: every chargeback should trigger an automatic check for a prior refund on the same order, and every refund should be visible to whoever handles disputes. Accounts that double-dip once almost always try it again, so the first catch should land the account on a watchlist, not just resolve the single case.
Shared signals across both channels
The accounts doing this leave the same fingerprints in both systems: new accounts with immediate high-value activity, shipping and billing mismatches, repeated "not as described" claims across unrelated products, and disputes filed just inside the bank's time limit. A returns-side risk score and a payments-side risk score built on the same account history catch far more than either alone.
At minimum, share the block and watch lists. An account banned from returns for wardrobing should not get frictionless checkout on its next order, and an account with two chargebacks should not get instant-approve returns. Each team is currently handing the other team's problem a clean slate.
One owner for the account, not the channel
The structural fix is to score the account, not the transaction channel. When returns risk and payments risk roll up to one account-level view, the crossover patterns become obvious: the customer cycling between returns abuse and disputes, the household with three accounts doing the same thing, the spike in both channels after a policy change.
You do not need to merge the teams to do this. A shared weekly report with the top accounts by combined returns-plus-dispute cost will surface the crossover actors within a month. Start there; the organizational argument makes itself once the numbers are on one page.