Netverify to Jumio Platform Transaction Data Mapping

The data model for Jumio Platform transactions is different from the data model for Netverify ID verification transactions. In general, the Jumio Platform data is more complex than the Netverify data, reflecting the additional workflow steps and capability options that are available in the Jumio Platform. The purpose of this document is to provide a mapping from common fields and values in the Netverify data to corresponding fields and values in the Jumio Platform data, to help facilitate the transition from the former to the latter.

Callbacks

Jumio Platform callbacks do not include decision details about the transaction. They are intended to convey whether or not the workflow completed, and provide other metadata. All details about the transaction can be obtained by calling the retrieval APIs.

Retrieval API Responses

A Netverify ID verification transaction includes an overall status result and details including:

  • Transaction metadata.
  • Document data describing the scanned or uploaded documents, including the status and reject reasons if applicable.
  • Verification data describing whether or not the selfie matches the document, and any reject reasons.

Jumio Platform transactions execute:

  • A defined workflow consisting of a sequence of steps.
  • The workflow is passed a set of credentials, including any scanned or uploaded documents and the selfie, which are then passed to each step in turn.
  • Each step is implemented by one or more capabilities that perform some specific task. Each capability evaluates the credentials and generates decision data.

The workflow renders an overall decision based on the cumulative results of the decisions rendered by each capability.

The mappings in the following section identify the data fields in the Jumio workflows and capabilities that most directly correlate with the transaction, document, and verification fields in the Netverify transactions.

For example, a typical Netverify transaction includes a “document” object with fields for the values extracted from the scanned or uploaded document:

Copy
Netverify Document Object
"document": {
        "type": "DRIVING_LICENSE",
        "dob": "1990-01-01",
        "expiry": "2022-12-31",
        "firstName": "FIRST NAME",
        "issuingCountry": "AUT",
        "issuingDate": "2013-01-01",
        "lastName": "LAST NAME",
        "number": "123456789",
        "status": "APPROVED_VERIFIED"
    },

In a Jumio Platform transaction, the corresponding values are in a nested object for a capability called “extraction” that is contained in a top-level “capabilities” array:

Copy
Capabilities Array
"capabilities": {
        "extraction": [
            {
                "id": "1a11111-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
                "credentials": [
                    {
                        "id": "33333333-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
                        "category": "ID"
                    }
                ],
                "decision": {
                    "type": "PASSED",
                    "details": {
                        "label": "OK"
                    }
                },
                "data": {
                    "type": "PASSPORT",
                    "subType": "E_PASSPORT",
                    "firstName": "JANE",
                    "lastName": "DOE",
                    "dateOfBirth": "1990-01-01",
                    "expiryDate": "2023-12-01",
                    "issuingDate": "2014-01-01",
                    "documentNumber": "xxxxxxxx",
                    "personalNumber": "<<<<<<<<<<<<<<",
                    "address": {
                        "country": "AUT",
                        "formattedAddress": "AUT"
                    }
                }
            }
        ],

Similarly, the Netverify transaction includes a “verification” object that includes a nested “identityVerification” object with values for “similarity” and “validity” that provide the results of the comparison of the selfie to the picture on the photo ID:

Copy

Netverify Verification Object

"verification": {
        "identityVerification": {
            "similarity": "MATCH",
            "validity": "true"
        }
}

In the Jumio Platform transaction, each scan or uploaded document in the transaction is passed to a set of capabilities, depending on the type of scan or document. The selfie is passed to a capability called “liveness” that provides a “decision” object with a nested “details” object that contains a “label” value corresponding to the Netverify “similarity” value:

Copy

Jumio Platform Liveness Capability Object

"capabilities": {"liveness": [
    {
        "id": "fdf7a6f2-2905-45da-a4ec-587d590795cc",
        “validFaceMapForAuthentication”: “https://retrieval.emea-1.jumio.link/api/v1/accounts/3dceeccd-d364-4c16-8769-514a8f76bb89/credentials/f518e6c4-20b1-4d66-b1d1-92b9face8bf0/parts/FACEMAP”,
        "credentials": [
            {
                "id": "6760a8e4-f1ee-4209-a43c-5e66526ac166",
                "category": "SELFIE"
            },
            {
                "id": "09cc66aa-03d2-4951-b38d-bbd07d6998fd",
                "category": "FACEMAP"
            }
        ],
        "decision": {
            "type": "REJECTED",
            "details": {
                "label": "LIVENESS_UNDETERMINED"
            }
        },
        "data": {
            "type": "JUMIO_STANDARD"
        }
    }
],

The tables in the following section provide specific mappings between values in the Netverify transactions and the Jumio Platform transactions.

Status and Reason Mappings

The rows in the following tables show the corresponding Netverify and Jumio Platform values: