Use case · build on OZAV
Treasury Live
Hold, move, and reconcile dollar balances across corridors and networks — built on OZAV's live Accounts and Corridors.
Build treasury on OZAV.
Manage multi-currency, multi-rail balances with the controls your finance team needs, composed from OZAV's live primitives.
Multi-rail balances
Hold value across fiat and stablecoins.
Transparent conversion
Convert between currencies with conditions shown up front.
Approval workflows
Velocity limits and multi-party approvals.
Real-time visibility
One view across every corridor.
Configure per client. Pooled or segregated balances, approval workflows, velocity limits — configure per client.
Built for developers
Treasury is one GET /balances call — idempotent, typed, and webhook-backed. Sandbox, TypeScript SDK, and docs from day one.
Read the docs# Read balances across rails GET /balances → 200 OK { "usd": 125000, "brl": 0, "usdc": 50000, "eurc": 12000 }
Security & controls
Every action on Treasury runs on regulated infrastructure, with controls that satisfy compliance from day one.
Authorization required
No unilateral movement of funds — every privileged action is explicitly approved.
Expiring approval sessions
Approvals expire by default, limiting blast radius, with instant revocation.
Approval & per-transaction limits
Approval workflows plus per-transaction limits on external crypto transfers.
Tenant data isolation
Each client's data is isolated end to end with row-level security.
Build in hours. Go live in weeks.
Build with Treasury in hours; go live on your brand in weeks — not a multi-quarter banking project.
Build in hours, live in weeks
Your brand & product
You own the relationship
Hosted or bring-your-own KYC/KYB
Custom model
Compliance built in, not bolted on.
Compliance for Treasury is part of the flow — KYC, KYB, AML screening, transaction monitoring, and Travel Rule support come standard, so you grow without owning the regulatory overhead.