Retrieve a Customer's On-Ramp Session
Retrieves the on-ramp session for a specific customer, keyed by your partner-facing customer ID. A customer has at most one on-ramp session, so this returns that single session — useful for per-customer integrations that would otherwise have to list every session and filter client-side. Returns 404 if the customer does not exist, is inactive, or has no session.
Authorizations
Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>.
Path Parameters
Unique identifier for the customer.
Response
The customer's on-ramp session.
Unique identifier for the created on-ramp session.
Unique identifier for the customer associated with the session.
Date and time the on-ramp session was created.
The target crypto currency for every on-ramp transaction performed with the created session.
The blockchain network to be used for the conversion.
The customer's deposit address on the chosen blockchain network.
Instructions for the customer to complete the fiat deposit. Structure varies depending on payment method and currency: bank_transfer (Argentina) returns cvu and optionally alias (a human-readable identifier that can be used instead of the CVU for transfers — to enable alias customization, contact the Ripio team), bank_transfer (Mexico) returns clabe, breb (Colombia) returns brebKey. Methods backed by a persistent deposit account (cvu, clabe, brebKey) also include a status field (processing, enabled or disabled) indicating whether the deposit account is ready to operate; while processing, the deposit key/identifier may be null.
{
"cvu": "0000465160000000070078",
"alias": "juan.perez.ramp",
"status": "enabled"
}{
"cvu": "0000465160000000070078",
"status": "enabled"
}{
"clabe": "706180196550550550",
"status": "enabled"
}{
"brebKey": "@E6JZKEPG5S",
"status": "enabled"
}A list containing every transaction that has been either started or completed through this session. On creation, will always be empty.