Skip to main content
The widget is a hosted, themeable flow that takes a user from local currency to crypto and back. You mint a session token, send the user to a URL, and Ripio handles everything in between — identity, verification, payment, payout, history, refunds and support — while your backend follows along through the webhooks you already receive. There is nothing to install: no SDK, no npm package, no script tag.

​
What your users can do inside

Sign in with an email

A one-time code establishes who they are, and Terms & Conditions acceptance is shared with your API integration.

Verify their identity

The full KYC flow, including the hand-off to the identity provider and the wait for a decision.

Buy crypto

Bank transfer, PIX, request-to-pay, Mercado Pago, PSE or card, depending on the country.

Sell crypto

Paid out to a destination account they nominate and can reuse next time.

See their past operations

A history with per-operation timelines, and the ability to claim money back when something went wrong.

Fix a rejected payout

Change the destination account and have the order reprocessed — from inside the session, or from an emailed link days later.

Get help

Open a support ticket from most screens, visible to your team through the public API.

Read it in their language

Spanish, Rioplatense Spanish, English and Portuguese, chosen automatically or forced by you.

​
What depends on your configuration

Not every capability is on for every account. These are the ones worth confirming before you build against them: See Partner settings for what else is configurable. All of it is set by Ripio — ask your Ripio contact to change any of it.

​
Countries and methods

Buying crypto Selling crypto
For the full country-by-country breakdown, including limits and provider details, see Countries & payment methods.

​
What stays on your side

The widget owns the user’s experience, not your integration. You are still responsible for:
  • Minting a session token per user, per visit. See Authentication.
  • Mapping external_ref to your own user. It is the key every webhook and redirect comes back with.
  • Receiving webhooks. The widget produces the same Ramps events an API integration does, so your ledger, notifications and reconciliation work unchanged.
  • Handling the return. The widget sends users back to one redirect URL. See Returning to your app.
Deciding between this and integrating the API directly? See Choose your integration.

​
Get started

Authentication

Request credentials and mint a session token.

Launch the widget

The URLs, the sandbox hosts, and every parameter you can prefill.