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

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

Compliance review can affect timelines. This is normal when operating at the boundary between crypto capital and regulated banking rails.

---

Mini FAQ

Does compliance-aware mean fully regulated bank?

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

Can compliance review delay execution?

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