> 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/security-compliance.md).

# security compliance

Billz Pro is built with an infrastructure mindset: **security, controls, and auditability**.

## Security principles (high-level)

* no user private key storage
* bounded execution scope (orchestration-focused)
* minimized sensitive data exposure where possible
* traceable payment execution artifacts

## Compliance posture (high-level)

Billz Pro is **compliance-aware** and built to interface with regulated rails.

Workflows may involve (depending on jurisdiction, volume, and risk profile):

* KYC (individual)
* KYB (business)
* enhanced due diligence (EDD)
* risk-based transaction monitoring

```mermaid
flowchart TD
    A[Payment Intent] --> B{Risk / Policy Checks}
    B -->|Pass| C[Proceed to Execution]
    B -->|Needs Review| D[Additional Review / EDD / Data Clarification]
    D --> E{Resolved?}
    E -->|Yes| C
    E -->|No| F[Delay / Reject / Rework]
```

> ### Review triggers (visual summary)

***

## What can trigger additional review

* unusual volume or frequency
* higher-risk recipient or jurisdiction profiles
* incomplete / inconsistent data
* transaction pattern anomalies
* threshold events under internal or partner policies

{% hint style="info" %}
Compliance review can affect timelines. This is normal when operating at the boundary between crypto capital and regulated banking rails.
{% endhint %}

***

## Mini FAQ

<details>

<summary>Does compliance-aware mean fully regulated bank?</summary>

No. Billz Pro is infrastructure built to interface with regulated systems, not replace them.

</details>

<details>

<summary>Can compliance review delay execution?</summary>

Yes. That is a normal possibility in regulated rail workflows.

</details>


---

# 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/security-compliance.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.