Compliance · Security

Security built for money.

Defense-in-depth across infrastructure, keys, and access — designed to protect customer funds and data.

Security at Stellus starts from the assumption that we're a target. We apply layered controls across our infrastructure, encrypt data in transit and at rest, enforce least-privilege access, and separate duties around any operation that touches funds or keys.

Our controls

  • Encryption

    Data encrypted in transit and at rest, with modern cipher suites and rotation.

  • Access

    Least-privilege, role-separated access with mandatory MFA and audited activity.

  • Key management

    Keys protected under HSM-backed controls with multi-party approval for sensitive operations.

  • Monitoring

    Continuous logging, anomaly detection, and incident response.

  • Testing

    Regular independent penetration testing and code review.

✦ Programmable compliance

Compliance, as code.

Stellus lets banks and PSPs define the rules their tokenized dollars must follow — counterparty, jurisdiction, risk, velocity, quorum, hours — and enforces them inline on every transfer, before settlement. Chainalysis screening powers the wallet and sanctions layer.

Chainalysis
TRM Labs
Elliptic
policy.ts
Inline
1// Programmable policy · runs inline on every transfer
2policy.require({
3 counterparty: verified("OzID"),
4 riskScore: ≤ 3 // Chainalysis KYT,
5 jurisdiction: not.in(sanctions.list),
6 velocity: ≤ $1M / 24h,
7 approvers: quorum(2, role.treasurer),
8});
9 
10// → policy resolves before settlement; failure is deterministic
Things you can program
  • Counterparty
    Only OzID-verified wallets, Chainalysis risk score ≤ 3.
  • Jurisdiction
    Block transfers originating from or terminating in sanctioned regions.
  • Velocity
    Cap institutional outflows at $1M per 24h; auto-flag bursts.
  • Quorum
    Require two-of-three approver signatures above a configurable threshold.
  • Hours
    Permit on-chain settlement only during your defined operating window.
  • Asset
    Allow OZD-only flows between specific account types; allow ozUSD broadly.

Programmable compliance applies to both ozUSD (the bearer stablecoin) and OZD (the tokenized deposit). Policy is a runtime contract — change it, and the next transfer obeys.

Read our security overview.
Talk to us