KYC in Mexico
Galileo clients who operate in Mexico and who have chosen Galileo as their BIN sponsor have special KYC requirements, different from the requirements in the United States and Canada. This page explains how to meet those requirements on the Galileo platform.
Enrollment fields
We have added these fields to accommodate Mexico KYC requirements. You can find these new input parameters as follows:
| Request parameter | Definition |
|---|---|
id3 | Contains the tertiary ID value |
idType3 | Specifies the type of ID in id3 |
kycRefNo | Identifier from the KYC process |
nationality | Current citizenship of the applicant |
placeOfBirth | Birthplace of the applicant, in ISO 3166 format |
curp | CURP identifier |
politicalAffiliation | Whether the applicant is a PEP |
Note
As input parameters for the API, these fields are optional by default, but you can set the PINED parameter to make some or all of them required for Create Account and Update Account. Making these fields required is obligatory only when Galileo is your BIN sponsor.
Using the ID fields
Mexican clients can pass up to four official identifiers in the Create Account endpoint:
idid2id3curp
These idTypes are specific to Mexico. You may use other idTypes, as appropriate:
- 6 — Matrícula Consular number
- 16 — RFC tax ID
- 17 — INE number
Note
For all Mexico-specific identifiers, Galileo validates the input according to the regex, but Galileo does not contact the issuing authority to verify that the ID corresponds to the applicant. Clients are responsible for performing that type of verification before calling Create Account.
See Using the id and idType parameters for the rules that apply to id and id2. The id3 field has most of the same usage rules as id2. In summary:
id | id2 and id3 |
|---|---|
| Masked in the RDFs | id2 is not masked in the RDFs, and id3 is not included in the RDFs |
| Used as a search parameter for Get Account by ID | Not valid as search parameters |
| Cannot be used to specify card art | id2 can be used to specify card art but id3 cannot |
Because Galileo does not use any of the ID fields to conduct KYC/CIP when it is the BIN sponsor, you can decide which ID to put in each ID field. Galileo strongly recommends that you be consistent. For example, you might decide to populate the ID fields like this:
| Parameter | Value |
|---|---|
id | {INE number} |
idType | 17 |
id2 | {RFC tax id} |
idType2 | 16 |
id3 | {Passport number} |
idType3 | 4 |
By passing the same ID types in the same fields with each endpoint call, the Galileo database will be consistently populated.
Note
Because you are not using Galileo's integrated KYC process, make sure there is no value set for VALID or VLDLV; otherwise, you must populate
idwith unique values.
Creating accounts
Only the Create Account endpoint has the Mexico-specific parameters for input. The other enrollment endpoints (Start Enrollment, Create Virtual Card Account) do not have them. You can update these parameters with the Update Account endpoint.
To enroll a new customer with the Program API, follow the instructions in Creating an Account with these differences:
- The "Create Account using Galileo CIP" workflow is not valid for your use case; instead, consult Create Account using your own CIP.
- Use these new Parameters as follows:
| Parameter | Usage |
|---|---|
id3 | Identifier for the tertiary form of ID |
idType3 | Type of identifier in id3 |
locale | es_MX. en_MX. |
| Name parameters | |
| Address parameters | address1 cannot be a P.O. box. To disable this default, set the EAPOB parameter. |
cipStatus | Do not pass this parameter |
kycRefNo | Pass the reference number from your KYC process to link to the customer record in the Galileo system. |
monthlyIncome | The monthly income of the applicant. |
nationality | Current country where the applicant is a citizen. |
placeOfBirth | Birthplace of the applicant, in ISO 3166 format. For Mexican localities, use the format XX-XXX as shown here. |
curp | CURP identifier. |
politicalAffiliation | Whether the applicant is a PEP |
Updated about 18 hours ago
