Forged documents, injected selfies and second accounts get through onboarding checks that only look at pictures. JERIX is the identity-verification step inside your KYC process: the document is proven genuine, the face is matched to it, and you receive the identity fields you need. No images or biometrics are retained.
Fraud that opens an account is cheaper to stop at the door than to chase after the money moves.
A convincing fake passport passes a check that only looks at the picture of the page. The account opens, and the loss arrives weeks later.
How it is stopped. The passport chip is read and its signature is verified to the issuing state's root, offline. A forged or altered passport fails that signature, however good it looks.
Fraudsters feed a virtual camera or a replayed video into the onboarding flow, so the face on screen never stood in front of a phone.
How it is stopped. On iPhone, every capture is signed on the device with a single-use nonce and Apple App Attest. A frame that did not come from the device's own camera does not verify.
A customer you closed for fraud comes back under a new email, or one person opens several accounts to farm sign-up incentives.
How it is stopped. Each verified customer is tied to one person, and that person cannot open a second account with you. Two clients receive different references for the same person, so no one can cross-reference your customer base.
A stolen password is enough to change payout details or add a new device, and the real owner disputes everything after.
How it is stopped. Put a fresh selfie check in front of payout changes, large transfers or a new device. It must resolve to the person the account was verified for. No second document scan.
Why the chip matters more than the picture: passport chip verification. Why a convincing selfie is no longer proof: deepfakes and remote identity.
One step, done thoroughly. The rest of your compliance program stays where it is.
| Step | Who handles it |
|---|---|
| Identity verification | JERIX. A genuine government document, matched to the live person in front of the camera. |
| Identity fields for your records | Delivered to you. A regulated client can receive name and ID number, with larger field sets configured per client. |
| Sanctions, PEP and risk screening | Your existing AML tools and policy. |
| Transaction monitoring | Your existing AML tools and policy. |
| Record keeping and the compliance decision | You, under the rules your regulator sets. |
Online customer identification at payment companies and other regulated fintechs runs on its own rules. JERIX supplies the verification and the fields. Whether a flow meets your obligations is your compliance team’s call, and this page is not legal advice.
Fraud is stopped at the check. Right after it, the images and biometrics are deleted.
You receive the identity fields your process needs, not face images or templates. JERIX retains no images or biometrics, so there is no archive of customer faces to breach and nothing to feed the next deepfake. For a fintech, that is one fewer category of sensitive data to secure, audit and explain.
Read more: why storing face data is a liability.
One URL opened inside your existing onboarding, and two server-to-server calls. No SDK is required, so your stack is not a gating question. When the check should run inside your own app, use the React Native or Flutter SDK. Results arrive through signed webhooks, and verifications are recorded in a tamper-evident audit chain.
What the two calls look like →Bring your onboarding flow and the fields your compliance team needs. Twenty minutes, a real passport, and the chip verified offline in front of you.
Book a demo