The user decides what is shared before the result is released.
Closed Beta · Invitation only
Document and biometric identity verification processed on the device, with no biometric data stored. Integrate it with a single lightweight SDK or a simple call, for web and mobile.
The user decides what is shared before the result is released.
When biometrics travel across SDKs, backends and custodians, complexity grows before trust does.
Each extra vendor or backend widens the perimeter your team has to protect.
Each hop of sensitive data adds leak points, operational error and legal review.
Changing a rule or a vendor often becomes rework across teams and SDKs.
From start to a signed result, the sensitive moment stays on the device.
Move through the five real states of the flow and see what the user sees at each step.
Turn on only what you need and add capabilities without touching your code.
Validate passports, IDs and official documents: check security features, detect forgeries and confirm the document's authenticity.
15,000+ document types · 200+ countries & territories
Confirm the person matches their document and detect spoofing with liveness.
Estimate age from a face scan for age-restricted services.
End-to-end onboarding: document, face match and fingerprint in one flow.
Re-authenticate sensitive operations with a quick biometric check (step-up).
IDVerifier keeps sensitive analysis on the device and returns a minimal, authorized and verifiable outcome to the client.
Capture, analysis and decision happen in memory, on the user's phone.
No biometric templates are stored in a persistent backend.
Only encrypted, short-lived messages travel between the phone and your system.
The client receives an authorized, encrypted and signed result — not a copy of the sensitive flow.
IDVerifier concentrates the critical flow into a single integration surface.
Simple start, signed return path
const session = await idVerifier.start({ useCase: 'kyc-onboarding' });
const result = await session.verify({ channel: 'qr_or_sdk' });
if (result.status === 'verified') approveCustomer(result.token); The same on-device flow adapts to sectors where trust and compliance are critical.
Remote onboarding, KYC and authorization of sensitive operations.
Less fraud at signup and in high-value operations, with no central biometric storage.
Secure access to records and privacy-preserving patient verification.
Privacy-preserving verification, without building a central repository of sensitive data.
Reduce fraud at signup and payment without hurting conversion.
Protects conversion and reputation with fast, frictionless verification.
Digital identity for citizen services and procedures with ENS compliance.
Compliance and traceability without inflating centralized-storage risk.
The essentials on what IDVerifier does, how it integrates and how privacy is protected.
Our team answers technical and commercial questions about the Beta program.
Contact the teamDocument verification (passports, IDs, government documents), face biometrics with liveness, age estimation, full registration with facial match and fingerprint, and authorization of sensitive transactions (step-up).
All processing happens in memory, on the user's device. Biometric data is never stored centrally and never leaves the device in clear form.
With the IDVerifier SDK (web and mobile), or a direct integration if you prefer no SDK. Either way you never integrate multiple vendors' heavyweight SDKs. The SDK is in preview during the Beta.
The architecture and operating model are designed to align with GDPR, ISO/IEC 27001, ISO/IEC 27701 and practices compatible with ENS High Level: minimal data footprint, encrypted transport, explicit consent and auditing without exposing personal data.
The product is in closed, invitation-only Beta. Request access in the form and we'll reach out for a demo and to assess your use case.
Tell us about your use case and we'll reach out for a demo and to assess your access to the closed Beta program.