Skip to main content
Ripio has been building crypto infrastructure in Latin America since 2013. Through our B2B APIs you can bring that infrastructure into your own product: local-currency stablecoins, global crypto assets, and the fiat rails to move between them. Everything is available through two products, Crypto as a Service and Ramps, each with a REST API, an embeddable widget and a sandbox to test the whole integration.

​
Local stablecoins

Ripio’s wFiat stablecoins are fully collateralized tokens pegged 1:1 to Latin American currencies. They let your users hold, send and pay in their own unit of account on-chain, without converting to USD. Each token uses the same contract address on Ethereum, Base, Polygon, World Chain, BNB Smart Chain and Gnosis.
On Tempo the contract addresses are different. Contact [email protected] if you need them.
Next to the local stablecoins, the same APIs give you access to global assets such as BTC, ETH, USDC and USDT.

​
Choose your product

Both products give you access to the same assets. The difference is where your users’ crypto lives.

Crypto as a Service

Your users get a crypto account inside your product. They buy, sell, swap, hold, send and receive local stablecoins and crypto, and can earn yield on their balances. Ripio holds the assets on their behalf.Ideal for custodial products: neobanks, fintechs, exchanges and apps that hold their users’ funds.

Ramps

Your users convert between fiat and crypto. They pay in local currency and receive stablecoins or crypto at a wallet address, or send them and get paid out to their bank account. No balance is held in between.Ideal for self-custodial and DeFi products: wallets, dApps and protocols where users keep their own keys.
To decide, answer this: do your users need to keep a balance inside your product?
  • Yes: they open your app to check their balance, trade, and decide later what to do with it. You need Crypto as a Service.
  • No: the tokens go to (or come from) a wallet they or you already have, and your product handles the conversion. You need Ramps.

​
Common use cases

Your users pay with a local bank transfer or PIX and receive wARS, wBRL, wMXN or wCOP straight to their self-custodial address. → Ramps: On-Ramp
Your users see their stablecoins and crypto next to their money, buy when the price drops and sell later. They keep a balance in your app. → Crypto as a Service
This is the perfect use case for our local stablecoins: move value on-chain in wFiat and convert only at the endpoints, with fiat in on one side and fiat out on the other. For these flows we operate OTC. → Contact the team to set it up.
Your users (or you) receive stablecoins or crypto and turn them into ARS, MXN, COP or BRL in a local bank account. → Ramps: Off-Ramp
Your users keep a stablecoin balance in your app and earn yield on it over time. → Crypto as a Service
Your users pay a merchant’s QR code with crypto, and the merchant receives fiat. → Ramps: Sell and Pay

​
API or widget?

Once you’ve chosen a product, decide how much of the experience you want to build. Both products offer two integration paths on the same account:
  • REST API: you build every screen and call the endpoints from your backend. Maximum control.
  • Widget: you embed Ripio’s pre-built, themeable UI. The fastest way to go live.

Crypto as a Service: API or widget

Compare the CaaS API with the Crypto Widget.

Ramps: API or widget

Compare the Ramps API with the Ramps Widget.

​
Start building

1

Get your sandbox credentials

Register your company and the team will set up your sandbox account.
2

Pick your product and integration

Use the sections above to choose between Crypto as a Service and Ramps, and between the API and the widget.
3

Authenticate

Get an OAuth2 access token for Crypto as a Service or Ramps.
4

Follow the walkthrough

Start with Trading integration for CaaS, or the On-Ramp walkthrough for Ramps.
Not sure which fits your product? Write to [email protected] and we’ll help you choose.