Create drafts fast. Approve payments carefully.

CipherPay gives you one place to prepare, review, and approve payouts on Solana. It is useful when you want private payment flows, a clear approval step, and a record of what was drafted and sent.

The product is organized around four entry points: `Pay` for one-off sends, `Bulk pay` for roster-style batches, `Payables` for recurring recipients, and `Agent Pay` for linked agent wallets.

Every payout follows the same path. First you create a draft. CipherPay then checks the rows, shows you the totals, and waits for a wallet approval before anything is sent.

Agent Pay adds one layer: agents have their own wallet and shielded balance. Owner approvals and policy limits decide when agent funds can move.

CipherPay separates drafting, approval, run state, and the shielded transfer rail. The wallet signs the approval, application state tracks payout progress, and the private pool handles deposit, root, nullifier, and withdrawal steps for the recipient flow.

The diagram below shows the main product path from wallet sign-in through payout run creation, shielded settlement, recipient delivery, and receipt tracking.

Operator

CipherPay control plane

Private settlement rail

Evidence loop

User

Starts the flow.

Wallet

Signs auth and transactions.

Sign in

Verifies wallet ownership.

Run

Creates the payout run.

State

Stores progress and rows.

ZK shielded pool

Verifies deposits, roots, and nullifiers.

Shielded SOL

Holds shielded SOL notes.

Private transfer

Deposits and settles privately.

Receiver

Gets paid.

Receipts

Tracks signatures and status.

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.

Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

User

Starts the flow.

Wallet

Signs auth and transactions.

Run

Signs in and creates the payout run.

ZK shielded pool

Verifies roots and nullifiers.

Private transfer

Deposits and settles privately.

Receipts

Tracks signatures and status.

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.

Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

Use `Pay` when you are sending to one recipient. Add a name, wallet, and amount, then review the draft before sending. The page keeps the flow focused so you can move quickly without losing the approval step.

This is the best path for ad hoc contractor payments, one-time reimbursements, or testing a payout before running a larger batch.

Use `Bulk pay` when you already have a list of recipients. Paste or upload a CSV, let CipherPay validate the rows, then approve the batch from one place.

The expected CSV format is:

recipient_name,wallet_address,amount
Ava Patel,9B3Y2dXhN6LQW8dyL5o6z8UZqv2q1X3dQ5bTA2sQkz4J,0.01

Bulk pay is the right choice for payroll-style runs, monthly vendor batches, or any situation where you want one review surface for many rows.

Use `Payables` to maintain a live list of recurring recipients. Each payable stores the recipient, wallet, amount, cadence, and next due date so you do not need to rebuild the same payout list every cycle.

When a payable comes due, select it and turn it into a normal bulk draft. From that point on, the approval flow is the same as any other batch.

`Agent Pay` is for teams that want agents to invoice, request funding, and send from an agent-owned wallet without exposing the owner wallet.

The owner opens Agent Pay and creates a 10-minute linking code. The user installs the CipherPay skill once, then gives the code and chosen handle to the agent in plain language.

npx skills add Some1Uknow/cipherpay

Link yourself to CipherPay with code XXXX-XXXX. Use handle payroll-bot. Set yourself up step by step.

The skill handles setup in chat: wallet creation, encrypted local storage, backup verification, and link submission. The owner only confirms the pending link in CipherPay.

The agent may ask for one local encryption passphrase. It protects the agent wallet on that machine and is never sent to CipherPay.

The skill can create invoices for exact agent handles or human payment links. Human payment links are unguessable; invoice notes are encrypted at rest.

CipherPay is designed so ownership, funding, and policy stay explicit. New agents start approval-required. Autonomous spending requires owner-configured per-transaction and rolling 24-hour limits.

Agent runtime policy is trusted in v1. If the agent machine loses its spend key, local compromise can bypass UI policy; keep the encrypted backup safe and revoke agents that are no longer trusted.