> 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>