Перейти к содержимому
guide13 ноября 2026 г. · 9 min read

USDT mass payouts for marketplaces and affiliate platforms: batches, fees and controls

How USDT mass payouts work for marketplaces and affiliate networks: payout runs, address checks, approvals, batching per chain, fees per payout, failures.

BitPolaris Engineering

English original

USDT mass payouts are how marketplaces, affiliate networks, creator platforms and contractor platforms pay hundreds or thousands of people in one run, in stablecoin instead of bank wires. The platform locks what each payee has earned, sends USDT to each payee’s own address on the chain they chose, and records a transaction hash against every line. The transfer itself is the easy part. The work is in what happens around it: whose address it is, who approved the run, whether the hot wallet holds enough USDT and gas on each chain, and what happens when line 412 of 2,000 fails.

Below: the payout run step by step, the cost per chain with figures read on 13 November 2026, how batching behaves on each chain, the controls a compliance head should ask for, and when a processor is the better choice. Our examples come from the withdrawal and payout pipelines we run in production behind the reference exchange.

Who uses mass payouts, and why stablecoins

The pattern is the same across verticals: many small amounts, many countries, a fixed schedule.

Platform Who gets paid Typical schedule Why USDT
Marketplace Sellers, after the refund window Weekly or on request Sellers in countries with slow or costly inbound wires
Affiliate network Publishers and media buyers Weekly, net 7 to net 30 Many payees outside the banking corridors the network uses
Creator or gig platform Creators, freelancers Weekly or on demand Small amounts where a wire fee would take a large share
Broker or trading platform Introducing partners, rebates Monthly Partners already hold USDT

A USDT transfer costs the same to Lagos as to Lisbon, settles in minutes and carries a hash both sides can look up. It also cannot be recalled, which is why every control below exists.

The payout run, step by step

A mass payout run has eight steps. Treat the run as one object with a status, and each line in it as its own record with its own idempotency key.

  1. Lock the earnings. Freeze the amounts owed as of a cut-off time, after refunds, chargebacks on the fiat side and clawbacks. A payout computed from a ledger that is still moving pays some people twice and others nothing.
  2. Check every recipient address. The address must have been registered by the payee, verified for the chain (a TRC-20 address on an ERC-20 run fails a format check; an EVM address is valid on every EVM chain, so the payee must also pick the network), and past any change delay.
  3. Screen. Sanctions lists and, where your risk assessment calls for it, a blockchain analytics check on each destination. A screening timeout goes to a manual queue, never to “sent”.
  4. Approve the run. One officer prepares, a second approves, and runs above a threshold need more approvers or a delay. The approver should see totals per chain, the largest lines and every address that is new since the last run.
  5. Fund the hot wallet. Each chain needs the USDT for the run plus the native coin for fees: TRX on TRON, ETH on Ethereum. Moving funds from warm or cold storage has its own approval, so start this step early.
  6. Send. Sign and broadcast line by line or in batches (below), at a rate the RPC provider and the chain accept. Record the transaction ID before broadcast.
  7. Confirm and notify. Mark each line paid at the confirmation depth you set per chain, then email or webhook the payee with the hash.
  8. Reconcile and report. The sum of confirmed lines plus fees must equal the drop in the hot-wallet balance; every failed or held line needs a reason code and an owner.

Step 6 is where money is lost. If a broadcast times out, do not sign a new transaction for the same line: look up the transaction ID you recorded first, because it may already be in the mempool and a second signature means a second payment. Why crypto withdrawals get stuck covers the per-chain rules for a safe retry: nonce reuse on Ethereum, expiry on TRON and Solana.

What a USDT payout costs per chain

The sender pays the network fee. One USDT transfer cost:

Chain Network cost of one USDT transfer About, 13 November 2026 Notes
TRON, recipient already holds USDT 64,285 energy, 6.43 TRX $2.01 Our measurement of 16 October 2026; the energy fee was still 100 sun on 13 November
TRON, recipient holds no USDT 130,285 energy, 13.03 TRX $4.06 Exchange deposit addresses can be swept to zero, so budget for this rate
Ethereum 46,097 to 63,209 gas in transfers we sampled About $0.04 at 0.33 gwei At 20 gwei the same transfer is about $2.47
Bitcoin One output in a shared transaction Depends on the fee market Not USDT; listed because batching changes the cost most

TRX was $0.3119 and ETH $1,956 on CoinGecko when we read them; the Ethereum gas price came from a public node at the same time. Two settings matter on TRON. Set fee_limit above the zero-balance case, because a transfer that runs out of energy fails and still burns TRX up to the limit; we use 15 TRX. And keep at least 1 USDT in the hot wallet so it never drops to zero itself. How to cut TRON energy costs has the receipts and the rent-versus-burn arithmetic.

