Submit a send request. This will lock in a rate and await approval.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Updated TerminologyPayments are now called Sends. These Send endpoints replace the legacy Payments endpoints. The functionality remains identical, only the terminology has changed. Legacy payment endpoints are deprecated but will continue to work. We recommend migrating to these new
/sendendpoints for future compatibility.
Amount in USD or local currencyThe
amountfield and thelocalAmountfield are interchangeable in the request body. Either one is required, but not both. Specifying the USDamountwill then calculate an amount in local currency based on the partner rates, while specifying alocalAmountin the local currency will fix this amount for the user while calculating the USD amount from the rates. TheconvertedAmountin the response body indicates the amount in local currency that has either been fixed or calculated.
Ten Minute ExpirySend requests have ten minutes to be accepted or will automatically mark itself as expired.
Force AcceptSetting
forceAcceptfield totrueallows you to skip the accept send request and your send would start processing once you submit send request.
Channel NoteYou can now use
channelTypeas an alternative to specifying a channelId in your Submit Send API Request.When using
channelTypeyou're required to pass thecountryandcurrencyin the send requestWhen you provide a
channelType,countryandcurrencythe system will automatically select an appropriate active channel for your transaction.Available Channel Types:
- momo
- bank (P2P and EFT channel types should be passed in as bank)
LATAM Send Fields
When sending send transactions to LATAM currencies, additional fields are required beyond the standard request body. This document outlines the currency-specific fields per currency.
MXN — Mexico
No extra fields required. Ensure destination.accountNumber is a valid 18-digit CLABE number.
ARS — Argentina
| Field | Location | Required | Description |
|---|---|---|---|
accountNumber | destination | Yes | CVU or CBU — must be exactly 22 digits |
cuit | request root | Yes | Argentine tax ID — must be exactly 11 digits |
BRL — Brazil
| Field | Location | Required | Description |
|---|---|---|---|
pixKeyType | destination | Yes | Pix key type — one of: CPF, CNPJ, EMAIL, PHONE, RANDOM_KEY |
Pix key format by type (destination.accountNumber):
pixKeyType | Expected format |
|---|---|
CPF | 11 digits |
CNPJ | 14 digits |
EMAIL | Valid email address |
PHONE | 10–11 digits |
RANDOM_KEY | UUID format (contains -) |
COP — Colombia
| Field | Location | Required | Description |
|---|---|---|---|
identificationType | request root | Yes | Document type code (see table below) |
identificationNumber | request root | Yes | Document number |
accountType | request root | No | Account type code — defaults to ch (savings) if omitted |
accountType values:
| Value | Description |
|---|---|
cc | Checking account |
ch | Savings account (default) |
dp | Electronic deposit |
identificationType values:
| Value | Description |
|---|---|
cc | Citizenship ID |
nit | Tax ID |
ce | Foreigner ID |
pa | Passport |
ppt | Temporary Protection Permit |
ti | Identity Card |
rc | Civil Registry |
te | Foreigner Card |
die | Foreign ID Document |
nd | No Document |