Paying people across borders in stablecoins can be faster and cheaper than wires, and many contractors now ask for it. The hard part isn't sending one payment. It's sending hundreds every pay run without paying anyone twice, getting the right sign-off, and proving afterwards what went where.
What a payout platform needs
- Retry-safe payouts: a crash halfway through a run must not pay anyone twice.
- Approvals that match the risk: finance approves the run, not every line, while large or unusual payments still get a second look.
- The right network per payee, because fees decide the economics.
- Receipts: a transaction hash for every payment, and an export for finance.
How a pay run works on Valtu
| Wallet | Type | Role |
|---|---|---|
| Payouts | operational | Funded before each run with what the run needs |
| Reserve | treasury | Funds the payouts wallet; two approvers |
| Gas | operational | Pays token-transfer fees through the gas station |
- Fund the run. Finance moves the run's total from reserve to the payouts wallet. That transfer needs two approvers: the approval is the decision to pay this run.
- Send. Your system submits each payment with its own
externalIdin batches of up to 100. A crash halfway through is safe: run the batch again, and payments already created come back unchanged. - Exceptions. A rule such as "over $5,000 needs approval", or "a new address over $1,000 needs approval", catches what deserves a person. Approvers confirm with a passkey.
- Track.
transfer.confirmedgives you the hash to show the payee;transfer.failed,rejectedorcancelledtell you to retry or follow up.
Choosing networks
| Network | Typical cost per payout | Notes |
|---|---|---|
| Tron (USDT) | About 2 USD in TRX, roughly double to an address that has never held USDT | The most widely held USDT. Cheaper with rented energy. |
| Base, Polygon (USDC) | Cents | The cheapest EVM options |
| BNB Chain | Cents | |
| Ethereum | Varies widely | Best kept for large payouts |
Exact fees move with network load; each transfer records the fee actually paid.
Controls finance will ask about
- Approval policies by amount, destination, wallet and recent outflow, with Block for what must never happen.
- An address book for recurring payees, with a cooldown before a new address counts as saved.
- An audit log of every approval, policy change and key, exportable for auditors.
- Screening of payee addresses with your own KYT provider.
Good to know
- Valtu sends what your system decides; payroll calculations, tax and contractor compliance stay in your systems and with your advisers.
- The external security audit isn't done yet; see the security page.
Build it with the Node.js payouts guide, and see the payouts and remittance guide in the docs.