Support

Support for evaluating IDVerifier

Centralize FAQs, resources and commercial contact details for teams considering the closed Beta.

Product

What 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).
How many documents and countries are covered?
IDVerifier supports more than 15,000 document types from over 200 countries and territories: passports and e-passports, national ID cards, driver's licenses, residence permits, visas and other official documents. It automatically recognizes the document type and country of origin, reads data from the visual zone, the machine-readable zone (MRZ) and barcodes, and supports multiple languages and scripts.
Does it detect fake or tampered documents?
Yes. Beyond reading the data, IDVerifier validates the document's authenticity: it checks its security features, detects forgeries, documents presented as a copy or screenshot, and tampering such as photo substitution. It also cross-checks information across the document's zones (visual zone, MRZ, barcode and, for electronic documents, the chip) to confirm it is consistent and legitimate.
Is liveness detection certified?
Yes. Presentation-attack detection (liveness) is certified at PAD Level 2 under the international ISO/IEC 30107-3 standard, evaluated by an independent accredited lab. It confirms a real person is in front of the camera and blocks spoofing attempts with photos, screens, masks or generated images. It offers active mode (a prompt such as blinking or turning the head) and passive mode (just staying in front of the camera for a moment).

Integration

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.
Do I have to integrate several vendors' SDKs?
No. With IDVerifier you integrate a single surface: a lightweight IDVerifier SDK for web and mobile, or a direct integration if you prefer more control. That one integration covers document capture, face biometrics, liveness, secure messaging and encryption, without your team having to integrate and maintain multiple vendors' heavyweight SDKs or coordinate the pieces. This reduces implementation time, cross-testing and ongoing maintenance.
Can I verify without integrating an SDK?
Yes. If you prefer not to add an SDK, you can start verification with a link or a QR code: the user completes the journey in a mobile experience and your system still receives an authorized, signed result, ready to continue your flow. It's a good option for one-off checks or to get started quickly during the Beta.
Which platforms does it work on?
Verification runs in a mobile experience for Android and iOS, where the sensitive moment happens (capture, biometrics and liveness). It can be launched from your website, your native app, a link or a QR code, and the integrating client stays lightweight: it just starts the session and receives the signed result.
What does my team need to get started?
During the closed Beta, it is enough to define the use case, industry and flow you want to validate. Integration is done with the IDVerifier SDK (web and mobile, in preview) or a simple link/QR, and it is built to be integrated with the help of AI agents (Claude, Codex) using LLM-friendly documentation. We will coordinate a demo and the next step for the pilot.

Security & privacy

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.
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.

Beta program

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.
What is included in the closed Beta?
It includes a commercial review of the use case, demo sessions and hands-on guidance to define the scope of the initial pilot.
Resources

Resources

We are preparing additional materials to support pilots, demos and future integrations.

Coming soon

Documentation

Introductory guides and product materials for future customers.

Coming soon

Service status

Future channel for operational visibility and service notifications.

Coming soon

Integration guides

Support materials for teams that move forward to technical evaluation.

Beta

Request a closed Beta demo

Tell us about your use case and we will get in touch to assess fit, timing and next steps.

Request access to the closed Beta

Tell us your use case and we'll reach out for a demo and to assess your access to the Beta program.