Skip to main content

First-Party Fraud

TL;DR
  • First-party fraud means your customer is lying, using their own real identity. They aren't hiding who they are
  • Umbrella category that includes: friendly fraud (real purchase, knowingly disputed without a valid reason), refund fraud, and promo abuse
  • No stolen identity. The person is who they claim to be
  • Hard to detect because the customer looks legitimate
  • Prevention: Clear policies, evidence collection, behavioral patterns
  • The lie is the line. A customer who borrows and can't repay hasn't committed fraud, unless they lied to get the money. Why definitions don't match

A real customer's dispute, return or promo claim doesn't add up? If they're lying, it's first-party fraud. This is the umbrella category for fraud where the customer uses their own real identity, including friendly fraud (detail), refund fraud, and promo abuse.

First-party fraud occurs when a customer uses their own real identity and lies. No stolen card, no fake identity, just a real customer making a false claim.

The lie takes two shapes. Lying about facts, like inflating income on an application. Or lying about an event, like denying a purchase they made. Both are first party. The full definition and how others differ.

Key Distinction

Unlike third-party fraud, there's no victim cardholder. The fraudster IS the cardholder. That makes it harder to spot at checkout. Afterwards, the evidence can point at the cardholder (how). The defense still depends on the dispute condition.

Types of First-Party Fraud​

Friendly Fraud​

Customer makes a real purchase, then knowingly disputes it without a valid reason. Forgetting it, a valid complaint and a relative's real unauthorized use are different cases (classification).

PatternDescription
"I didn't order this"Claims they never made the purchase
"It never arrived"Falsely claims non-delivery
"It wasn't as described"Knowingly exaggerates quality issues
Family fraudClaims family member used card without permission. Which class this really is depends on whether they handed the card over

See Friendly Fraud for detailed coverage.

Refund Fraud​

Customer exploits your return and refund policies.

PatternDescription
WardrobingWear or use an item, then return it as unused
Empty box returnsReturn empty or wrong item
Receipt manipulationUse old receipts for new "returns"
Double-dippingGet refund AND chargeback

See Refund Fraud for detailed coverage.

Promotion Abuse​

Customer exploits discounts, coupons, and referral programs.

PatternDescription
Multi-accountingCreate fake accounts for new-customer discounts
Referral fraudSelf-refer with multiple accounts
Coupon stackingCombine offers your terms rule out. If the terms allow it, fix the terms. It isn't fraud
Free trial abuseCycle through trials with new accounts

See Promo Abuse for detailed coverage.

Detection Signals​

First-party fraudsters look like legitimate customers, but patterns emerge:

Behavioral Red Flags​

SignalWhy It Matters
Repeated disputes on one accountA pattern to investigate order by order
Returns outside comparable product and customer historyCheck the orders and reasons before treating a high return rate as abuse
Multiple accounts, same devicePossible multi-accounting for promos. Check for a shared household first
Claims "not received" despite signatureA lead. Check who signed and where it went
Disputes only high-value ordersA lead. Check each claim

Velocity Indicators​

PatternDescription
Disputes within days of deliveryCheck the claim. They may not have tried it, or it may have arrived broken
Surge in refund requestsCould be a product or delivery problem. Check before you call it abuse
Multiple promos same payment methodCheck the offer's terms

Prevention Strategies​

Clear Policies​

  1. Explicit return policy: No surprises, clear timeframes
  2. Documented terms: Screenshot at checkout
  3. Refund caps: Limit discretionary goodwill refunds under your published terms. What the law or your terms owe stays owed (UK rules are one example)
  4. Promo rules: One per customer, verification required

Evidence Collection​

Keep the records that fit the channel, where you lawfully collect them:

  • Physical goods: delivery confirmation, with a photo or signature where you use them
  • Digital services: access and use records
  • Customer communication history
  • Account creation and login timestamps, plus IP address and device fingerprint if you actually collect them

Behavioral Monitoring​

What to TrackWhy
Dispute historyFlag repeat disputes to investigate
Refund rate by customerSpot returns to look into
Account age vs. disputesNew accounts disputing quickly
Promo usage patternsMulti-account abuse

Fighting First-Party Fraud Chargebacks​

What can answer one of these disputes depends on its condition, and evidence of a real purchase isn't a guaranteed win. The same test applies to third-party fraud, where an eligible authenticated Mastercard payment has a remedy even when the use was fraudulent (Chargeback Guide, 13 May 2025, pp. 423-425):

Evidence TypeWhat It Shows
Delivery confirmationDelivered to the address on the order
Device fingerprint matchSame device as prior orders
Customer communicationThey acknowledged receipt
Return historyContext. It doesn't prove this claim is false
CE 3.0 matchQualifying earlier purchase history

The evidence to answer these can exist: delivery, access, earlier purchases. Track your own win rate instead of assuming one.

Response Playbook​

Before restricting a repeat buyer, review the orders and case IDs. A local restriction isn't permission to share buyer details. Check reporting and correction steps.

When first-party fraud is confirmed:

  1. Block the customer: No more orders from this account
  2. Block the identifiers: Email, phone, device, address, on your own block list
  3. Document everything: For future representment
  4. Review policies: Close any loopholes exploited
  5. Before an external report, check the reporting channel, permission and correction steps. A local restriction doesn't establish permission to share buyer details.

Next Steps​

Preventing first-party fraud?

  1. Implement device fingerprinting: Track across accounts
  2. Set up velocity rules: Catch patterns
  3. Strengthen return policies: Close loopholes

Fighting chargebacks?

  1. Review compelling evidence: CE 3.0 requirements
  2. Check friendly fraud tactics: Specific strategies
  3. Collect proper evidence: Before you need it

Stopping promo abuse?

  1. Review promo abuse patterns: Detection tactics
  2. Implement account linking: Link by device, then check shared households
  3. Set redemption limits: Cap per customer

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.