Ban List
Ban List lets you maintain a blocklist of individuals who should be automatically prevented from completing identity verification journeys. When a new journey progresses through document capture or selfie capture, IDWise compares the applicant's data against your ban list in real time. A confirmed match immediately flags the journey as banned.
| Ban Type | Description |
|---|---|
| Extracted Fields | Matches on document data — name, date of birth, personal number, or document number |
| Face Biometrics | Matches on facial recognition against a stored face image |
| Device Fingerprint | Matches on the device fingerprint used during the onboarding journey |
Ban entries can be created manually via the IDWise Dashboard, or automatically when an operator bans a completed journey from the Journey Verification Dashboard.
Ban List is enabled at the business level. Enable it in IDWise Studio at Settings → Ban List → Enable Ban List. If you run into any issues, contact IDWise to activate it for your account. Once enabled, the check runs automatically on every new journey — no changes to your journey flow definition are required.
How Matching Works
IDWise matches new journeys against ban list records using these data points:
Personally Identifiable Information (PII)
Matches on document-extracted fields — Full Name, Date of Birth, Personal Number, and Nationality. If a match is found against a ban list record, the journey is flagged as banned.
Facial Biometrics
Compares the selfie captured during the journey against stored face images in your ban list.
Device Fingerprint
Matches the device used during the onboarding journey against previously banned devices.
All three checks run automatically when the corresponding step completes. A confirmed match immediately flags the journey.
API Response
You can find the ban result in the Get Journey Results API under rule_results. The rule name is ban_list.
{
"rule_results": {
"ban_list_clearance": {
"name": "Ban List Clearance",
"result": "Failed",
"description": "Verifies that the applicant is not on the ban list."
}
}
}| Result | Meaning |
|---|---|
Passed | No match found — the applicant is not on the ban list. |
Failed | A match was found — the applicant is banned. |
CouldNotApply | The rule could not be evaluated (e.g., required data was missing). |
Updated about 2 hours ago
