> 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/how-we-fix-it/the-nofi-account.md).

# The NØFI Account

{% hint style="info" %}
A self-custody stablecoin account with three core pillars: **Hold, Spend, Earn.**
{% endhint %}

## The Three Pillars

### Hold

Funds sit in a **non-custodial embedded wallet** the user controls — not a NØFI-held balance. Powered by Privy, users get a real self-custodial account without managing seed phrases directly.

* No custody risk — NØFI never holds user funds
* No exchange counterparty risk
* Portable — the wallet is the user's, not NØFI's

### Spend

A **self-custodial Visa card**, live in Colombia via Gnosis Pay, that spends directly from the user's wallet at 80M+ merchants worldwide.

* Works at any Visa merchant, online or in-store
* Apple Pay and Google Pay compatible
* Spends directly from self-custody — no need to "load" a card

### Earn

**Idle balances earn pass-through yield** via M^0 rather than sitting flat. In a world where local savings accounts earn 1-3% in a currency depreciating 15-50%/year, earning yield in USD stablecoins is transformative.

## The UX Standard

The NØFI account is live today on web, with account opening and card issuance built to feel like **signing up for a neobank** rather than configuring a crypto wallet.

The target user shouldn't need to understand:

* ❌ Which chain they're on
* ❌ What a gas fee is
* ❌ How to bridge assets
* ❌ How to manage private keys

That complexity is handled underneath. The user sees a balance, a card, and a clean interface.

{% hint style="success" %}
**Design principle:** If the user has to think about crypto infrastructure, we've failed. The blockchain is the backend — not the product.
{% 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/how-we-fix-it/the-nofi-account.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.