The job
Every service has people it does not want back: a banned user, a person who defrauded a customer, a seller removed for abuse. It may also keep lists of other people it wants to recognise. These are lists that you own, and the check should work from the face, because a name can change.
The flow
- The selfie. The new user takes a selfie in the widget, and liveness confirms a live person.
- The check against your lists. The face is checked against your blocklists and person lists. See face search.
- The outcome. A match on a blocklist or on a person list is reported with the other results of the session.
- The decision. Your rules decide what to do. A reviewer can make a manual decision in the dashboard.
Scenario setup
In the scenario editor you choose the lists that the scenario checks. Different scenarios can check different lists.
How it differs from other checks
- Duplicate account detection looks among people who were verified before.
- AML screening looks at external sanctions, PEP and adverse media lists.
- A blocklist looks at the people you chose to list.
What your system receives
A session status and the results of each step, including the outcome of the list check. See session statuses.
Next
Read about face search, or talk to us about your lists.
Questions, answered plainly
What is the difference between a blocklist and a person list?
A blocklist holds people you want to check every new user against. A person list is a list of people that you keep for your own purposes. Both are checked by face.
Who maintains the lists?
You do. The lists are yours, and the platform checks faces against them.
What happens when there is a match?
The match is a signal in the session. Your rules, or a reviewer in the dashboard, decide whether to block, hold or let the person through.
How does it relate to AML screening?
AML screening checks a person against sanctions, PEP and adverse media lists through a licensed data provider. A blocklist is a list you keep yourself. They can run in the same flow.