Duplicate account prevention for gaming, marketplaces and fintech. JERIX verifies the person behind each account against a government document, so a second account, a returning ban or a review farm needs a different real person. The images and biometrics are deleted right after each check.
An email address is free and a phone number is cheap. A verified person is neither.
One player, ten accounts, ten welcome bonuses. The same pattern runs through referral rewards, sign-up credits and free trials.
How it is stopped. Each account is tied to one verified person, and that person cannot open a second account with you. A new email, a new phone or a new device does not make a new person.
A user you removed for fraud, abuse or cheating is back an hour later under a different name and address.
How it is stopped. The ban sits on the person, not on the email. Where cross-operator lockout applies, an identity locked out by another operator is refused at onboarding too, without disclosing which operator.
One seller or one buyer runs a set of accounts to post reviews, inflate ratings or bury a competitor.
How it is stopped. Every reviewing account resolves to a verified person, and one person gets one account. A review farm needs a real, different person behind each account, each with their own document.
The second account is opened with someone else's document, or with a forged one.
How it is stopped. A forged or altered passport fails its chip signature, verified offline to the issuing state's root. A borrowed passport does not verify for someone else, because the live selfie is matched to the face the state stored on the chip. On iPhone, a selfie injected from a virtual camera fails the signed capture check.
The same person always resolves to the same reference at your platform, and to a different one everywhere else.
Duplicate detection built on faces needs a gallery of faces to search. That gallery is the most valuable thing an attacker could take from you.
No images or biometrics are retained, so there is no gallery to breach. Identity is per client: you get a reference that only works at your platform. Cross-operator lockout refuses a locked-out person without disclosing who they are or which operator locked them out.
The biometric honeypot →On the web, a hosted verification page is two server-to-server calls and one URL. In your app, the check runs through the React Native or Flutter SDK. Either way your server receives a signed result and the person’s reference, with no name, no ID number, no date of birth and no image.
Real request and response shapes →Twenty minutes. Verify once, then try to open a second account with a new email, and see it refused.
Book a demo