Skip to main content
The widget is a native web component your users’ cripto operations happen inside of — buying, selling, and tracking a portfolio — while your backend follows along through the webhooks you already receive. You mint a session token from your server, mount the component with it, and Ripio handles the trading flow: quoting, execution, and settlement. There is no SDK to install beyond the component’s own script tag.

​
What your users can do inside

See their portfolio

Total balance, holdings, recent activity and the market — all in one screen.

Buy crypto

A quote with a guaranteed rate for a short window, then a one-tap confirmation.

Sell crypto

The same quote-then-confirm flow, in the other direction.

Read it in their language

Spanish, Portuguese or English, set by you at embed time.

​
What depends on your configuration

Not every operation is on for every account. The session you mint reflects what your account has enabled: You can further narrow a single session with requested_operations on POST /auth — the effective set is always the intersection of what your account has enabled and what you requested, never the union. Asking for an operation your account doesn’t have simply has no effect; it never grants something you haven’t contracted.
Ask your Ripio contact to change what’s enabled for your account.

​
What stays on your side

The widget owns the trading UI, not your integration. You are still responsible for:
  • Minting a session token per user, per visit, from your server. See Authentication.
  • Mapping external_ref to your own user. It’s the identifier every webhook comes back with.
  • Receiving webhooks. Approving a purchase before it executes, and finding out how each operation resolved. See Webhooks.

​
Get started

Authentication

Request credentials and mint a session token.

Embedding the widget

The script tag, the element’s attributes, and the events it emits.