Skip to main content

Fraud Classification

TL;DR
  • First party: the person is lying. Own identity, own details, false claim. Confusion and valid complaints aren't lies; this site keeps them out
  • Second party (this site's convention): they handed it over. Mule, family member, or someone talked into it
  • Third party: nobody gave them anything. It was taken
  • Synthetic: a fabricated person or entity. Real people's identifiers can be inside it, and those people can be victims
  • Your response differs: eligible 3DS payments for third party, evidence for friendly fraud, payout controls for second party
  • The industry doesn't agree on any of this. The main competing definitions are below, each beside its source

A dispute lands, or a vendor's report uses a fraud label you don't recognize. Here's how to tell which kind of fraud you're looking at, and what each one needs from you.

Quick Classification​

What You SeeLikely TypeYour Response
Customer disputes a purchase they really made, with no valid reasonFriendly FraudCollect evidence. On Visa, CE 3.0 may let earlier purchases answer it
Card used by someone who was never given accessThird-Party FraudEnable 3DS; liability can shift on eligible payments
Same device, many accountsFraud RingDevice fingerprinting, block infrastructure
Burst of small transactionsCard TestingVelocity rules, CAPTCHA
Good customer acting strangeAccount TakeoverAdd MFA (two different kinds of factor, not two steps of the same kind), and flag logins that don't match the customer's usual behavior
Excessive returns/refundsRefund FraudPolicy enforcement, tracking
Promo/coupon abusePromo AbuseDevice linking, limits
Fake account signupsAccount FraudEmail/phone verification
Mismatched identity infoFake IdentityIdentity verification

The Four Types, Defined​

TypeThe testIn one line
First partyIs the person lying?They're using their own identity, not hiding who they are, and lying about something
Second partyDid they hand it over?The real owner gave their details, card or account to someone else
Third partyWere they authorized?Somebody who was never given access is using it
SyntheticIs this a real person?A fabricated person or entity, assembled from identifying information, real, fake, or both

First party: the person is lying​

They aren't hiding who they are. Their name is their name, their address is their address. The lie is about something else.

Two shapes, and they're the same act:

  • Lying about facts. Inflating income on an application, misstating what a business does
  • Lying about an event. Saying they didn't make a purchase they made

That second one is the merchant-facing version, usually called friendly fraud. A customer who forgot a purchase, or has a fair complaint, hasn't lied. This site keeps confusion and valid disputes out of first party; some vendors group them in, which is one reason their numbers differ.

Not repaying isn't fraud

A customer who borrows and can't pay hasn't lied. That's credit risk, and it's a pricing problem rather than a fraud problem. A customer who lied to get the money committed fraud. The lie is the line. Experian's definition below, for one, requires an intent not to repay when the promise is made. Owing money you later can't pay doesn't meet it.

Second party: they handed it over​

Someone gave their identity, card, account or device to another person. The details are genuine because they really are genuine. The owner participated.

This handover test is this site's convention. It classifies the case; it doesn't settle who authorized a particular payment, or who bears the loss. Record those separately: who initiated the payment, what authority they had for that use, and whether deception or coercion was involved. Credentials phished and then used by someone else weren't an authorized payment just because they changed hands.

Why they did it varies enormously, and the reason doesn't change the classification:

SituationStill second party?
Paid to let their account move money (a money mule)Yes
Lent a card to a parent, sibling or partnerYes
Talked into it on the phone, or by a fake job adYes
Pressured or controlled by someone elseYes
An employee abusing internal accessNo. That's insider fraud, and it goes under first party
Classifying is not blaming

Second party covers people who were paid and people who were tricked. Same classification, completely different culpability. Say which one you're looking at, separately.

Somebody deceived by a phone call still handed their details over. That's second party. They're also a victim. Both are true.

Third party: nobody gave them anything​

The person using the card or identity was never given access to it. It was taken, not handed over. Stolen card data, a breached account, a hijacked login.

Under this site's convention, that's the difference from second party. Did the owner hand it over, or did somebody take it?

Synthetic: a fabricated person​

A fabricated person or entity, assembled from identifying information. The composite persona doesn't exist, but real people's identifiers can be inside it, and those people can be victims. Work out whose details were used instead of assuming nobody is affected. (Federal Reserve, 2019 review, pages 5 and 17.)

The Fed's 2019 paper names three ways they're built:

TermWhat it is
FabricationBuilt from wholly fictitious identifying data
ManipulationReal identifying data altered
CompilationReal and fictitious identifying data combined into a new identity

SentiLink's 2020 proposal cuts it differently, into first-party and third-party synthetics. That's SentiLink's cut, not the Fed's. (SentiLink, Defining Synthetic Fraud, 2020, pages 5 to 6.)

Worked example: "my family member used my card"​

This is an ambiguous case merchants see, and it lands in a different class depending on one fact. Filing all of it as friendly fraud hides that fact, and it changes what you should do.

What actually happenedClassWhat you do
Cardholder gave the card to a relative, then disputed the chargeFirst party, if the denial is knowingAnswer with your evidence, including who used the card if you can show it
Cardholder gave the card to a relative, and genuinely forgotConfusion, not fraud on these factsRefund or answer on cost, and fix your descriptor. Don't log it as fraud
Cardholder knowingly let a relative use it to move moneySecond partyTreat as mule risk, not a dispute
Relative took the card without askingThird partyA real unauthorized use. The cardholder is a victim

Amex names this on its own merchant material, describing charges made by "family or staff." Some of what merchants log as fraud is a second cardholder in the same house or business, and some of that isn't fraud at all.

The question to ask, and it's one question: did the cardholder hand the card over?


Does the Rest of the Industry Agree?​

Closer on first, third and synthetic. Not on second. Here's what the sources say.

Visa's rules use first-party fraud, in issuer customer validation (24 October 2026 edition, section 10.4.7.3). When someone says "the networks define it this way," ask which document.

Where the numbering comes from​

One way to see the confusion, as an analogy rather than a history: a normal transaction has two parties, you and your customer.

PartyWho that is
First partyyour customer
Second partyyou, the merchant
Third partyan outsider who was never in the transaction

Read that way, "second-party fraud" would mean fraud by the merchant. That's not how the sources below use it. Whether the numbering started here isn't documented in them; treat the table as an illustration, and the disagreements below as the evidence.

First party: two camps, one act​

Lenders describe the application. The Experian and DataVisor wording below is as reproduced in SentiLink's 2020 paper, page 11.

SourceWhat they say
Experian"an individual who makes a promise of future repayment in exchange for goods / services without the intent to repay"
TransUnion"misrepresenting one's personal information in order to receive a product or service to which they have no entitlement." Also calls it "credit muling"
Equifax"an individual intentionally misrepresents their identity and/or gives false information for financial or material gain"
Socure"the use of one's own identity to open an account and/or commit a dishonest act for personal or financial gain"
DataVisor"the fraudster is not misrepresenting who they are, but rather, they're being deceptive about their information, and their intentions"

Payments people describe the dispute.

SourceWhat they say
Ethoca (Mastercard)uses first-party fraud and friendly fraud as overlapping names for a customer disputing a genuine purchase
Mastercard"When cardholders dispute a genuine transaction, that's first-party misuse or 'friendly' fraud"
Signifyddefines it around a real identity used to defraud an online merchant, and separates deliberate deception from mistaken disputes

Those look like two definitions. They're the same test applied at two moments: own identity, false statement. Lying about your income and lying about a purchase are both lying. That's why we test for the lie instead of picking a camp.

It matters when you read a number. "First-party fraud is up 40%" tells you nothing on its own. Ask what it counts: loan applications, disputed charges, or both. Visa's commissioned research concedes it: "This abuse of the dispute system has many names, such as first-party fraud, friendly fraud, and dispute misuse. Regardless of what it is called..."

SentiLink has said it plainly in print. First: "First Party Fraud has differing definitions depending upon who or what company you ask." Then: "The definition of First Party Fraud is confusing and can be interpreted both as (1) credit risk or (2) fraud risk."

Second party: five different definitions​

Every source below describes something real. They disagree about how willing the person had to be.

How willing was the account holder?ExampleWho calls this second party
Paid volunteer. Knew, took a cutclassic money muleTransUnion, SEON, Persona, FraudNet
Helping someone. Knew, wasn't paidlending a card to a relativeLinkurious, Persona
Tricked. Handed details over believing a liephishing, fake job adThis site (see below)
Coerced. Under someone else's controltrafficking, an abusive relationshipAlloy
Not the account holder at allan employee abusing accessAU10TIX, NordVPN

Some of the wording, so you can see the gap:

SourceWhat they say
Personadescribes paid sharing and helping family, with both people as active participants
Alloydescribes one person controlling another to commit fraud
AU10TIXdescribes collusion between an insider and an external party
NordVPNdescribes a perpetrator with an existing relationship to the target, or an insider

Two of those point at opposite people. For TransUnion and Persona, the second party is the customer who handed their details over. For AU10TIX, it's the employee.

And "knowingly" is doing a lot of work. Definitions built on willing complicity drop the person tricked by a fake job ad and the person under someone else's control. They handed over the same details, and the money moves the same way. We keep them in, and treat classification and culpability as separate questions.

We take the first four rows and reject the fifth. Handing something over is one act, whatever the reason. It's also something you can observe. An employee abusing access never handed over anything of their own. Insider fraud already has a mature home: the ACFE (Association of Certified Fraud Examiners) covers it as occupational fraud.

Third party: the closest to agreement​

SourceWhat they say
Experiandescribes use without the owner's consent or knowledge
TransUnion"the person whose information is being used is unaware and has not given consent"
Ethoca (Mastercard)describes an unauthorized person using someone's card information
AU10TIXdescribes an external actor, with phishing among its examples

Unauthorized is the word that keeps recurring, and it's the test we use. Even here conventions differ: Alloy groups some authorized-push-payment scams under third party. This site's handover line is a choice, not a consensus.

Synthetic: defined, and filed by the Fed's model​

The Federal Reserve put 12 fraud experts in a room to settle it. They landed on this: "the use of a combination of personally identifiable information (PII) to fabricate a person or entity in order to commit a dishonest act for personal or financial gain." (Recommended definition, 2021, page 4.)

SentiLink: "fraudsters combine fictitious and/or real information to create new identities with the intent to defraud."

The definition itself doesn't put synthetic in a party bucket. The Fed's separate FraudClassifier model does classify payments, and it files Synthetic ID under "Authorized Party Acted Fraudulently," with a fabricated-account example.

Vendors file it differently too; Linkurious is among those folding it toward first party. This site keeps synthetic as its own category. That's our convention, not the Fed's, and it doesn't decide who bears a loss.

Some vendors aren't sorting by actor at all​

One reason two lists don't line up:

Everything above sorts by who did it. Some vendors sort by when it happened instead: at the application, at the transaction, or on the account afterwards.

An application-fraud bucket, "lying on the form," can hold three different actors at once:

Inside one application bucketWhere we put it
Stolen identityThird party
Synthetic identityIts own class
First-party fraudFirst party

So one of their classes contains three of ours. Neither list is wrong. They answer different questions, and a term that's a subtype in one is a top-level class in the other.

What to do with that. When a vendor's taxonomy doesn't match yours, check the axis before you argue about definitions. Ask: is this sorted by who, or by when? A lot of what looks like disagreement is one list sorted by actor and another sorted by stage, set side by side as though they measured the same thing.

When a vendor quotes you a number

Ask one question: does that figure count loan applications, disputed charges, or both?

LexisNexis reported first-party fraud as 36% of reported fraud in its Digital Identity Network's 2024 observations, across more than 104 billion platform transactions of many kinds: account creation, logins, payments and more. That's a different population from a chargeback-abuse figure. Compare definition, coverage, denominator and period before comparing percentages.


By Actor​

First-Party Fraud (Your Customer)​

The customer is real and uses their own identity, but abuses your policies.

SubtypeDescriptionDefense
Friendly FraudDisputes a purchase they really made, with no valid reasonEvidence collection, CE 3.0
Refund FraudExploits return policiesPolicy enforcement
Promo AbuseGames promotions/discountsDevice linking, limits
Insider fraudAn employee abuses their accessRole-based access, reviews

Chargeback outcome: Can be won with proper evidence

Second-Party Fraud (Your Customer, Working For Someone Else)​

The real owner handed over their details, card or account. The identity is genuine because it really is genuine. The money goes to somebody else. Merchants can meet this as a marketplace or payout problem rather than at checkout.

SubtypeDescriptionDefense
Money muleAccount exists to receive and forward fundsPayout pattern review, no-trade sellers
Family and friendsA relative uses the card with permissionAsk before treating it as fraud
Talked into itFake job ad, phone scam, romance scamTreat the holder as a victim
Account farmingAged accounts sold on for their historyDormant-then-active review

Chargeback outcome: can show up as account closure and payout risk rather than a card dispute

Watch the line here

Someone talked into handing over their details is second party, because they handed them over. They're also a victim. Classification and culpability are separate questions, and you should answer both.

Third-Party Fraud (Taken, Not Given)​

Somebody who was never given access is using the card or identity. It was taken, not handed over. If the owner handed it over, however they were persuaded, that's second party instead.

SubtypeDescriptionDefense
Stolen CardUses compromised card3D Secure, AVS/CVV
Card TestingValidates stolen cardsVelocity rules, CAPTCHA
Account TakeoverHijacks customer accountAdd MFA (two different kinds of factor, not two steps of the same kind), and flag logins that don't match the customer's usual behavior

Chargeback outcome: Hard to win without liability shift on an eligible 3DS payment

Fake Identity Fraud​

Fraudster creates fabricated or mixed identity information.

SubtypeDescriptionDefense
Fake IdentityFabricated personaIdentity verification
Account FraudFake account signupsEmail/phone verification

Chargeback outcome: depends on the network condition. An identity mismatch alone doesn't win it; prove the facts that condition requires

Organized Fraud​

This one is a different question. The classes above ask who the actor was. This asks how many. Several accounts are a pattern to investigate, not proof of a ring: a ring is an organized group, and one person can run many accounts.

SubtypeDescriptionDefense
Fraud RingsMulti-account attacksDevice fingerprinting, consortium data
TriangulationResale scheme using a fake storefrontShipping address analysis

Chargeback outcome: Document network evidence for representment


Classification Decision Tree​

Treat this as a set of investigative hypotheses. Actor, identity construction, compromise mechanism and coordination are separate questions. They can overlap, and "unknown" is an allowed answer. A synthetic account can be taken over; one actor can run several accounts.


Response by Classification​

Fraud TypeImmediate ActionPreventionChargeback Strategy
Friendly FraudCollect delivery proofClear descriptors, communicationThe evidence your network condition allows; CE 3.0 where it applies
Second-PartyReview payouts, close if confirmedPayout change controlsAnswer inside the actual dispute, if one is filed
Third-PartyCancel if caught. If it's already disputed, answer inside that dispute instead of refunding separatelyEnable 3DSEligible 3DS liability shift, where its conditions are met
Card TestingBlock IP/deviceVelocity limits, CAPTCHASuccessful test payments can be disputed; answer those cases
ATOLock account, notify customerMFA, device recognitionCompromise alone isn't a defense; use the defense your network condition permits
Refund FraudFlag accountEnforce policiesDocument abuse pattern
Promo AbuseRevoke benefitsDevice linkingHandled on the account, unless a disputed charge is involved
Fraud RingBlock infrastructureDevice fingerprintingDocument the pattern the network condition asks for

Financial Trouble Versus Deliberate Abuse​

A share of what gets counted as first-party fraud isn't fraud. It's people who can't pay.

  • LexisNexis runs a whole category called "distressed consumers," separate from fraud
  • Visa's commissioned research found consumer motivations split roughly evenly between wanting to avoid payment and facing economic hardship (2,276 surveyed consumers, Q2 2024, in the markets covered)
  • LexisNexis again: first-party fraud is "exacerbated by periods of inflation and the rising cost of living"

One more finding, before you build rules around age. The behavior is "not limited to younger demographics."

That matters for policy, but how a customer responds to a payment plan doesn't prove what they intended. Weigh authority, whether the claim is valid, account history, and what each remedy costs. Keep hardship, mistakes and deliberate deception as separate hypotheses until the facts separate them.


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