Country requirements
Country requirements
Country requirements summarize jurisdiction-specific constraints that impact onboarding and operations.
Using this section early prevents late-stage failures caused by country-specific validation differences.
Exchange values
Use the exchange field in your onboarding payload to indicate the user's jurisdiction. Each country maps to a specific value:
| Country | exchange value | Main fiat |
|---|---|---|
| 🇦🇷 Argentina | ARGENTINA | ARS, USD |
| 🇧🇴 Bolivia | BOLIVIA | BOB |
| 🇧🇷 Brazil | BRAZIL | BRL |
| 🇨🇱 Chile | CHILE | CLP |
| 🇨🇴 Colombia | COLOMBIA | COP |
| 🇨🇷 Costa Rica | COSTA_RICA | CRC |
| 🇬🇹 Guatemala | GUATEMALA | GTQ |
| 🇲🇽 Mexico | MEXICO | MXN |
| 🇵🇦 Panama | PANAMA | PUSD |
| 🇵🇾 Paraguay | PARAGUAY | PYG |
| 🇵🇪 Peru | PERU | PEN |
| 🇵🇭 Philippines | PHILIPPINES | PHP |
Currency display
Amounts are returned as plain strings ("15000.00") with the currency in a separate field ("ARS"), so you decide how to render them. Each country writes amounts its own way — showing every currency with a $ sign will read as wrong to your users.
| Currency | Symbol | Decimals | Renders as |
|---|---|---|---|
| ARS | $ | 2 | $ 1.234,56 |
| BOB | Bs | 2 | Bs 1.234,56 |
| BRL | R$ | 2 | R$ 1.234,56 |
| CLP | $ | 0 | $ 1.234 |
| COP | $ | 2 | $ 1.234,56 |
| CRC | ₡ | 2 | ₡ 1.234,56 |
| GTQ | Q | 2 | Q 1,234.56 |
| MXN | $ | 2 | $ 1,234.56 |
| PEN | S/ | 2 | S/ 1,234.56 |
| PHP | ₱ | 2 | ₱ 1,234.56 |
| PYG | ₲ | 0 | ₲ 1.234 |
| USD | US$ | 2 | US$ 1,234.56 |
| VES | Bs. | 2 | Bs. 1.234,56 |
Three things to watch:
- Chile and Paraguay have no cents. Neither the peso chileno nor the guaraní is divided into decimals, so
CLPandPYGamounts are shown as whole numbers. - The decimal separator changes by country. Argentina, Bolivia, Brazil, Chile, Colombia, Costa Rica, Paraguay and Venezuela use a comma; Guatemala, Mexico, Panama, Peru, the Philippines and the US dollar use a dot. The thousands separator is always the other one.
- Panama's currency is the US dollar. We call it
PUSDin the API, but the amounts are dollars and follow the US convention.
Crypto assets are shown with the ticker instead of a symbol, and allow up to 8 decimals: USDT 12.50.
Supported legal IDs by country
Each jurisdiction accepts one or more legalId types. Send any of the accepted types for the user's country — the platform validates the submitted value against the format of every accepted type and accepts it if it matches any of them. See the individual country page for the exact regex of each type.
| Country | Accepted legalId type | Local name | Validation |
|---|---|---|---|
| 🇦🇷 Argentina | CUIT / CUIL | Clave Única de Identificación Tributaria / Laboral | 11 digits, regex + checksum |
| 🇦🇷 Argentina | DNI | Documento Nacional de Identidad (pseudo legalId, when enabled) | 7–9 digits, format only |
| 🇧🇴 Bolivia | CI | Cédula de Identidad (individuals) | 5–10 digits; optional 2-letter department prefix/suffix; E-prefixed for foreigners |
| 🇧🇴 Bolivia | NIT | Número de Identificación Tributaria (taxpayers) | 7–13 digits, format only |
| 🇧🇷 Brazil | CPF | Cadastro de Pessoas Físicas (individuals) | 11 digits, regex + checksum |
| 🇧🇷 Brazil | CNPJ | Cadastro Nacional da Pessoa Jurídica (companies) | 14 digits, regex + checksum |
| 🇧🇷 Brazil | RG | Registro Geral | 7–9 digits (+ optional check char), format only |
| 🇧🇷 Brazil | CNH | Carteira Nacional de Habilitação (driver's license) | 11 digits, format only |
| 🇨🇱 Chile | RUT | Rol Único Tributario | 7–8 digits + verifier (0–9/K), regex + checksum |
| 🇨🇴 Colombia | NUIP | Número Único de Identificación Personal | 10 digits, format only |
| 🇨🇴 Colombia | CC | Cédula de Ciudadanía | 6–10 digits, format only |
| 🇨🇴 Colombia | PPT | Permiso por Protección Temporal | 6–15 alphanumeric, format only |
| 🇨🇷 Costa Rica | CI / CJ | Cédula de Identidad / Cédula Jurídica | 9–10 digits, format only |
| 🇨🇷 Costa Rica | DIMEX | Documento de Identificación Migratorio para Extranjeros | 11–12 digits, format only |
| 🇬🇹 Guatemala | CUI | Código Único de Identificación | 13 digits, regex + municipality/checksum |
| 🇲🇽 Mexico | CURP | Clave Única de Registro de Población | 18 chars, regex + state/date/checksum |
| 🇲🇽 Mexico | RFC | Registro Federal de Contribuyentes | 12–13 chars, format only |
| 🇵🇦 Panama | RUC | Registro Único de Contribuyentes | digit groups with optional E/N prefix, format only |
| 🇵🇾 Paraguay | CI | Cédula de Identidad (individuals) | 6–8 digits, format only |
| 🇵🇾 Paraguay | RUC | Registro Único de Contribuyentes (businesses/entities) | 8–9 digits, format only |
| 🇵🇪 Peru | DNI | Documento Nacional de Identidad | 8 digits (+ optional verifier), format only |
| 🇵🇪 Peru | CE | Carné de Extranjería | 9–12 alphanumeric, format only |
| 🇵🇭 Philippines | PID | Passport, PCN, UMID, or Driver's License | per-document formats (see Philippines page) |
Note: "regex + checksum" means the value must also pass a verification-digit check, not only match the pattern. Types marked "format only" are validated by pattern/length and are not checked against an issuing authority at validation time.
Restricted countries
Users whose legal ID (legalIdNationality) was issued by one of the countries below cannot be onboarded. The restriction applies to every product and currency, and onboarding is rejected with RESTRICTED_NATIONALITY (HTTP 400).
A user's country of residence is the country that issued their legal ID (legalIdNationality). The nationality field in personal data does not determine residence.
| Country | legalIdNationality | ISO alpha-2 | ISO alpha-3 |
|---|---|---|---|
| Algeria | ALGERIA | DZ | DZA |
| Angola | ANGOLA | AO | AGO |
| Bulgaria | BULGARIA | BG | BGR |
| Cameroon | CAMEROON | CM | CMR |
| Democratic Republic of the Congo | DEMOCRATIC_REPUBLIC_OF_CONGO | CD | COD |
| Haiti | HAITI | HT | HTI |
| Iran | IRAN | IR | IRN |
| Ivory Coast | IVORY_COAST | CI | CIV |
| Kenya | KENYA | KE | KEN |
| Korea North | KOREA_NORTH | KP | PRK |
| Kuwait | KUWAIT | KW | KWT |
| Laos | LAOS | LA | LAO |
| Lebanon | LEBANON | LB | LBN |
| Myanmar | MYANMAR | MM | MMR |
| Namibia | NAMIBIA | NA | NAM |
| Nepal | NEPAL | NP | NPL |
| Papua New Guinea | PAPUA_NEW_GUINEA | PG | PNG |
| South Sudan | SOUTH_SUDAN | SS | SSD |
| Syria | SYRIA | SY | SYR |
| United States | UNITED_STATES | US | USA |
| Vietnam | VIETNAM | VN | VNM |
| Yemen | YEMEN | YE | YEM |
Note: On top of this list, every onboarding is screened against sanctions lists and watchlists, and Manteca's compliance team may reject individual users on a case-by-case basis.
Banking fields vary by country
The banking.accounts object is not uniform across jurisdictions. Argentina identifies the bank and branch through the 22-digit cbu, so no extra fields are needed. Other countries (Bolivia, Costa Rica, Guatemala, Panama, and more) require explicit bank.code and accountType values alongside the account identifier. Always use the country page's JSON example as the source of truth for your payload — copying Argentina's shape into another jurisdiction will fail validation.
Available country pages
Identity, onboarding, and operational requirements for Argentina.
Identity, onboarding, and operational requirements for Bolivia.
Identity, onboarding, and operational requirements for Brazil.
Identity, onboarding, and operational requirements for Chile.
Identity, onboarding, and operational requirements for Colombia.
Identity, onboarding, and operational requirements for Costa Rica.
Identity, onboarding, and operational requirements for Guatemala.
Identity, onboarding, and operational requirements for Mexico.
Identity, onboarding, and operational requirements for Panama.
Identity, onboarding, and operational requirements for Paraguay.
Identity, onboarding, and operational requirements for Peru.
Identity, onboarding, and operational requirements for Philippines.
Identity verification by country
Each country uses different sources for identity verification. This determines whether personal data is populated automatically or must be supplied by the integrator.
| Country | Behavior |
|---|---|
| Argentina | Personal data (name, birthDate, work, etc.) is auto-populated from official records using the user's CUIT/CUIL. The integrator only needs to provide the legalId. |
| Brazil | Personal data is auto-populated using the user's CPF. |
| All others | The integrator must submit all required personal data fields via onboarding actions. |
All countries run background security checks (sanctions lists, watchlists) automatically during onboarding.
Required personal data by country
Fields that must be provided (or auto-populated) before the user can be activated.
| Field | ARG | BRA | CHL | COL | MEX | PAN | CRI | GTM | PHL | BOL | PER | PRY |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
name | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
surname | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
birthDate | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
phoneNumber | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
nationality | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
address.street | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
sex | — | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
maritalStatus | — | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
work | ✓ | — | ✓ | — | — | ✓ | — | — | — | — | — | — |
How to apply in implementation
- Select target jurisdiction.
- Align onboarding payload and document requirements.
- Validate lifecycle states in sandbox.
- Confirm production readiness with compliance and operations.
Operational note
Country requirements apply across services (Ramps, QR Payments, Bill Payments, and CaaS) and should be part of your release checklist.
Updated 7 days ago