Skip to content
Identivero

The Identivero verification platform

From identity document to result record, under your brand.

The Identivero verification platform captures and reads identity documents, checks liveness and face match, flags document images with tamper and forgery indicators for manual review and keeps a result record for every verification. Licensees run it under their own brand.

01 / 07

Document capture and reading

Captures and reads passports, national identity cards and driving licences: machine-readable zone and visual zone extraction, and document type detection.

  • Passports, national identity cards and driving licences
  • Machine-readable zone extraction
  • Visual zone extraction
  • Document type detection
Specimen · TD1 machine-readable zone3 × 30 characters
<<<<<<<<<<<

Field

Document code

Raw
I<
Read as
Identity card (TD1)
Position
line 1, 1–2
Fields marked in green are check digits. Select one to see how it is computed.

Select any field of the specimen's machine-readable zone to decode it. The check digits are computed live with the ICAO 9303 method.

Illustrationdocument photo ↔ live selfie
DOCUMENT PHOTOLIVE SELFIE
Liveness Face match

02 / 07

Liveness and face match

Checks liveness on a live selfie and matches the face to the photo on the document.

  • Liveness check on a live selfie
  • Face match between the document photo and the selfie

03 / 07

Forgery and tamper detection

Image-level tamper and forgery indicators from noise-pattern analysis of document images; flags documents for manual review.

  • Noise-pattern analysis of document images
  • Proprietary models trained by Identivero
  • Flags documents for manual review

Try it below. Edit a field of the specimen, then drag the handle to compare the document with its noise residual or indicator map. This simplified version of the principle runs in your browser.

Simplified illustration · runs in your browser

Edit the specimen

DOCUMENTINDICATOR MAP

Date of birth changed: 12.08.1990 → 12.08.1984

04 / 07

Configurable verification flows

Which steps are on, in which order and with which thresholds, set per licensee and per use case: terms and consent, custom forms, email and phone verification, document reading, liveness and face match.

  • Terms and consent, with your own text and version
  • Custom forms, with your own fields
  • Email and phone verification by one-time code
  • Document reading, liveness and face match, with thresholds

Switch steps on and off, reorder them, add form fields and set thresholds. The configuration on the right follows your choices.

Use case
  1. Terms and consent
    your own terms text · version
  2. Custom form

    select a field to make it required

  3. Email verification
    one-time code · expires after
  4. Document capture and reading

    Tamper and forgery indicators · on indicators → manual review

  5. Liveness and face match
    face match threshold
  6. Phone verification
Flow configuration · simplified5 steps
  1. terms
  2. →form_data
  3. →email
  4. →document
  5. →liveness
  6. →result
{
  "use_case": "full-verification",
  "flow": [
    "terms",
    "form_data",
    "email",
    "document",
    "liveness"
  ],
  "modules": {
    "terms": {
      "version": "1"
    },
    "form_data": {
      "fields": [
        {
          "name": "full_name",
          "label": "Full name",
          "required": true
        },
        {
          "name": "customer_number",
          "label": "Customer number",
          "required": false
        }
      ]
    },
    "email": {
      "code_expiry_minutes": 10
    },
    "document": {
      "accept": [
        "passport",
        "id_card",
        "driving_licence"
      ]
    },
    "liveness": {
      "face_match": "standard"
    }
  },
  "policies": {
    "integrity": "manual_review"
  }
}

05 / 07

Results and audit trail

A result record per verification with time stamps, the steps performed and their outcomes; counters per licensee and per flow type; export in machine-readable form.

  • Time stamps, steps performed and their outcomes
  • Counters per licensee and per flow type
  • Machine-readable export

Verification

3f6c2a9e-41d7-4b0e-9c55-8e2b7d1a6f03

In progress
Licensee
your-company
Flow
full-verification
Started
10:42:03.118Z
Completed
—
  1. Document read

    Identity card · UTO · MRZ and visual zone

    10:42:06.214Z
  2. Liveness

    Live selfie captured

    10:42:13.580Z
  3. Face match

    Document photo ↔ selfie

    10:42:14.031Z
  4. Tamper and forgery indicators

    Document image analysed

    10:42:14.902Z
Counterslicensee: your-company flow: full-verification

06 / 07

Integration

A web flow the licensee embeds under its own brand; an API to start a verification and read its status and result; webhooks.

  • Web flow under the licensee's own brand
  • API: start, status, result
  • Webhooks

Type your brand name and pick a colour: the web flow on the right takes them on. The code shows the calls behind it.

Accent colour

Corners

Theme

// 1. Start a verification from your server
const res = await fetch("https://api.yourbrand.example/api/verifications", {
  method: "POST",
  headers: { "X-SDK-Key": process.env.VERIFY_KEY, "Content-Type": "application/json" },
  body: JSON.stringify({
    flow: ["document", "liveness"],
    return_url: "https://www.yourbrand.example/welcome",
  }),
});
const { verification_id } = await res.json();

// 2. Send the user to the web flow on your own domain
redirect(`https://verify.yourbrand.example/?verification_id=${verification_id}`);

07 / 07

Data handling

The licensee decides where data is processed and how long it is kept; an on-premise deployment keeps all data inside the licensee's infrastructure.

  • The licensee decides where data is processed
  • The licensee decides how long data is kept
  • On-premise: all data stays inside the licensee's infrastructure
On-premise deploymentall data stays inside
YOUR INFRASTRUCTUREWeb flowon your domain, your brandAPI and webhooksstart · status · resultVerification servicesflows, checks, result recordsMachine-learning servicesincluded in the deliveryStorageretention set by youYour usersYour systemsUpdates from Identiveroduring the licence term

Deployment

How it is deployed

On-premise

Delivered as containers for your own infrastructure, with the machine-learning services included. You operate it; Identivero delivers updates.

  • Containers
  • Machine-learning services included
  • Updates from Identivero

Hosted by Identivero

Available on request.

Licence

What a licensee gets

  • The running platform

    Containers for on-premise deployment, or hosted access.

  • Your own brand

    The web flow runs under the licensee's brand, for its own business and its own customers.

  • Documentation

    For deployment, configuration and integration.

  • Updates

    Updates during the licence term.

  • Second-line support

    Included. Custom development on separate terms.

  • A non-exclusive licence

    Per-transaction fee, under a written licence agreement. No source code.

In development: the Identivero Trust Platform.

An attestation and verification service with an EUDI-compatible digital identity wallet, built on the European Digital Identity architecture and reference framework and the OpenID for Verifiable Credentials protocols. Not yet available. Contact us if you would like to be informed when it is.