Screening that never
leaks a name
Every document verification can screen the extracted identity against global sanctions and politically-exposed-person lists — on our own EU infrastructure, with a human deciding every match. No second vendor, no second integration, no name ever sent to a screening bureau.
One verification, one more answer
Screening rides the document verification you already run — nothing extra for your user, one extra field for your backend.
Identity is extracted
During a document verification, the name, date of birth, and nationality are read from the presented ID — data you already needed for the age or identity check. Screening adds zero friction for the user.
Matched inside our infrastructure
The extracted identity is matched against the consolidated OpenSanctions dataset on our own EU servers. No third-party screening vendor is called — the name never leaves our infrastructure.
Humans decide, never a name collision
A strong match routes the session to your review queue with reason aml_match and full match context for your reviewer. Nobody is auto-rejected because they share a name with a sanctioned person.
You read one field
Every verification result carries a checks.aml entry — the same {performed, passed} shape as every other check, in the API response and the webhook alike. One field, no second integration.
The data behind a match
Powered by the consolidated OpenSanctions dataset — the broadest open aggregation of official watchlists in existence, self-hosted on our servers.
400+ data sources, consolidated
OFAC SDN (US), the EU consolidated list, UN Security Council, UK OFSI, Swiss SECO, Interpol notices, World Bank debarment and hundreds more — 443 sources at the time of writing, merged and de-duplicated into one dataset by OpenSanctions.
Politically exposed persons
Heads of state, ministers, legislators and senior officials worldwide — the PEP layer regulators expect licensed operators to screen against.
Multilingual name matching
Entries carry names in their original scripts and transliterations — Cyrillic, Arabic, Chinese and more — so a match is not defeated by a spelling variant on the document.
Refreshed nightly
The dataset is re-downloaded and re-indexed every night. New designations are live in screening within a day of publication, automatically.
Why self-hosted matters
Most platforms bolt screening on by sending your users' names to a third-party bureau — one more processor in your DPA, one more place a name can leak. We took the other path: the matching engine and the full dataset run inside our own EU infrastructure. The screened name never crosses a network boundary we don't control, and your sub-processor list stays exactly as short as it was yesterday.
Honest scope, in one sentence: Xident provides sanctions and PEP screening as a control inside your compliance program — we flag and route, your team decides, and your obligations under AML law remain your own.
See it in a sandbox session
The free sandbox runs the same screening path as production. Verify a
document, read checks.aml, done.