Choose your integration - Ripio B2B API

There are two ways to add crypto trading — buying, selling, deposits, withdrawals — to your platform. Both run on the same account and the same underlying service — 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.

Crypto Widget

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

Which one should you use?

Feature	API Integration	Crypto Widget
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 custom properties
Development effort	Higher — you build the UI and handle trading logic yourself	Lower — mainly generating session codes and mounting the component
Control	Granular control over quotes, execution and every screen	Streamlined flow managed by the widget
Identity verification (KYC)	Depends on your company: stored as submitted, or completed with a liveness check — see Identity verification (KYC)	You send the user’s data when opening the widget — see User verification (KYC)
Use case	Deep, custom trading integrations	A quick, easy way to add buy/sell
Authentication	OAuth2 Client Credentials for API access	One-time session code generated via API, which the widget exchanges for its session

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

Next steps

Once you’ve decided:

API Integration → start with Identity verification (KYC), then follow the Trading integration walkthrough.
Crypto Widget → Crypto Widget overview.