Before the deposit
Before receiving funds, you must define how the payer will fund the operation.
Same-name depositsFiat ramp deposits must be sent from the account holder (or the sender you declare when creating the operation). Funds received from a different payer are not credited automatically.
You can start in two ways:
- Manual flow:
GET /v2/info/deposit-info/{coin} - Automatic flow:
POST /v2/synthetics/ramp-on
Manual flow — deposit-info
GET /v2/info/deposit-info/{coin} returns an object keyed by network, each containing the deposit address.
Crypto example — GET /v2/info/deposit-info/USDT:
{
"ETHEREUM": {
"address": "0x7921319332714EBea5c1219439c34309e600DF54",
"network": "ETHEREUM"
},
"BINANCE": {
"address": "0x7921319332714EBea5c1219439c34309e600DF54",
"network": "BINANCE"
},
"POLYGON": {
"address": "0x7921319332714EBea5c1219439c34309e600DF54",
"network": "POLYGON"
}
}Fiat example — GET /v2/info/deposit-info/ARS:
{
"BANK_TRANSFER": {
"address": "0000633600000000000086",
"alias": "YOUR_ACCOUNT.ALIAS"
}
}Static vs dynamic routes
The response can represent:
- Static route: reusable destination (permanent account/address). Funds can be sent directly to that destination.
- Dynamic route: unique destination per operation (e.g. Brazil, Bolivia, Guatemala). In the manual flow, create a deposit intent with
POST /v2/deposit-actions/deposit-request. In the automatic flow below this is done for you — the generated QR is returned in the synthetic response. - Per-user deposit address (optional): a permanent account assigned to a single user: issued in the user's name in Argentina and Brazil, individualized (assigned to the user, not held in their name) in Colombia and Mexico. Create it once per user with
POST /v2/user-actions/assign-deposit-address; deposits the user sends to it are credited to their balance.
Automatic flow — synthetic response
When you create a Ramp-on synthetic with POST /v2/synthetics/ramp-on, the response includes the deposit destination inside details:
{
"syntheticId": "6931f6c47cb84dd42b784e33",
"status": "STARTING",
"type": "RAMP_OPERATION",
"details": {
"depositAddress": "4310001343800000045110",
"depositAlias": "YOUR_COMPANY.ARS",
"depositAddresses": {
"BANK_TRANSFER": {
"address": "4310001343800000045110",
"alias": "YOUR_COMPANY.ARS"
}
},
"withdrawCostInAgainst": "3948.04",
"withdrawCostInAsset": "3.002311",
"price": "1315.00",
"priceExpireAt": "2025-07-28T12:36:23.024-03:00"
},
"currentStage": 1,
"stages": {
"1": { "stageType": "DEPOSIT", "asset": "ARS", "thresholdAmount": "1001150.00" },
"2": { "stageType": "ORDER", "side": "BUY", "asset": "USDT", "against": "ARS" },
"3": { "stageType": "WITHDRAW" }
}
}Read details.depositAddress (or details.depositAddresses for the full network breakdown) and share it with the payer. For dynamic-QR routes (Brazil, Bolivia, Guatemala) the generated QR code already comes inside details.depositAddresses — no separate deposit-request call is needed.
Supported crypto deposit networks
Crypto deposits are available on all networks configured for your account. Common networks include Ethereum (ERC-20), Tron (TRC-20), and BNB Chain. Check GET /v2/info/deposit-info/{coin} for the live list of available networks per asset.
Updated 28 days ago