First party fraud is often read as friendly fraud on a card, a customer disputing a purchase they made. That is one of its types. The identity is real and the intent is false, so know your customer checks pass. Nacha, which runs the US ACH rules, describes the bank's side in a March 2026 post: the institution verifies the customer at onboarding, then receives an R10 return on the funding debit "after there is no longer an account balance left". Like any fraud, it is deception for gain. What sets it apart is who acts, and under whose name.
What is first party fraud, and how is it different from second and third party fraud?
| Who acts | Whose identity | What identity checks show | Example | |
|---|---|---|---|---|
| First party | The customer | Their own, real | Pass | Customer calls their own debit unauthorized |
| Second party | Someone the customer let in | The customer's, with consent | Pass, on the customer's credentials | Relative uses a card the customer handed over |
| Third party | A stranger | Stolen or invented | Fail, if the checks work | Loan opened in a stolen name |
First, second and third party fraud (as of November 2026).
The test is identity against intent. In third party fraud the identity is false, so identity verification is the control. In first party fraud, also written 1st party fraud, the identity is true and the intent is false, and the question moves from who the customer is to what they meant.
Visa's 2026 fraud report calls the card form first party misuse. A mistaken dispute is an error; intent is what turns a dispute into fraud.
Second party fraud sits in between. Under Regulation E, a transfer by a person the consumer gave the access device to does not count as unauthorized until the consumer tells the bank that transfers by that person are no longer authorized. Third party fraud runs on a stolen or invented identity.
What types of first party fraud do banks, lenders and merchants see?
Every type follows one path. The customer takes value first, then withdraws consent or payment through a dispute, a return, a claim or a default; types differ in where the money leaves and which record shows the intent. Take a subscriber who uses a service for a month and then tells the bank the monthly debit was never authorized. That is Nacha's false claim variant, and the signed authorization answers it, because the identity file only shows that the customer is real.
| Type | Where it shows up | What the customer does | First signal | Record that proves intent | Who loses |
|---|---|---|---|---|---|
| Card dispute abuse | Card payments, ecommerce | Disputes a purchase they made | Repeat disputes on delivered goods | Delivery proof, device and login match | Merchant |
| False ACH unauthorized claim | Bank accounts, bill pay | Calls an authorized debit unauthorized (R10) | Debit from a known originator | Proof of authorization, payment history | Originator |
| Account opening funding fraud | New bank and wallet accounts | Funds by debit, drains, then claims R10 | Money out within days | Funding debit, withdrawal trail | Bank that opened the account |
| Bust out | Cards, credit lines | Builds a clean record, then maxes out | Spend jumps to the limit | Spend and payment history | Issuer or lender |
| Loan stacking | Online lending | Takes several loans at once | Applications close together | Application times, device | Each lender |
| Never pay | Loans, BNPL, phone contracts | Borrows with no intent to repay | First payment missed | Application statements | Lender or provider |
| Refund and return abuse | Retail, ecommerce | Returns used or other goods | High return rate | Return logs, item checks | Merchant |
| False APP scam claim (UK) | Push payments | Claims to be a scam victim | Payee linked to the claimant | Payment and contact history | Sending and receiving firms, if reimbursed |
Types of first party fraud and the record that proves intent.
Size figures count different things. LexisNexis Risk Solutions' Cybercrime Report 2026 release found first party fraud the leading source of fraud reported in its network in 2025: almost two in five worldwide, 51.7 percent in EMEA and under 10 percent in Latin America. Its first party fraud page puts the same report's share at 43.6 percent once chargeback fraud is added.
Cifas recorded over 106,000 misuse of facility cases in 2025 (Fraudscape 2026). That category also holds mule accounts. Nacha is still asking: its October 2026 call wants to know what share of unauthorized returns were in fact authorized.
What is bust out fraud?
Bust out fraud runs in two acts. The customer builds a clean record, pays on time for months and earns higher limits, then draws every line to the limit at once and stops paying. FinCEN's identity fraud trend analysis of January 2024 describes bust out schemes on credit card accounts opened "with false information"; when that information is invented, the case is synthetic identity fraud. The first party kind uses the customer's own name, so no identity check fails and the months of normal use become the evidence.
What does first party fraud look like in banking?
Nacha's account opening scenario involves two banks. A customer opens an account at bank A, funds it with an ACH debit pulled from their own account at bank B, drains the new account and then tells bank B the debit was unauthorized. Bank B returns it as R10, and bank A, which checked the customer properly, is left with the empty account. In every scenario of Nacha's request for information, a person "falsely claims" that an authorized debit is unauthorized.
The work group's presentation names two more variants: a false claim on a bill payment, subscription, donation or purchase, and the funding of an existing account or a digital wallet. In all three the customer is who they say they are, so the checks that catch application fraud at account opening pass.
What red flags on an account or a claim suggest first party fraud?
- An unauthorized return rate above the network's. Nacha puts the ACH average at 0.05 percent and tells receiving banks to search for reasons at a rate such as 0.1 percent, double the average.
- Several R10 claims or card disputes on one account. One claim can be honest; a run of them looks like a habit.
- A disputed debit from an originator the customer has paid before. An established or recurring relationship weakens the claim.
- A new account funded from outside and emptied within days, Nacha's opening scenario and also the shape of a mule account.
- Spend that jumps to the limit after months of on time payments, the turn in a bust out.
- Several credit applications in a short window or from one device. Stacking needs speed.
- Delivery or login evidence on an order the customer disputes.
- A first payment missed on a new loan or BNPL plan, where never pay shows first.
No single flag proves intent; together they decide which claims a reviewer reads first. In complead, formerly Sanction Scanner, every fraud prevention decision comes back as approve, decline, review or step up, and every outcome carries its reason.
How do you stop first party fraud without blocking good customers?
Picture an illustrative BNPL provider. A customer's first installment fails on a large order, and a week later the customer says the order was never placed. If your file holds the checkout device and login, the delivery confirmation and the signed plan, you answer the claim with evidence. Without them, it is one word against another.
So the first control is the record, kept at onboarding and at each authorization. complead's device and behavior analysis spots a single device used for multiple accounts, maps onboarding clusters from one device and shows the drivers behind every score. For a name the firm has not seen, the Consortium KB shows what other institutions already learned about that name or a pattern, without exposing the firm's own customers.
A reviewer decides, and each confirmed case becomes a label for a model trained on the firm's own cases.
For bank claims, Nacha suggests three checks: has the originator debited this customer before, does the name in the entry match the account, and did open banking with the bank's positive response verify it. Its October request adds ideas for comment, such as asking the originating bank for proof of authorization.
Timing comes from Regulation E. A bank must, as a rule, determine within 10 business days whether an error occurred; to take up to 45 days instead, it must, among other steps, credit the account provisionally within those 10. Nacha's proposed Section 3.11 text says prompt recredit does not have to come before that provisional credit point. Some banks read "promptly" as same day. That may rule out a review.
Nacha's limit holds for every control: the search for first party fraud "shouldn't be a deterrent" to a consumer with a legitimate claim. As in all fraud detection and prevention, the friction goes where the flags point.
Is first party fraud a crime, and when is it reported?
It can be, in both the US and the UK. Under Regulation E, a transfer initiated "with fraudulent intent by the consumer or any person acting in concert with the consumer" is not unauthorized, so the unauthorized transfer protections do not apply. Nacha's rules treat a debit the receiver initiated with fraudulent intent the same way, and since an operations bulletin of March 2023 its sample written statement of unauthorized debit warns customers of potential criminal liability for false claims.
Federal law can reach it. Bank fraud and a false statement on a loan or credit application to an insured bank or another lender the statute names each carry a maximum of $1,000,000 in fines, 30 years in prison or both.
Reporting runs through the suspicious activity report. FinCEN's bank rule sets its line at $5,000, counted on one transaction or in aggregate, once one of its listed suspicions applies.
For national banks, the OCC's own rule sets $5,000 "where a suspect can be identified". In first party fraud the suspect is the customer.
In England, Wales and Northern Ireland, section 2 of the Fraud Act 2006 counts a representation about the speaker's own state of mind, so a dishonest promise to repay can be fraud by false representation, with up to 10 years on indictment.
The PSR's APP reimbursement rules, in force since 7 October 2024, leave it out: policy statement PS23/3 says the requirement is not meant "to reimburse customers who have been complicit in fraud".
What happened on first party fraud in 2026?
- 20 January. Nacha put the network's average unauthorized debit return rate at 0.05 percent and told receiving banks well above it to search for the reasons.
- 26 March. LexisNexis Risk Solutions named first party fraud the leading source of reported fraud for the second year running.
- 8 October. Nacha opened a request for information and comment: three scenarios and the Section 3.11 proposal, responses due 11 December 2026, proposed effective date 18 June 2027.
- 24 October. In the Visa Core Rules of that date, the two earlier transactions behind Compelling Evidence 3.0 may come from one or more merchants (p. 709).
What is left to decide is which record each product line keeps before a customer can dispute, return or default: the device, the login, the delivery, the authorization or the funding source. In a post of 5 November 2026, Nacha asked originators the same question: what information could tell a legitimate dispute from first party fraud.