IDCheck 1

IDCheck.

Summary

IDnow IDCheck is a modular, configurable software solution for document capture, automated analysis and verification workflows that Customers adapt to their use cases and regulatory requirements.

Service Description

IDnow IDCheck is a module‑based, configurable software solution that enables Customers to perform document capture, automated document analysis and verification workflows according to their use case and regulatory requirements. The product is delivered as a technical platform: Customers select and order specific modules and integrations in the Order Agreement and adapt workflow options to their regulatory and operational needs. IDnow supplies the software, APIs and optional frontends; the Customer is responsible for providing required hardware, integrating the chosen interfaces, operating any on‑site verification steps and ensuring that selected modules and configurations satisfy applicable laws and internal policies.

Key Capabilities

Product Configuration: Customers may configure the product in terms of:

Identity Document Verification

  • Broad document support: Recognises and processes national ID cards, passports, residence permits and driver’s licences; country‑specific supported document lists available on request.
  • Modular analysis engine, including the following configurable modules:
    • Basic Document Analysis: automatic document recognition and classification; MRZ and VIZ OCR extraction; model identification; issuer matching; MRZ checksum, font and alignment checks; expiration date and configurable age verification. 
    • Advanced Document Analysis: extends coverage to paper‑based documents; cross‑checks MRZ & VIZ and front-back consistency; country‑specific field checks; barcode reading; static security feature detection; detection of cut corners where applicable.
    • eMRTD Chip Authenticity Checks: passive chip authentication to verify integrity and issuer linkage of eMRTD chips using PKI (ICAO DOC 9303); alternative chip‑presence tests where chip data readout is restricted by law. 
    • Identity Match Across Documents: cross‑document data matching and comparison against Customer‑provided data to confirm that multiple documents belong to the same person. 

Unstructured Document Verification

Analysis and data extraction from non‑structured documents (e.g., utility bills, payslips, tax notices) for proof of address, income or account ownership. 

  • IBAN extraction & validation: extracts IBAN from bank documents, returns account components (branch code, account number, BIC) and runs syntax (checksum) plus data consistency checks against provided input where available. 

IDCheck: IBAN Verification capability (available for French IBANs only) (optional)

  • Detects and prevents account‑takeover and identity fraud by verifying whether a provided French IBAN belongs to the claimed identity.
  • Check logic: matches first name, last name and (optionally) date of birth against the IBAN owner data and returns a verification status.
  • Validation is performed via the SEPA Mail network database and covers only French IBANs from banks participating in the SEPA Mail network.
  • Additional fraud signal: a verified result increases confidence in account ownership, while a non‑verified result should trigger further checks; coverage is limited to participating French banks.

Biometric Verification

Adds counter‑fraud by matching captured biometrics to the document holder’s photo to verify that the person performing onboarding is the document owner. 

The biometric modules can be enabled independently or combined according to the Customer’s workflow requirements (for example: Selfie only, Selfie + Liveness, or Liveness as a fallback). Thresholds, retry limits and escalation rules (e.g., automatic referral to expert review) are configurable to match the Customer’s risk appetite and operational needs.

Biometric processing is subject to applicable data protection rules: retention and use of biometric images are governed by Customer configuration and local law. Verification results and evidence are made available via APIs for downstream decisioning and audit logging.

  • Biometric Selfie (Face Recognition)
    • Face comparison between a selfie and the photo extracted from the identity document or the biometric photo from an eMRTD chip (where available and authorised). 
    • Automated similarity scoring and configurable acceptance thresholds to align with Customer risk appetite.
    • Available via Face Recognition API folder and integrable with Document Analysis modules for end‑to‑end verification
  • Video Liveness (Liveness Detection) 
    •  Real‑time “proof of life” checks to detect presentation and replay attacks by requiring user actions during a live video sequence.  
    • Advanced anti‑spoofing detection to identify masks, screens or other presentation fraud vectors. 
    • Delivered via the Liveness Detection API folder and combinable with Biometric Selfie for layered assurance.

