Configuration of Verification Providers

This document describes configuration of providers for personal identity document verification and user presence check.

Document Verification

The document verification process is currently supported for following providers:

• ZenID - use value zenid in configuration
• Innovatrics - use value innovatrics in configuration
• Mock - useful for simple testing and local runs - use value mock in configuration

ZenID

API key

The authorization of all API calls is secured by an API key value. It has to be sent as the Authorization: api_key VALUE header value. Check the bottom of the Manual/Configuration page for more details.

The API key value can be configured/get from the Access page configuration:

• Role to be granted: ApiFull
• Condition: ApiKeyEqualsValue
• Value: the value here is the value of the API key

Validators

It is recommended to create a custom validation profile. The sensitivity of selected validators can be tuned-up or disabled completely at the Sensitivity page. The profile can be then set as the default or specified in the configuration properties.

SDK Initialization

When calling document-verification/init-sdk following implementation fields are used:

• Init token - send a token value sdk-init-token in the request body attributes map field
• SDK response - receive the value under zenid-sdk-init-response from the response attributes map field

Innovatrics

Innovatrics documentation for developers can be found at this link.

OCR Threshold

During a document validation Innovatrics provides a list of fields extracted from the document, that have OCR confidence lower than configurable threshold. If the list is not empty, there is a high probability that some information is read incorrectly. For that reason, this document will be rejected. The OCR confidence threshold is 0.92 by default, and can be tuned using innovatrics.dot.dis.customer.document.inspection.ocr-text-field-threshold.

Text Consistency

For each document Innovatrics tries to read visual zone, machine-readable zone and barcode. These isolated parts are cross-checked during a document validation by Innovatrics. If there are inconsistency between visual zone and machine-readable zone, or between visual-zone and barcode, the document will be rejected. However, some editions of identification documents are inconsistent by design. To prevent false rejection of those document modify the configuration.
Following example excludes issuingAuthority field of Czech identity card 2005 edition from text consistency check:

innovatrics:
  dot:
    dis:
      customer:
        document:
          inspection:
            text-consistency-check:
              CZE_identity-card_2005-01-01:
                exclusions:
                  - issuingAuthority

The format of the document name is {country}_{type}_{edition} according to the response of /metadata request.

Presence Check

The document verification process is currently supported for following providers:

• iProov - use value iproov in configuration
• Innovatrics - use value innovatrics in configuration
• Mock - useful for simple testing and local runs - use value mock in configuration

iProov

There are a few needed configuration changes to bring a successful integration. All the following configuration tuning has to be requested from the iProov’s support team on a per-service basis:

• presence check image
  • an accepted person image from finished and successful presence check process
  • requires enabling of the frame response feature for /api/v2/claim/verify/validate
• failure reason
  • a more detailed description of the presence check failure
  • requires enabling of the reason response feature for /api/v2/claim/verify/validate