Friendly Fraud on Shopify: What It Is and How to Actually Fight It

---

The most frustrating chargeback you'll ever get is not from a stolen card.

It's from a real customer. They bought your product with their own card. It arrived. They kept it. And then they told their bank they never made the purchase.

That's friendly fraud. The name is terrible because there is nothing friendly about it. But it's the version of chargebacks most Shopify merchants actually deal with, and almost nobody explains how to fight it.

So here's what I've learned from reading a lot of these cases while building ChargebackWiz.

What friendly fraud actually looks like

Friendly fraud is any dispute where the real cardholder made the purchase and then disputed it anyway. It shows up in a few repeatable shapes:

The regret purchase. They bought it at 1am, felt bad about the money later, and disputing felt easier than asking for a refund.

The family purchase. A kid or spouse used the card. The cardholder sees a charge they don't remember approving and calls the bank. They're not lying exactly. They just didn't buy it themselves.

The impatient refund. They asked for a refund, didn't want to wait or didn't want to ship the item back, and went to the bank instead.

The forgotten subscription. They signed up, forgot, saw the renewal, disputed it.

And the deliberate one. Some people have learned that disputing works. Buy the thing, keep the thing, dispute the thing. Free product.

Different motives, same result for you. Money gone, product gone, plus a dispute fee on top.

Why the bank sides with them

This is the part that makes merchants angry, so let me be direct about it.

The dispute process was designed to protect cardholders from real fraud. When a cardholder says "I didn't make this purchase," the bank's default is to believe them. The burden of proof is entirely on you.

The bank reviewer doesn't know your customer. They can't tell a liar from a fraud victim. All they have is the cardholder's claim on one side and your evidence packet on the other. No packet, cardholder wins. Weak packet, cardholder wins.

That sounds bleak. It's actually good news.

Because friendly fraud has a built-in weakness: the purchase was real. Which means real evidence exists. The card matched. The address matched. The package got delivered to their door. A stolen-card fraudster leaves none of that behind. Your regretful customer leaves all of it.

The reason code it hides under

Friendly fraud almost always arrives labeled as fraudulent. Sometimes "unrecognized." The cardholder told their bank it was a stolen card, so that's the code you get.

This matters because the reason code decides what the bank reviewer checks. I wrote a full breakdown of the codes in chargeback reason codes explained, but for a fraud-coded dispute the checklist is basically: prove the real cardholder made this purchase.

And for friendly fraud, you usually can.

The evidence that wins these cases

Here's what actually moves a fraud-coded dispute in your favor:

AVS and CVV match. The payment gateway checked the billing address and the card security code at purchase time. If both matched, the buyer had the physical card details AND knew the cardholder's address. Say that plainly in your response.

Billing address = shipping address. The "stolen" card's owner shipped the order to their own house. Point at it.

Order history. This is the one almost everyone forgets. If this customer ordered from you 3 times before with the same card and never disputed, put that front and center. Fraud victims don't have a purchase history with you. Regulars do.

Delivery confirmation. Carrier, tracking number, delivery scan at the address on file. The product is at their house. Make the reviewer see that.

Customer communication. Any email, chat, or DM where they discuss the order, ask about shipping, or request a refund. Someone who emailed you about "my order" has a hard time claiming they never made it.

Device and IP data. Same IP or device as previous legitimate orders is a strong signal.

None of these wins alone. Together they tell a simple story: the cardholder bought this, received this, and disputed it anyway. Bank reviewers see that pattern constantly. You just have to lay it out for them. The full packet structure is in how to win a chargeback as a merchant.

One honest caveat. Some friendly fraud cases lose even with good evidence. Card-network rules still tilt toward cardholders, and some issuing banks barely read responses. You're playing for a better win rate, not a perfect one. I don't have enough won-case volume across ChargebackWiz merchants to publish our numbers yet. Once I do, I'll share them.

Cutting friendly fraud off before the dispute

Fighting is half of it. The cheaper half is prevention:

Fix your statement descriptor. If your store is "Cozy Candle Co" but the card statement says "SUNRISE TRADING LLC," you are manufacturing "unrecognized" disputes. Make them match. This is the highest-ROI fix on this list and takes 5 minutes in your payment settings.

Make refunds easier than disputes. A visible refund policy and fast support replies matter. Customers dispute when refunding feels hard. If the bank feels easier than you, you lose.

Use delivery confirmation on everything. Signature on high-value orders. The delivery scan is your single strongest evidence item, so make sure it always exists.

Send a reminder before subscription renewals. Costs you a few cancellations. Saves you the disputes, and each one of those costs the sale plus a fee.

Keep every customer message. Support threads become evidence. Don't delete them.

When to just refund instead

Not every dispute is worth fighting. If it's a $12 order and the dispute fee is $15, fighting a weak case can cost more than it recovers. Refund fast, block the customer, move on.

But run the math before you fold. On a $180 order with delivery confirmation and an AVS match, folding is just donating margin to someone who kept your product.

Also worth knowing: repeat offenders get flagged. Banks track how often a cardholder disputes. Every well-documented response you file makes the next false dispute a little harder for them.

What we automate

This whole post is a checklist, and checklists are what software is for. ChargebackWiz reads the reason code, pulls the matching evidence from the Shopify order automatically, and builds the response packet before the deadline. Order history, AVS/CVV results, tracking, delivery scan, the works. You review and submit, or let auto-pilot handle it.

Common questions

Is friendly fraud illegal? Deliberately disputing a purchase you made and kept is fraud, and in most places it's technically a crime. In practice, nobody prosecutes a $60 chargeback. Your realistic remedy is winning the dispute, not the courtroom.

Can I block a customer who filed a friendly-fraud dispute? Yes. Shopify lets you cancel and refuse future orders, and I'd recommend it. One successful dispute teaches them it works. Also consider blocking their email and address at checkout with a fraud filter.

Should I contact the customer after a dispute is filed? It can work, especially for the "family purchase" and "forgot the subscription" cases. Some customers genuinely don't realize a dispute hurts you more than a refund would have. If they agree it was a mistake, they can ask their bank to withdraw it. Keep the whole exchange in writing. It becomes evidence either way.

Does winning stop them from disputing again? That dispute, yes. It's decided. They can't refile the same charge under a new reason. And your win goes into the network's data on that cardholder.

Is "item not as described" also friendly fraud? Sometimes. A customer who wants a free product but knows "stolen card" is a lie will file not as described instead. Different code, different evidence checklist, same fight.

So look at your last few disputes. How many were actually stolen cards, and how many were your own customers?