Skip to main content
POST
The field you need to send alongside paymentMethodType and amount depends on the customer’s country. Use the value returned in fiatPaymentInstructions from the Create On-Ramp Session or Create On-Ramp Order response.
For Brazil the deposit is simulated using the order’s brCode from Create On-Ramp Order — there is no reusable deposit account to provision first, and pix is not available through an On-Ramp Session. See Brazil (PIX).
This endpoint only exists in sandbox — it is not routed in production.A successful call returns 200 with no body at all (a zero-length response, not {}), so don’t try to parse the response as JSON.

Authorizations

Authorization
string
header
required

Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>.

Body

application/json

Details for simulating the deposit.

paymentMethodType
string
required

The payment method type for the simulated deposit.

Example:

"bank_transfer"

amount
number
required

The amount of fiat to send.

Example:

2100

alias_or_cvu
string

Alias or CVU to which the deposit will be made (from onramp fiatPaymentInstructions). Used for ARS deposits.

Example:

"0100000000000000000001"

clabe
string

CLABE to which the deposit will be made (from onramp fiatPaymentInstructions). Used for MXN deposits.

Example:

"706180196550550550"

payment_url
string<uri>

Payment URL to identify the order (from onramp fiatPaymentInstructions). Used for COP deposits.

Example:

"https://example.com/payment/abc123"

brcode
string

BR Code from the order's fiatPaymentInstructions, which identifies the PIX payment to simulate. Used for BRL deposits with paymentMethodType: pix.

Example:

"00020101021226360014BR.GOV.BCB.PIX0114+55119876543215204000053039865802BR5913Store Name XYZ6009SAO PAULO62070503***6304ABCD"

Response

Deposit simulation successful. The response has no body at all — a zero-length payload, not {}. Do not try to parse it as JSON.