> For the complete documentation index, see [llms.txt](https://amelias-organization-20.gitbook.io/olio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amelias-organization-20.gitbook.io/olio/readme.md).

# Welcome to Olio

**Private by default. Provable when needed.**

Olio is a private payment rail for businesses, built on Stellar. Your customers pay your invoices in USDC. The payments stay confidential on chain, so competitors, other customers and strangers can't read your revenue. When a bank, accountant or tax office asks, you can still prove any single payment.

## How it works, in one minute

* **Verify** your business, or yourself if you work as a sole proprietor.
* **Issue an invoice**, or share a payment link or QR code.
* **Your customer pays** in USDC, from Stellar or from another chain such as Ethereum, Base or Solana. They don't need an Olio account.
* **The payment settles privately.** It becomes a private note that only you can read and spend, and it is matched to the invoice it paid.
* **Prove it when asked.** Export a disclosure for any single payment without revealing the others. Publish your verified badge so customers can check that Olio verified your business.
* **Cash out** to a Stellar wallet.

The privacy happens in the background. Neither you nor your customers need to understand the cryptography.

## What stays private, and what doesn't

Observers on chain can't see who paid you, how much, or connect a payment to the money you later withdraw. Olio sees invoice amounts and due dates so it can match payments to invoices, but invoice content such as customer names and line items is encrypted in your browser. When you withdraw, the amount and destination are public. [Olio's Practical Privacy](/olio/is-olio-for-you/practical-privacy.md) covers the details.

## Where to start

{% hint style="info" %}
**New to crypto?** Start with [The Basics, No Jargon](/olio/new-to-crypto-start-here/new-to-crypto.md).
{% endhint %}

* **Deciding whether Olio fits your business** → [Who Olio Is For](/olio/is-olio-for-you/who-its-for.md) and [Why Privacy Matters](/olio/is-olio-for-you/why-privacy-matters.md)
* **Ready to set up** → [Quickstart](/olio/getting-started/quickstart.md)
* **Proving payments to a bank or auditor** → [Traceability, on your terms](/olio/is-olio-for-you/practical-privacy.md#traceability-on-your-terms)
* **How the privacy works** → [How Olio Works](/olio/under-the-hood/how-it-works.md)
* **Questions** → [FAQs](/olio/more/faqs.md)

## Current status

Olio runs on **testnet**, a practice network that uses test money. It has not been independently audited yet. Don't use it for real funds until launch. Some features will change before then, and these docs say clearly what is live and what isn't.

Olio will never ask for your PIN, passkey or recovery details. Anyone who does is not Olio.


---

# 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://amelias-organization-20.gitbook.io/olio/readme.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.