🇦🇷 Argentina
Argentina onboarding has specific identity and documentation rules that should be validated early in integration.
Exchange profile
| Field | Value |
|---|---|
| Exchange | ARGENTINA |
| Main fiat currencies | ARS, USD |
| Typical local rails | Bank transfer and QR 3.0 context |
Identity rules (legalId)
legalId)In Argentina, legalId can be sent as either:
CUIT/CUILDNI(pseudo legalId when enabled)
Accepted formats:
- CUIT/CUIL:
/^\d{2}-?\d{8}-?\d{1}$/ - DNI:
/^[\d]{1,3}\.?[\d]{3}\.?[\d]{3}$/
CUIT is also validated with checksum rules in addition to regex format.
Documentation requirements
Users must upload identity document images:
- front side
- back side
The standard document is the DNI (Documento Nacional de Identidad). Passport images are also accepted for identity upload.
Important: Because passports only have one side, you must upload the same passport image twice — once with
side: "FRONT"and once withside: "BACK". Both uploads are required for identity validation to complete.
However, the core identity verification in Argentina is based on the CUIT/CUIL (tax ID), which is validated against official records regardless of the physical document type uploaded.
Use Upload Identity Image to generate signed upload URLs.
Identity data auto-population
For Argentine users, identity data is pulled automatically from official records using the CUIT/CUIL. This means most personal data fields (name, surname, birthDate, sex, work, etc.) are populated without integrator input.
Use GET /crypto/v2/stats/onboarding/missing-personal-data/:userAnyId to check if any fields still need to be submitted manually.
Payload guidance
For onboarding in Argentina, validate these fields carefully:
legalId— CUIT or CUIL formatexchange: "ARGENTINA"- personal identity/compliance fields (
isPep,isFep,isFacta,phoneNumber,nationality) address.street
Request example
{
"externalId": "user-ARG",
"email": "[email protected]",
"legalId": "20300000009",
"type": "INDIVIDUAL",
"exchange": "ARGENTINA",
"personalData": {
"name": "JOHN",
"surname": "DOE",
"sex": "M",
"work": "SERVICIOS RELACIONADOS CON LA SALUD HUMANA N.C.P.",
"birthDate": "1990-01-01",
"isPep": false,
"isFacta": false,
"isFep": false,
"phoneNumber": "1100000000",
"nationality": "Argentina",
"maritalStatus": "Soltero",
"address": {
"street": "AV. SIEMPRE VIVA",
"postalCode": "1000",
"locality": "CIUDAD EJEMPLO",
"province": "BUENOS AIRES",
"numeration": "1",
"floor": "-",
"apartment": ""
}
},
"banking": {
"accounts": [
{
"cbu": "0000000000000000000000",
"currency": "USD",
"description": "Cta USD"
},
{
"cbu": "0000000000000000000001",
"currency": "ARS",
"description": "Cta ARS"
}
]
}
}Virtual accounts
Argentina supports virtual accounts in ARS over CVU rails. Once the user is ACTIVE, assign one with:
{
"userAnyId": "100009791",
"asset": "ARS",
"externalId": "user-acc-ars-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: a CVU issued in the user's name. Assign it once the user is ACTIVE; deposits the user sends to it are credited to their balance.
Only transfers from an account in the user's own name (same CUIT/CUIL) are accepted. A transfer from anyone else is returned automatically to the account it came from, and no webhook is sent for it.
{
"userAnyId": "100009791",
"asset": "ARS",
"externalId": "user-dep-ars-001"
}See POST /crypto/v2/user-actions/assign-deposit-address.
Example entrypoint
Then use the missing-data (crypto) or missing-data (WALLET) endpoint, plus onboarding-task endpoints, to complete remaining requirements before operating.
Updated 27 days ago