Merchant Fraud Guide Sections

First-Party Fraud: When Customers Dispute

The card is real. The buyer is real. The dispute comes later, on purpose or by mistake. Here is how to see it coming.

The payment clears. The card is real and the person owns it. At a later date the cardholder disputes the charge anyway. That is first-party fraud.

What first-party fraud means

First-party fraud is also referred to as friendly fraud or first-party misuse. It happens when a legitimate cardholder makes a purchase but then disputes it at a later date. The buyer is not a stranger with a stolen card. The buyer is your customer, using their own card, on purpose or by mistake.

Some of it is a genuine accident. The customer did not recognize the transaction on their statement, so they asked the bank about it. Some of it is deliberate. The plan is to keep the goods and get the money back too.

First-party versus third-party fraud

The difference is who the fraudster is. In third-party fraud, someone else has the card. A thief buys with stolen details, and the real cardholder spots the charge later. See the card not present fraud definition for how that works when the card is not physically handed over.

In first-party fraud, the cardholder is the fraudster. There is no stolen card and no thief. The order comes from the account owner, at their address, with their email. A real owner's order can pass every check.

Common examples

The main example is a disputed card payment. The customer buys, receives the goods, then tells the bank they never got them, or never made the purchase at all. The sale can then turn into a chargeback.

Refund abuse is another. A buyer wears the dress, then returns it. Or they claim an item never arrived when it did. The money goes out through your own refund button. The payment was real.

Account takeover fraud can look similar, where someone breaks into a real customer's account. That is third-party fraud, but it can also turn into a chargeback.

Why it is hard to detect online

Online fraud is harder to detect than fraud at brick-and-mortar businesses, because it is harder to be certain who the buyer is. In a shop, the card is in someone's hand. On your site, you have a name, an address, and a device. None of them prove intent.

The buyer also controls the timing. Everything looks normal until the dispute lands at a later date. By then the goods have shipped.

Red flags to watch

No single order tells you much. Patterns do. Look at purchase history, return rates, and chargeback patterns across accounts, not one basket at a time.

Watch for customers with a history of disputes or frequent returns. One dispute is bad luck. Repeat disputes from one buyer are a pattern.

What it costs you

The costs stack up. A disputed sale can later turn into a chargeback, and you may lose the goods as well. You cannot catch this one at checkout, because at checkout it looked like a normal order.

Defenses that help

You cannot stop all of it, but you can make it harder and protect yourself when it happens.

Write a clear return policy and show it at checkout, where the customer must agree to it. For physical goods, ship to a verified billing address and require signature on delivery. Stripe's guide says each of these can help combat friendly fraud.

Handle refunds carefully. A customer cannot dispute fully refunded payments, but can dispute partially refunded ones. Never refund using a different method than the one originally used. If a card has legitimately been closed, you can still perform a refund.

Where tools fit

Rules and models help with the pattern problem. Machine learning can flag potential friendly fraud cases by analyzing customer purchase history, return rates, and chargeback patterns. See how ai fraud detection works and what it can and cannot catch.

You can also tighten the rules themselves. If you use Stripe, its guide says you can change a 3DS rule into a block rule. Stripe says that can stop users who pass 3DS from committing first-party fraud. For the wider problem of spotting bad orders before they ship, start with card not present fraud detection.

None of this removes the risk. It narrows it.

Sources

The rest of Fraud prevention