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:

Countryexchange valueMain fiat
🇦🇷 ArgentinaARGENTINAARS, USD
🇧🇴 BoliviaBOLIVIABOB
🇧🇷 BrazilBRAZILBRL
🇨🇱 ChileCHILECLP
🇨🇴 ColombiaCOLOMBIACOP
🇨🇷 Costa RicaCOSTA_RICACRC
🇬🇹 GuatemalaGUATEMALAGTQ
🇲🇽 MexicoMEXICOMXN
🇵🇦 PanamaPANAMAPUSD
🇵🇾 ParaguayPARAGUAYPYG
🇵🇪 PeruPERUPEN
🇵🇭 PhilippinesPHILIPPINESPHP

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.

CurrencySymbolDecimalsRenders as
ARS$2$ 1.234,56
BOBBs2Bs 1.234,56
BRLR$2R$ 1.234,56
CLP$0$ 1.234
COP$2$ 1.234,56
CRC₡2₡ 1.234,56
GTQQ2Q 1,234.56
MXN$2$ 1,234.56
PENS/2S/ 1,234.56
PHP₱2₱ 1,234.56
PYG₲0₲ 1.234
USDUS$2US$ 1,234.56
VESBs.2Bs. 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 CLP and PYG amounts 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 PUSD in 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.

CountryAccepted legalId typeLocal nameValidation
🇦🇷 ArgentinaCUIT / CUILClave Única de Identificación Tributaria / Laboral11 digits, regex + checksum
🇦🇷 ArgentinaDNIDocumento Nacional de Identidad (pseudo legalId, when enabled)7–9 digits, format only
🇧🇴 BoliviaCICédula de Identidad (individuals)5–10 digits; optional 2-letter department prefix/suffix; E-prefixed for foreigners
🇧🇴 BoliviaNITNúmero de Identificación Tributaria (taxpayers)7–13 digits, format only
🇧🇷 BrazilCPFCadastro de Pessoas Físicas (individuals)11 digits, regex + checksum
🇧🇷 BrazilCNPJCadastro Nacional da Pessoa Jurídica (companies)14 digits, regex + checksum
🇧🇷 BrazilRGRegistro Geral7–9 digits (+ optional check char), format only
🇧🇷 BrazilCNHCarteira Nacional de Habilitação (driver's license)11 digits, format only
🇨🇱 ChileRUTRol Único Tributario7–8 digits + verifier (0–9/K), regex + checksum
🇨🇴 ColombiaNUIPNúmero Único de Identificación Personal10 digits, format only
🇨🇴 ColombiaCCCédula de Ciudadanía6–10 digits, format only
🇨🇴 ColombiaPPTPermiso por Protección Temporal6–15 alphanumeric, format only
🇨🇷 Costa RicaCI / CJCédula de Identidad / Cédula Jurídica9–10 digits, format only
🇨🇷 Costa RicaDIMEXDocumento de Identificación Migratorio para Extranjeros11–12 digits, format only
🇬🇹 GuatemalaCUICódigo Único de Identificación13 digits, regex + municipality/checksum
🇲🇽 MexicoCURPClave Única de Registro de Población18 chars, regex + state/date/checksum
🇲🇽 MexicoRFCRegistro Federal de Contribuyentes12–13 chars, format only
🇵🇦 PanamaRUCRegistro Único de Contribuyentesdigit groups with optional E/N prefix, format only
🇵🇾 ParaguayCICédula de Identidad (individuals)6–8 digits, format only
🇵🇾 ParaguayRUCRegistro Único de Contribuyentes (businesses/entities)8–9 digits, format only
🇵🇪 PeruDNIDocumento Nacional de Identidad8 digits (+ optional verifier), format only
🇵🇪 PeruCECarné de Extranjería9–12 alphanumeric, format only
🇵🇭 PhilippinesPIDPassport, PCN, UMID, or Driver's Licenseper-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.

CountrylegalIdNationalityISO alpha-2ISO alpha-3
AlgeriaALGERIADZDZA
AngolaANGOLAAOAGO
BulgariaBULGARIABGBGR
CameroonCAMEROONCMCMR
Democratic Republic of the CongoDEMOCRATIC_REPUBLIC_OF_CONGOCDCOD
HaitiHAITIHTHTI
IranIRANIRIRN
Ivory CoastIVORY_COASTCICIV
KenyaKENYAKEKEN
Korea NorthKOREA_NORTHKPPRK
KuwaitKUWAITKWKWT
LaosLAOSLALAO
LebanonLEBANONLBLBN
MyanmarMYANMARMMMMR
NamibiaNAMIBIANANAM
NepalNEPALNPNPL
Papua New GuineaPAPUA_NEW_GUINEAPGPNG
South SudanSOUTH_SUDANSSSSD
SyriaSYRIASYSYR
United StatesUNITED_STATESUSUSA
VietnamVIETNAMVNVNM
YemenYEMENYEYEM

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 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.

CountryBehavior
ArgentinaPersonal 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.
BrazilPersonal data is auto-populated using the user's CPF.
All othersThe 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.

FieldARGBRACHLCOLMEXPANCRIGTMPHLBOLPERPRY
name✓✓✓✓✓✓✓✓✓✓✓✓
surname✓✓✓✓✓✓✓✓✓✓✓✓
birthDate✓✓✓✓✓✓✓✓✓✓✓✓
phoneNumber✓✓✓✓✓✓✓✓✓✓✓✓
nationality✓✓✓✓✓✓✓✓✓✓✓✓
address.street✓✓✓✓✓✓✓✓✓✓✓✓
sex—✓✓✓✓✓✓✓✓✓✓✓
maritalStatus—✓✓✓✓✓✓✓✓✓✓✓
work✓—✓——✓——————

How to apply in implementation

  1. Select target jurisdiction.
  2. Align onboarding payload and document requirements.
  3. Validate lifecycle states in sandbox.
  4. 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.


Did this page help you?