A worked example

Assumptions, not market data: an affiliate network pays 2,000 publishers a month, $150 each on average, $300,000 in total, all in USDT on TRON, burning TRX for energy.

  • If every recipient already holds USDT: 2,000 × 6.43 = 12,860 TRX, about $4,011, or 1.3% of the amount paid out.
  • If no recipient holds USDT: 2,000 × 13.03 = 26,060 TRX, about $8,127, or 2.7%.

The same run on Ethereum at 13 November gas prices would cost about $80 in network fees, and about $4,950 at 20 gwei. That spread is why many platforms let payees pick the chain and pass on a fixed network fee per chain, and why renting energy pays for itself on TRON at this volume.

Batching: what each chain allows

“Batch payouts” means different things on different chains.

  • Bitcoin. One transaction can pay many outputs (Bitcoin Core’s sendmany). Inputs and overhead are paid once, so a batch costs much less per payee than separate transactions.
  • Ethereum and other EVM chains. A multisend contract can pay many recipients in one transaction and saves the 21,000 gas base cost per extra transfer, but each token transfer inside it still pays its own storage writes. If one line reverts, the whole batch reverts. The contract also needs a token allowance from your hot wallet, which is one more thing to audit.
  • TRON. The same contract pattern exists. Energy per token transfer stays about the same, so the saving is small and the all-or-nothing risk remains.
  • Solana. Several transfer instructions fit in one transaction, up to the 1,232-byte transaction size limit, and fail together.

Our practice on account-based chains is one transaction per payee, with nonces assigned in order by one signer: one approval, one funding step and one report per run, many transactions.

Recipient addresses: where the fraud happens

The address is where a payout run is most exposed: a chain does what it is told, so a wrong or redirected address is a final loss. The controls:

  • Collect once, change rarely. The payee registers an address in their account. A change needs a second factor and starts a hold, so an attacker who takes over the account cannot redirect the next run. Our custody policy holds new withdrawal addresses for 24 hours by default; pick a hold that is longer than your payout cycle’s review window.
  • Confirm the network with the address. Store the chain with the address and show it to the payee in words (“USDT on TRON (TRC-20)”), not only as a logo.
  • Destination tags. Payouts to an exchange account on the XRP Ledger, and some other chains, need the tag or memo the exchange gave the payee. Without it the funds reach the exchange but not the person.
  • Never copy from history. Attackers send dust from addresses that share the first and last characters with a real one, hoping an operator copies the wrong line. Payout addresses come only from the registered record.
  • Show the approver what changed. New and changed addresses since the last run, highlighted, with the date of change.

Issuer freezes are the other address risk. Tether’s terms allow it to freeze tokens and blacklist addresses; a blacklisted hot wallet cannot send USDT, which stops every payout from it. Keep the payout hot wallet small and separate from collection wallets. USDT vs USDC for merchant payments has the issuer terms and the published freeze counts.

Compliance: whose money is it?

The first question for counsel is whether the payout moves the platform’s money or the payee’s. A platform paying its own affiliates a commission is paying its own bills. A marketplace holding sellers’ sale proceeds and sending them out is moving funds on behalf of others, and in many places that is a regulated activity. Under MiCA, “providing transfer services for crypto-assets on behalf of clients” is a crypto-asset service (Article 3(1)(16)(j) of Regulation (EU) 2023/1114). This is a technical reading of the rules, not legal advice; counsel should confirm how they apply to your model.

The controls that follow are the same either way:

  • Sanctions screening. OFAC expects firms that process virtual currency to run a risk-based programme that generally includes sanctions list screening (FAQ 560), and says its listed digital currency addresses are “not likely to be exhaustive” (FAQ 562). A list check is the minimum.
  • Travel Rule data, where it applies. In the EU, a crypto-asset service provider sending a transfer must send originator and beneficiary information with it, and for a transfer above EUR 1,000 to a self-hosted address it must assess whether the address is owned or controlled by its customer (Regulation (EU) 2023/1113, Article 14). If the payee’s address belongs to an exchange, the payout may need a Travel Rule message; our Travel Rule guide covers what to do when the other side cannot receive one.
  • A record per line. Payee, amount, chain, address, screening result, approvers, transaction hash, confirmation time and fee. That record answers both auditors and payees.

Processor, exchange account or your own payout rail

There are three ways to run mass payouts, and the right one depends on volume and on whose permissions cover the activity.

Payout processor Exchange or custodian API Your own payout rail (software)
What it is A service that holds your float and pays out for you Withdrawals from your corporate account, scripted Payout software on your infrastructure or a hosted instance, with your wallets
Cost model Per payout fee or percentage The venue’s withdrawal fee per transfer Fixed licence or monthly fee, plus network fees at cost
Who holds the float The processor The venue You
Licence for the activity Usually the processor’s Yours, if you move others’ funds Yours
Address controls and approvals The processor’s Limited to the venue’s whitelist features Configured to your policy
Time to first run Days Days Weeks

