> For the complete documentation index, see [llms.txt](https://docs.bill-z.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bill-z.com/readme.md).

# README

## Billz Pro Hybrid Execution Infrastructure for Crypto Treasury

Billz provides **hybrid crypto-to-fiat execution infrastructure** for businesses and individuals.

**Primary focus:** **Billz Pro** (business-first)\
**Secondary:** Billz (personal use, intentionally lighter documentation)

{% hint style="info" %}
**Positioning**\
Crypto-native in capital logic.\
Fintech-aligned in execution
{% endhint %}

```mermaid
flowchart LR
    A[On-chain Treasury] --> B[Billz Pro Orchestration]
    B --> C[Compliance & Risk Controls]
    C --> D[SEPA EUR]
    C --> E[ACH USD]
    B --> F[Proof & Reconciliation]
    A -. Optional .-> G[Vault]
    A -. Optional .-> H[Collateralized Liquidity]
```

## What Billz Pro is built for

Billz Pro is designed for operators who:

* hold treasury in crypto
* need to pay real-world obligations in fiat
* require **execution clarity** (not just a cash-out path)
* want a **compliance-aware** route into regulated rails

### Supported execution rails (high-level)

* **EUR via SEPA**
* **USD via ACH**

### Core product themes

* **Execution-first** payment workflows
* **Proof-oriented** documentation and reconciliation artifacts
* **Collateralized liquidity** workflows (lending/borrowing-based, where applicable)
* **Optional Treasury Vault** (market-driven, up to 10% APY)
* **Enterprise posture** (KYB, controls, documentation)

***

## Recommended reading order

### Billz Pro (business-first)

1. [Overview](/billz-pro/overview.md)
2. [Why Billz Pro](/billz-pro/why-billz-pro.md)
3. [Why Billz Pro vs Traditional Off-Ramps](/billz-pro/why-vs-offramps.md)
4. [Why Non-Custodial Matters](/billz-pro/why-non-custodial-matters.md)
5. [How It Works](/billz-pro/how-it-works.md)
6. [Capital Efficiency, Collateral & Lending/Borrowing](/capital-efficiency-lombard.md)
7. [Fees & Pricing Principles (Billz Pro)](/billz-pro/fees-old-version.md)
8. [Security & Compliance](/security-compliance.md)
9. [Regulatory Positioning (EU / US)](/regulatory-positioning.md)
10. [For Investors](/for-investors.md)
11. [Enterprise Onboarding & Contact](/enterprise-onboarding-contact.md)

### $BILLZ (teaser)

* [$BILLZ - Coming Soon](/usdbillz-token-overview.md)

### Billz (personal use)

* [Overview](/billz/overview.md)
* [How It Works](/billz/how-it-works.md)
* [Fees](/billz/fees.md)
* [FAQ](/faq.md)

***

{% hint style="info" %}
**Documentation boundaries**\
This documentation is intentionally high-level and strategic:

* enough detail to explain product scope and operating model
* without exposing sensitive implementation details, execution routing logic, or partner configuration

This documentation does not constitute legal, tax, or investment advice.
{% 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.bill-z.com/readme.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.