> For the complete documentation index, see [llms.txt](https://docs.fairmath.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmath.xyz/fair-math-payments/key-features.md).

# Key Features

Fair Math Payments is based on two key abstractions:

#### Privacy Zones

Configurable privacy compatible environments that define:

* What metadata is hidden (amounts, senders, timing)
* What performance/cost is expected
* How compliance is handled (audit logs, disclosure rules)

Each zone can be tailored for general use, enterprise-grade flows, or app-specific needs.

#### Privacy Providers

Entities that power zones using one of three models:

* **Trusted** — custodians, issuers, or internal teams
* **Cryptographic** — ZK, MPC, or FHE backends
* **Hybrid** — TEE + proof-based logic

This separation allows privacy to be **modular and composable**, with asset movement and policy enforcement across zones.


---

# 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.fairmath.xyz/fair-math-payments/key-features.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.