Affiliate and partner commissions
Pay every affiliate or partner for the period in one run.
Crypto payouts
Pay out withdrawals, commissions, refunds and partner payments in cryptocurrency. Create a single payout when a request comes in, or send many transfers together as a mass payout.
01 Single payouts
A single payout sends funds to one external wallet. Use it when requests arrive one by one and each needs its own decision.
Wallet address, asset, network and amount, entered by your team in the dashboard or sent by your system through the API.
Review the details before confirming. Blockchain transfers generally cannot be reversed once sent.
See the payout in the dashboard or through the API and record it against the request it settles.
02 Mass payouts
When many recipients need to be paid at the same time, creating transfers one by one is slow and easy to get wrong. A mass payout groups them into one batch that you prepare, check and submit once.
Collect recipients, assets, networks and amounts in your own system or in the dashboard.
Review the total and the recipient details. A second pair of eyes on the batch is good practice.
Send the whole batch through the API or the dashboard instead of creating each transfer separately.
Follow the batch and the transfers in it, and match them to your commission, reward or withdrawal records.
Pay every affiliate or partner for the period in one run.
Distribute earnings or rewards to many users of your platform.
Process approved customer or player withdrawals together when that suits your operations.
03 Comparison
| Aspect | Single payout | Mass payout |
|---|---|---|
| Recipients | One | Many, in one batch |
| Best for | Requests that arrive one at a time | Scheduled runs: commissions, rewards, grouped withdrawals |
| Review | Each payout on its own | The batch as a whole, plus its lines |
| Started from | API or dashboard | API or dashboard |
Terms that apply
04 Good practice
Crypto payouts move value directly to external wallets. These habits protect your business and your recipients.
Use exactly the address, asset and network the recipient gave you. A transfer sent to a wrong address or network usually cannot be recovered.
Payout requests should come from your backend. Never place API credentials in a browser, a mobile app or a shared document.
Within your team, let one person prepare a batch and another check it before it is submitted.
Your obligations toward your customers, players and partners, such as verification before withdrawals, stay with your business.
A payout sends funds to one recipient. A mass payout groups many transfers into one batch that is prepared, checked and submitted together.
Yes. Single payouts and mass payouts can be started through the API or by your team in the dashboard.
Generally not. Once a transfer is confirmed on the blockchain it cannot be pulled back, which is why recipient details should be checked before confirming.
Supported assets: USDT, USDC, BTC, ETH, TRX, LTC. Supported networks: Bitcoin, Ethereum (ERC-20), Tron (TRC-20), BNB Smart Chain (BEP-20), Polygon, Litecoin. If recipients expect an asset you did not receive, convert first.
Tell us who you pay, how often and in which assets. We review your application, agree terms and help you connect.