DOCSEARCHbyAlgolia
Submit Docs

IDnow Trust Platform Documentation

website·Indexed 31 days ago

https://docs.eu.platform.idnow.sx

Developer guides for the IDnow Trust Platform, featuring identity verification (IDV) services, electronic signing, and orchestration flows. Includes technical specifications for headless address and bank document verification, national electronic identity (eID) authentication via AusweisApp and France Identité, device intelligence risk assessment, and the DocIDV service.

Tokens
77.3K
Snippets
235
Records
496
Agent score
51%

What's inside IDnow

  1. Overview of Headless Signing

    Headless Signing is a backend-only operation used to sign or seal documents instantly without user interaction. It integrates with the Sphinx credential system to issue either Advanced Electronic Signatures (AES) for natural persons or Qualified Electronic Seals (QSEAL) for legal entities. The process is handled server-side via a Temporal workflow that initiates the request, polls for completion, and finalizes the operation.

  2. Overview of Automated Verification using pre-captured images (Headless v2)

    The Headless v2 verification flow allows applications to collect identity evidence (such as ID document images) via their own front end and submit them to IDnow via API. IDnow performs AI-based analysis and data extraction on these static inputs.

    Important Constraints:

    • No User Interaction: Unlike Capture mode, there is no IDnow front end interaction.
    • Limited Accuracy: Because it relies solely on static images and lacks dynamic/live capture, it is not suitable for regulated use cases like KYC or AML.
    • Use Cases: Best for unregulated scenarios, document data extraction, image quality assessment, or pre-validation.
    • Compatibility: This step cannot be combined in the same flow as 'Verifying IBAN - API only (v1)' or 'Verifying proof of address - API only (v1)' as they require different document types.

  3. Overview of Phone Verification (PHONE_VERIFY:v1)

    The PHONE_VERIFY:v1 step verifies that an end-user owns a specific phone number by sending a one-time password (OTP) via SMS. This step has no built-in Player UI; the developer's backend is responsible for presenting the OTP input screen to the user and submitting the response via the sessions API. The step resolves as completed once the code is validated or ends as not_verified if retry attempts are exhausted.

  4. Overview of eID authentication (eids-v2)

    The eids-v2 step type allows businesses to authenticate users through government-issued eID schemes (e.g., France Identité, Personalausweis). It uses OpenID Connect (OIDC) for authentication and routes users to the appropriate provider backend based on the selected method. The result of the authentication is returned as a unified Verification data block containing the method used, authority, cryptographic evidence, and assurance level.

  5. Overview of Document-Based Identity Verification (v4)

    The v4 document-based identity verification process verifies identity using secure documents through multiple modes. In 'Capture mode', users are guided by the IDnow frontend to provide identity evidence, including document images, biometric checks (face matching and liveness detection), and optional NFC reading of electronic document chips. It is compliant with eIDAS, AML, GwG, EAA, and BaFin standards.

  6. Overview of IDnow DocIDV identity verification

    The DocIDV service verifies a user's identity through document analysis using two primary methods:

    1. Agent-assisted verification (VideoIdent): A live video session where a trained agent guides the user through document capture and verifies security features, face matching, and liveness.
    2. Automated verification (AutoIdent): An AI-driven process that analyzes document authenticity, security features, face matching, and liveness without human intervention.

    The service can optionally cross-check identity data provided by upstream steps and returns a unified Verification data block detailing the checks performed and the assurance level achieved.

  7. Overview of Document-based Identity Verification and Signing

    This process combines DocIDV (document-based identity verification) with electronic signature capabilities. It verifies a user's identity via document analysis, security feature checks, face matching, and liveness detection, then issues a signature.

    Two signing modes are supported:

    1. Qualified Electronic Signature (QES): Legally binding signatures under the eIDAS framework, equivalent to a handwritten signature. Requires strict identity verification.
    2. Contract Signing Mode: Standard electronic signatures applied to customer-supplied contract documents without QES requirements.

  8. Overview of Headless bank document verification

    The Headless bank document verification step verifies a bank document using static evidence collected by the customer's own front end and submitted via API. IDnow performs automated analysis and data extraction to produce a FundingSource data block. This is a headless process; there is no user-facing capture step provided by IDnow.

    Key Features:

    • Customer-managed collection: Images are captured and submitted via API.
    • Funding source extraction: Extracts IBAN, BIC, bank code, branch code, bank name, address lines, account number, and account key.
    • Identity cross-check: If compareIdentity is enabled, the document holder's name is cross-checked against a prior BasicIdentity step.
    • Verification result: A Verification data block is produced for all output routes.

    Compatibility Note: This step cannot be combined in the same flow as 'Verifying proof of address - API only (v1)' or 'Verifying ID document - API only (IDC) (v2)' as they require different document types.

  9. Overview of Biometric Authentication (v2)

    Biometric Authentication (v2) provides real-time identity confirmation using a face scan to prevent impersonation, spoofing, and deepfakes. It features liveness detection to ensure the user is physically present and face comparison to match the live capture against an enrolled biometric template. This step requires that the user has previously completed the Biometric Enrolment (v1) process.

  10. Overview of Electronic Signing with Legally Recognized Assurance Levels

    This step enables real-time electronic signature issuance using verified identity data already available at the time of signing. It is designed for flows where AML-compliant identity data has already been verified (either by the customer's system or a reusable identity scheme), allowing for immediate signature issuance without a new identity verification process. It supports two levels of assurance according to eIDAS:

    • QES (Qualified Electronic Signature): The highest level of assurance, legally equivalent to a handwritten signature. Requires strict, verified identification of the signer.
    • AES (Advanced Electronic Signature): A secure digital signature uniquely linked to the signer, but without the strict regulated identity-proofing process required for QES.

  11. Overview of eKYC UK identity verification

    The eKYC UK step is a headless, server-side verification process that cross-references a person's identity against UK credit bureau and electoral roll sources. It uses a tiered corroboration model to determine the result based on the number of independent sources that match the identity elements:

    • Verified: A full '2+2' pass (two identity elements corroborated by at least two independent sources).
    • Inconclusive: A partial match ('2+1' or '1+1').
    • Not Verified: Results below the '1+1' threshold or no corroborated elements.

    The verificationProcessId returned in the Verification data block is the vendor-assigned transaction ID.

  12. Overview of Document-Based Identity Verification (Capture Mode)

    The document-based identity verification step in 'Capture' mode uses the IDnow frontend to guide users through providing identity evidence. This includes capturing document images, performing biometric checks (face matching and liveness detection), and optionally reading electronic document chips via NFC. This is an end-to-end managed process where IDnow handles evidence collection, ensuring high-quality data and regulatory compliance (eIDAS, AML, GwG, BaFin). Verification can be performed via automated visual AI, automated NFC chip reading, or agent-assisted review.