First-Party Fraud
- 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.
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).
| Pattern | Description |
|---|---|
| "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 fraud | Claims 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.
| Pattern | Description |
|---|---|
| Wardrobing | Wear or use an item, then return it as unused |
| Empty box returns | Return empty or wrong item |
| Receipt manipulation | Use old receipts for new "returns" |
| Double-dipping | Get refund AND chargeback |
See Refund Fraud for detailed coverage.
Promotion Abuse
Customer exploits discounts, coupons, and referral programs.
| Pattern | Description |
|---|---|
| Multi-accounting | Create fake accounts for new-customer discounts |
| Referral fraud | Self-refer with multiple accounts |
| Coupon stacking | Combine offers your terms rule out. If the terms allow it, fix the terms. It isn't fraud |
| Free trial abuse | Cycle 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
| Signal | Why It Matters |
|---|---|
| Repeated disputes on one account | A pattern to investigate order by order |
| Returns outside comparable product and customer history | Check the orders and reasons before treating a high return rate as abuse |
| Multiple accounts, same device | Possible multi-accounting for promos. Check for a shared household first |
| Claims "not received" despite signature | A lead. Check who signed and where it went |
| Disputes only high-value orders | A lead. Check each claim |
Velocity Indicators
| Pattern | Description |
|---|---|
| Disputes within days of delivery | Check the claim. They may not have tried it, or it may have arrived broken |
| Surge in refund requests | Could be a product or delivery problem. Check before you call it abuse |
| Multiple promos same payment method | Check the offer's terms |
Prevention Strategies
Clear Policies
- Explicit return policy: No surprises, clear timeframes
- Documented terms: Screenshot at checkout
- Refund caps: Limit discretionary goodwill refunds under your published terms. What the law or your terms owe stays owed (UK rules are one example)
- 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 Track | Why |
|---|---|
| Dispute history | Flag repeat disputes to investigate |
| Refund rate by customer | Spot returns to look into |
| Account age vs. disputes | New accounts disputing quickly |
| Promo usage patterns | Multi-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 Type | What It Shows |
|---|---|
| Delivery confirmation | Delivered to the address on the order |
| Device fingerprint match | Same device as prior orders |
| Customer communication | They acknowledged receipt |
| Return history | Context. It doesn't prove this claim is false |
| CE 3.0 match | Qualifying 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:
- Block the customer: No more orders from this account
- Block the identifiers: Email, phone, device, address, on your own block list
- Document everything: For future representment
- Review policies: Close any loopholes exploited
- 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?
- Implement device fingerprinting: Track across accounts
- Set up velocity rules: Catch patterns
- Strengthen return policies: Close loopholes
Fighting chargebacks?
- Review compelling evidence: CE 3.0 requirements
- Check friendly fraud tactics: Specific strategies
- Collect proper evidence: Before you need it
Stopping promo abuse?
- Review promo abuse patterns: Detection tactics
- Implement account linking: Link by device, then check shared households
- Set redemption limits: Cap per customer
Related Topics
- Prevent Fraud: The fraud hub
- Friendly Fraud: Real purchases, disputed, in detail
- Refund Fraud: Return and refund exploitation
- Promo Abuse: Promotion and coupon fraud
- Device Fingerprinting: Tracking fraudsters across accounts
- Velocity Rules: Pattern detection
- Compelling Evidence: Fighting chargebacks
- Third-Party Fraud: Stolen card fraud (different problem)
- Risk Scoring: Combining fraud signals