TL;DR: Synthetic identity fraud is accelerating in UK financial services because fraudsters can combine real and fabricated data to pass lightweight KYC, build credit histories, and then bust out, according to Sift and Cifas. The control problem is not only detection accuracy but governance across onboarding, data sharing, and manual review thresholds.
NHIMG editorial — based on content published by Sift: Synthetic Identity Fraud: Why It’s the Fastest-Growing Financial Crime
Questions worth separating out
Q: How should security teams reduce synthetic identity fraud in customer onboarding?
A: Security teams should combine document proofing, data validation, device intelligence and reputation checks in a single onboarding policy.
Q: Why do synthetic identities make modern KYC harder?
A: Synthetic identities are harder because they can pass individual checks while still being fake in aggregate.
Q: What do teams get wrong about synthetic identity detection?
A: They often assume a single signal will identify the fraud case.
Practitioner guidance
- Tighten onboarding escalation thresholds Require step-up review when an application combines a real identifier with weak supporting evidence, device reuse, or inconsistent identity attributes.
- Join fraud consortium workflows Feed confirmed synthetic markers into shared fraud intelligence schemes and use consortium matches to halt repeat applications across lenders, retailers, and fintech channels.
- Correlate device and identity signals Link device fingerprinting, IP reputation, address reuse, and application velocity so analysts can detect clusters instead of isolated applications.
What's in the full article
Sift's full article covers the operational detail this post intentionally leaves for the source:
- Examples of UK onboarding signals that most often let synthetic profiles through before account approval
- Specific fraud consortium and shared-database workflows used to cross-check applicants against known markers
- Operational guidance on velocity rules, pattern triggers, and manual review queues for high-risk applications
- Regulatory context on FCA expectations, SAR filing, and how firms are being reviewed for synthetic fraud controls
👉 Read Sift's analysis of synthetic identity fraud in UK onboarding →
Synthetic identity fraud in onboarding: what identity teams miss?
Explore further
Synthetic identity fraud is a verification governance problem before it is a fraud analytics problem. The article shows that the core weakness is not simply missed anomalies, but onboarding models that assume each identity record belongs to a real, traceable person. In practice, that assumption fails when fabricated identities are assembled from plausible fragments and allowed to age into trusted profiles. Identity teams should treat coherence across signals as the control objective, not field-level completeness alone.
A question worth separating out:
Q: Who is accountable when synthetic identity fraud inflates onboarding growth?
A: Accountability should sit across identity verification, fraud operations, and product growth leadership because the harm is both security-related and financial. If synthetic users consume biometric spend, manual review time, or incentives, the issue is not only fraud prevention. It is also governance of the onboarding workflow and the metrics used to judge success.
👉 Read our full editorial: Synthetic identity fraud is outpacing UK onboarding controls