> For the complete documentation index, see [llms.txt](https://docs.gofi.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gofi.cash/how-it-works.md).

# How it works

The user signs one payment from their own wallet. GoFi prices the order, routes it to a licensed provider, and the result appears in the GoFi dashboard within minutes. GoFi builds on existing suppliers and card issuers instead of becoming a telecom or a bank, which keeps launch fast and lets it add providers market by market.

| Step | Who              | What happens                                                           |
| ---- | ---------------- | ---------------------------------------------------------------------- |
| 1    | Your wallet      | Pays in USDC on Solana or USDG on Robinhood                            |
| 2    | GoFi checkout    | Shows the price in your token, routes the order, never holds your keys |
| 3    | eSIM suppliers   | Deliver the eSIM QR code to your dashboard                             |
| 3    | Number providers | Deliver the number to your dashboard                                   |
| 3    | Card issuer      | Loads and holds the card balance                                       |


---

# 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.gofi.cash/how-it-works.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.