What's New
Release history of the IDV Platform. The most recent release is listed first, and every entry links to the page that describes the feature in depth.
How the platform is versioned
- Releases are numbered MAJOR.MINOR.PATCH (for example
1.2.0). A minor release adds features and may change configuration or workflow vocabulary; a patch release contains fixes only. - SaaS tenants are upgraded by Innovatrics on the release date. No action is needed unless a release lists an Action required item for a feature you use.
- Self-hosted deployments receive each release as a versioned package and upgrade at their own pace. Read the Action required items of every release between your current and target version.
- The documentation always describes the latest release. This page is where the differences between releases are recorded.
- Innovatrics communicates the version deployed in each environment; self-hosted operators see it in the release package they installed.
IDV Platform 1.2.0
Scheduled release date: 15 September 2026
New features
- Document duplicity check across all records (1:N) — the document duplicity check now searches the new applicant's name and document numbers against the whole Customer, Blocklist and In-progress watchlists, not only against a single known Customer. Names are searched as non-reversible name vectors, so spelling variants and transliterations are found while the stored names cannot be reconstructed. Every text hit is cross-checked by face.
- Combined duplicity outcome — a new
best_duplicateworkflow step merges the face and the document signal into one combined outcome (full_hit,similar_face,similar_name,face_missmatch,doc_missmatch,multiple_full_hits) that decision rules can branch on. The Duplicates tab of the Digital Identity detail shows the face and the document score of each hit side by side with an outcome badge, and the Document dedup comparison rules can be edited as a form or as JSON in IDV Configuration. - Age verification trust factors — the
age_estimation(face) andage_verification(document date of birth) Trust Factors are now evaluated, with default reject below thresholds of 25 and 18 years, and the predefinedage_check_v1workflow for age verification is available in the template picker. - Palm verification (optional) — palms become an additional biometric modality: both palms are enrolled during onboarding and a single palm authenticates a Customer 1:1. New workflow steps (
both_palms_capture,single_palm_capture,palm_matching), two Palm Trust Factors, a Palms tab and a multi-modality Matching tab in the back office. Enabled per tenant on request. See Palm Verification. - Self-service single sign-on — an Administrator can connect the Company's own identity provider (Google, Microsoft Entra ID, any OpenID Connect provider, or SAML 2.0) under Users & Access → Single sign-on, without involving Innovatrics. Sign-in becomes email-first: the user's email domain routes them to their organization's provider, with a per-organization login page and a configurable default role for SSO users.
- Configurable Customer external ID — the
create_new_customerandcreate_blocked_customeroutcome actions accept anexternal_id_template(for example${document.personal_number}_${uuid}) so the Customer'sexternal_idfollows the Company's own scheme. The Customer API can supply an external ID on create (for migrations) and query by it. See the manifest reference. - Usage reporting — the platform reports its usage to the Innovatrics Transaction Counting System: the biometric and document operations of each session, plus a daily count of stored records. Self-hosted deployments can choose a count-only mode or an offline export. No personal data leaves the platform. See Usage Reporting.
Improvements
- Higher throughput, lower latency — the verification pipeline was audited against the recommended sequence of biometric operations; redundant model executions and re-uploads were removed, and captured artefacts are reused across steps. Verification results are unchanged.
- Start-up model pre-loading (self-hosted) — the biometric engine can optionally pre-load the age-estimation model at start-up, removing the first-request latency after a restart.
IDV Platform 1.1.0
Released 4 August 2026
New features
- Document OCR quality check — a captured document is validated before its data is trusted: OCR confidence, plausible date-of-birth, issue and expiry ranges, MRZ consistency and checksum, portrait not covered, and fixed-length field rules. A failing capture is re-prompted with a retake reason that the Capture & Workflow API returns to your app; when the retake budget is exhausted the workflow can route the case to review. Configurable per tenant in IDV Configuration → Document OCR Quality; see OCR — data extraction.
- Matching tab in the Digital Identity detail — authentication cases show the probe and the reference face side by side with the comparison score, and the detail view shows only the tabs relevant to the workflow that produced the identity. See Digital Identity Detail.
- Self-hosted deployment automation — a complete platform can be deployed to a fresh cluster in one step through GitOps, with tenant lifecycle tooling for creating and decommissioning tenants. See Deployment Models.
Improvements
- Tenant isolation and data security hardening — strengthened separation of tenant data and credentials across all services.
- Large-scale performance validation — load testing in two cloud regions produced sizing and right-sizing guidance for high-volume deployments.
IDV Platform 1.0.0
Released 17 July 2026 — first general release.
- Multi-tenant verification workflows with predefined workflows for onboarding, personal data update and biometric authentication, and custom workflows built from a declarative manifest with a visual builder, raw JSON view and validation.
- Configuration settings — Trust Factor configurations, accepted documents, workflow settings, integration settings and environments, in a redesigned settings UI.
- Customer API for reading, correcting and transitioning stored records, with integration tests.
- Face duplicity check (1:N) — vector search of every applicant's face against the Customer and Blocklist watchlists, with concurrent-onboarding protection and consistent duplicate hitlists after a case is resolved.
- Back Office UI — dashboard, Digital Identities, Customers, Assignments and manual review with role-based access and audit log.
- Hosted verification app — one consistent user experience for the website redirect and iframe integrations.
- Security components — injection attack detection, deepfake detection and liveness are part of every capture; see Security & Anti-fraud.