Fraud & Risk Intelligence
Ban List
Tenant-controlled blocklists matched across PII identifiers, face biometrics, and device fingerprint, stopping banned individuals from re-onboarding under new identities.
Built for Enterprise Integration
⚠ Duplicate detected
Existing journey found with matching PII + face biometric
PII matchCONFIRMED
Face similarity94% MATCH
Device fingerprintSAME DEVICE
3
Match dimensions: PII, face, device
Tenant
Controlled, you own the list
Configurable
Enforcement actions
How it works
Permanently block known fraudsters, across PII, face, and device.
1
Add individuals to your ban list
Add PII identifiers, selfie biometrics, and device fingerprints of known bad actors to your tenant-controlled blocklist via IDWise Studio or API.
2
Every new journey is screened
All new journeys are automatically checked against your ban list across all three match dimensions simultaneously.
3
Match triggers instant action
A ban list hit immediately triggers the configured action (Refer or Reject), the applicant cannot proceed.
4
Match evidence logged for compliance
Ban list matches are logged to the journey audit trail with match evidence for compliance review.
Why Enterprises Choose IDWise for Ban List
01
Stop re-registration
Banned individuals attempting to re-onboard with new documents or devices are caught via biometric and fingerprint matching.
02
Three match dimensions
PII, face biometrics, and device fingerprint, catching banned users who change their name, get a new document, or use a new device.
03
Full tenant control
Your ban list is yours, add, remove, and manage entries via Studio or API. No cross-tenant data sharing.
04
Configurable enforcement
Apply Refer or Reject actions according to your configured policy when a ban-list match is detected.
Capabilities
Robust, enterprise-grade features built for regulated industries
PII Blocklisting
Block specific name, DOB, document number, and nationality combinations, preventing re-registration with the same identity.
Biometric Blocklisting
Add a selfie biometric to the ban list, the same face is blocked even if the individual presents a different identity document.
Device Fingerprint Blocking
Add a device fingerprint, blocks the device even if the user presents a new identity and selfie.
Studio & API Management
Manage ban list entries from IDWise Studio or via the API. Bulk import and individual entry management both supported.
Feature detail
Everything you need for ban list
Block on name, DOB, document number, and nationality. Configurable match threshold for fuzzy name matching.
Block on face similarity, the same face is caught even with a different identity document or different personal details.
Block a device fingerprint, the device is rejected even when new identity documents and a new selfie are presented.
Add, remove, and query ban list entries from IDWise Studio or the API. Bulk import via CSV for large enforcement actions.
Built for Enterprise Integration.
Simple API & SDK
Start with a few lines of code. Full sandbox, webhooks for every event, and docs your engineers will use.
Consistent controls across supported channels
Same fraud models, document coverage, and UX on iOS, Android, Web, React Native, and Flutter.
iOSAndroidWebReact NativeFlutterREST API
</> View documentation
// Start a journey with ban-list const journey = await idwise.startJourney({ flowId: 'your_flow_id', referenceNo: 'USR_000001' }); // Receive result via webhook app.get('journey/v2/get/12345667899', (req) => { const { decision } = req.body; // Passed | Refer | Rejected });
Frequently asked questions
It depends on which dimensions were added to the ban list. If a face biometric was added, the same face is blocked regardless of what ID document is presented. If only PII was added, a different document could pass PII checks, this is why IDWise recommends adding all three dimensions.
Yes. Ban list entries can be removed individually or in bulk from IDWise Studio or via the management API.
No. Each tenant's ban list is strictly private and scoped to that tenant. No ban list data is shared across tenant boundaries.
You can add ban list entries manually from IDWise Studio, import them in bulk via CSV, or use the Ban List management API to add entries programmatically.
Talk to an IDWise Specialist about Ban List
Discuss your markets, regulatory requirements, risk controls and integration architecture with our team, and see how IDWise fits your operating model.