Skip to main content

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

Released 6 November 2026

Action required​

  • Callback URL replaced by webhook endpoints — the single callback URL is replaced by webhook endpoints, each with its own signing secret. An existing callback URL was moved to an endpoint with a new secret that has never been shown. Rotate the secret in Integration Settings → Webhooks, verify the X-IDV-Signature header, and read the result from the workflow.completed envelope. The customer fields keep their names and are now under payload.customer.

  • emit_event outcome action deprecated — events are now sent by the new emit_event workflow step. Workflows that still use the emit_event outcome action or an outcome events[] list keep working and are flagged in the dashboard, but a future release will refuse them. Move each event to an emit_event step placed after the last decision. See Deprecated: emit_event outcome action.

  • Licensed features — data storage, NFC and face 1:N identification are licensed per tenant by Innovatrics, and data storage can no longer be switched by the tenant. Without a licence, the step is not offered in the workflow builder and a workflow that contains it cannot be saved (feature_not_licensed). See Data Storage & Features.

  • Sandbox limits and go-live — a Sandbox is limited to 150 verifications and 14 days by default. When a limit is reached, session start returns 403 SANDBOX_LIMIT_REACHED. The switch to Production is now made by Innovatrics. See Sandbox limits.

  • Changes in the predefined workflows — templates that you run directly behave differently; workflows you cloned earlier are unchanged. In the predefined workflows:

    • an exhausted OCR retake budget rejects instead of going to review;
    • age verification creates no Customer and rejects a trust review;
    • a face that is only similar to a blocklisted person goes to manual review instead of being rejected and blocklisted automatically;
    • rejected attempts are linked to the blocked Customer instead of being added to the Blocklist.

    See Predefined Workflows and Customer Uniqueness.

  • Palm enrolment in custom workflows — palms captured in a re-onboarding of an existing Customer are used only when the merge outcome contains repoint_primary_DI. Add it to forked palm-enrolment workflows. See Palm Verification.

  • Repeated-attempt protection per client IP — after 7 rejected verifications from one client IP within one tenant in 30 minutes, further submissions get 429 RATE_LIMIT_EXCEEDED. If your backend relays sessions for many end users, pass each user's address in the new endUserIp field so they do not share one budget. See Start a session.

New features​

  • Platform webhooks — register several HTTPS webhook endpoints and receive signed workflow.completed results for verified and rejected verifications, workflow.event events sent by workflow steps, and record.action events for every back-office operator action. Undelivered events are listed and can be replayed.
  • Emit event workflow step — add an emit_event step anywhere in a workflow to send a workflow.event webhook when the run reaches it. The payload combines fixed values with results of earlier steps, such as the trust result or the decision outcome, and works on every data tier. See Emit event step.
  • Search in the back office — Customers and Digital Identities can be searched by name (a similarity search that tolerates typos and spelling variants) or exactly by document number, personal number or external ID, combined with filters. See Finding records.
  • Export and import of the IDV configuration — Administrators can download the complete configuration as one JSON file and import a modified one: all Trust Factor configurations, document OCR quality, both duplicity checks and all workflows. Import shows a preview, applies everything or nothing, and keeps a snapshot of the previous configuration. See Export and import.
  • Mandatory switch for Trust Factors — each Trust Factor has a Mandatory switch that decides what happens when its input is missing: Rejected ("Missing input") when on, Skipped when off. It is on by default only for age_estimation and age_verification, so existing verdicts do not change. See Missing input: Skipped or Rejected.
  • NFC onboarding workflow — a new predefined onboarding_nfc_v1 workflow and an idv_nfc_trust_factors configuration evaluate the three chip Trust Factors. Available to tenants with NFC enabled. See Chip trust factors.
  • Dashboard in Spanish — the dashboard is available in English, Spanish, Portuguese and Slovak; each user picks the language in the user menu. See Dashboard language.
  • One-command self-hosted installation — the platform installs into the Company's Kubernetes cluster with one command and one configuration file. The installer checks the configuration, the database connection and the licences before it changes anything, then sets up the databases, migrations and the identity provider in the right order. Every image can be pulled from a private registry mirror, and the telemetry of all components goes to one OTLP endpoint. See Self-hosted installation.

Improvements​

  • OR and parentheses in decision rules — rule conditions can combine comparisons with || and group them with parentheses; && binds tighter than ||. See Condition syntax.
  • Accept missing date of birth — a new Document OCR quality toggle, off by default, lets documents without a readable date of birth pass capture without a retake. See Document OCR Quality.
  • Faster verification results — the result is returned right after the decision, and webhook delivery no longer delays it.
  • API keys provisioned automatically — keys generated in Integration Settings come with their roles, organization membership and Customer API access already set up, following the storage setting. See API interface.
  • Safer dashboard sign-in and sessions — sign-in attempts are rate-limited; an expired session returns the user to the sign-in page and back to where they were. Only Administrators change roles, never their own, and a change takes effect immediately. See Sign-in and sessions and Managing roles.
  • Reliable blocklisting — Put on Blocklist also moves the person's document data to the Blocklist and, on tenants with 1:N, enrols faces that were never enrolled. Watchlist updates that fail are retried, raise an alert and can be re-applied. See Watchlists.
  • Erasure survives a backup restore — every anonymization is recorded in a separate, write-protected erasure log that is re-applied after a restore, so the data of an erased person does not come back from an older backup. Anonymization also deletes the stored face template; if the biometric erasure fails, nothing is wiped and the call returns 502 watchlist_erase_failed to be retried. See Data retention and GDPR.
  • No searchable face index without 1:N — for tenants without the 1:N add-on, the face template kept for 1:1 comparison is not added to any searchable face index.
  • Platform security hardening — tenant isolation, role management and identity-provider configuration were hardened across services after an independent security review. See Platform security.

Fixes​

  • Mid-flow decisions end the workflow — a decision step in the middle of a workflow whose rule ends the workflow now stops it; the steps after it no longer run. See Decision rules.
  • Rejected URL — in the web redirect flow, a rejected verification now lands on the Rejected URL, falling back to the Unverified URL when none is set. See Outcome front end.
  • Customer API audience error — a token without the record-store audience now gets 403 instead of 401, so a missing storage licence can be told apart from bad credentials. See Customer API.
  • Webhook secret rotation — rotating an endpoint's signing secret now returns the new secret, and permanent 4xx refusals now appear in the failed deliveries for replay.
  • Duplicate resolution — Merge works for hits found only by the document search, a similar-face duplicate offers the merge and blocklist actions, an automatically merged identity no longer appears as a second hit (which sent later onboardings to review as multiple_full_hits), hits of a review-pending identity disappear when it is rejected or anonymized, and the update_identified_customer outcome works for a recognised returning customer. See Resolving duplicates.
  • Palm authentication of returning customers — palms captured in a re-onboarding are stored when it becomes the primary identity, and authentications no longer change the primary identity.
  • Face authentication — a missing reference template is rebuilt from the archived selfie instead of returning no match.
  • Back office — the Matching tab appears only when a comparison was made, the Selfies tab shows liveness images, Palm Liveness appears once with its value, and Analytics figures are current instead of a five-minute-old snapshot.

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_duplicate workflow 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) and age_verification (document date of birth) Trust Factors are now evaluated, with default reject below thresholds of 25 and 18 years, and the predefined age_check_v1 workflow 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_customer and create_blocked_customer outcome actions accept an external_id_template (for example ${document.personal_number}_${uuid}) so the Customer's external_id follows 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.