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

# Integration options

> Three ways to let customers buy and sell stablecoins: the widget on your website, the hosted page, or the API.

You can offer buying and selling in three ways. Pick by how much of the experience you want to own.

| | Widget | Hosted page | API |
| - | - | - | - |
| Where the customer pays | In a window on your page | On `ramp.onstacks.io` | In an interface you build |
| Your work | Add a script and a button | Add a link | Build the flow and a backend integration |
| Branding | Your name, colour and logo | Onstacks | Yours |
| Customer sign-in and identity check | Handled by Onstacks | Handled by Onstacks | Your own onboarding |
| Where you see payments | Dashboard, and webhooks if you want them | The customer sees the status on the page | Dashboard, API and webhooks |
| Fixing the amount or destination | Signed links | URL parameters | Request fields |
| Buy and sell | Yes | Yes | Yes |

## Widget on your website

Your page loads one script and opens the widget with your widget ID. The customer picks an amount, signs in with an email code, completes identity verification the first time, and pays or sends without leaving your site. You configure the name, colour, logo, directions and currencies in the dashboard, and payments appear under **Ramps**.

Choose this when you want buying and selling inside your product without building payment screens or handling identity checks.

<Card title="Add the widget" icon="code" href="/ramps/widget/quickstart" />

## Hosted page

Link or redirect the customer to `https://ramp.onstacks.io`; add `?tab=offramp` to open on the sell side. Sign-in, identity verification, payment and status all happen on that page. There's nothing to integrate beyond the link, and nothing to show in your dashboard: the customer sees the status on the page.

Choose this when the ramp isn't part of your product and you want a link that works today.

<Card title="Hosted page quickstart" icon="app-window" href="/ramps/hosted/quickstart" />

## API

Your backend requests a quote, confirms it with a destination (bank account, mobile money or wallet), funds the payment, and tracks it by polling or webhooks. You own every screen and your own customer onboarding.

Choose this when the ramp is core to your product, you need to trigger payouts from a backend with nobody in the loop, or you already verify your customers and don't want them to repeat it.

<Card title="API overview" icon="braces" href="/ramps/api/overview" />

## How a payment settles

For every payment, Onstacks picks a licensed provider for the local-currency leg based on the currency, the payment method, the amount and which providers are available for that combination. The rate shown to the customer includes all fees. On the API you can see the quoted options and choose, or let Onstacks choose. If a provider can't complete a payment, it is marked failed and any reserved funds are released.

Which assets, networks, currencies and directions are supported today is listed under [Coverage](/ramps/reference/coverage). On the API, the routes endpoint returns the current set.


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