Please wait

Sanctions and PEP screening

Screen people and businesses against sanctions and PEP lists, once or with ongoing monitoring.

Screen a person or a business against sanctions and PEP (politically exposed person) lists, once with POST /api/v1/aml/screen, or continuously with monitoring.

One-off screening#

curl -sS -X POST 'https://api.trustverify.co.uk/api/v1/aml/screen' \
  -H "Authorization: Bearer $TRUSTVERIFY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Test Person",
  "type": "person",
  "dateOfBirth": "1980-01-01",
  "country": "GB"
}'

Send dateOfBirth and country when you have them. They cut false matches on common names.
Set type to business to match against organisations instead of people.

Result

Field	Meaning
`sanctionsMatch`	true when a hit is on a sanctions list.
`pepStatus`	Whether a hit is a politically exposed person.
`totalHits`	How many possible matches were found.
`hits`	Each possible match, with its score and lists.
`riskLevel`	Overall risk for the screening.

A hit is a possible match

A hit means the name is similar to a listed person or business. Someone on your team must review it before you act.

Ongoing monitoring#

Add a subject with POST /api/v1/aml/monitor and we keep screening it. A new match sends an aml.hit webhook. Monitoring needs a plan that includes it; otherwise the call returns 403.

curl -sS -X POST 'https://api.trustverify.co.uk/api/v1/aml/monitor' \
  -H "Authorization: Bearer $TRUSTVERIFY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "entityId": "seller_123",
  "name": "Test Person",
  "entityType": "person",
  "dateOfBirth": "1980-01-01",
  "country": "GB"
}'

Test it#

With a test key, a name containing sanction test returns a sanctions match and pep test returns a PEP match.