> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ripio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get started with Ripio's local stablecoins and crypto infrastructure

> Ripio's local stablecoins and crypto infrastructure for Latin America. Offer wARS, wBRL, wMXN, wCOP, wPEN, wCLP and global crypto to your users through Crypto as a Service or Ramps.

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.

| Token | Pegged to | Contract |
| - | - | - |
| ![wARS](https://b2b-widget-onramp.ripio.com/wars.png) **wARS** | Argentine peso | `0x0dc4f92879b7670e5f4e4e6e3c801d229129d90d` |
| ![wBRL](https://b2b-widget-onramp.ripio.com/wbrl.png) **wBRL** | Brazilian real | `0xd76f5faf6888e24d9f04bf92a0c8b921fe4390e0` |
| ![wMXN](https://b2b-widget-onramp.ripio.com/wmxn.png) **wMXN** | Mexican peso | `0x337e7456b420bd3481e7fa61fa9850343d610d34` |
| ![wCOP](https://b2b-widget-onramp.ripio.com/wcop.png) **wCOP** | Colombian peso | `0x8a1d45e102e886510e891d2ec656a708991e2d76` |
| ![wPEN](https://coin-images.coingecko.com/coins/images/70975/large/wpen_logo_1.png) **wPEN** | Peruvian sol | `0x4F34c8b3b5FB6D98Da888F0feA543d4d9C9F2eBE` |
| ![wCLP](https://coin-images.coingecko.com/coins/images/70976/large/wclp_logo_1.png) **wCLP** | Chilean peso | `0x61D450a098b6a7f69fC4b98CE68198fe59768651` |

Each token uses the same contract address on **Ethereum, Base, Polygon, World Chain, BNB Smart Chain and Gnosis**.

> [!NOTE]
>
> On **Tempo** the contract addresses are different. Contact [b2b@ripio.com](mailto:b2b@ripio.com) 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](https://docs.ripio.com/crypto-as-a-service/overview/introduction.md)**
>
> 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](https://docs.ripio.com/ramps-api/overview/introduction.md)**
>
> 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**.

| | Crypto as a Service | Ramps |
| - | - | - |
| **Ideal for** | Custodial products: neobanks, fintechs, exchanges | Self-custodial and DeFi products: wallets, dApps, protocols |
| **What your users do** | Hold, buy, sell and swap assets, and deposit and withdraw them on-chain | Turn fiat into crypto (On-Ramp) or crypto into fiat (Off-Ramp) |
| **Where the assets end up** | In the user's account, held by Ripio, until they sell or withdraw them | At the destination wallet address, right after the conversion |
| **Where the fiat comes from or goes** | The user's fiat account, with [Banking as a Service](https://docs.ripio.com/crypto-as-a-service/guides/banking-as-a-service.md), or a daily settlement between you and Ripio | A local payment method, and the user's own bank account for payouts |
| **Extra features** | [Yields](https://docs.ripio.com/crypto-as-a-service/opt-ins/yield-opt-in.md), swaps, [auto swap addresses](https://docs.ripio.com/crypto-as-a-service/auto-swap-addresses/create-auto-swap-address-for-end-user.md) | [Sell and Pay](https://docs.ripio.com/ramps-api/sell-and-pay/create-sell-and-pay.md) (pay QR codes with crypto), [refunds](https://docs.ripio.com/ramps-api/refunds/overview.md) |
| **Fiat coverage** | Ask the team for the countries available to your company | [Argentina, Mexico, Colombia and Brazil](https://docs.ripio.com/ramps-api/overview/countries/overview.md). Peru and Chile coming soon |

## Common use cases

> **A wallet or dApp where users fund their address in local currency**
>
> 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](https://docs.ripio.com/ramps-api/guides/on-ramp-integration.md)**

> **A neobank or fintech app that wants a crypto section**
>
> 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](https://docs.ripio.com/crypto-as-a-service/overview/introduction.md)**

> **Cross-border payments and remittances**
>
> 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](mailto:b2b@ripio.com)** to set it up.

> **A platform that settles in crypto and needs to cash out**
>
> 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](https://docs.ripio.com/ramps-api/guides/off-ramp-integration.md)**

> **Savings in stablecoins with yield**
>
> Your users keep a stablecoin balance in your app and earn yield on it over time. → **[Crypto as a Service](https://docs.ripio.com/crypto-as-a-service/overview/introduction.md)**

> **Paying QR codes with crypto**
>
> Your users pay a merchant's QR code with crypto, and the merchant receives fiat. → **[Ramps: Sell and Pay](https://docs.ripio.com/ramps-api/sell-and-pay/create-sell-and-pay.md)**

## 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](https://docs.ripio.com/crypto-as-a-service/overview/choose-your-integration.md)**
>
> Compare the CaaS API with the Crypto Widget.

> **[Ramps: API or widget](https://docs.ripio.com/ramps-api/overview/choose-your-integration.md)**
>
> Compare the Ramps API with the Ramps Widget.

## Start building

**1. Get your sandbox credentials**

[Register your company](https://platform.ripio.com/register) 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](https://docs.ripio.com/crypto-as-a-service/access-token/get-access-token.md) or [Ramps](https://docs.ripio.com/ramps-api/authentication/acquire-access-token.md).

**4. Follow the walkthrough**

Start with [Trading integration](https://docs.ripio.com/crypto-as-a-service/guides/trading-integration.md) for CaaS, or the [On-Ramp walkthrough](https://docs.ripio.com/ramps-api/guides/on-ramp-integration.md) for Ramps.

Not sure which fits your product? Write to [b2b@ripio.com](mailto:b2b@ripio.com) and we'll help you choose.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.