State 01 Consent
The user decides what is shared before the result is released.
Closed Beta · Invitation only
Identity verified with security, speed and control
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.
- Local processing Critical checks happen on the user’s phone.
- Encrypted outcome The client receives an authorized signed result, not raw biometrics.
- No persistent custody The architecture avoids creating a central biometric repository.
Closed Beta The challenge
Identity verification today is complex, fragile and costly
When biometrics move across SDKs, backends and custodians, operating complexity grows before trust actually improves.
- More custodians, more liability
Every extra vendor or backend expands the perimeter your team has to justify and protect.
- More transit, more exposure
Every handoff of sensitive data adds new leak points, operating risk and legal review.
- More coordination, more operating debt
Changing a rule, vendor or flow usually turns into rework across multiple teams and SDKs.
Conventional vs IDVerifier
Fragmented stack IDVerifier on-device
Flow entry
Fragmented stack
The experience is often split across multiple SDKs, handoffs and checks that feel like separate products.
IDVerifier on-device
A single entry point leads the user into one coherent mobile verification experience.
Biometric custody
Fragmented stack
Validation often depends on sending or duplicating sensitive data outside the device.
IDVerifier on-device
The critical check stays on the device and only the authorized outcome leaves it.
Compliance operations
Fragmented stack
More systems mean more controls, more justification and more audit surface.
IDVerifier on-device
Fewer sensitive moving parts make retention, access and traceability easier to explain.
Change velocity
Fragmented stack
Updating the flow reopens integrations, QA and vendor coordination.
IDVerifier on-device
A tighter model shortens change cycles, testing and rollout.
How it works
A clear experience, in visible steps
From the initial handoff to the signed outcome, the flow guides the user while keeping the sensitive moment on the device.
Move through the five real states of the flow and see what the user sees at each step.
Step 01 
Flow entry A clear start connects the customer channel with the mobile verification experience.
Step 02 Consent and authorization Control starts with an explicit action from the user.
Step 03 
Document capture Document validation moves forward with visual guidance instead of extra friction.
Step 04 
Liveness and biometrics The experience itself communicates immediacy, control and authenticity.
Step 05 
Signed result The sequence closes with a clear completed-verification signal.
Capabilities
A complete set of checks, modular and composable
Turn on only what you need. Add new capabilities without touching your application code.
Document verification
Validate passports, driver's licenses and government IDs. Extract and verify data and security features.
Face biometrics + liveness
Confirm the person matches their document and detect spoofing with liveness checks.
Age estimation
Estimate age from a facial scan to comply with age-restricted products and services.
Full registration
End-to-end onboarding combining document, facial match and fingerprint in a single flow.
Transaction authorization
Re-authenticate users for sensitive operations with a quick biometric check (step-up).
Security & privacy
Privacy by design, not as an add-on
IDVerifier keeps sensitive analysis on the device and returns a minimal, authorized and verifiable outcome to the client.
- 01 On-device processing
Capture, analysis and decision happen in memory, on the user's phone.
- 02 No central biometric custody
No biometric templates are stored in a persistent backend.
- 03 Encrypted, short-lived transport
Only encrypted, short-lived messages travel between the phone and your system.
- 04 Only the necessary data leaves
The client receives an authorized, encrypted and signed result — not a copy of the sensitive flow.
Integration
One lightweight SDK. Or a simple call.
IDVerifier concentrates the critical flow into one integration surface to reduce dependencies, cross-QA and operational overhead.
Simple start, signed return path
One call starts verification and returns an authorized outcome ready for your workflow.
The advantage is not adding another layer. It is cutting down dependencies around the verification moment.
const session = await idVerifier.start({ useCase: 'kyc-onboarding' });
const result = await session.verify({ channel: 'qr_or_sdk' });
if (result.status === 'verified') approveCustomer(result.token);Fewer pieces between initiation, verification and decision
- Your client starts the session with an identifier and the use-case policy.
- IDVerifier orchestrates the mobile experience and processes the verification on-device.
- Your system receives a signed, actionable result instead of a chain of scattered SDKs.
Industries
Built for sectors where trust is critical
The same on-device flow adapts to sectors where trust, compliance and fraud reduction are critical.
Banking & fintech
Remote onboarding, KYC and authorization of sensitive operations.
Why it matters
Less fraud at signup and in high-value operations, with no central biometric storage.
Healthcare
Secure access to records and privacy-preserving patient verification.
Why it matters
Privacy-preserving verification, without building a central repository of sensitive data.
E-commerce
Reduce fraud at signup and payment without hurting conversion.
Why it matters
Protects conversion and reputation with fast, frictionless verification.
Public sector
Digital identity for citizen services and procedures with ENS compliance.
Why it matters
Compliance and traceability without inflating centralized-storage risk.
Business impact
Security & anti-fraud
On-device biometric authentication that removes identity-theft and unauthorized-access vectors.
Operational efficiency
Cut onboarding from minutes to seconds and reduce reliance on manual review.
Compliance by design
Minimal data footprint, encrypted transport and explicit consent aligned with key frameworks.
Scalable & modular
Add or adjust capabilities without rewriting your app. Ready to grow across verticals.
Support
Frequently asked questions
The essentials on what IDVerifier does, how it integrates and how privacy is protected.
Can't find what you're looking for?
Our team answers technical and commercial questions about the Beta program.
Contact the teamWhat can IDVerifier verify?
Document 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).
Where is biometric data processed?
All processing happens in memory, on the user's device. Biometric data is never stored centrally and never leaves the device in clear form.
How does it integrate into my app?
With the IDVerifier SDK (web and mobile): it generates the link/QR, handles secure messaging, signing and decryption, and exposes every check through a simple API — so you integrate in little time. Prefer not to add an SDK? We also offer a direct integration to build it your own way. Either way, you never integrate multiple vendors' heavyweight biometric SDKs. The SDK is in preview during the Beta.
Which platforms are supported?
Verification runs through a mobile app for Android and iOS. The integrating client (web or native app) stays lightweight.
Is it compliant with privacy regulations?
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.
How do I get access to the Beta program?
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.
Limited Beta seats
Request a demo focused on 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.
- Tailored demo We show the flow applied to your industry and use case.
- Fit assessment We review the technical and compliance fit together.
- Clear next steps We coordinate the demo, pilot and integration path.