> For the complete documentation index, see [llms.txt](https://docs.nofi.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nofi.money/current-gaps/fiat-crypto-interoperability.md).

# Fiat/Crypto Interoperability

{% hint style="info" %}
**The core problem:** Stablecoins are only useful to most people at the moments they touch the real world — and every one of those moments involves friction.
{% endhint %}

## Where Value Meets the Real World

Stablecoins touch the real world at three critical points:

1. **Inflow** — when they land as a payout from a platform or client
2. **Spend** — when they're used at a merchant via card or payment
3. **Outflow** — when they're converted to local currency for bills and rent

Every one of these moments today involves friction — a manual off-ramp, a P2P trade, a card that doesn't work, or a delay that costs money on a depreciating currency.

## The Cost of Friction

| Friction Point                   | Current Cost     | Time     | User Experience                  |
| -------------------------------- | ---------------- | -------- | -------------------------------- |
| CEX off-ramp to local bank       | 2-5% fees        | 1-3 days | Multiple apps, KYC per platform  |
| P2P stablecoin trade             | 3-8% spread      | Hours    | Counterparty risk, scam exposure |
| International wire (traditional) | $25-50 flat + FX | 3-5 days | Branch visit often required      |
| Crypto debit card (custodial)    | 1-3% + FX        | Instant  | Gives up self-custody entirely   |

> For a creator earning $3,000/month internationally, these frictions cost **$150-400/month** in fees and spread alone — that's **$1,800-4,800/year** lost to broken infrastructure.

## The Invisible Rails

For stablecoins to function as money rather than as an asset people trade, on-ramps and off-ramps have to be **invisible**. The user shouldn't need to think about which network they're on or which local rail is settling their withdrawal — they should just get paid, spend, and save.

NØFI is built around this interoperability layer:

* **Koywe** for local COP off-ramps in Colombia
* **Bridge** for USD rails and stablecoin infrastructure
* **LI.FI** for cross-chain routing and liquidity aggregation
* **Gnosis Pay** for self-custodial Visa card spend

{% hint style="success" %}
**NØFI's approach:** Use best-in-class local partners for each market rather than asking users to solve interoperability themselves. The crypto rails do the work underneath — the user just sees money moving.
{% 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.nofi.money/current-gaps/fiat-crypto-interoperability.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.