Maximize Conversion
Stop losing users to blurry document photos and endless retakes. The passport chip is read over NFC, so the check takes under 10 seconds, and every result is a clear yes or no, with no manual review queue.
Identity-fraud prevention for enterprises
Hardware-rooted NFC passport verification in under 10 seconds, with zero biometric data retention. Forged passports and injected selfies don’t verify, and no face database is left behind to breach.
Scan passport chip
Hold the top of your phone to the passport
Reading chip · 72%
Take a selfie
Center your face in the ring
Frames signed on device
Verified
Images deleted
Stop losing users to blurry document photos and endless retakes. The passport chip is read over NFC, so the check takes under 10 seconds, and every result is a clear yes or no, with no manual review queue.
Generative AI broke optical OCR: a photo of a document can no longer be trusted. JERIX reads the cryptographic signature inside the passport chip, so an AI-generated or altered document cannot verify. On iPhone, every selfie frame is signed on the device, so injected video does not pass.
Retained biometric data is a breach waiting to happen. Our Verify & Delete architecture validates the identity and deletes the face and document images as soon as the check completes. We keep no biometrics, so there is no biometric database to leak.
One verification, start to finish: your platform asks, the person taps a passport and takes a selfie, and you get a yes or no with the images already deleted.
01Your platform starts a verification
Legacy IDV judges how a picture looks. JERIX verifies where it came from, and keeps no biometrics afterwards.
Core Verification Technology
Legacy OCR Providers
Probabilistic (optical image analysis)
JERIX
Deterministic (hardware NFC chip extraction)
Deepfake & GenAI Exposure
Legacy OCR Providers
High (synthetic media can pass an optical check)
JERIX
Resistant by design (a forged passport fails the state's cryptographic signature)
Data Security & Privacy
Legacy OCR Providers
Creates honeypots (face and document images are retained)
JERIX
Verify & Delete (zero biometric data retention)
User Experience (UX)
Legacy OCR Providers
Frustrating (lighting issues, blur, endless retakes)
JERIX
Frictionless (tap the passport, under 10 seconds)
Manual Review Operations
Legacy OCR Providers
Requires expensive human fallbacks
JERIX
No manual review queue (every result is a clear yes or no)
Forged Documents
Legacy OCR Providers
Visual inspection of a photo of the document
JERIX
Chip signature verified to the issuing state's root: 588 certificates, 112 countries
Injected Selfies & Virtual Cameras
Legacy OCR Providers
Analyses the picture, which a generator can perfect
JERIX
On iPhone, every frame is signed on the device, so a frame from anywhere else does not verify
Data Shared With Your Platform
Legacy OCR Providers
Full identity record and images
JERIX
Only what you ask for: verified, and age as a yes or no
Returning Users
Legacy OCR Providers
Full re-verification, billed again
JERIX
Selfie only, not billed as a new verification
Duplicate Accounts & Ban Evasion
Legacy OCR Providers
Fuzzy matching against stored faces
JERIX
One person, one account, with lockout across operators
Deployment
Legacy OCR Providers
Typically the vendor's cloud
JERIX
Cloud, on-premises or air-gapped, with the trust chain verified fully offline
Integration
Legacy OCR Providers
Heavy SDKs and a long rollout
JERIX
Two server calls and one URL, from any backend language
Fraud where someone pretends to be someone else, or to be more than one person. Each one is stopped by something a fraudster cannot fake, not by a risk score.
Every passport chip is signed by the issuing state. We verify that signature to the state’s root, offline. A forged or altered document fails.
On iOS, every capture is signed on the phone, inside its own camera session. A selfie fed in from a virtual camera, a file or a replay was never part of that session, so it does not verify.
Each verified person maps to one identity on your platform. The same person cannot open a second account with you.
A person locked out for abuse stays locked out across operators that use JERIX. The lockout travels, the identity is never shared.
Before a payout or a password change, ask the owner to confirm again from the verified credential on their own phone, unlocked by their biometrics.
Ask “is this person over 18?” and get yes or no. You never see or store the date of birth.
The person taps their passport against the phone and takes a selfie.
We check the chip’s state signature and match the selfie to the photo the state signed.
You get a clear yes or no at the assurance level you set, plus an age answer if you asked.
The images and biometrics are deleted when the check ends. You keep a token for that person.
Stored face and ID images are the raw material of the next deepfake. In June 2026, a suspect in Israel allegedly passed banks’ remote checks with identity photos taken from breached databases and animated with AI. About 120 people were defrauded.
JERIX stops the fraud at the check and then deletes the images and biometrics. There is no biometric database to breach, and nothing to fuel the next attack.
SOURCE: CALCALIST, 21.06.2026
| After the check | A typical verification vendor | JERIX |
|---|---|---|
| Face and document images | Stored for the retention period | Deleted when the check ends |
| Biometric templates | Often kept to re-match later | Never kept |
| One person, two platforms | Often linkable | A different token per platform, never linkable |
Two calls from your server and one link for your user. No SDK is required, so any stack works.
Teams that want the check inside their own app can use our React Native and Flutter SDKs.
Read the developer docs →Your server starts a verification and gets back a link.
Your user opens the link and completes the check on their phone.
Your server receives a signed result: verified or not, and the age answer.
In production
The platform receives a yes or no and an age answer for each player, and nothing else: no name, no ID number, no image. A second integration, built on our native SDK, is underway.

Stop synthetic identities and multi-accounting at the gate, with a frictionless 10-second onboarding that keeps player drop-off low.
In detail →
Strengthen KYC onboarding with a chip-verified identity check, without storing toxic biometric data on your servers. Seamless, high-assurance onboarding for your highest-value customers.
In detail →
One real person behind every seller and courier account. Re-check at shift start with a selfie only, without keeping a gallery of their faces.
In detail →Digital identity for public services without building a new biometric database. The chip check runs fully offline.
In detail →
Onboard employees, contractors and partners securely. Verify each person against their passport chip before you grant access, with hardware-backed proof: a forged passport fails the chip signature, and on iPhone every capture is signed on the device.
In detail →Your industry is not listed?
Talk to usTwenty minutes with a real passport. See the fraud fail, and see that the images are gone when the check ends.
Book a demo