The Custom Watchlist module screens the user's collected data, including biometric face data when available, against your organization's private watchlist of blocked or trusted users, and influences the Session outcome accordingly. It runs as a background process and isn't visible to the end user.
Integrations
:white_check_mark: Web | :white_check_mark: iOS | :white_check_mark: Android
How It Works
Custom Watchlist operates as a background process. It runs after user data has been collected earlier in the Session and does not present any visible step to the end user.
Each watchlist entry is associated with one of the following list types:
- Blocklist: Identifies users your organization wants to review or deny.
- Allowlist: Identifies users your organization wants to explicitly trust or grant special access.
When the module runs, it performs layered matching between the current session's collected data and your organization's watchlist entries. Matching can include:
- Data matching against fields such as name, date of birth, ID number, personal ID number, email, phone, and device fingerprint.
- 1:N biometric face search against face data in the watchlist.
- An optional fallback search.
Matches are scored, with Blocklist matches reducing the Session score and Allowlist matches increasing it. The final result is made available as a condition that your Workflow or Flow can branch on, enabling you to block the user, route them for additional review, or apply special privileges. You can view watchlist matches on the Risk tab in single Session view.
Watchlist entries can be added in several ways: manually through the Dashboard, from a completed session, via CSV bulk import, or automatically. Each entry stores a snapshot of the user's data at the time of creation; entries are not automatically updated if the underlying identity record changes later.
Use Custom Watchlist
- Custom Watchlist (Dashboard)
- Custom Watchlist (iOS)
- Custom Watchlist (Android)
- Custom Watchlist (Web SDK)