Fraud & Risk Intelligence
Duplicate Account Detection
Cross-references PII and face biometrics across all journeys to surface applicants who have already verified, preventing duplicate account fraud at scale.
Built for Enterprise Integration
⚠ Duplicate detected
Existing journey found with matching PII + face biometric
PII matchCONFIRMED
Face similarity94% MATCH
2-way
PII + face biometric cross-reference
Tenant
Scoped, single-tenant only
Reusable
Block can appear multiple times
How it works
Stop repeat applicants before they create a second account.
Duplicate Account Detection
Current Journey
Inconsistent Submission
SelfieFull NameStart DateReference numberJourney Link
View
Previous Onboarding Submission
SelfieFull NameStart DateReference numberJourney Link
View
All Submissions from Same Person
SelfieFull NameStart DateReference numberJourney Link
View
View
View
View
1
Journey completes with ID + selfie
The Duplicate Account Detection block runs after document and selfie steps, using all collected signals.
2
Cross-reference runs across all tenant journeys
The new applicant's PII and face biometric are checked against all completed journeys in the same tenant.
3
Duplicate signals scored
Matches are scored across all three dimensions. Threshold-based matching surfaces true duplicates while reducing false positives.
4
Action on failure applied
Duplicate journeys are referred or rejected based on your configuration. Existing journey IDs are linked for compliance review.
Why Enterprises Choose IDWise for Duplicate Account Detection
01
Prevent double onboarding
Catch users who have already onboarded attempting to create a second account, with new documents or the same face.
02
Biometric face matching
PII and face biometric cross-reference produces high-confidence duplicate signals with minimal false positives.
03
Tenant-scoped privacy
Duplicate detection is single-tenant only, your data never crosses tenant boundaries, meeting data protection requirements.
04
Reusable block
The block can appear multiple times in a journey, enabling duplicate checks across different risk stages or product lines.
Capabilities
Robust, enterprise-grade features built for regulated industries
PII Cross-Reference
Name, DOB, document number, and nationality compared across all completed journeys within the same tenant.
Biometric Matching
Face similarity compared against all enrolled faces, detecting the same person submitting under different identity documents.
Linked Journey Audit
When a duplicate is detected, the linked journey IDs are surfaced in IDWise Studio for compliance review and evidence export.
Feature detail
Everything you need for duplicate account detection
Face similarity scoring against all enrolled selfies in the tenant, configurable face match threshold, no PII cross-referencing.
Face similarity scoring against all enrolled selfies in the tenant, configurable face match threshold.
Strictly single-tenant scope. No biometric data crosses tenant boundaries, meeting GDPR and regional data protection requirements.
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 duplicate-detection 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
No. Duplicate detection is strictly scoped to a single tenant. No data or biometrics are shared across tenants, meeting GDPR and regional data protection requirements.
The journey is referred or rejected (configurable). The duplicate is flagged in IDWise Studio with the linked journey IDs so compliance teams can review the evidence.
Yes. The Account Duplication Detection block can be placed multiple times in a flow, enabling duplicate checks at different stages, for example after ID submission and again after AML screening.
IDWise uses face biometrics only: the submitted selfie is compared against all previously enrolled selfies in the tenant using a similarity score with a configurable match threshold.
Talk to an IDWise Specialist about Duplicate Account Detection
Discuss your markets, regulatory requirements, risk controls and integration architecture with our team, and see how IDWise fits your operating model.