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

# The problem

Crypto is easy to hold and hard to spend. Around 741 million people own crypto, most of them in Asia, Africa and Latin America. Turning a wallet balance into something useful still runs through a bank, an exchange and an identity check.

Three everyday needs show the gap:

* **Travel data.** Travellers land, look for a SIM shop and pay roaming prices. A travel eSIM costs about $16 a trip against $41 for roaming, but the major eSIM apps accept cards, not wallets.
* **Spending online.** Most crypto cards are offered only in the US, Europe and a handful of other markets. Wise, Revolut and MetaMask Card are unavailable across much of Asia and Africa.
* **Verification.** Account sign-ups and two-factor codes require a phone number, which usually means a local SIM and an ID.

The infrastructure to close this gap now exists. Visa supports more than 160 stablecoin-linked card programs, annual crypto card spending has passed $18 billion, and travel eSIM revenue grew 85% to $1.8 billion in 2025. What is missing is a consumer product built around the wallet.


---

# 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/the-problem.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.