Prompt
Do I need to check for synthetic identities during onboarding?
Latest observation
Nov 18, 2026
OpenAI APIWeb search: off
Yes — if you’re onboarding customers, you should check for synthetic identity risk as part of your identity/fraud controls.
Why it matters:
- Synthetic identities are often created from a mix of real and fake data.
- They can pass basic KYC checks, then be used for fraud, account abuse, or credit loss.
- They’re especially common in digital onboarding where verification relies heavily on documents or static identity data.
What to do:
- Verify identity across multiple signals: document verification, liveness/selfie checks, device intelligence, email/phone risk, address consistency, and behavioral signals.
- Screen for anomalies: reused phone numbers/emails, mismatched SSN/DOB/name patterns, thin or inconsistent credit/file history, velocity across applications, and device/IP reuse.
- Use risk-based step-up checks: ask for additional verification when risk is elevated.
- Monitor after onboarding: synthetic identities may look normal initially and only reveal themselves through transaction behavior.
If you’re in a regulated environment, this should be part of your CIP/KYC and fraud prevention program. If you want, I can give you a practical onboarding checklist or a synthetic identity detection control set tailored to your business.