Use case · Platforms, marketplaces, payroll, affiliates

Payouts and payroll on U.CASH

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. 34 networks, any listed asset, one transaction instead of a thousand.

How it works

From setup to settled.

Step 01

Prepare the list

Addresses or web3 names plus amounts, in a CSV: payroll, settlements, or the monthly affiliate run.

Step 02

Upload and review

The console totals the batch per asset, shows the network fee, and flags anything malformed before anything moves.

Step 03

Confirm once

One signature dispatches the batch. Your wallet signs; U.CASH never holds the funds.

Step 04

Recipients receive

Every address gets its amount direct, with one batch record to audit and export.

What you get

CSV batch sends

Thousands of recipients, one transaction, one confirmation: dispersion without tedium.

Web3 names in the file

Recipients as names instead of hex: readable, verifiable, fewer support tickets.

34 networks

Pay in the asset and on the chain each recipient expects, from a single flow.

Non-custodial dispatch

Your keys sign the batch; the platform never holds the payroll.

Pre-flight validation

Malformed rows and bad amounts flagged before dispatch, not after.

Audit exports

One batch record with every recipient, amount, and hash: bookkeeping the auditor can verify on-chain.

Product and docs

Payouts docsDistribute app

Crypto payouts: FAQ

Can I pay salaries in stablecoins?
Yes: batch USDC or any pegged token to a CSV of wallets or names, one signature, settled with crypto finality. The batch record exports for payroll systems.
What does a batch cost?
The on-chain network fee for the batch plus a small dispersion fee: a rounding error versus per-recipient transfers.
Do recipients need accounts?
No. Payouts land in whatever wallet address (or web3 name) the file specifies; the recipient needs nothing but their keys.

Related use cases

Crypto invoicing

Freelancers, agencies, B2B sellers.

White-label payments

Platforms, SaaS, resellers, franchises.

Get started

Crypto payouts, live in minutes

Every rail on one non-custodial platform, under your brand.