Skip to main content
The off-ramp turns the user’s crypto into local currency paid into a bank account they nominate. The account they choose is the part that most often needs attention, so the widget keeps a reusable list of them.

​
The flow

1

Choose an amount

Quoted and refreshed the same way as the on-ramp.Off-ramp amount entry with the quote
2

Choose where the money should land

The user picks one of their saved destination accounts, or registers a new one.
3

Choose a network and deposit the crypto

The widget shows a deposit address for the chosen network.
4

Ripio sells and pays out

Once the deposit confirms, the crypto is sold and the local currency is sent to the destination account.

​
The destination account book

Saved accounts persist across sessions, so a returning user sells in a few taps. The destination account book listing a saved account What a new account requires depends on the country: Every account carries a status, and only an enabled account can receive a payout. The widget marks the others as unselectable and says why:
The authoritative rules — including the one-active-account-per-payment-method constraint and how a suspended account comes back — are in Fiat account lifecycle. The widget surfaces those rules; it does not change them.
Bank-side validation is asynchronous and can be slow. Colombia BRE-B in particular can take up to an hour to resolve. The widget waits about 5 minutes and then tells the user it will email them when the account is ready, rather than blocking the flow.

​
How the user gets back to you

Decided by whether the QR deposit screen is enabled on your account:
  • Not enabled — the widget redirects to your URL as soon as the sale is confirmed, with transaction parameters appended. The user never sees a deposit screen, so you are expected to send the crypto on their behalf.
  • Enabled — the widget shows the deposit address and a QR code so the user sends the crypto themselves, plus a button back to you.
Ask your Ripio contact which of the two your account uses. Both forms append the full parameter set. See Returning to your app.

​
What your backend observes

OFF-RAMP.DEPOSIT.RECEIVED → OFF-RAMP.TRADE.COMPLETED → OFF-RAMP.WITHDRAWAL.PROCESSING → OFF-RAMP.WITHDRAWAL.COMPLETED A payout that cannot be delivered arrives as OFF-RAMP.ORDER.CANCELLED, and what you can do about it depends on refundable — see Recovering a rejected payout. Full payloads are in Off-Ramp Webhook Events.