Blocklist Management
The blocklist feature provides a powerful tool to automatically decline verification sessions that match previously identified documents or faces that should be rejected. This helps prevent fraud and ensure the integrity of your verification process.
Overview
The blocklist operates on two different entities:
- Document Blocklist: Prevents reuse of specific documents that have been identified as fraudulent, stolen, or otherwise problematic
- Face Blocklist: Prevents users whose biometric data matches previously blocklisted faces from passing verification
When a document or face on the blocklist is detected during verification, the session is automatically declined regardless of other verification settings.
How Blocklisting Works
Document Blocklisting
When a document is added to the blocklist, the system stores secure fingerprints of the document's unique identifiers (document number, MRZ data, etc.). During future verification sessions, if a document matches these fingerprints, the session is automatically declined with the ID_DOCUMENT_IN_BLOCKLIST warning.
Document blocklisting is particularly useful for:
- Preventing reuse of known fraudulent documents
- Blocking documents reported as stolen
- Preventing multiple accounts using the same document
Face Blocklisting
When a face is added to the blocklist, the system stores biometric templates derived from facial features. These templates are used to compare against faces in new verification sessions. If a face matches a blocklisted template, the session is automatically declined with the FACE_IN_BLOCKLIST warning.
Face blocklisting is useful for:
- Preventing users who have attempted fraud from creating new accounts
- Enforcing platform bans across new registration attempts
- Implementing regulatory exclusion requirements
Items can be added to blocklists through the admin dashboard.