🇲🇽 Mexico
Mexico onboarding has jurisdiction-specific identity and documentation requirements that should be validated early in integration.
Exchange profile
| Field | Value |
|---|---|
| Exchange | MEXICO |
| Main fiat currency | MXN |
| Typical local rails | Bank transfer |
Identity rules (legalId)
legalId)In Mexico, supported legal IDs are:
CURPRFC
Accepted formats:
- CURP:
/^[A-Za-z]{4}[0-9]{6}[HMhm][A-Za-z]{5}[A-Za-z0-9][0-9]$/ - RFC:
/^[A-Za-zÑñ&]{4}\d{2}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])[A-Za-z0-9]{3}|[A-Za-zÑñ&]{3}\d{2}(0[1-9]|1[0-2])(0[1-9]|[12]\d|3[01])[A-Za-z0-9]{3}$/
CURP is also validated with additional checksum/state/date checks.
Documentation requirements
Identity images are required according to onboarding/limit controls.
Use Upload Identity Image for signed upload URLs.
Payload guidance
Validate at least:
legalIdexchange: "MEXICO"name,surname,sexbirthDate,phoneNumber,nationality,maritalStatusaddress.street
Request example
{
"externalId": "user-MEX",
"email": "[email protected]",
"legalId": "hecj720131hdfrnv00",
"type": "INDIVIDUAL",
"exchange": "MEXICO",
"personalData": {
"name": "MARTHA",
"surname": "ECHEVERRY PULGARIN",
"sex": "M",
"work": "SERVICIOS RELACIONADOS CON LA SALUD HUMANA N.C.P.",
"birthDate": "1990-01-01",
"isPep": false,
"isFacta": false,
"isFep": false,
"phoneNumber": "511110442881",
"nationality": "Mexico",
"maritalStatus": "Soltero",
"address": {
"street": "Alfeñique 32 180",
"postalCode": "01549",
"locality": "Alvaro Obregon",
"province": "Ciudad de Mexico",
"numeration": "1",
"floor": "-",
"apartment": ""
}
},
"banking": {
"accounts": [
{
"cbu": "638180000132628778",
"currency": "MXN",
"description": "Cta MXN"
}
]
}
}Virtual accounts
Mexico supports virtual accounts in MXN over CLABE rails. Once the user is ACTIVE, assign one with:
{
"userAnyId": "100009792",
"asset": "MXN",
"externalId": "user-acc-mxn-001"
}Foreign legalIdNationality is allowed. See POST /wallet/v1/user-actions/assign-virtual-account.
Deposit address
Each user can get a permanent deposit address for ramps: an individualized CLABE, assigned only to that user but not held in their name. Assign it once the user is ACTIVE; deposits the user sends to it are credited to their balance.
{
"userAnyId": "100009792",
"asset": "MXN",
"externalId": "user-dep-mxn-001"
}See POST /crypto/v2/user-actions/assign-deposit-address.
Example entrypoint
Then use missing-data and onboarding-task endpoints to complete remaining requirements before operating.
Updated 27 days ago