Spain eKYC non-doc verification leverages Spain's source of truth (Utility - Phone Register) to validate individuals. It is essential in eKYC processes for ensuring identity authenticity, regulatory compliance, and enhanced security. It helps prevent fraud, boosts user trust, and streamlines operations through automated and efficient verification methods.

Integration

User Input Flow

eKYC module configuration gives various options to specify different search criteria with various sources of truth for each country (eg. US has multiple via Telco, Credit Bureau, and Driver's License). User data can be collected via a user input flow by using pre-selected fields where users can type in their name or date of birth, etc. See an example below:

Module configuration

The module configuration can be leveraged to select the applicable fields for the input data you would like to collect from the end user.

Direct API Approach

All module configurations and user data can be forwarded directly in the request for performing an eKYC search. This will override existing configuration and data collected about the user.

📘

API Authentication

All endpoints require authentication headers to be specified as stated in Incode API Documentation

eKYC request

POST /omni/externalVerification/ekyc

This endpoint performs an eKYC check for the individual specified. Note: Endpoint can have empty body {} and in that case information will be pulled from module configuration and session details.

• source: (mandatory) String. Must be "ES_1".
• country: (mandatory) String. Two letter Alpha-2 country code. (Must be ES).
• taxID: (mandatory) In Spain, ID is 9-characters, consisting of 8 digits followed by a letter.
• firstName:: (mandatory) String. First name of the individual.
• middleName:: (optional) String.
• surName: (mandatory) String. Last name of the individual.
• houseNo: (optional) String. House number or building number.
• street: (optional) String. Name of the street.
• city: (optional) String. City of the individual's address. (eg. Madrid).
• state: (optional) String. (eg. Comunidad de Madrid)
• postalCode: (optional) String. postalCode formatted based on per-country postalCode basis.
• dateOfBirth: (optional) String. Format: yyyy-mm-dd (eg. 1980-06-01)
• phone: (optional) String.

Example Incode request:

{
    "plugins": "kyc", // mandatory
	  "source": "ES_1" , //mandatory
    "firstName": "Iker", //mandatory first_name refers to Nombre (First Name).
    "middleName": "", //optional - middle_name refers to Apellido1 (Father's last name).
    "surName": "Casillas ", //mandatory last_name refers to Apellido2 (Mother's last name).
    "houseNo": "45", //optional
    "street": "Calle de Alcalá", // optional
    "city" : "Madrid", // optional
    "state" : "Comunidad de Madrid", // optional
    "postalCode": "94014", // optional
    "country": "ES", //mandatory 
    "dateOfBirth" : "1991-08-02", // optional
    "phone": "612345678", // optional
    "idNum": "12345678Z" // mandatory DNI 
}

Direct API Response

📘

API Authentication

All endpoints require authentication headers to be specified as stated in Incode API Documentation

Note: Endpoint can have empty body {} and in that case information will be pulled from module configuration and session details.

Example Incode response:

{
    "kyc": [
        {
            "key": "firstNameMatch",
            "status": "Exact"; 
        },
        {
            "key": "middleNameMatch",
            "status": "Exact"
        },
        {
            "key": "lastNameMatch",
            "status": "Approximate Match"
        },
        {
            "key": "fullNameMatch",
            "status": "Fuzzy"
        },
        {
            "key": "dobMatch",
            "status": "Exact"
        },
        {
            "key": "streetMatch",
            "status": "Exact"
        },
        {
            "key": "cityMatch",
            "status": "Exact"
        },
        {
            "key": "stateMatch",
            "status": "Exact"
        },
        {
            "key": "postalCodeMatch",
            "status": "Exact"
        },
        {
            "key": "fullAddressMatch",
            "status": "Fuzzy"
        },
        {
            "key": "idNumMatch",
            "status": "Exact"
        },
        {
            "key": "phoneMatch",
            "status": "No Match"
        },
        {
            "key": "overallLevel",
            "status": "Low"
        }
    ]
}

eKYC error responses

Please refer to error response to see conventional HTTP response codes to indicate the success or failure of an API request. For Spain, custom 400 error messages if taxId, or country is “ “ or null:

message: taxId, and country are minimum required fields.

overallLevel

Overall Level is the API response key for the submitted name. The fields low, medium, and high are mapped to a proprietary fuzzy matching algorithm that is mapped to a score from 0 to 100.

As a default, overallLevel will return:

low: when fullNameMatch & idNumMatch are exact;

high: when fullNameMatch & idNumMatch are nomatch;

medium: for all otherwise combination of fullNameMatch & idNumMatch.

Single Session Dashboard Result