The Outlier Lab

First-Party Fraud

Hub for transaction fraud committed by the real account holder (false disputes, kiting, bust-outs, refund and receipt abuse), and how to separate it from third-party fraud and credit loss.

What it is

First-party fraud (1PF) is defined by who commits it; the method can be anything. That makes it a classification problem as much as a detection problem. The same chargeback, ACH return, refund claim or charge-off can be third-party fraud, first-party fraud, a service failure, or a genuine credit loss, and each needs a different response.

To classify a case, ask whether the account holder authorized (or benefited from) the transaction and then misrepresented something to get value back or avoid paying. If yes, it's first-party.

Diagram: Loss event: chargeback, return, refund, default, Did the account holder authorize or benefit?, Third-party fraud (ATO, stolen identity, stolen card), Was there misrepresentation or intent not to pay?, Service failure, dispute error, or genuine credit loss, First-party fraud, Was a deceived customer moving their own money to a scammer?, Victim-authorized (scam), not 1PF, Classify by mechanism below

Two boundaries cause the most confusion:

  • 1PF vs credit loss. A customer who couldn't pay is a credit loss; one who never intended to pay is fraud. The Federal Reserve's synthetic identity white paper notes institutions often book fraud-driven defaults as credit losses, which understates fraud (Federal Reserve, 2019). Synthetic identities sit awkwardly here, since there is no real victim and no real customer either. Most programs treat them as their own bucket.
  • 1PF vs scam victim. A customer who sends money under deception is a victim (Authorized Push Payment (APP) Scams). A customer who sends money and then falsely claims they were scammed or that the send was unauthorized is committing 1PF. Investigations must distinguish the two; getting it wrong either re-victimizes a real victim or rewards abuse.

See Loss Taxonomy and Attribution for a full classification scheme and Frameworks and Taxonomies for industry models such as the Federal Reserve's FraudClassifier, which starts by asking whether an authorized party initiated the payment (FedPayments Improvement).

How it works

1PF follows a common shape regardless of rail:

  1. Gain a reversible or trust-based value position: a purchase that can be disputed, a deposit made available before it settles, a refund policy, a reward that pays before it vests, a credit line.
  2. Extract the value: use the goods, withdraw the money, redeem the reward.
  3. Reverse or default: dispute, return, claim non-receipt, let the deposit bounce, stop paying.
  4. Repeat or scale across merchants, platforms, household members, or a crowd following the same playbook.

The common enabler is an asymmetry between how fast a platform gives value and how fast it learns the truth. Each mechanism in the table below exploits that asymmetry on a specific rail.

The first-party family

MechanismRail and reversalWhere it bites hardestNote
False card disputesCard chargebacksEcommerce, digital goods, card-funded walletsChargeback and Friendly Fraud
Kiting and instant funding abuseACH returns, check returns, card chargebacksBrokerages, neobanks, P2PInstant Funding Abuse (Kiting)
False unauthorized ACH claimsACH unauthorized returns (up to ~60 days)Brokerages, neobanksACH Funding Fraud
Duplicate and bad check depositsCheck returns, warranty claimsNeobanks, banksCheck and Mobile Deposit Fraud
Bust-outCredit, overdraft, instant limitsNeobanks, card issuers, BNPL, brokeragesBust-Out Fraud
Refund and return abuseMerchant refund policyRetail, marketplacesRefund and Return Fraud
INR / SNAD claim abuseMarketplace buyer protectionMarketplacesBuyer Protection Claim Abuse (INR and SNAD)
Receipt and offer abuseRewards payoutCashback and coupon appsReceipt Fraud (Cashback), Card-Linked Offer Abuse
Bonus and promo abusePromo eligibilityFintech, rewards, retailSign-Up Bonus Abuse, Promo Code Abuse, Referral Abuse
Multi-accountingPer-account limits and offersRewards, fintech, marketplacesMulti-Accounting
Logic exploits shared virallyProduct rules working as designed, or bugsAnyBusiness Logic Exploitation

Transaction footprint

StageWhat you see in the dataDecision point
AccountReal identity, often tenured; device and contact data consistent with historyIdentity checks won't catch 1PF, so limit exposure as well as verifying identity
Value positionDeposit, purchase, claim or bonus at the edge of what policy allowsExposure limits and availability rules
ExtractionFast use of value: withdrawal, consumption, redemptionExit gating on unaged value
ReversalDispute or claim from the same device and account as prior good activity; contact with support beforehand (or none); narrative inconsistenciesEvidence-based response: representment, claim denial, recovery
RepeatSame customer, household, payment instrument or device; similar narratives across unrelated accountsEnforcement: limits, deny lists, offboarding; ring investigation

