Skip to main content
Crypto as a Service (CaaS) lets partners offer crypto to their own users without running the infrastructure behind it. Ripio holds the assets, executes the trades and moves the funds on-chain, while you keep the relationship with your users and decide how much of the experience you build yourself. The API is RESTful, uses JSON for requests and responses and OAuth2 for authentication, and is described with OpenAPI v3.0. A sandbox environment replicates production so you can test the whole integration safely.

​
Two ways to integrate

You can call the REST API directly and build your own UI, or embed Ripio’s pre-built Crypto Widget. Both run on the same account and the same underlying service. See Choose your integration for a full comparison and help deciding which one fits your product.

​
What you can build

​
Where to start

​
FAQ

​
What’s the difference between the API and the Crypto Widget?

The API gives you full control over the experience: you build every screen and call each endpoint yourself. The Crypto Widget is an embeddable component where Ripio handles the UI and the trading flow, so you mainly generate a session code and mount it. For a detailed comparison, see Choose your integration.

​
Do my users need to complete KYC?

Your users’ identity data is required, and how it is verified depends on the integration and on your company: see User verification (KYC) for the Crypto Widget and Identity verification (KYC) for the API.

​
Can I test without moving real funds?

Yes. The sandbox environment works with test networks and offers tools to test your integration, such as simulating fiat deposits and sending test webhooks. See the sandbox sections of each walkthrough.