Screen before you serve.

Check a name against sanctions, politically exposed persons, wanted and crime lists before you open the account. Run it from your backend, or from KYC Desk.

AML screening · Level 11 possible match
Samuel K. OtienoPEP
ClassificationNational governmentPositionMember of Parliament (2015-2019)CountryKenyaSourcePublic record
Illustrative example

Two levels

As deep as the customer's risk.

Start with a worldwide check for everyone. Go deeper when the customer, the amount or the country calls for it.

Level 1Worldwide watchlistsSanctions, politically exposed persons, wanted and crime lists from around the world. The everyday check for every new customer.See the lists we screen against
Level 2Local depth, with adverse mediaSanctions, politically exposed persons and adverse media, focused on the customer's country. For higher-risk customers and enhanced due diligence.

What you send

A name, and what you know.
  • First and last name
  • Optional details like date of birth, nationality, and citizenship to narrow down matching results.

What you get back

Every possible match, with its source.
  • Name, aliases, date and place of birth, country
  • Why they're listed: classification, topics such as PEP, and position held
  • A link to the source. No matches means an empty list.

For developers

One call, a list of matches.

Screen at sign-up, before a payout, or whenever your records change. The check runs at Level 1.

POST /kyc/client/api/aml/check
{
  "firstName": "Samuel",
  "lastName": "Otieno",
  "dateOfBirth": "1971-03-14",
  "nationality": "ke"
}

200 OK
[
  {
    "name": "Samuel K. Otieno",
    "classification": "National government",
    "topics": "role.pep",
    "position": "Member of Parliament (2015-2019)",
    "sourceUrl": "https://..."
  }
]
A possible match is not a verdictNames repeat. Send the date of birth and the nationality to narrow the list, and let a person decide on what's left.