> 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/about.md).

# About

<figure><img src="https://1912462442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPgl1t8uCisy0T57qHG35%2Fuploads%2FbSUu6kp3KqfbXBE9ADky%2Ffonbnk-widget.png?alt=media&#x26;token=23384c47-b45e-49fe-b466-397f5e1ad378" alt=""><figcaption></figcaption></figure>

Welcome to the Fonbnk documentation.

Fonbnk moves money between local currency and crypto in [20 countries](/supported-countries-and-cryptocurrencies.md). A user pays with a bank transfer, mobile money, a digital wallet or airtime, and receives crypto — or the other way round. We find the counterparty, hold the rate, run KYC, and settle.

### Pick your integration

|                 | [Pay Widget](/widget-integration/getting-started.md) | [Server to server](/server-to-server/getting-started.md)       |
| --------------- | ---------------------------------------------------- | -------------------------------------------------------------- |
| What it is      | Our hosted checkout, opened at a URL you build       | Our REST API, called from your backend                         |
| You build       | A link or an iframe                                  | The whole user journey                                         |
| Who owns the UI | Fonbnk                                               | You                                                            |
| KYC screens     | Handled for you                                      | You collect and submit the documents                           |
| Good for        | Getting live in a day, or embedding a checkout       | Full control of the experience, aggregators, automated payouts |

The two are not exclusive. A common shape is the API for pricing and the widget for the payment itself — create a quote server-side, then hand the `quoteId` to the widget so the price you advertised is the price the user gets.

### What you can build

* **On-ramp** — a user pays local currency, crypto lands in their wallet. [How it works](/how-it-works.md)
* **Off-ramp** — a user sends crypto, local currency lands in their bank or mobile money account.
* **Collections** — a user pays local currency and **your** USD merchant balance is credited.
* **Payouts** — you spend your USD balance to pay users in their local currency.

The five order shapes and how to call them are on [Flow examples](/server-to-server/integration-guide/flow-examples.md).

### Start here

1. Register on the [sandbox dashboard](https://sandbox-dashboard.fonbnk.com/login) and get your keys.
2. Read [How it works](/how-it-works.md) for the end-user journey.
3. Follow [Widget integration](/widget-integration/getting-started.md) or [Server to server](/server-to-server/getting-started.md).

{% hint style="info" %}
Everything works in sandbox with simulated money, including forced failures, underpayments and overpayments. Build there first — moving to production is a change of base URL and keys. See [Servers](/server-to-server/servers.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fonbnk.com/about.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
