Topic starter
24/06/2026 11:33 pm
TL;DR: Synthetic identity fraud combines stolen personal data with fabricated details, fake IDs and controlled phone numbers to bypass onboarding checks, then uses fraudulent accounts for credit, purchases and laundering, according to Transmit Security. Legacy validation alone is not enough because confidence now depends on layered proofing, data validation and decisioning.
Editorial analysis by NHI Mgmt Group, based on content published by Transmit Security: “How Synthetic Identities Circumvent Security and What’s Needed to Secure Onboarding”.
Key questions
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 fake identities bypass legacy validation so easily?
A: Legacy validation often checks whether individual data points look valid, not whether they belong to one real person.
Q: What are the signs that a customer onboarding process is failing under fraud or compliance pressure?
A: Common signs include long approval cycles, repeated manual escalations, inconsistent outcomes across similar applicants, and weak fraud detection at the point of entry.
Practitioner guidance
- Build layered onboarding assurance Use identity proofing, data validation and risk scoring together so one weak signal cannot authorise a new account on its own.
- Escalate only when signals conflict Let passive validation handle low-risk applicants, then trigger document and selfie proofing when data sources disagree or risk exceeds threshold.
- Reconcile inconsistent data sources Create rules that resolve mismatches across name, address, phone and device data before an application is approved or manually reviewed.
Bottom line: Synthetic identity fraud exploits the gap between what looks valid and what is actually real.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 8:30 am
Legacy onboarding controls fail when truth is fragmented across multiple signals: Synthetic identity fraud succeeds because no single field, document or callback proves legitimacy on its own. A real name and date of birth can coexist with a fake address, controlled phone number and forged ID, which makes the applicant look plausible to weak validation. The governance lesson is that onboarding cannot treat identity as a static attribute check. Practitioners need a confidence model that understands cross-signal consistency, not isolated correctness.
A question worth separating out:
Q: When should organisations require document proofing instead of passive validation?
A: Require document proofing when the business risk, regulatory expectation or transaction profile demands stronger assurance than background validation alone can provide. High-value accounts, regulated industries and accounts with conflicting data signals usually need a stepped-up flow. The key is to tie the proofing requirement to risk, not to apply it universally.
👉 Read our full editorial: Synthetic identity fraud exposes the limits of legacy onboarding controls