Where it shows up

  • Retail and Ecommerce: friendly-fraud chargebacks and return abuse dominate; Mastercard cites research that about 75% of fraud at online businesses is first-party (Mastercard, 2023).
  • Online Marketplaces: buyers pick between card disputes and platform claims; sellers bust out.
  • Cashback, Coupons and Rewards: the largest share of loss at many rewards programs is first-party: real users submitting borrowed or edited receipts, buy-claim-return, or multiple accounts. The reversal is often the merchant's reversal of commission after a return, leaving the platform holding paid-out cashback.
  • Neobanks and Consumer Fintech: instant deposits, overdraft and early pay create provisional exposure; false unauthorized claims on ACH and P2P add reversal risk.
  • Brokerage and Investing: instant buying power and unauthorized ACH claims are the main paths; market moves turn a deposit failure into a larger loss.
  • Payments and P2P: false "unauthorized" claims on P2P sends, and card-funded top-ups that are later disputed.

Impact

  • Share of losses: for online businesses, network and industry sources put first-party fraud at the majority of fraud, with commentary commonly estimating 60–80% of chargebacks are friendly fraud (Mastercard, 2023; PaymentsJournal). Definitions vary; treat as directional.
  • Understated in reporting: booked as credit loss, operational loss, customer service cost or "returns" rather than fraud (Federal Reserve, 2019).
  • Label contamination: 1PF chargebacks labeled as third-party fraud train models to decline good-looking customers. See Fraud Labeling and Feedback Loops.
  • Network and partner exposure: 1PF disputes count toward card network monitoring ratios (Rapyd); first-party ACH unauthorized returns count toward Nacha's 0.5% unauthorized return threshold (Nacha).
  • Customer relationship cost: many first-party cases are good customers behaving badly once. Heavy-handed enforcement costs lifetime value, while lenient enforcement teaches customers that abuse pays.

Red flags

Prevention and detection at a glance

LayerControl or signalWhat it does here
PreventVelocity and Exposure Limits, Funds Availability HoldsSize trust-based exposure to history; age value before it can leave
PreventClaims and Returns Policy Controls, Reward Vesting and ClawbackPolicy design that removes the asymmetry
PreventPromotion Design GuardrailsEligibility and payout timing that resist abuse
DetectCustomer-level abuse scoringUses Dispute and Return History and cross-product behavior
DetectGraph AnalyticsFinds households, rings and viral cohorts
RespondNetwork evidence programsVisa CE 3.0, Mastercard First-Party Trust; see Chargeback and Friendly Fraud
RespondCase Management Systems, Negative Lists and Deny ListsEvidence, recovery, restriction and offboarding
RespondConsortium and Data SharingShares repeat-abuser signals across institutions

Emerging variants and adversary adaptation

  • Viral abuse. Social media turns a single exploitable rule into a crowd event within days, carried out by real customers rather than rings. The provisional-funds trend in 2024 is the template (Case Study - Chase Infinite Money Glitch (2024)). Add social listening to Threat Intelligence and Horizon Scanning.
  • Abuse-as-a-service. Coached disputes, refund services and receipt-generation services professionalize first-party abuse: the customer is real but follows an outsourced playbook. Graph and narrative analysis across cases is the counter.
  • Networks are rebalancing toward merchants. Visa CE 3.0 (April 2023) and Mastercard First-Party Trust (U.S. rollout October 2024) give merchants data-driven ways to rebut false fraud claims (Adyen; Chargeflow). Expect abusers to shift to dispute types and channels those programs don't cover.
  • ACH rules now name fraud monitoring explicitly. Nacha's 2026 rules require risk-based processes to identify unauthorized and False Pretenses entries, and treat a thorough return-rate monitoring program as meeting the minimum for debits (Nacha Phase 1). That makes first-party ACH abuse partly a compliance issue.
  • Scam-claim abuse. As reimbursement for scam victims expands (see Case Study - UK APP Scam Reimbursement Rules (2024)), some first parties will falsely claim to be scam victims. Investigation standards must separate the two without penalizing real victims; see Investigation Standards.

Real-world examples

Sources and further reading