A stablecoin payout is money going the other way: instead of a customer paying you, you pay a list of people in USDC or USDT. PYMSTR Payouts is now live, and it turns what is usually a slow, manual, one-at-a-time chore into a single on-chain batch of up to 100 recipients. This is the outbound counterpart to a payment link, built for player cashouts, affiliate commissions, vendor settlements, and payroll.
Why mass payouts break on traditional rails
Paying a lot of people at once is where most rails fall apart. Bank wires and ACH take days and get flagged the moment they cross a border. Card networks and PayPal mass-pay cap you, restrict you by region, and exclude high-risk businesses outright. 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. And the do-it-yourself version is worse: you paste wallet addresses into a spreadsheet and sign dozens of transactions by hand.
What PYMSTR Payouts does
PYMSTR Payouts pays up to 100 recipients in one batched on-chain transaction. It is non-custodial: the money never touches a PYMSTR balance, it moves straight from your wallet to the recipients. The batch is atomic, so every recipient is paid together or the whole thing reverts, and one bad address can never leave half your affiliates unpaid. Each payout uses one chain and one stablecoin, and recipients need no PYMSTR account, just a wallet address.
The API creates it, a person signs it
This is the part that matters for anyone automating withdrawals. Your backend can create a payout over the API as your cashout or commission queue fills up, but creating a payout does not move any money. It produces a payout link, the same way a payment link works. You (or a teammate you give the link to) open that payout link, connect a wallet, and sign the batch. The wallet that opens the link is the one that pays, usually your own; it does not have to be whoever created the payout. The API can queue payouts but can never execute one, so an automated queue can never pay itself out. The money only ever moves behind a human who opens the payout link and signs.
How a payout works, step by step
From queued batch to settled on-chain:
- Queue the batch. Add up to 100 recipients with amounts, in the dashboard or over the API. Pick one chain and one stablecoin.
- Approve the payout link. A team member opens the payout link, connects their wallet, reviews the total, and signs once.
- The chain settles. One transaction pays everyone at once, all or nothing, and a webhook fires the moment it completes.
What you can use it for
Common payout jobs, all the same batch flow:
- Player cashouts. Automate an iGaming withdrawal queue over the API, then approve the batch before it goes on-chain.
- Affiliate and referral commissions. Pay your whole affiliate run in one signed transaction.
- Marketplace and vendor settlements. Settle every seller at once instead of one transfer at a time.
- Payroll and contractor pay. Pay a global team in stablecoins without wires or FX markup.
Pricing
Payouts are 1% flat, charged on top of the payout total. If you pay out $10,000 across your recipients, your wallet is debited $10,100 and every recipient receives the full amount you entered. There is no FX markup, no per-transfer wire fee, and no rolling reserve.
Batch stablecoin payouts: a worked example with 100 players
Say an iGaming operator ends the day with 100 approved withdrawals totalling $25,000, all to be paid in USDC on Polygon. Here is what that batch stablecoin payout looks like end to end, who touches it, and what it costs.
| Step | Who | What happens | Cost |
|---|---|---|---|
| Queue the batch | Your platform, over the API (or the dashboard) | One payout with 100 recipients and their amounts, one chain (Polygon), one stablecoin (USDC). This creates a payout link. Nothing moves yet. | $0 |
| Review | A team member with the payout link | Opens the link, connects the treasury wallet, checks the chain, the coin and the $25,000 total. | $0 |
| Sign once | The wallet that opened the link | One on-chain transaction pays all 100 players. All or nothing: a single bad address reverts the whole batch and nobody is half paid. | One network fee for the whole batch instead of 100; on Polygon that is cents, not dollars |
| PYMSTR fee | PYMSTR | 1% flat on the $25,000 total, charged on top. Your wallet is debited $25,250 and every player receives the full amount you entered. | $250 |
| Settled | The chain, then your webhook | Money lands in 100 player wallets in about 2 seconds on Polygon and is final. A signed webhook fires so your platform can mark the withdrawals paid. | $0 |
Compare that with paying 100 players one transfer at a time: 100 signatures, 100 network fees, 100 transaction hashes to reconcile, and a queue that only moves as fast as the person signing. The batch is one signature, one fee, one hash, and the API did the queuing. The same run works for 100 affiliates or 100 contractors; only the recipient list changes.
The bottom line
If you already accept stablecoins with PYMSTR, paying people back out is now the same shape: create a batch, have someone sign it, and let the chain settle. Non-custodial, 1% flat, up to 100 recipients at a time, and final the moment it confirms.
Add the stablecoin rail to your checkout.
Non-custodial. 1% flat. Stable-in, stable-out. Live in minutes, not months.