🇧🇴 Bolivia

Bolivia onboarding has jurisdiction-specific identity requirements that should be validated early in integration.


Exchange profile

FieldValue
ExchangeBOLIVIA
Main fiat currencyBOB
Typical local railsBank transfer and QR contexts

Identity rules (legalId)

In Bolivia, legalId can be:

  • CI (Cédula de Identidad, individuals), including a foreign-resident variant
  • NIT (Número de Identificación Tributaria, taxpayers — companies and self-employed individuals)

Accepted formats:

  • CI: /^\d{5,10}$/, /^[A-Z]{2}\d{5,10}$/, /^\d{5,10}[A-Z]{2}$/
  • CI (foreigners): /^E-?\d{5,10}$/
  • NIT: /^\d{7,13}$/

Department-code validation applies for prefixed/suffixed CI formats (valid codes: BE, CB, CH, LP, OR, PD, PT, SC, TJ).

NIT has no published verification-digit algorithm (unlike Argentina's CUIT or Brazil's CPF) — it's validated by format/length only. Accepted length is 7 to 13 digits, covering both the legacy NIT and the modern biometric NIT issued by Bolivia's Servicio de Impuestos Nacionales (SIN).


Documentation requirements

Identity images are required according to onboarding/limit controls.

Use Upload Identity Image for signed upload URLs.


Payload guidance

Validate at least:

  • legalId
  • exchange: "BOLIVIA"
  • name, surname, sex
  • birthDate, isPep, isFep, isFacta
  • phoneNumber, nationality, maritalStatus
  • address.street

Request example

{
  "externalId": "user-BOB",
  "email": "[email protected]",
  "legalId": "7794988",
  "type": "INDIVIDUAL",
  "exchange": "BOLIVIA",
  "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": "1155051020",
    "nationality": "Bolivia",
    "maritalStatus": "Soltero",
    "address": {
      "street": "SANCHEZ LIMA",
      "postalCode": "2520",
      "locality": "ANDRES IBAÑEZ",
      "province": "SANTA CRUZ DE LA SIERRA",
      "numeration": "2520",
      "floor": "-",
      "apartment": ""
    }
  },
  "banking": {
    "accounts": [
      {
        "cbu": "1566987425",
        "currency": "BOB",
        "description": "Cta BOB",
        "bank": {
          "code": "001"
        },
        "accountType": "SAVINGS"
      }
    ]
  }
}

Example entrypoint

Then use missing-data and onboarding-task endpoints to complete remaining requirements before operating.


Did this page help you?