CSV batch sends
Thousands of recipients, one transaction, one confirmation: dispersion without tedium.
Payouts at batch scale: a CSV of addresses (or web3 names) and amounts, one confirmation, one on-chain batch that disperses to every recipient. Payroll in crypto, marketplace settlements, affiliate runs, creator payouts: the same flow.
Funds move non-custodial: your wallet signs the batch, recipients receive direct, and the batch record exports for the audit. 35 networks, any listed asset, one transaction instead of a thousand.
Payouts are the treasury's outbound face, and their failure modes are all concentration events: one wrong paste at scale, one approval that skipped the preview, one reconcile that ran before the report landed. The U.CASH payout machinery is engineered against exactly those: validation at entry catches format errors before they cost anything, the preview surfaces every leg's destination and fee before signature, and the report carries per-leg references that make the aftermath audit-ready.
The composition question payouts raise is destination mix. Wallets, stablecoin conversions, local rails, and card credits can all appear in one run, and the engine treats them as one workflow with per-leg timing. Businesses that schedule their runs, read their previews, and file their reports convert the scariest money movement into the most boring, which in treasury operations is the highest available compliment.
One scheduling note worth standardizing: run payouts on a published calendar rather than on demand. A fixed rhythm turns every stakeholder expectation, from recipients to finance to the person reading the preview, into a habit instead of a negotiation, and it gives the treasury a predictable float cycle to plan against. The calendar also compounds the safety properties: previews read at a known cadence get read properly, and reports filed on schedule stay boring, which in money movement is the goal state.
From setup to settled.
Addresses or web3 names plus amounts, in a CSV: payroll, settlements, or the monthly affiliate run.
The console totals the batch per asset, shows the network fee, and flags anything malformed before anything moves.
One signature dispatches the batch. Your wallet signs; U.CASH never holds the funds.
Every address gets its amount direct, with one batch record to audit and export.
Thousands of recipients, one transaction, one confirmation: dispersion without tedium.
Recipients as names instead of hex: readable, verifiable, fewer support tickets.
Pay in the asset and on the chain each recipient expects, from a single flow.
Your keys sign the batch; the platform never holds the payroll.
Malformed rows and bad amounts flagged before dispatch, not after.
One batch record with every recipient, amount, and hash: bookkeeping the auditor can verify on-chain.
Freelancers, agencies, B2B sellers.
Platforms, SaaS, resellers, franchises.
Every rail on one non-custodial platform, under your brand.