Fraud committed by the account holder themselves, using their real identity to obtain credit, goods, or services with no intention of repayment or return. Unlike third-party fraud — where a criminal impersonates a victim — first-party fraud is perpetrated by individuals who are genuinely who they claim to be. Common forms include: bust-out fraud (building credit lines then deliberately defaulting), friendly chargebacks (disputing legitimate purchases after receiving goods), and false income or asset declarations on loan applications. Because the identity itself is real and verified, first-party fraud does not trigger standard identity verification alerts. Detection depends on behavioral and transactional signals, cross-institution data sharing, and historical account patterns rather than document verification anomalies. The synthetic identity fraud variant occupies a grey zone: a real Social Security number paired with fabricated identity elements blurs attribution between first- and third-party fraud.
First-party fraud is structurally harder to detect than third-party fraud because the perpetrator is a legitimate account holder with genuine access — their behavior mimics real usage until the moment of default or dispute. Traditional fraud models trained on third-party patterns (stolen credentials, account takeover) perform poorly here because there is no identity mismatch to flag. Detection requires a different signal set: account history, application velocity, cross-institution consortium data, and behavioral analytics over time. Since document verification confirms the identity is genuine, the detection burden shifts to transactional behavior, application inconsistencies, and shared industry intelligence. This distinction is critical for practitioners evaluating identity verification vendors: a strong document verification capability does not reduce first-party fraud risk — that requires behavioral analytics and data consortium access.
When First-Party Fraud appears in a vendor claim, control description, policy, or assessment, record the exact meaning being used and the boundary it covers. Ask what is measured, which systems and users are in scope, what evidence supports the claim, how exceptions are handled, and when the evidence was last reviewed. Similar labels can describe different implementations, so a term match alone is not proof that a requirement is met.
Do not assume that two policies, standards, or products use First-Party Fraud in exactly the same way. A label may describe an objective, a technical mechanism, an operating process, a measurement, or a commercial feature. Check the surrounding definition and avoid expanding a narrow statement into a broader assurance claim.
For a durable review, note the authoritative source, publication or version date, applicable system boundary, and any thresholds or exclusions. If the meaning is disputed or changes over time, preserve both the original wording and the interpretation used for the decision. That makes later reassessment possible without treating this glossary entry as a substitute for the governing source.
Category: fraud prevention. This entry is part of the Identity Technologist Glossary, a practitioner reference for identity verification, KYC/AML, biometrics, fraud prevention, authentication, security, and compliance terminology.
Last reviewed: 2026-06-15