Run crypto treasury likethe rest of finance.
Hold stablecoins and reserves with the controls you expect from a bank portal: a vault per entity, approval chains by amount, and exports your auditors can read. Your team keeps one of the keys, always.
Run crypto treasury like the rest of finance.
What usually goes wrong.
One person, one seed phrase
Many companies still keep reserves behind a single hardware wallet or one executive's seed phrase. That is a key-person risk your board will ask about.
Custodians slow everything down
Handing assets to a custodian adds counterparty risk, withdrawal queues and per-transfer tickets, which makes stablecoin payments slower than wires.
Spreadsheets as controls
Approvals happen in chat, limits live in a spreadsheet, and audit evidence is a screenshot. None of that survives a SOC 2 or year-end audit.
Built for corporate treasury.
Every capability below runs on 2-of-3 MPC keys where your share, or your approval, is always required.
A vault per entity
Separate vaults for each subsidiary, region or business line, each with its own approvers and limits.
Approval chains by amount
Under $25k needs one approver, over $100k needs the CFO plus one, and new destinations always need two.
Batch payouts
Pay vendors, contractors or payroll in stablecoins from a CSV or the API, with one approval per batch.
Audit-ready exports
Fiat value at transfer time, approver identities and policy decisions in every export, ready for your ERP.
A typical day, step by step.
- Step 1
Request
Accounts payable uploads a payout batch or a teammate requests a transfer in the console.
- Step 2
Policy
The batch is checked against destination allow-lists, per-day limits and screening.
- Step 3
Approve
The controller and CFO approve on their phones with the full batch in front of them.
- Step 4
Sign and settle
Your share and ours sign; the payout settles on-chain in minutes and lands in your ledger export.
Questions from corporate treasury teams.
Can we keep separate vaults for each legal entity?
Yes. Create as many vaults as you need, each with its own policies, approvers and reporting, and see consolidated balances in one view.
How do we account for crypto transfers?
Every transfer records the asset, amount, fiat value at the time, approvers and policy decision. Export statements per entity and vault, or pull them through the API into your accounting system.
Do we need a custodian for our auditors?
No. Auditors get a read-only role with access to balances, the hash-chained audit log and exports. Because you hold a key share, assets remain under your control.
Other solutions
See it with your own vault structure.
We'll configure a sandbox with your entities, approvers and limits before the first call ends.