PYMSTR
Launch app
Home/Products/Payouts
ProductPayouts

Stablecoin Payouts. One batch. Up to 100 wallets.

Pay players, affiliates, vendors, and staff in USDC or USDT. Your systems queue the batch, then you open the payout link and sign one transaction to pay from your own wallet. We never hold the money.

Launch app →
//Problem · Solutionwhy this exists
× the problem

Paying a lot of people at once is where every rail breaks.

Bank wires and ACH take days, get flagged the moment they cross a border, and make you upload a file or key in recipients one at a time. Card networks and PayPal mass-pay cap you, restrict you by region, and quietly exclude high-risk businesses like iGaming. Custodial crypto processors will batch it, but only after your money sits in their wallets and clears their withdrawal queue, so you inherit their delays and their hack risk, the same architecture behind roughly $1.8 billion in processor losses between 2023 and 2025.

The do-it-yourself version is worse: you paste wallet addresses into a spreadsheet, sign dozens of transactions by hand, hope you picked the right chain every time, and reconcile a pile of transaction hashes afterward. Player cashouts, affiliate commissions, vendor settlements, and payroll should not require any of that.

→ the solution

PYMSTR Payouts pays up to 100 recipients in a single on-chain batch.

Build the batch in the dashboard or create it over the API, with a fiat amount per recipient in any of 14 currencies: this creates a payout link. You open that link, connect your wallet, review the chain, coin, and total, and sign once. The wallet that opens the payout link is the one that pays, so the funds come straight from it, usually your own treasury wallet. It does not have to be: because whoever holds the payout link and a funded, authorized wallet can sign, the person who created the payout need not be the one who pays it, the same way a payment link is created by you but paid by your customer.

The whole batch settles together: every recipient is paid or none are, so one bad address can never leave half your affiliates unpaid. We never hold the money. It moves from your wallet straight to the recipients, with no processor balance in the middle, no withdrawal queue, and nothing for a hack to drain. Recipients need no PYMSTR account, just a wallet address.

Pricing is 1% flat, charged on top of the payout, so recipients always receive the full amount you entered. And because the API can create a payout but can never move funds, an automated withdrawal queue always waits for a human to open the payout link and sign.

//How it works3 steps

Three steps, on-chain.

Step 01

Queue the batch

Add up to 100 recipients with amounts, in the dashboard or over the API. One chain and one stablecoin per payout.

Step 02

Open the payout link and sign

You open the payout link, connect your wallet, review the total, and sign once. The wallet that opens the link pays, usually your own. The API can create payouts but never moves funds.

Step 03

The chain settles

One batched transaction pays everyone at once. All or nothing. A signed webhook fires the moment it completes.

//payouts settle on 5 networks5 networks
// chain.01

Ethereum

Gas~$2-10
Settle~15 sec
USDCUSDT
// chain.02

Base

Gas~$0.05
Settle~2 sec
USDCUSDT
// chain.03

Polygon

Gas~$0.01
Settle~2 sec
USDCUSDT
// chain.04

Arbitrum

Gas~$0.10
Settle~2 sec
USDCUSDT
// chain.05

BNB Smart Chain

Gas~$0.10
Settle~3 sec
USDCUSDT
//stablecoin payouts · mass payout by approachcompiled
ApproachSpeedCustodyBatchHigh-risk friendly
Bank wire / ACHDays, slower across bordersBank holds and can freezeFile upload or one at a timeOften flagged or blocked
Card / PayPal mass payLimited, region-restrictedProcessor holds the fundsCaps and eligibility limitsExcludes high-risk verticals
Custodial crypto processor (CoinsPaid)After their withdrawal queueProcessor wallet, then payoutBatch, via their UIYes, with custody + hack risk
PYMSTR PayoutsSeconds, on-chainNon-custodial, wallet to walletUp to 100 in one signed batch★ Built for it. 1% flat, no KYB
//What you get4 primitives

What you get.

01

We never hold your money

Funds move from your wallet straight to recipients in one on-chain batch. No processor balance, no withdrawal queue to wait on.

02

Up to 100 in one batch

One signature, one on-chain transaction, up to 100 recipients. Atomic: everyone is paid or no one is.

03

API creates, a person signs

Automate your withdrawal or commission queue over the API. Money only moves when you (or a teammate) open the payout link and sign, paying from that wallet.

04

1% flat, on top

No FX markup, no per-wire fees, no rolling reserve. The 1% is added on top, so recipients get the full amount.

//Payouts questions8 answers

Short
answers.
No jargon.

A single on-chain transaction that pays up to 100 recipients in USDC or USDT. You build the batch in the dashboard or over the API, which creates a payout link; you open that link and sign once, paying from your wallet, and every recipient is paid together. It is the outbound counterpart to a payment link: instead of requesting money in, you send money out.
Up to 100 per payout, in one batch. Each payout uses one chain and one stablecoin, chosen at approval time. The same address can appear on more than one line if you need it to.
Usually you do, from your own wallet. It is not limited to the creator, though: anyone who opens the payout link with a funded, authorized wallet can sign and pay, so you can hand approval to a treasurer or co-signer. Creating a payout does not move any money; the wallet that opens the link is the one that pays. Your API can create payouts but can never execute one, so an automated queue can never move funds on its own.
The wallet that opens the payout link and signs, most often your own treasury wallet. It does not have to be: whoever created the payout, or the API that created it, does not need to hold the funds, so you can hand the payout link to a funded, authorized wallet to sign, the same way a payment link is created by you but paid by your customer.
The whole batch reverts. Payouts are atomic: either every transfer in the batch succeeds or none do, so you never end up with half a payroll run sent. If a batch fails, clone it, fix the bad row, and sign again.
No. Any wallet address works. Recipients do not sign up, install anything, or get an email. The stablecoin simply arrives in their wallet on-chain.
1% flat, charged on top of the payout total. Pay out $10,000 across your recipients and the wallet that signs the payout is debited $10,100, while every recipient receives the full amount you entered. No FX markup, no per-transfer wire fees, no rolling reserve.
Yes. Your backend can create payouts over the API as your withdrawal or commission queue fills up, and each one waits as a pending batch until a person opens the payout link and signs. Webhooks (payout.created, payout.processing, payout.completed, payout.failed) keep your systems in sync. The queue stays automated while the money movement stays behind a human signature.

Add stablecoin payments to your checkout.

1% flat. No chargebacks. Money lands in your own wallet in seconds.

Launch app →