Skip to main content
On-Ramp lets your users buy crypto with fiat. There are two ways to run an on-ramp, and you can use either (or both) depending on your product. For request and response details, follow the endpoint link in each step.
Available payment methods depend on the country. See Countries & payment methods first.

​
Two ways to run an on-ramp

Both share the same setup (customer and KYC).

​
Common setup

1

Authenticate

Get an access token with the OAuth2 Client Credentials flow using your client_id and client_secret. Send it as a Bearer token on every subsequent call.→ Acquire Access Token
2

Create the customer

Register the end user as a customer. You’ll use the returned customerId throughout the flow.→ Create Customer
3

Accept Terms & Conditions

Right after creating the customer, register their acceptance of the active Terms & Conditions. This is a required step before the customer can operate.→ Terms & Conditions · Accept Terms
4

Verify identity (KYC)

The customer must complete KYC before operating — the status must be COMPLETED. Choose the model that fits your integration (Ripio-hosted redirect or partner-submitted via API), and reuse an existing Ripio KYC via OTP when possible.→ Identity verification (KYC)
5

Provision the deposit account (when required)

Some countries and payment methods require the fiat deposit account to exist before operating (for example, a CLABE in Mexico or a PIX key in Brazil). Create it and wait until it becomes enabled — you’ll receive an ACCOUNT.ENABLED webhook when it’s ready. For methods that generate the deposit instructions on the fly, you can skip this step.→ Create Deposit Account · Account Events

​
Option 1 — Single on-ramp order

1

Create a quote

Request an on-ramp quote (fiat → crypto) with the customerId, specifying amount and payment method. The quote holds a price for a limited time and returns a quoteId. Quotes are scoped to a customer, so this step always comes after creating one.→ Create Quote
2

Create the on-ramp order

Create the order with the quoteId, the customerId, the destination depositAddress (crypto) and a partner externalRef. The response includes the fiat payment instructions (for example, the CVU/CLABE to transfer to, or a payment link).→ Create On-Ramp Order
3

User pays and the order completes

The customer pays the fiat amount using the returned instructions. Once the deposit is detected and the trade executes, the order moves to COMPLETED and the crypto is sent to the destination address.Track it with On-Ramp Events (recommended) or by polling List On-Ramp Orders.

​
Option 2 — On-ramp session

1

Create the on-ramp session

Create a session for the customer with the destination crypto address, network and currency. The response includes a reusable fiat deposit account (e.g. a CVU) and its payment instructions. If the customer already has a session, it is reused/updated. The session does not expire.→ Create On-Ramp Session
2

User deposits fiat — orders are created automatically

The customer can send fiat to the session’s deposit account as many times as they want. Each deposit automatically creates an on-ramp order, converts the funds at the current rate and sends the crypto to the destination address. No per-deposit API call is needed.Track each order with On-Ramp Events or by inspecting the session via Retrieve an On-Ramp Session.

​
Order lifecycle

​
Testing in sandbox

In sandbox there’s no real fiat movement. Use the deposit simulation endpoint to move an order forward as if the user had paid. → Simulate Deposit for On-Ramp (Sandbox)