Skip to main content

Blocklist Overview

The Blocklist helps prevent known fraudulent or spam individuals from completing identity verifications. During verification, iDenfy compares new data (face, document, or personal info) against entries in the blocklist. If a match is found, the verification is marked “suspected” and flagged with one of the following tags:
  • Face_Blacklisted — selfie image matched
  • Doc_Face_Blacklisted — face from document matched
  • Data_Blacklisted — personal details matched
The blocklist check runs automatically once a verification is approved.

Interface Notes

  • Access via sidebar: Menu → Blocklist
  • Tabs:
  • Selfie
  • 🪪 Face in Document
  • Document Data
  • Use the search bar to find existing records by ScanRef or enable Search all records.
  • Use the Create new button to open the blocklist creation form.
  • Required fields are marked — incomplete entries cannot be submitted.

Operational Tips
  • Use ScanRef when you already have a completed verification—this ensures accurate data/face extraction and saves time.
  • For Document data, adding a Personal number and Nationality significantly improves matching accuracy.
  • Keep Reason short but specific (e.g., “Chargeback fraud, 2025-10-21; internal case #1234”).

Face Blocklist (Selfie / Face in Document)

Use when you want to block by image.

Fields in “Create new → Face”

FieldValues / FormatRequiredNotes
Ban byPhoto or ScanRefChoose Photo to upload; choose ScanRef to pull images from an existing verification.
Ban typeSelfie or Document FaceSelect which face source to block.
Upload photoPNG, JPG, HEIFif Ban by = PhotoDrag & drop or click to upload.
ReasonFree textOptionalInternal note/context.
How it works
  • If Ban by = Photo → you must upload a file.
  • If Ban by = ScanRef → the system uses the face(s) from that verification.
  • On future approved verifications, the system compares faces and flags with Face_Blacklisted or Doc_Face_Blacklisted.
image-20251028-095933.png

Document Data Blocklist (Personal Information)

Use when you want to block by identity details (no image required).

Fields in “Create new → Document data”

FieldValues / FormatRequiredNotes
Ban byData (or ScanRef, if enabled in your setup)With ScanRef, fields auto-fill from that verification.
Full nameTextPerson’s full legal name.
Date of birthDateDate picker; must be a valid date.
Personal numberTextOptionalNational ID / personal code (improves match accuracy).
NationalityCountry selectOptionalISO country selection (improves match accuracy).
Document numberTextOptionalAdds another strong identifier.
ReasonFree textOptionalInternal note / context.
How it works
  • If details match on a future approved verification, it’s flagged with Data_Blacklisted.
  • If created via ScanRef, the system pre-fills name, DOB, personal number, and nationality (when available).
image-20251028-101018.png

Validation & Behavior

  • Required fields are enforced (you’ll see “Please fill in all required fields.” if missing).
  • Files: Accepts PNG / JPG / HEIF.
  • Dates: Must be valid (DOB uses a date picker).
  • Submission: Create is disabled until the required fields are completed.

Directly from a Verification

On any verification results page, click Add verification to a blocklist (top-right corner). This opens a quick-action modal allowing you to add that verification immediately. Fields:
FieldDescription / Options
Block reasonChoose the reason:
  • Fake document
  • Same person, multiple identities
  • Deepfake / AI-generated face
  • Fraudulent behavior during onboarding
  • Blocklist by internal risk rules
  • Confirmed criminal activity
  • Other
| | Block by | Select which data to block — Face, Document, Personal data, depending on verification type | Once submitted, that verification’s data (face/document/personal info) is stored in the internal blocklist for future matching. image-20251028-102045.png