Argentina Renaper Biometric Verification

Biometric Verification checks a Selfie provided by the end user against the photo on record with Renaper. The ID number and selfie are provided as inputs, along with name and gender data, and a decision on the risk is returned in the response.

Supported Credentials

The Renaper number can be uploaded as Prepared Data. Alternatively, it can be extracted by an upstream capability in a workflow. The Selfie can be uploaded through the API, or obtained as part of the customer journey.

To use the API to upload Prepared Data and the Selfie use workflow key 10093. The Selfie will be checked by the Usability capability prior to calling the biometricVerification capability.

To use Renaper Verification along with the standard Jumio IDIV service use workflow key 10094.

The following value can be uploaded as Prepared Data.

Details

Key	Type	Mandatory	Description
firstName	string	no	First name of the subject. Optimal to include
lastName	string	no	Last name of the subject. Optimal to include
middleName	string	no	Middle name of the subject.
sex	string	yes	M - Male / F - Female
address.country	string	yes	Country in ISO Alpha-3 format only, e.g., "ARG".
id	Object	yes	ID-related details
id.idNumber	string	yes	DNI number .

Response

Response data is available for transactions that include the risk signal. For information on transaction data see Viewing or Retrieving Workflow Transactions.

Example Response

"biometricVerification": [
            {
                "id": "4c9de7c7-0e91-4476-a303-dde196357ec5",
                "credentials": [
                    {
                        "id": "b0e79c4e-b0e9-4121-bc93-a67b8e1ffc85",
                        "category": "ID"
                    },
                    {
                        "id": "233641de-2a97-4764-9153-180308145a00",
                        "category": "SELFIE"
                    }
                ],
                "decision": {
                    "type": "WARNING",
                    "details": {
                        "label": "MEDIUM_RISK"
                    }
                },
                "data": {
                    "nameMatch": "MATCH",
                    "faceMatch": "PARTIAL_MATCH",
                    "idNumberMatch": "MATCH",
                    "genderMatch": "MATCH"
                }
            }

Decision Details Labels

Details

Decision Type	Label	Description
PASSED	LOW_RISK	The provided Selfie matches the photo on record.
REJECTED	HIGH_RISK	The provided Selfie does not match the photo on record.
WARNING	MEDIUM_RISK	It cannot be determined whether the Selfie matches the photo on record.
NOT_EXECUTED	TECHNICAL_ERROR	Verify the provided data is correct and retry, or contact Support.
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.

Data

Details

Key	Possible Values	Description
nameMatch	MATCH, NOT_MATCH	Indicates whether the concatenated firstName and lastName values provided in the input data exactly match the corresponding name stored in the Renaper database.
faceMatch	MATCH, NOT_MATCH, PARTIAL_MATCH	Indicates the result of the face comparison between the submitted selfie and the photo on record in the Renaper database. A PARTIAL_MATCH means some facial similarity was detected, but not enough to be considered a full match.
idNumberMatch	MATCH, NOT_MATCH	Indicates whether the identification number provided in the input data matches a valid identification number stored in the Renaper database.
genderMatch	MATCH, NOT_MATCH	Indicates whether the gender provided in the input data matches the gender stored in the Renaper database.

PII Fields Returned (DPA Restricted)

The following PII fields from the Argentina Biometric check API response will be returned ONLY for customers who have signed the updated Data Processing Agreement (DPA). This feature is disabled by default and must be explicitly enabled by Jumio. Please work with your Jumio account manager if you require this.

"data": {
                    "faceMatch": "MATCH",
                    "idNumberMatch": "MATCH",
                    "genderMatch": "MATCH",
                    "fullName": "MXXXX RXXXX",
                    "dateOfBirth": "YYYY-MM-DD",
                    "idNumber": "XXXXXX",
                    "taxId": "XXXXXXX",
                    "taxIdType": "CUIT",
                    "gender": "M"
}

Field Mapping (DPA Restricted)

Jumio Output	Description
fullName	Individual’s registered name
dateOfBirth	Date of birth on record
idNumber	Documento Nacional de Identidad (DNI)
taxId	Taxpayer identification number
taxIdType	Taxpayer type – CUIT or CUIL
gender	Gender (M = Male, F = Female)

Response Example with PII Fields

{
  "biometricVerification": [
    {
      "id": "f1a60eca-536f-4907-8661-8707a49d3df2",
      "credentials": [
        {
          "id": "bea35edd-92a3-4357-89a0-f7f7cc755c76",
          "category": "DATA",
          "label": "DATA"
        },
        {
          "id": "93bc29d7-20a5-41f5-9af5-8b3618a21667",
          "category": "SELFIE",
          "label": "SELFIE"
        }
      ],
      "decision": {
        "type": "PASSED",
        "details": {
          "label": "LOW_RISK"
        }
      },
      "data": {
        "faceMatch": "MATCH",
        "idNumberMatch": "MATCH",
        "genderMatch": "MATCH",
        "fullName": "MXXXXX RXXXX",
        "dateOfBirth": "YYYY-MM-DD",
        "idNumber": "12345678",
        "taxId": "12345678912",
        "taxIdType": "CUIT",
        "gender": "M"
      }
    }
  ]
}

warning

DNI numbers and names may be partially masked in logs and documentation examples to comply with data protection requirements.