Prompt
sanctions screening and identity verification
Latest observation
Oct 29, 2026
OpenAI APIWeb search: off
Sanctions screening and identity verification are related but distinct compliance processes:
1) Sanctions screening
Checks a person or entity against official restricted-party lists to ensure you’re not doing business with someone prohibited or restricted by law.
- Purpose: detect matches to sanctions lists
- Common sources: OFAC, UN, EU, UK HMT, other national/regional lists
- What it looks for: names, aliases, DOB, addresses, nationality, company names, beneficial owners
- Outcome: clear, possible match, or confirmed match requiring review/escalation
2) Identity verification
Confirms that someone is who they claim to be.
- Purpose: validate identity
- Methods: government ID checks, biometric checks, document authenticity, address verification, liveness detection, database checks
- Outcome: verified, failed, or needs manual review
Key difference
- Sanctions screening asks: “Is this person/entity prohibited or restricted?”
- Identity verification asks: “Is this person/entity real and genuine?”
How they work together
In onboarding or KYC/AML workflows, organizations often:
- Collect identity information
- Verify the identity
- Screen the verified identity against sanctions and watchlists
- Escalate alerts for manual review if needed
Example
A customer submits a passport and selfie for onboarding:
- Identity verification confirms the passport is valid and the selfie matches
- Sanctions screening checks whether the customer’s name matches any restricted-party list
If you want, I can also provide:
- a comparison table
- a sample workflow
- or a regulatory/KYC context explanation