EU identity verification and AML screening, one integration.
One API for EU digital identity verification, sanctions and PEP screening, and audit-ready AML decisions. Built for solicitors, accountants, fintechs, and AML-obliged firms who need this to hold up under a regulator's or a pentester's scrutiny, not just a demo.
curl -X POST https://compliance.nexiel.io/v1/screen \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 4b9e6e2a-df1a-4c3a-9d2a" \
-d '{"name": "Jane Doe", "dob": "1990-01-01", "nationality": "IE"}'{
"classification": "CLEAR",
"candidates": [],
"meta": {
"mode": "sandbox",
"humanReviewRequired": false,
"engineVersion": "0.1.0-provisional",
"gatesHash": "sha256:8f2c…"
}
}* Applies to Nexiel Verify's end-user identity flows (EUDI wallet). Nexiel Screen's KYB customer due-diligence records are retained for the statutory period EU AML law requires. See data handling.
Six capabilities, one shared compliance core
Every capability runs on the same identity verification, matching engine, and audit trail, callable on its own or combined into one integration.
Verify an EU identity through the EU Digital Identity Wallet, requesting only the claims a check needs.
Nexiel ScreenScreen a name against sanctions and PEP lists on its own, no identity verification required.
Nexiel AgeProve someone is old enough to buy, without ever collecting their name or date of birth.
PreviewNexiel CredentialsIssue verifiable degree, module, and enrolment credentials straight into a student's EUDI wallet, signed with your institution's own key.
ViDA e-invoicing (EN 16931 + Peppol) for the EU's cross-border mandate. Second-phase product, on our public roadmap.
The same identity and AML core, extended with blockchain wallet risk scoring and Travel Rule compliance. Second-phase product, on our public roadmap.
The EU is also building a separate EU Business Wallet for organizational identity, distinct from the personal EUDI wallet used above. Nexiel is tracking it and has not built support for it yet.
Built to survive an audit, not just a demo
The mechanics behind every decision: a self-hosted matching engine, mandatory human review, and an audit trail built to hold up under a regulator's questions.
Exact match, full-text search, fuzzy (Levenshtein) and phonetic (Double Metaphone) matching, ensemble-scored against sanctions and PEP data spanning 34 government and multilateral sources: EU FISMA, OFAC SDN, the UN Security Council consolidated list, HMT UK, and PEP rosters across 21 EU member states among them. A fifth, AI-similarity layer is validating in shadow mode before it's trusted with a live decision.
Every screen resolves to one of three tiers: Clear, Possible match, or Confirmed match. A possible match always routes to a human and is never auto-cleared. This is the EU AI Act's human-in-the-loop requirement, enforced automatically, not left to a policy document.
Every decision's audit row pins the exact engine version, list snapshot, and scoring weights in force at the time, so a regulator asking what logic produced a match months ago gets an exact, re-derivable answer.
Compliance roadmap: Evidence collection is underway, mapped to Annex A controls, on the way to ISO 27001 and eIDAS 2.0.
"A regulator asking what logic ran for this case six months ago should get an exact answer, not a shrug."
Built for the people who carry the risk
Three groups rely on Nexiel to hold up when a regulator, a bank, or an employer asks how a decision was made.
Solicitors, accountants, and fintechs get a sanctions and PEP answer on one call, plus an evidence pack ready to hand to a regulator.
Institutions issue verifiable degree, module, and enrolment credentials straight into a student's EUDI wallet, signed with their own key.
Video platforms, social apps, and marketplaces confirm a user is old enough to buy, without ever learning their name or date of birth.
Integration measured in lines, not weeks
Every legacy AML vendor's sales process starts with a demo call and ends weeks later in a real integration. Ours is a REST API with public documentation, and most teams have a working integration running in an afternoon.
import { NexielScreenClient } from '@nexiel/sdk';
const screen = new NexielScreenClient({
baseUrl: 'https://compliance.nexiel.io',
});
const result = await screen.screenName({
name: 'Jane Doe',
dob: '1990-01-01',
nationality: 'IE',
});
result.classification; // 'CLEAR' | 'POSSIBLE_MATCH' | 'CONFIRMED_MATCH'- Idempotency keys on every mutating call, 24-hour dedupe, safe retries by design.
- SDKs in TypeScript and Python, generated from the same OpenAPI spec that documents the API.
- Public OpenAPI + Swagger UI, unauthenticated, in every environment including production.
- Sandbox mode for early testing: no key required, synthetic data only, clearly labelled in every response.
Call the REST API straight from your backend, documented with a public OpenAPI spec and Swagger UI in every environment.
Client SDKsTyped TypeScript and Python clients generated from the same OpenAPI spec that documents the API.
Agent Toolkit (MCP)Point a coding agent at Nexiel Verify and Nexiel Age through a real MCP server, authorized by your own restricted API key.
Simple, usage-based pricing
Nexiel Screen is priced by subscription tier. Nexiel Verify and Nexiel Age are pay-as-you-go, and you can see real numbers before you talk to anyone.
Ready to integrate?
Read the full API docs today, and join the waiting list for production access. No open-ended sales process, just a real queue.