Watchlists
Watchlists are the galleries that face duplicity check and document duplicity check searches against. Each tenant (in case of SaaS) has its own isolated watchlists; a new applicant's face is compared against them to decide whether the person is new, returning, or blocked.
The watchlists
| Watchlist | Who is in it | Effect of a match |
|---|---|---|
| Customer | Active, verified customers. | Recognized as a returning customer — the attempt can be merged or updated instead of creating a duplicate. |
| Blocklist | People to refuse — known fraudsters or otherwise unwanted. | The onboarding attempt is automatically rejected. |
| Concurrent (in-flight) | Applicants whose verification is still undecided. Internal, transient, not visible to the Company. | Flags a second simultaneous attempt by the same person as concurrent. |
Membership rules
- A person is represented by one watchlist member, tied to their Customer record.
- A member is in at most one watchlist at a time — a person is a customer, or blocked, or in flight, never two at once.
- A member's watchlist follows the Customer's state: activating, blocking, or anonymizing a Customer moves or removes their member accordingly.
How outcomes move members
Workflow outcomes and operator actions move members between watchlists:
| Action | Effect |
|---|---|
| Onboarding accepted as a new, unique customer | Member added to the Customer watchlist. |
| Onboarding rejected as fraud / operator blocks the person | Member added to the Blocklist. |
| Attempt held for manual review | Member kept in-flight until an operator decides. |
| Customer anonymized | Member removed entirely. |
Underlying images
Watchlists store biometric templates, not raw photos. The original images are retained separately (on the Stored tier) so that templates can be regenerated without asking users to re-enrol.
See also
- Face Duplicity check (1:N)
- Digital Identity Lifecycle — Customer states
- Manual Review