> 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/regulatory-positioning.md).

# regulatory positioning

## Billz Pro is built to interface with regulated systems, not replace them

Billz Pro positions itself as a **hybrid execution infrastructure**:

* crypto-native in treasury logic,
* compliance-aware in execution,
* aligned with regulated fiat rails for settlement.

```mermaid
flowchart LR
    A[Billz Pro Hybrid Execution Layer] --> B[EU Context]
    A --> C[US Context]
    B --> D[SEPA / EUR Execution]
    C --> E[ACH / USD Execution]
    A --> F[Compliance-Aware Controls]
    A --> G[Documentation & Proof]
```

> ### Regulatory framing (visual, high-level)

{% hint style="info" %}

### Why this page is intentionally high-level

Regulatory interpretation depends on:

* jurisdiction
* facts and implementation details
* user profile and transaction type

Public docs should not overstate legal conclusions.
{% endhint %}

***

## EU / US framing (high-level)

### EU

Billz Pro supports EUR execution via SEPA and is designed to coexist with regulated payment infrastructure and compliance requirements.

### US

Billz Pro supports USD execution via ACH and is designed to operate with jurisdiction-aware controls and regulated rail requirements.

## What Billz Pro does not claim in public docs

Billz Pro does not publicly claim:

* to be a bank
* to replace regulated institutions
* to eliminate compliance obligations
* to provide legal or tax advice

***


---

# 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/regulatory-positioning.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.