Skip to main content

Fraud vs. Friendly Fraud

TL;DR
  • True fraud = Stolen card/identity, cardholder is the victim
  • Friendly fraud = Cardholder disputes their own legitimate purchase
  • This distinction determines your response strategy: fraud prevention vs. evidence collection
  • 60-80% of chargebacks are friendly fraud, not true fraud
  • "Friendly fraud" and "first-party fraud" mean the same thing here. Not everyone agrees

A chargeback lands and you've got one question to answer first. Did the real cardholder make this purchase? If they didn't, you're looking at true fraud. If they did, you're looking at friendly fraud. The two arrive as different reason codes and need completely different responses.

Definitions​

True Fraud (Third-Party)​

An unauthorized transaction where someone else used the card and the real cardholder wasn't involved:

  • Stolen card credentials
  • Account takeover
  • Identity theft

Your odds of winning one of these are low. The cardholder's telling the truth, so there isn't much to argue with.

Friendly Fraud (First-Party Misuse)​

A legitimate transaction the actual cardholder turns around and disputes:

  • "I don't recognize this" (but made the purchase)
  • Family member made purchase without disclosure
  • Buyer's remorse disguised as fraud claim
  • Intentional abuse of chargeback process

These are the ones you can actually win. The evidence is usually sitting in your own systems.

Why It Matters​

AspectTrue FraudFriendly Fraud
Cardholder InvolvementNoneDirect
Representment PotentialLowHigh
Prevention MethodFraud detectionEvidence collection
LiabilityOften merchantDisputable

True fraud is a prevention problem, so you spend the money before the sale. Friendly fraud is an evidence problem, and you spend the effort after it.

Detection Indicators​

No single signal settles it on its own. It's how many stack up on one side that gives you the answer.

Signs of Friendly Fraud​

  • ✅ Delivery confirmed to billing address
  • ✅ Device fingerprint matches prior purchases
  • ✅ IP geolocation consistent with cardholder
  • ✅ Customer contacted support before dispute
  • ✅ Digital goods accessed after purchase

Signs of True Fraud​

  • ⚠️ Shipping address differs from billing
  • ⚠️ New device/browser fingerprint
  • ⚠️ IP from different country
  • ⚠️ Multiple failed payment attempts
  • ⚠️ No prior customer relationship
Quick Classification (3 Questions)

If you don't have device fingerprinting or advanced analytics, these three questions get you most of the way:

  1. Did the customer use the product after claiming non-receipt or unauthorized? Check login logs, download records, or delivery confirmation. If they used it = friendly fraud.
  2. Does the shipping address match the billing address? If yes and they claim unauthorized = likely friendly fraud. If different country with no purchase history = likely true fraud.
  3. Did the customer contact you before disputing? If they went straight to their bank without reaching out = likely friendly fraud or billing confusion.

What to do with the answer:

  • Friendly fraud - fight it with evidence. See winning evidence.
  • True fraud - take the loss and tighten prevention. See 3DS.
  • Billing confusion - fix your descriptor. See descriptors guide.

Next Steps​

Dealing with friendly fraud?

  1. Review compelling evidence - Build winning cases
  2. Improve descriptors - Reduce recognition disputes
  3. Set up device fingerprinting - Prove cardholder involvement

Dealing with true fraud?

  1. Implement 3DS - Get liability shift
  2. Review prevention options - Stop fraud before it happens
  3. Enhance detection - Catch more fraud earlier

Trying to classify disputes?

  1. Check detection indicators - Score the signals
  2. Review third-party patterns - True fraud signs
  3. Review friendly fraud patterns - First-party abuse
Last updated on