Before the payment
Before sending funds, prepare destination and settlement context.
You can start in one of two ways:
- Manual flow: prepare withdrawal execution with
POST /crypto/v2/withdraws(optionally usingPOST /crypto/v2/withdraw-locksif lock-based confirmation is required). - Automatic flow: create a Ramp-off synthetic with
POST /crypto/v2/synthetics/ramp-off.
Before execution, validate destination data, route/network compatibility, and available balance.
Destination validation
Before executing a withdrawal, Manteca validates the destination against:
- account format (CVU/CBU/CLABE/PIX key, etc.) for the target country,
- compliance rules for the recipient.
Invalid destinations are rejected at creation time with INVALID_PARAMS. Always validate destination format before submitting.
For sending funds to third-party beneficiaries (not your own accounts), see Third-party Transfers.
Preview a destination
For third-party destinations to Argentina (BANK_TRANSFER), Brazil (PIX), or Colombia (BREB), you can preflight the destination with GET /crypto/v2/info/withdraw-destination/{destination} before submitting the withdraw. It returns the owner's name and a masked legal ID so you can confirm with the end user who will receive the funds. If the endpoint returns a WITHDRAW_DESTINATION error, the withdraw itself would also fail on submission.
Destination fields by country
| Country | Asset | Network | Address format | Required destination fields |
|---|---|---|---|---|
| Argentina | ARS | BANK_TRANSFER | CBU/CVU (22 digits) or Alias | address |
| Bolivia | BOB | BANK_TRANSFER | Account number (7 to 14 digits) | address, accountType, bankCode |
| Brazil | BRL | PIX | PIX key (CPF, phone, email, or random key) | address |
| Chile | CLP | BANK_TRANSFER | Account number (5 to 22 digits) | address, accountType, bankCode |
| Colombia | COP | BANK_TRANSFER | Account number (4 to 18 digits) | address, network, accountType, bankCode |
| Colombia | COP | BANK_TRANSFER | Phone with prefix (+57...) | address, network |
| Colombia | COP | BREB | Key, phone, email, or CC | address, network |
| Costa Rica | CRC | BANK_TRANSFER | CR + 18 to 20 digits | address, accountType, bankCode |
| Guatemala | GTQ | BANK_TRANSFER | Account number (4 to 14 digits) | address, accountType, bankCode |
| Mexico | MXN | SPEI | CLABE (18 digits) | address, accountType, bankCode |
| Mexico | MXN | SPEI | Debit card or phone | address, bankCode |
| Panama | PUSD | BANK_TRANSFER | Account number (5 to 20 digits) | address, accountType, bankCode |
| Paraguay | PYG | BANK_TRANSFER | Account number (4 to 16 digits) | address, accountType, bankCode |
| Peru | PEN | BANK_TRANSFER | CCI (20 digits) | address, accountType, bankCode |
| Philippines | PHP | INSTACASH | Account number (4 to 22 digits) | address, accountType, bankCode |
network is required only in Colombia. In every other country there is one network per asset and it is applied when you omit it. In Argentina bankCode is optional.
For valid values, see:
- Supported Networks: payment rails per country
- Supported Account Types: account type values per country
- Supported Banks: bank codes per country
- Coverage: countries and execution times
Updated 27 days ago