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

# Integration examples

This page assumes you have a registered merchant and know how to [sign the URL](/widget-integration/signing-the-url.md). Every parameter used here is documented on [URL params](/widget-integration/url-params.md).

### On-ramp to a predefined address

The user pays fiat and we deliver 10 Polygon USDT to a wallet you choose. Neither the wallet nor the amount is theirs to change:

* `source`
* `signature`
* `network` — POLYGON
* `asset` — USDT
* `address` — 0x41018795fA95783117242244303fd7e26e964eE8
* `amount` — 10
* `currency` — crypto
* `freezeWallet` — true, so the user cannot change the wallet
* `freezeAmount` — true, so the user cannot change the amount

{% code overflow="wrap" %}

```
https://sandbox-pay.fonbnk.com?source=...&signature=...&network=POLYGON&asset=USDT&address=0x41018795fA95783117242244303fd7e26e964eE8&amount=10&currency=crypto&freezeWallet=true&freezeAmount=true
```

{% endcode %}

When the user creates an order from this URL you receive [webhooks](/server-to-server/webhooks.md) at the endpoint configured in your dashboard.

### Off-ramp to a specific fiat type

The user sells Celo CUSD and receives 50,000 NGN. Note the `/offramp` path — that is what selects the sell flow:

* `source`
* `signature`
* `network` — CELO
* `asset` — CUSD
* `amount` — 50000
* `currency` — local
* `countryIsoCode` — NG

{% code overflow="wrap" %}

```
https://sandbox-pay.fonbnk.com/offramp?source=...&signature=...&network=CELO&asset=CUSD&amount=50000&currency=local&countryIsoCode=NG
```

{% endcode %}

### On-ramp using a quote

You are an on-ramp aggregator: you want to show our price in your own UI and have it hold when the user reaches the widget. Fetch a quote from [Create quote](/server-to-server/api-endpoints/create-quote.md) and pass its `quoteId`.

Here the user converts 1,000 KES of M-PESA into Tron USDT:

* `source`
* `signature`
* `quoteId` — the quote ID from the API response
* `network` — TRON
* `asset` — USDT
* `amount` — 1000
* `currency` — local
* `paymentChannel` — mobile\_money
* `countryIsoCode` — KE

{% code overflow="wrap" %}

```
https://sandbox-pay.fonbnk.com?source=...&signature=...&quoteId=...&network=TRON&asset=USDT&amount=1000&currency=local&countryIsoCode=KE&paymentChannel=mobile_money
```

{% endcode %}

{% hint style="warning" %}
A quote expires. Fetch it when the user is ready to be sent to the widget, not when your page loads — `quoteExpiresAt` on the quote tells you how long you have.
{% endhint %}

### Going further

All three examples still show the widget's own screens. To skip them — amount, wallet, auth, even the order form — see [Skipping screens](/widget-integration/skipping-screens.md).


---

# 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.fonbnk.com/widget-integration/integration-examples.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.