> For the complete documentation index, see [llms.txt](https://docs.swapped.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swapped.com/swapped-ramp/readme-1.md).

# On-ramp Integration

Swapped.com Onramp is an embeddable widget that lets your users buy cryptocurrency directly within your application. Support for 40+ payment methods across 150+ countries.

#### Why Swapped

* **Competitive fees** - Among the lowest rates in the market
* **Global coverage** - 150+ countries, 40+ local payment methods
* **24/7 human support** - Real support agents, no bots

<figure><img src="https://2102146608-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDf1VBRUItvdLkWUnkNIb%2Fuploads%2FPQibrvMkvSegnXyLKBWW%2FSwapped%20Widget.gif?alt=media&amp;token=30696059-bf50-46ba-afa3-6c8eb7ff5eed" alt=""><figcaption></figcaption></figure>

### User Flow

1. Select cryptocurrency, fiat currency, and amount
2. Choose payment method
3. Authenticate via one-time password (OTP)
4. Enter destination wallet address
5. Complete payment
6. Receive crypto

### Merchant Dashboard

Manage your integration at [dashboard.swapped.com](https://dashboard.swapped.com):

* View volume and transaction statistics
* Monitor orders
* Configure integration parameters


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.swapped.com/swapped-ramp/readme-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.