Published processor terms on 13 November 2026: CoinGate charges €0.50 plus 0.5% per crypto payout without conversion and €0.50 plus 1.5% with conversion on its standard plan. NOWPayments’ mass payments page advertises “$0 fees” on payouts and “from 1 to 100,000 recipients”; ask how network fees are charged before you compare. On the worked example above, CoinGate’s formula comes to €1,000 plus $1,500 for the month before any conversion.

Our view: below a few hundred thousand dollars a month, or without the permissions to move other people’s funds, use a processor. If payouts are part of your product or must sit inside your own approval policy and ledger, own the rail.

What BitPolaris Payments includes for payouts

BitPolaris Payments is gateway and payout software we license. Payouts go only to pre-approved addresses, confirmed with 2FA, scheduled or on demand; the operator console has a payouts queue with approvals and reconciles merchant balances against custody; a signed payout.sent webhook reports each line. The Mass payouts API module adds bulk payout submission through the API. Self-hosted, the Custody block adds M-of-N approvals by amount band, delays on new addresses and daily caps (how those policies work).

List prices from our pricing page: Payments is €2,100 setup plus €410 a month on the hosted cloud (white-label, under your brand), or €7,700 one-time self-hosted plus 20% a year for updates and support. The Mass payouts API is €40 a month on cloud or €980 one-time. Year one on cloud with the module is €7,500; self-hosted it is €8,680 one-time. Network fees, energy, RPC and screening vendors are extra on every model.

USDT mass payouts FAQ

What is a crypto mass payout?

A run that pays many recipients from one balance in a single operation, usually on a schedule. Each payee gets an ordinary on-chain transfer to their own address; the run adds the shared approval, funding, sending and report. Marketplaces, affiliate networks and creator platforms use it to pay sellers, publishers and freelancers in USDT or USDC.

How much does a USDT TRC-20 payout cost?

On 13 November 2026 the network cost was 6.43 TRX (about $2.01) to an address that already held USDT and 13.03 TRX (about $4.06) to one that held none, burning TRX for energy at 100 sun per unit. Renting energy lowers this. A processor’s fee comes on top or replaces it, depending on its terms.

Can I send one transaction to pay all affiliates?

On Bitcoin, yes: one transaction can have many outputs. On Ethereum and TRON a multisend contract can do it, but one failed line reverts the batch and the saving per payee is small. Most operators send one transaction per payee and batch the approval and reporting instead.

How do I stop payouts going to a hijacked account?

Hold address changes for a fixed period with a second factor, notify the payee by email on every change, show new addresses to the approver of each run, and never take an address from transaction history. Screen every destination before the run is approved.

Do I need a licence to send mass crypto payouts?

It depends on whose money moves. Paying your own commissions is usually a payment of your own funds; sending sellers’ or clients’ funds is often a regulated transfer service, for example under MiCA in the EU. Ask counsel in each country where you operate; a processor covers this under its own licence where it has one.

BitPolaris Payments runs payouts to pre-approved addresses with 2FA, an approval queue, signed webhooks and reconciliation against custody, on our hosted cloud, on your servers or as source code. Prices are public.

See Payments · Build an estimate

Sources

  1. TronGrid, chain parameters (energy fee 100 sun), read 13 November 2026; How to cut TRON energy costs (our measurements of 16 October 2026)
  2. CoinGecko, TRX and ETH prices, read 13 November 2026; Ethereum gas price via eth_gasPrice on a public node, read 13 November 2026; USDT gas range from USDT vs USDC for merchant payments (block 26,367,501, 8 November 2026)
  3. Bitcoin Core, sendmany RPC
  4. Solana, transactions (1,232-byte size limit)
  5. Tether, terms of service (last updated 26 February 2026), read 13 November 2026
  6. OFAC, FAQs on virtual currency, FAQ 560 and FAQ 562, read 13 November 2026
  7. Regulation (EU) 2023/1114 (MiCA), Article 3(1)(16)
  8. Regulation (EU) 2023/1113 (Transfer of Funds Regulation), Article 14, read 13 November 2026
  9. CoinGate, pricing, read 13 November 2026
  10. NOWPayments, mass payments, read 13 November 2026
  11. BitPolaris, pricing and Payments, list prices as of 13 November 2026

CoinGate, NOWPayments and Tether are trademarks of their owners; this article describes their public documentation and pricing and implies no affiliation.

Назначить 30-минутный звонок

Crypto exchange, payments, wallet, custody and token launch software, already running in production. Run it on your own servers, license the source code, or let us host it under your brand.