Business
Treasury controls
Role-based policies, co-signers, vaults and yield on idle balance: the controls a finance team expects, on a balance nobody else can see.
Status: pre-launch. Noirpay is being built. This page describes the design as specified in the whitepaper; nothing on it is live on Robinhood Chain yet, and details can change before launch. See What's live today.
Seats and roles
Each finance user has a seat (pricing) and a role:
| Role | Can |
|---|---|
| Viewer | See balances and history for the vaults they're granted |
| Preparer | Build batches and payments; cannot approve |
| Approver | Approve within their limit |
| Admin | Manage seats, roles, policies and viewing keys |
Policies
- Spending caps per vault, per day and per month.
- Approval thresholds: above X requires one approver; above Y requires two, or a co-signer.
- Allowlists for recurring recipients.
- Time locks on policy changes, so a compromised admin can't loosen controls instantly.
Shielded multi-sig
For companies that can't put funds behind a single key, the treasury's spending key can be a threshold key across co-signers (for example 2 of 3 directors). Every spend, batch and viewing-key issuance requires the threshold. Co-signers use hardware wallets.
Vaults
A business account uses vaults like a personal one: operating, payroll, tax reserve, treasury. Policies attach per vault.
Yield on idle balance
Auto-sweep above an operating float moves idle treasury into the yield allocation, credited per note, invisible on-chain.
Books and audit
Grant the accountant a viewing key scoped to the fiscal year and revoke it after filing. The tax and accounting export is generated locally from that key.