Technical Integration

  • Configurable workflows & controls — enable customers to combine modules, adjust checks and define acceptance rules to meet use‑case and regulatory requirements.
  • API integration — IDnow exposes a dedicated REST API for customers to upload captured document images and submit orders for automated analysis; the API handles order creation, result retrieval and error reporting. 
  • Guided Capture SDK — out‑of‑the‑box capture toolkit that provides a customizable user interface and guided onboarding flow for document and selfie capture; ideal for improving quality and conversion. 
  • Capture Link Sender— service to send onboarding links via email or SMS so users can complete the guided capture on their own device.

Optional Fraud Prevention Modules and Configurations

360 Signals (optional)

360 Signals aggregates intelligence from millions of identity transactions to detect fraud patterns and partial matches across verifications. It compares new verifications with historical data to surface full or partial matches (full match = same person; partial match = possible document modification or identity manipulation). By default, 360 Signals data is retained for 30 days to comply with data‑privacy rules.

  • Modes of operation
    • Global‑mode: compares against other IDnow customers who opted into global mode; alerts indicate a hit occurred but do not disclose origin or full identifier details.
    • Self‑mode: compares only against the Customer’s own transaction history; no cross‑customer matching.
    • Signal selection: Customers may enable one or more signals to tailor fraud detection to their risk model.
  • Available signals
    • Repeated document numbers — stores document number and key attributes and flags a case when a document number reappears with inconsistent data. 
    • Repeat document faces — stores document photos and compares new selfies/document photos to detect reused or altered faces; mismatches with prior attempts trigger alerts. 
    • Synthetic document template — stores captured document images and detects significant image‑level similarity to previously collected templates; similar images are flagged as potential synthetic/document‑template fraud.
  • Data handling and alerts
    • Retention: default data retention is 30 days (subject to Customer configuration and data‑privacy constraints).
    • Alerting: predefined match thresholds determine alert levels; alerts are surfaced to the Customer for investigation and remediation.
    • Privacy: configurable to respect Customer opt‑in choices (global vs self-mode) and to minimise disclosure of source data when matching across customers.

Digital Screen Detection (optional)

  • Detects whether a presented document originates from a physical document or is being shown on a digital screen (to counter screen‑based presentation fraud). 
  • Real‑time image‑recognition analysis of captured document frames to identify screen artefacts and display characteristics.

Specialist Agent Review (Manual Review) (optional)

  • Configurable complement to automated verification, where highly trained Specialist Agents perform additional checks on the evidence collected during the user’s onboarding journey.
  • Reviews are performed in one or multiple Ident Centers depending on the Customer’s chosen service level; Specialist Agents are trained and subject to regular quality assurance.
  • Triggering: reviews are initiated by configurable rules (e.g., automated checks scoring outside defined thresholds).
  • Evidence handover: all relevant automated flow evidence is provided to the Specialist Agent for assessment.
  • Specialist Agent’s findings and final decisions are returned via the same API endpoints and can update transaction status or trigger downstream workflows.

Standard Data Retention and Deletion

  • Standard retention: IDnow retains onboarding data recorded by the activated modules in electronic form for 30 days.
  • Extended retention (optional): when Extended Data Retention is selected, data is retained for six (6) months and the service auto-renews unless terminated by the Customer in accordance with the Order Agreement.
  • Post termination export: after termination of Extended Data Retention and/or the Order Agreement, IDnow will, on Customer request, compile the data in a market standard format for transmission.
  • Final deletion: following the contract end date, IDnow will retain the compiled data unchanged for a maximum of 30 calendar days to allow retrieval; after that period all data will be permanently deleted.

Service Hours

  • General service hours: 24/7 (00:00–24:00 CET, seven days a week) 
  • Maintenance windows: pre‑communicated maintenance periods are excluded from Service Hours. 
  • The automated identification flow can be completed by the user without waiting; waiting times only occur if a case is escalated to Ident Specialist Review — the Customer receives final confirmation once the manual result is available.

Compliance summary

IDnow IDCheck is designed to support regulatory and security requirements for identity verification: it provides configurable modules that Customers can combine to meet eIDAS, AML/KYC and other jurisdictional obligations. Customers remain responsible for selecting certified configurations and retaining or archiving evidence where legally required.

IDCheck 2

Questions?