Roles
Separates who can initiate from who can approve a run.
For teams
Businesses need private money that still integrates: APIs, roles, invoices, and checkout — without publishing salary bands or customer graphs.

Compensation stays a note, not a public payslip.
Payroll
On a public chain, payroll is a spreadsheet anyone can scrape. XEROPAY is designed so each employee receives into a stealth address, with roles for who can approve, and viewing keys for auditors.
Separates who can initiate from who can approve a run.
Large runs wait for a second operator.
CSV in, shielded notes out — without a public payslip.
Treasury
Competitors, journalists, and anyone with a block explorer can currently read a protocol's treasury in real time. A shielded treasury is designed so only operators and named auditors see the books.
| Public treasury | XEROPAY | |
|---|---|---|
| Runway | Visible to anyone | Encrypted notes |
| Payroll | Salary graph | Stealth destinations |
| Vendors | Every invoice on-chain | Private settlement, optional proof |
API and webhooks
REST-shaped endpoints for shield, unshield, and note queries. Events fire when a payment settles, fails, or a viewing key is disclosed. There is no public sandbox key yet — this is the intended surface, not a live contract list.
Intended surface
Checkout
Checkout is designed so a customer can pay from a shielded note or a one-time stealth address. You receive confirmation; you do not inherit a public list of every payer.
Invoicing
Issue an invoice to a handle. Each one gets a fresh destination. Paid invoices can export a proof for accounting without publishing the whole client list.
Draft
Internal only. Nothing on chain.
Issued
Payee handle + amount. Fresh destination per invoice.
Paid
Note lands in treasury. Optional viewing-key export.
Overdue
Local reminder. No public dunning trail.
Pricing
There is no public fee table yet. Early teams get a seat, a support channel, and a written scope of what is actually live. When numbers exist, they will live here — not as a teaser.
Starter
One operator, viewing keys, CSV export. For teams still mapping payroll.
Team
Roles, approval thresholds, and a named support channel.
Enterprise
SSO, custom screening policy, dedicated onboarding — scoped when you ask.