Biometric
AML screening

Check a customer against sanctions and PEP — in the same request as their identity

While others bolt on a separate screening service, Biometric.Vision checks a customer against sanctions lists, PEP and terrorist databases right inside identity verification. One request — identity confirmed and AML cleared.

500 checks a month free— no card
Customer · onboarding
Identity confirmed · eKYC
Screening · list matchingLive
OFAC · US sanctions
clear
EU · UN · HMT sanctions
clear
PEP · politically exposed
clear
Terrorist lists
clear
Local KZ / CIS stop-lists
clear
Clear — no matches foundIdentity confirmed and AML cleared in a single response
One eKYC verdict · no separate integration
Sound familiar?

Manual list matching — and the cost of one missed row

A request comes in from the regulator to check the customer base. A compliance officer opens the export and manually matches customers against sanctions lists in separate tabs — OFAC, EU, UN, local stop-lists. Hundreds of rows, different formats, name transliteration.

And the question isn't «will they find a match», but «how many will they miss». One sanctioned customer who slips through isn't an operational error — it's a conversation with the regulator about your license.

OFACEUUNLocal
#CustomerStatus
241Ivanov Ivan A.?
242Nurlan Zh. Serik…check
243A. Petrov / Петровrisk
244Sultanova A. K.?
245Wang Lei / 王磊check
+ 1,240,000 rows by hand, tab by tab
What you get

Screening that doesn't depend on manual matching

Screening out of the box

Customers are checked against sanctions, PEP and stop-lists automatically at signup — no manual matching and no third-party tools.

Global and local lists

International sanctions and local KZ / CIS lists in a single check — with name transliteration handled.

Audit-ready

Every check is logged. When the regulator's request arrives, the history is already there.

List coverage

Which databases we screen against

International sanctions, politically exposed persons and terrorist databases, adverse media mentions and local stop-lists of Kazakhstan and CIS countries — in a single check, with name transliteration handled.

Screening covers both individuals and companies.
Sanctions lists
OFACEUUNHMT
PEP

Politically exposed persons, their associates and related parties — with risk levels accounted for.

Terrorists and adverse media

Terrorist lists and screening against negative media mentions.

Local stop-lists
KazakhstanCISARDFM
Identity + AML in one request

Not a separate service, but part of the check

With most providers, AML is a separate call and a separate integration. With Biometric.Vision, screening is built into eKYC: one request runs Liveness, document recognition, face match and AML — and returns a single verdict.

1request instead of four
1provider instead of four
fewer points of failure
POST /v1/verify · one call
Liveness
Document recognition
Face match
AML screening
Single responseverdict: approved
Ongoing monitoring

A customer passed yesterday — and today they're on a list

A one-time check at signup isn't enough: sanctions lists get updated, and the customer stays with you. Ongoing monitoring re-checks your base against updated lists and sends a notification the moment a new match appears.

Auto re-checking of the base as lists are updated.
Webhook and dashboard notification on a new match.
Risk is caught before the regulator asks, not after.
Yesterday · onboarding
Customer passed the check
No list matches · verdict «clear»
Today · 06:00
Lists were updated
A new revision of the sanctions list was loaded
Now · auto re-check
New match · customer on a listAccount flagged for compliance reviewwebhook
Local compliance

AML/CFT compliance where global providers fall short

International services are built for the EU and US. The requirements of the national regulator, local stop-lists of Kazakhstan and CIS specifics they don't cover. Biometric.Vision is built for this market: screening accounts for local lists and the national regulator's requirements.

For banks and large platforms — On-Premise deployment: check data never leaves your perimeter.

Regulator requirements KZ / CIS stop-lists On-Premise
Global services
EU and US sanctions
Regulator requirements
Local KZ lists
CIS specifics
On-Premise in your perimeter
Biometric.Vision
EU and US sanctions
Regulator requirements
Local KZ lists
CIS specifics
On-Premise in your perimeter
How it works

Four steps — from customer to verdict

1

Identity verification

The customer passes identity verification — Liveness, document and face match.

2

List matching

The system matches the customer against sanctions lists, PEP and stop-lists.

3

Match scoring

Matches are ranked by relevance, obvious false positives are filtered out.

4

Verdict and history

Via API and in the dashboard: «clear», «match» or «for review» — all logged.

Integration

Live in a day

One REST API — AML is just another module in the shared request. A developer connects it in a few hours, or delegates the integration to an AI agent.

AML is added with a single field in the checks array.
Ready to work with Cursor and Claude Code.
onboarding.js — Biometric.Vision SDK
// Identity and AML — in one request
const result = await biometric.verify({
checks: ['document', 'liveness', 'face_match', 'aml'],
scenario: 'onboarding'
});
// → single verdict
{ "identity": "verified", "aml": "clear",
"verdict": "approved" }
Trust and certification

Compliance that's ready for the regulator's audit

ISO 27001Certificate № 760281
ARDFMRequirements compliance
FAQ

Frequently asked questions

It's checking a customer against sanctions lists, politically exposed persons (PEP) databases and stop-lists, to avoid serving sanctioned persons and to comply with anti-money-laundering (AML/CFT) requirements.

Get started

Close AML/CFT without manual list matching

Create an account and get API access in 60 seconds. 500 checks a month free — test it on your own base.