Government Database Check

The objective of the Government Database check is to provide additional confidence and assurance that the Information extracted from a government ID or document is real and valid by vetting it against an authoritative government source or database tied to the specific country of origin.

For example, this could involve validating a National ID number against an authoritative source, such as checking a Mexican CURP against the RENAPO (Registro Nacional de Población) database to confirm that the identity details provided are accurate and exist in the government registry.

These government database checks each connect to a specific, selected government database, and results depend on the accuracy and availability of the source. Some of these same databases may also be part of broader, multi-source checks—like eKYC or waterfall workflows—using the same provider (e.g., GDC or LSEG).

Other examples include validating Names, Date of Birth or National ID numbers from passports or ID cards against their respective issuing authorities. For example, the Government Database checks that, an Australian passport number is verified via the Document Verification Service (DVS), which is managed by the Australian Government Attorney General's Department.

Country-Specific Data and Biometric Verification

Some government checks require additional or specialized data or configuration. See the following:

Country	Data Check	Biometric Verification
Argentina	Renaper Check	Biometric Verification
Mexico	Credential Validation (Lista Nominal)	Mexican INE Data & Face Validation
	Mexican CURP Validation (Renapo)
Brazil	Brazilian CPF Number Check	CPF Biometric Verification
Colombia	Colombian Registraduria Check	-
Thailand	Thai DOPA Check	-
Peru	RENEIC Data Check	-
Other Countries	Contact Jumio Support

Refer to the figure below for a visual of how the Government Database check works.

Use Cases

Use Case 1

Extract the information from the ID document via Jumio’s ID Verification service and send the data to the pertinent authoritative data source to validate the information. Jumio will respond with a risk level of one of the following:

• Accept - Match
• Warning - Partial Match
• Reject - No Match

The risk level is sent to our customers with an overall decision and metadata pertaining to individual elements supplied.

Use Case 2

Customers provide personal information that they have collected from their consumers. Jumio provides an overall risk assessment based upon that information tied to the government database that it is configured to. Jumio will respond with a risk level of one of the following:

• Accept - Match
• Warning - Partial Match
• Reject - No Match

The risk level is sent to our customers with an overall decision and metadata pertaining to individual elements supplied.

Supported Credentials

The following values can be uploaded as Prepared Data. Alternatively, they can be extracted by an upstream capability in a workflow.

Details

Key	Type	Mandatory	Description
firstName	string	Yes	Optimal to include.
middleName	string	No	Middle name of the subject.
lastName	string	Yes	Optimal to include
dateOfBirth	LocalDate	No	Date of birth in YYYY-MM-DD format only
socialSecurityNumber	string	No	Either socialSecurityNumber, personalNumber or idNumber should be provided
personalNumber	string	No	Either socialSecurityNumber, personalNumber or idNumber should be provided
address	Object	No	Only the fields which are mentioned are required
address.line1	string	No	First line of the address.
address.line2	string	No	Second line of the address.
address.city	string	No	City of residence as it appears on the ID.
address.postalCode	string	No	Postal code AKA Zip code
address.subdivision	string	No	Subdivision AKA state
address.country	string	No	Country should be ISO Alpha 3 Code only
id	Object	No	See below
id.idNumber	string	Yes	Either socialSecurityNumber, personalNumber or idNumber should be provided
id.Type	string	conditional	Not required for all countries. Only required for countries where id Type is not sufficient. For more details, connect with Jumio Platform Integration Squad

Sample Prepared Data Body

{
    "firstName": "KARLA B***D",
    "lastName": "V***AVICENCIO ***",
    "dateOfBirth": "1***-04-27",
    "address": {
        "line1": "",
        "postalCode": "",
        "city": "",
        "subdivision": "",
        "country": "MEX"
    },
    "id": {
        "idNumber": "VIMK98**27MDFLN***",
        "type": "ID_CARD"


    }
}

Sample Response Body

"capabilities": {
"govtIdVerification": [
            {
"id": "f06b17ba-d760-4aac-9e43-59510ab0d928",
               "credentials": [
                   {
                       "id": "c0015c70-8518-4a6f-801e-ec71c230eb89",
                       "category": "ID"
                   }
               ],

               "decision": {
                   "type": "PASSED",
                   "details": {
                       "label": "OK"
                   }
               }

               "data": {
                   "country": "MEX",
                   "type": "ID_CARD",
                   "completeNameMatch": "MATCH",
                   "initialNameMatch": "MATCH",
                   "firstNameMatch": "MATCH",
                   "lastNameMatch": "MATCH",
                   "nationalIdMatch": "NOT_MATCH",
                   "dobDayMatch": "MATCH",
                   "dobMonthMatch": "MATCH",
                   "dobYearMatch": "MATCH",
                   "dobMatch": "MATCH",
                   "addressMatch": "NOT_MATCH",
                   "score": 10,                 }]
}

Decision Details Labels

Details

Decision Type	Label	Description
PASSED	LOW_RISK	No significant risk associated with the data.
REJECTED	HIGH_RISK	High risk associated with the data.
WARNING	MEDIUM_RISK	Moderate risk associated with the data.
NOT_EXECUTED	PERMISSION_DENIED	Cannot be executed because the required permissions or credentials are missing. Verify your API key and access rights.
NOT_EXECUTED	BAD_REQUEST	Malformed or missing required parameters. Ensure that all mandatory fields are included and correctly formatted before retrying.
NOT_EXECUTED	PRECONDITION_NOT_FULFILLED	Preconditions were not met to process the data.
NOT_EXECUTED	TECHNICAL_ERROR	There was an error in processing the request.

Data

Details

Parameter	Type	Values
Country	string	Country of Government Check
type	string	Type of ID used if applicable
completeNameMatch	string	Match, No Match
initialNameMatch	string	Match, No Match
firstNameMatch	string	Match, No Match
lastNameMatch	string	Match, No Match
nationalIdMatch	string	Match, No Match
dobDayMatch	string	Match, No Match
dobMonthMatch	string	Match, No Match
dobYearMatch	string	Match, No Match
dobMatch	string	Match, No Match
addressMatch	string	Match, No Match
score	int	10 - Pass, 20 - Warning, 30 - Reject

Portal View

Open a transaction in the Portal to review the response. The risk signal is labeled Government ID Verification as shown in the figure below.