Configuring Mitek

Mitek is a data provider you can use to run the ID verification (PassFort collects documents) check.

How it works

This is the default behaviour for a variant of the ID verification (PassFort collects documents) check with Mitek as the data provider. We support Mitek’s Mobile Verify- Auto product. 

You can upload one of the following documents for an individual to Mitek:

  • Driving Licence
  • Passport
  • State ID
  • Residence ID
  • Unknown (You can select Unknown if the document type is not known, Mitek will perform a check to determine the type of documentation provided.)
The document size limit is 5MB. The following file types are accepted: JPG, JPEG, PNG, HEIC.

Mitek checks for signs of forgery and extracts the following information from the documents:

  • Address
  • Name
  • Date of birth
  • Nationality
  • Gender
  • Document number
  • Date of expiry
  • Date of issue
  • Issuing country
    Issuing countries supported
    ABW, AFG, AGO, AIA, ALA, ALB, AND, ARE, ARG, ARM, ASM, ATF, ATG, AUS, AUT, AZE, BDI, BEL, BEN, BFA, BGD, BGR, BHR, BHS, BIH, BLR, BLZ, BMU, BOL, BRA, BRB, BRN, BTN, BVT, BWA, CAF, CAN, CCK, CHE, CHL, CHN, CIV, CMR, COD, COG, COK, COL, COM, CRI, CUB, CXR, CYM, CYP, CZE, DEU, DJI, DMA, DNK, DOM, DZA, ECU, EGY, ERI, ESH, ESP, EST, ETH, FIN, FJI, FLK, FRA, FRO, FSM, GAB, GBR, GEO, GGY, GHA, GIB, GIN, GLP, GMB, GNB, GNQ, GRC, GRD, GRL, GTM, GUF, GUM, GUY, HKG, HMD, HND, HRV, HTI, HUN, IDN, IMN, IND, IOT, IRL, IRN, IRQ, ISL, ISR, ITA, JAM, JEY, JOR, JPN, KAZ, KEN, KGZ, KHM, KIR, KNA, KOR, KWT, LAO, LBN, LBR, LBY, LCA, LIE, LKA, LSO, LTU, LUX, LVA, MAC, MAF, MAR, MCO, MDA, MDG, MDV, MEX, MHL, MKD, MLI, MLT, MMR, MNE, MNG, MNP, MOZ, MRT, MSR, MTQ, MUS, MWI, MYS, MYT, NAM, NCL, NER, NFK, NGA, NIC, NIU, NLD, NOR, NPL, NRU, NZL, OMN, PAK, PAN, PCN, PER, PHL, PLW, PNG, POL, PRI, PRK, PRT, PRY, PSE, PYF, QAT, REU, ROU, RUS, RWA, SAU, SDN, SEN, SGP, SHN, SJM, SLB, SLE, SLV, SMR, SOM, SPM, SRB, SSD, STP, SUR, SVK, SVN, SWE, SYC, SYR, TCA, TCD, TGO, THA, TJK, TKL, TKM, TLS, TON, TTO, TUN, TUR, TUV, TWN, TZA, UGA, UKR, UMI, URY, USA, UZB, VAT, VCT, VEN, VGB, VIR, VNM, VUT, WLF, WSM, YEM, ZAF, ZMB, ZWE

  • MRZ
    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.

You are required to submit documents via our portal or the API and then instruct the check. This is compatible with Mitek’s SDK. Contact Mitek to learn more.

PassFort cross-references the extracted data provided by Mitek with the details recorded in the individual’s profile (name, date of birth, nationality, and gender). If the check was run with PROOF_OF_ADDRESS as the document category, the address is also cross-referenced.

PassFort imports an image of the documents to the task on the profile.

The check passes when all three criteria are met:

  1. The document details obtained from Mitek match the details in the profile.
  2. Mitek confirms the document is authentic.
  3. Mitek confirms that the selfie check has passed.

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

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

To get step-by-step instructions for running this check, see Verify a document.

Configuration options

The following configuration options are available:

  • API environment: Choose the API environment you want to use. This will be either production or a sandbox environment.
  • API region: Choose the API region you want to use. If you selected the direct agreement option, you need to use a different group of credentials for each region. Contact Mitek about setting up a direct agreement.
  • Biometric verification: Add a biometric verification to the check. If you select this option, you need to send a selfie for each verification.
    • If this option is selected and a selfie is not sent, the check will error.
    • If this option is not selected and a selfie is sent, the check will error.

What we'll need

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

If you have a direct agreement, we’ll also need to know your Mitek client identifier and secret. This information is provided by Mitek.

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

Optional profile fields

These are the optional profile details matched with the document details extracted by Mitek:

Name

Description

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

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

Surname (personal_details.name.family_name)

The individual's last name.

Date of birth (personal_details.dob)

The individual's date of birth.

Gender (personal_details.gender)

The individual's gender. Leave unset for non-binary genders.

Address (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.

Nationality (personal_details.nationality)

The individual’s country of nationality.


How did we do?


Powered by HelpDocs (opens in a new tab)