Skip to main content
Each country has its own set of beneficiary fields, document types, and bank-account shape. The Pydantic models on the API enforce these, including check-digit validation for CLABE (MX), CPF (BR), CBU/CUIL (AR), RUT (CL), and CCI (PE).
For runtime form-building, call GET /v1/payouts/requirements/{country} — it returns the live shape directly from the server and stays in sync if fields are added.
A failing check digit raises 422 VALIDATION_ERROR, not a REJECTED payout — it’s a bad request, not a bad payout.

Mexico (MX)

CLABE is 18 digits with a mod-10 weighted check digit (Banxico spec). The algorithm: weight the first 17 digits cyclically by (3, 7, 1), take each product modulo 10, sum them, and the check digit is (10 - sum % 10) % 10.

Example


Colombia (CO)

Example


Argentina (AR)

If you pass document_type: "CUIL" for the beneficiary, the engine also runs the CUIL format check against document_id (11 digits).

Example (CBU)

Example (alias)


Brazil (BR)

CPF is 11 digits with two mod-11 check digits. The engine validates them when document_type: "CPF" (and again on PIX keys with pix_key_type: "CPF"). All-identical-digit CPFs (e.g. "11111111111") are rejected even though they pass the mod-11 algebra — that’s the standard Receita Federal rule.

BANK_TRANSFER shape

PIX shape

  • CPF keys are validated as CPFs (same check-digit rule)
  • EMAIL keys must contain @
  • PHONE keys must contain ≥ 8 digits
  • EVP keys are opaque (any non-empty string)

Chile (CL)

RUT follows the format NNNNNNNN-D (1–9 digits, dash, check digit). The check digit is computed with a mod-11 algorithm (weights 2..7 cycling over the digits, reversed). When the algorithm yields 11 the check digit is 0; when it yields 10 it’s K. Both upper- and lower-case K are accepted on input.

Example


Peru (PE)

Example (CCI)

Example (bank code + account number)


Live form-building

Hardcoding these field tables into your UI works, but the canonical source of truth is the API itself. Call:
…to get the structured shape — required fields, allowed document types, allowed account types, and format hints. New countries get added to that endpoint as a schema-only change, with no client work needed.
Countries outside MX/CO/AR/BR/CL/PE return 404 PAYOUT_COUNTRY_NOT_SUPPORTED.