Choose your integration

There are two ways to add On-Ramp (fiat → crypto) and Off-Ramp (crypto → fiat) to your platform. Both run on the same underlying service and support the same countries and payment methods — they differ in how much of the user experience you build yourself.

The two paths

API integration

Call the REST API directly and build your own UI. Maximum control over the experience.

Widget integration

Embed Ripio’s pre-built, themeable UI. Fastest way to ship.

Which one should you use?

Feature	API integration	Widget integration
Integration type	Direct API calls, backend-to-backend primarily	Embeddable UI, frontend integration
User experience	Fully customizable by the partner	Pre-built UI, themeable via CSS
Development effort	Higher — you build the UI and handle API logic	Lower — mainly token generation and URL redirection
Control	Granular control over each step	Streamlined flow managed by the widget
Use case	Deep, custom financial integrations	A quick, easy way to add on/off-ramp
Authentication	OAuth2 Client Credentials for API access	JWT token generated via API for the widget session

Choose the API if you want to own the end-to-end experience and embed the flows natively in your product. Choose the Widget if you want to go live quickly with minimal development.

Next steps

Once you’ve decided:

API → Authenticate, then follow the On-Ramp or Off-Ramp walkthrough.
Widget → Widget integration.

Either way, check Countries & payment methods for what’s available in your market.

⌘I

Overview

Widget integration

API Integration

The two paths

API integration

Widget integration

Which one should you use?

Next steps

​The two paths

API integration

Widget integration

​Which one should you use?

​Next steps

The two paths

Which one should you use?

Next steps