Earlier in our docs is an overview of our Know Your Business here. Now, this page is focused specifically on eKYB in the Mexico (MX). eKYB in MX leverages the government sources of truth to validate the legitimacy of businesses, including their taxID (either Vat No or Reg No), business name and business address.

Note: Only available in Incode demo environment today, not available in production. If interested, please contact Incode's customer support.

Note: UBOs and Directors are not currently supported for MX. If interested, contact our support team.

Integration

User input flow

Note: Only postal code verification is available in Mexico eKYB Lite.

Module Configuration

Module configuration gives various options to specify different KYB criteria you would like to check (eg. Business name, Business Address, and Business taxID).

Note: Only postal code verification is available in Mexico eKYB Lite.

Direct API Approach

All module configurations and user data can be forwarded directly in the request for performing an KYB 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

KYB request

POST /omni/externalVerification/ekyb

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

• plugins: must be["ekyb"]: (mandatory)
• businessName:: (mandatory) String. Name of the business.
• postalCode: (mandatory) String. postalCode formatted based on per-country postalCode basis. (MX has 5 digits long postal codes)
• country: (mandatory) String. Two letter Alpha-2 country code. (Must be MX)
• taxId: (mandatory) String. Tax ID of the business (RFC): Acceptable formats: Individual - 13 characters (4 letters, 6 numbers, 3 letters); Business - 12 characters (3 letters, 6 numbers, 3 letters)

Note: The country parameter is used to limit business validation to that specific region. We will only validate a business established in the country selected in the eKYB request.

REQUEST FORMAT EXAMPLE
{
  "plugins" : ["ekyb"], //required field
  "businessName" : "Aerolíneas del Sureste S.A. de C.V.", //required field
  "postalCode" : "03800", // required field
  "country" : "MX", //required field
  "taxId" : "ASU1003149Z1", //required field
}

Response

All module configurations and user data can be forwarded directly in the request for performing an eKYB 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

RESPONSE EXAMPLE

"kyb": [
    {
      "key": "name",
      "sub_label": "Verified"
    },
    {
      "key": "tin",
      "sub_label": "Verified",
    },   
    {
      "key": "postalCodeMatch",
      "sub_label": "Verified"
    },
    {
      "key": "registrationStatus",
      "sub_label": "Active"
    },
  	{
      "key": "entityType",
			"sub_label": "S.A. de C.V."
		}
}

KYB error responses

Please refer to error response to see conventional HTTP response codes to indicate the success or failure of an API request.

Custom 400 error messages if businessName, taxId, or country is “ “ or null:

message: businessName, taxId, and country are minimum required fields.

Single Session Dashboard Results

They are available on Single Session view under Business tab