IDCheck Web Capture (v3)
DOC_ID:v3 is in preview. The Verification data block implementation is not yet finalized and may change before general availability.
End-to-end, compliant document-based identity verification (v3)
Verifies identity using secure identity documents through multiple verification modes, adapted to business and regulatory needs.
In Capture mode, the end user completes verification through the IDnow frontend, which guides them step by step in providing the required identity evidence. This includes capturing document images, performing biometric checks (such as face matching and liveness detection), and optionally reading electronic document chips via NFC. The IDnow frontend ensures high-quality image capture, proper lighting checks, and guided user interaction, while maintaining a compliant and user-friendly verification experience.
This contrasts with the Headless approach, where customers collect document and biometric data within their own frontend and submit it to IDnow via API for verification. In Capture mode, IDnow takes full responsibility for the evidence collection process, optimizing data quality and regulatory compliance.
Users can complete verification through automated visual verification (AI-driven document and security feature checks), automated NFC verification (secure chip reading for eID-supported documents), or agent-assisted verification (review by trained identity specialists). Each mode ensures compliance with regulations such as eIDAS, AML, GwG, and BaFin. Configurations are modular, enabling flexible integration across fully automated or hybrid identity verification flows.
DOC_ID:v3 is the successor to DOC_ID:v2. It uses the unified Verification data block instead of the step-specific DocumentVerification data block, enabling cross-step verification data aggregation.
Key features
- Automated visual verification - AI-based analysis of ID document authenticity, integrity, and visual security features.
- Automated NFC verification - Secure reading and validation of embedded NFC chips in electronic identity documents.
- Agent-assisted verification - Expert review for complex, regulated, or escalated cases both in Autoident and VideoIndent products.
- Capture frontend – Guided user interface to collect document images, biometric samples, and NFC data directly from the end user through SDKs.
- Optimized data quality - Built-in guidance ensures correct document positioning, image sharpness, and proper lighting for improved verification outcomes.
- Configurable workflows - Automated and manual verification modes can be combined or sequenced based on business or regulatory requirements.
- Regulatory alignment - Fully compliant with eIDAS, AML, GwG, EAA and BaFin standards for secure remote identity verification.
Configuration
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
inputSources | Object | No | - | Maps identity data sources to flow step IDs for pre-filling the session. See Input mapping. |
inputSources.basicIdentity | String | No | - | The ID of the step providing the BasicIdentity data block. |
inputSources.extendedIdentity | String | No | - | The ID of the step providing the ExtendedIdentity data block. |
capture | Object | Yes | - | Capture configuration including document types and biometric sample types |
capture.documentTypes | Array | Yes | - | List of accepted document types: ID, PASSPORT, RESIDENT_PERMIT, VISA, DRIVING_LICENSE, HEALTH_CARD |
capture.biometricSampleTypes | Array | Yes | - | List of accepted biometric sample types: SELFIE, VIDEO |
capture.biometricConsentHandling | String | No | SDK | How biometric consent is handled during capture: SDK or CUSTOMER |
capture.withDocLiveness | Boolean | No | - | Enable document liveness detection during capture |
handoff | Boolean | No | false | When true, redirects the player immediately on manual review trigger and resumes polling in the background. Uses the session redirectUrl if configured; otherwise shows a submission-complete message. Default: false. |
config | Object | Yes | - | Environment-specific configuration |
config.live.realm | String | Yes | - | The realm identifier for the document verification service in the live environment |
config.staging.realm | String | Yes | - | The realm identifier for the document verification service in the staging environment |
Input data blocks
This step has no input data block requirements. Identity data from previous steps can be referenced via the inputSources configuration option to pre-fill the verification session, but this is a configuration-time mapping rather than a runtime data block dependency.
Routes
Routes for this step.
| Route | Description |
|---|---|
verified | Successful document processing with identity extraction. User's documents were successfully verified, either automatically or by an agent. |
not_verified | Document verification failed, no processing possible. |
fraud_detected | Document identified as fraudulent, identity data extracted for manual review. |
Output data blocks
Data blocks produced per route.
| Route | Data blocks produced | Notes |
|---|---|---|
| verified | BasicIdentity, ExtendedIdentity, DocumentData, DocumentImages, Verification, and conditionally BiometricSamples | BiometricSamples is only produced when biometric sample types are configured |
| not_verified | Verification | Contains verification failure details |
| fraud_detected | BasicIdentity, ExtendedIdentity, DocumentData, DocumentImages, Verification, and conditionally BiometricSamples | BiometricSamples is only produced when biometric sample types are configured |