Configuring Jumio Netverify

Jumio Netverify is a data provider you can use to run these checks:

  • ID verification (PassFort collects documents)
  • ID verification (service collects documents)

ID verification (PassFort collects documents)

How it works

This is the default behaviour for a variant of the ID verification (PassFort collects documents) check with Jumio Netverify as the data provider.

You upload the individual's document to PassFort. PassFort submits the document to Jumio Netverify who checks for signs of forgery and extracts the customer’s name, date of birth, document number and, where possible, nationality from the document.

You can upload these documents for the Verify identity task:

  • Driving licence
  • Passport
  • Visa
  • State ID
  • Residence ID
  • Unknown (You can select Unknown if the document type is not known, Jumio Netverify will perform a check to determine the type of documentation provided.
The document must be no larger than 15 MB and in either JPG or PNG file types.

Jumio Netverify performs image quality checks and the following security checks on documents:

  • Compromised document
  • Visual authenticity

PassFort cross-references the details recorded in the individual’s profile (name, date of birth, and, if available, nationality) with the extracted data provided by Jumio Netverify.

An image of the document is displayed in the check results.

The check passes when all three criteria are met:

  • The document details obtained from Jumio Netverify match the details in the profile.
  • Jumio Netverify confirms the document is authentic by confirming the status of the check is Clear.
  • Jumio Netverify confirms that any additional checks have passed.

If the individual's details do not match Jumio Netverify's data, the check fails.

Because cross-referencing the individual’s details is an action performed in PassFort and not in Jumio Netverify, it’s possible for the check to pass in Jumio Netverify but fail in PassFort.

If the individual’s profile doesn’t have data for the required fields, an error is displayed.

This check variant is supported for all countries. To get step-by-step instructions for running this check, see Verify a document.

Configuration options

The following configuration option is available:

API region: Choose the API region you want to use. Contact Jumio Netverify about setting up a direct agreement.

What we’ll need

Let us know that you’d like to add a variant of the ID verification (PassFort collects documents) and your Jumio Netverify API credentials. We’ll set it up for you.

Testing your configuration

Once the check variant is configured, create different profiles in your demo environment to test whether it's working as expected.

To get a PASSED result, check that the ID is authentic and the document details in the demo environment match profile details.

Create an individual profile with these details:

  • First name: Alex  
  • Surname: Wheeler.
  • Date of birth: 01 January 2000

Expected result: DOCUMENT_ALL_PASS

To get a FAILED result, use the example where the DOB entered is different from the details in the demo environment.

Create an individual profile with these details:

  • First name: Ashley 
  • Surname: Williams
  • Date of birth: 30 June 1980

Expected result: DOCUMENT_DOB_FIELD_DIFFERENT

Profile fields

These are the profile details matched with the document details extracted by Jumio Netverify:

Name

Description

First name(s) (personal_details.name.given_names)

Required

The individual’s first and, if applicable, middle names.

Surname (personal_details.name.family_name)

Required

The individual’s last name.

Date of birth (personal_details.dob)

Required

The individual’s date of birth.

Expiry

Optional

The expiry date of the documentation.

Issuing country

Optional

The country that issued the documentation.

Number

Optional

The documentation's unique number, i.e. a passport number.

ID verification (service collects documents)

How it works

This is the default behaviour for a variant of the ID verification (service collects documents) check with Jumio Netverify as the data provider.

The individual submits their documents to Jumio Netverify who checks for signs of forgery and extracts the individual’s name, date of birth, and, where possible, address history from the documents.

PassFort cross-references the extracted data provided by Jumio Netverify with the details recorded in the individual's profile (name and, where possible, date of birth and gender; if the check was run with PROOF_OF_ADDRESS as the document category, the address is also cross-referenced).

PassFort displays an image of the documents in the check results.

The check passes when all three criteria are met:

  1. The document details obtained from Jumio Netverify match the details in the profile.
    About MRZ validation
    PassFort performs MRZ validation as part of the check. On the identity page of your passport, the MRZ is the machine readable zone that cameras and software can quickly read. It contains two rows of 44 characters each. The characters used are A-Z and 0-9, demarcated with < separators. We extract the following fields from the MRZ:
    • issuing_country

    • issuer

    • nationality

    • given_names

    • family_name

    • When the MRZ has names with single separators only, the name components on the MRZ will be compared to the full name (given names and surname combined) on the PassFort profile.
    • dob

    • gender

    • number

    • expiry

    • Additionally, we mark the MRZ itself as invalid if any of the checksums fail or none of the above fields are found. This validation is enabled by default for the specific providers that return the MRZ details.
  2. Jumio Netverify confirms the documents are authentic.
  3. Jumio Netverify confirms that any additional checks have passed (e.g. police checks or selfie checks).

If the individual’s details do not match the data in Jumio Netverify’s sources, the check fails.

Because cross-referencing the individual’s details is an action performed in PassFort and not in Jumio Netverify, it’s possible for the check to pass in Jumio Netverify but fail in PassFort.

If the individual’s profile doesn’t have data for the required fields, an error is displayed.

This check variant is supported for all countries.

For more information about how Jumio Netverify handles this check, see Jumio Netverify’s documentation.

Configuration options

You can choose from the following configuration options:

  • Check the individual's nationality against the one extracted from the document (optional): When this option is selected, PassFort always cross-references the country of nationality recorded in the individual’s profile against the country of nationality that Jumio Netverify extracted from the document. If the country of nationality does not match, the check fails. If the profile does not have a country of nationality, an error is displayed.
  • Require full date of birth (year, month and day) to run the check (optional): When this option is selected, the full date of birth must be provided in the profile to run the check. When deselected, a partial date of birth (i.e. year and month or just year) can be used.

What we'll need

Let us know that you’d like to add a variant of the ID verification (service collects documents) check with Jumio Netverify and which configuration options you'd like to use. We’ll set it up for you.

We’ll also need to know:

  • Your Jumio Netverify API token and secret: For more information about getting your API token and secret from the Customer Portal, see Jumio Netverify’s Implementation Guide.
  • Your user agent: This is a way to identify that PassFort is making the request. We suggest using "PassFort" as your user agent, but it can be anything you want.
  • Your data centre location: Whether your Jumio Netverify data centre is inside or outside the European Union.

Testing your configuration

Once the check variant is configured, follow these steps in your demo environment to test whether it's working as expected.

  1. Does the check pass when the ID is authentic and the extracted document details obtained from Jumio Netverify match the details in the profile?

To run this test, first create an individual profile with an address.

You also can create a profile via the portal. To get the profile ID (used to run the check in the next step), view the profile in the portal and copy the string of letters and numbers displayed after /onboarding/ in the URL.

Next, run the check variant by making the following request to the following endpoint.

Request endpoint:

POST https://api.passfort.com/4.0/profiles/{profile_id}/checks

Request body:

{
"check_type": "DOCUMENT_FETCH",
"source": "JUMIO",
"reference": "1a4be3fb-aed6-6ca7-abcd-000000000000",
"task_ids": [
"de9b6b92-9937-11e7-b7d2-000000000000"
]
}
Replace the ID in `task_ids` with the actual task ID for your profile.

Response:

{
"check_type": "DOCUMENT_FETCH",
"deadline": "2019-08-09 13:45:25",
"id": "7156af42-b850-11e9-a7bd-1607eb36f19c",
"input_data": {
"address_history": [...],
"entity_type": "INDIVIDUAL",
"personal_details": {...}
},
"instructed_on": "2019-08-06 13:45:24",
"performed_on": "2019-08-06 13:45:25",
"providers": [...],
"reference": "1a4be3fb-aed6-6ca7-abcd-000000000000",
"source": "JUMIO",
"started_on": "2019-08-06 13:45:25",
"state": "RUNNING",
"task_ids": [
"d85c9994-b83a-11e9-b01b-e25efdb1a546"
],
"variant": {...}
}

The check is working as expected if:

  • The response above is returned.
  • The check has passed (in the portal, the check is marked Passed)
  • This image is displayed in the portal as the image of the ID in the check results:
  1. Does the check fail when the ID is not authentic?

To run this test, first create an individual profile.

You can create a profile via the portal. To get the profile ID (used to run the check in the next step), view the profile in the portal and copy the string of letters and numbers displayed after /onboarding/ in the URL.

Next, run the check by making a request to the following endpoint.

Request endpoint:

POST https://api.passfort.com/4.0/profiles/{profile_id}/checks

Request body:

{
"check_type": "DOCUMENT_FETCH",
"source": "JUMIO",
"reference": "fail",
"task_ids": [
"de9b6b92-9937-11e7-b7d2-000000000000"
]
}

Response:

{
"check_type": "DOCUMENT_FETCH",
"deadline": "2019-08-09 14:01:05",
"id": "a1b12798-b852-11e9-a526-aa8185f0a88e",
"input_data": {
"address_history": [...],
"entity_type": "INDIVIDUAL",
"personal_details": {...}
},
"instructed_on": "2019-08-06 14:01:05",
"performed_on": "2019-08-06 14:01:05",
"providers": [...],
"reference": "fail",
"source": "JUMIO",
"started_on": "2019-08-06 14:01:05",
"state": "RUNNING",
"task_ids": [
"d85c9994-b83a-11e9-b01b-e25efdb1a546"
],
"variant": {...}
}

The check is working as expected if:

  • This response above is returned.
  • The check has failed (when you view the check in the portal, the check is marked Failed and the error message is: “Your check provider failed this document check”)
  • This image is displayed in the portal as the image of the ID in the check results:

Profile fields

These are the profile details matched with the document details extracted by Jumio Netverify:

Name

Description

First name(s) (personal_details.name.given_names)

Required

The individual’s first and, if applicable, middle names.

Surname (personal_details.name.family_name)

Required

The individual’s last name.

Date of birth (personal_details.dob)

Required

The individual’s date of birth.

Addresses (address_history)

Required when the check was run with PROOF_OF_ADDRESS as the document category; not used when the check was run with PROOF_OF_IDENTITY as the document category

The individual’s address history.

If you’re running the check via the API, the ID verification check also uses the following keys:

Key name

Value

Description

source

Required

JUMIO

The provider that the results are retrieved from. In this case, the provider is Jumio.

reference

Required

Sample value: 6bba3592-d9de-1ee5-8e97-ba8d8d13c558

Learn how to get the scanReference.

The reference ID the data provider is using for the document. In this case it’s the scanReference provided by Jumio.

To learn how to run this check via the API, see Run a Document fetch check (API).


How did we do?


Powered by HelpDocs (opens in a new tab)