Blocklist Users

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 four different entities:

1. Document Blocklist: Prevents reuse of specific documents that have been identified as fraudulent, stolen, or otherwise problematic
2. Face Blocklist: Prevents users whose biometric data matches previously blocklisted faces from passing verification
3. Phone Number Blocklist: Prevents verifications using phone numbers that have been blocklisted
4. Email Blocklist: Prevents verifications using email addresses that have been blocklisted

📘

When a document, face, phone number, or email on the blocklist is detected during verification, the session is automatically declined with the corresponding warning: ID_DOCUMENT_IN_BLOCKLIST, FACE_IN_BLOCKLIST, PHONE_NUMBER_IN_BLOCKLIST, or EMAIL_IN_BLOCKLIST.

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

Phone Number Blocklisting

When a phone number is added to the blocklist, the system evaluates new verification sessions against the blocklisted numbers (including normalized formats such as E.164). If a match is found, the session is automatically declined with the PHONE_NUMBER_IN_BLOCKLIST warning.

Phone number blocklisting is useful for:

• Blocking numbers associated with repeat abuse or policy violations
• Preventing re-registration attempts using the same phone number
• Enforcing regional compliance requirements for communication channels

Email Blocklisting

When an email address is added to the blocklist, the system checks new verification sessions and email verifications against blocklisted addresses (case-insensitive, normalized). If a match is found, the session is automatically declined with the EMAIL_IN_BLOCKLIST warning.

Email blocklisting is useful for:

• Preventing repeat fraud or spam attempts from the same email address
• Enforcing bans across multiple accounts tied to the same email
• Meeting compliance requirements for communications and account creation

📘

Items can be added to blocklists through the admin dashboard.