How to build stablecoin payouts
Running stablecoin payouts is how a business pays the contractors, sellers, merchants or token holders it owes in stablecoins, sent to wallets they control, and shows each one was paid once.
This playbook sets out the decisions in the order you’ll make them. Each one links to the use case pages and docs that cover it in detail.
Choose how the money reaches recipients
Pay stablecoins straight to each recipient’s wallet, or through an off-ramp provider or payout network that pays them in local currency.
- Use caseStablecoin payouts for marketplaces and creatorsPay sellers, gig workers and creators in stablecoins from a marketplace balance.
- Use caseStablecoin payouts over Pix, SPEI and other instant railsPay suppliers and contractors from stablecoins into local bank accounts over instant rails such as Pix and SPEI, and tie each onchain transfer to its rail payment.
- Use casePayout prefunding in USDCPrefund a payout network in USDC and track the balance so payouts never stall.
Fund the payout wallet before each run
Your conversion provider turns dollars into stablecoins and your custody provider holds them, so decide how you’ll see each payout wallet’s balance before a run starts.
Keep a payout network’s prefund topped up
Set the floor where payouts would stall, and decide who is alerted and how the next top-up is sized.
Approve what each recipient is owed
Payouts start from your own records, so decide who approves each pay run or merchant settlement, and hold back anyone your verification provider hasn’t cleared.
- Use caseStablecoin payroll and contractor payoutsPay contractors and staff in stablecoins and confirm each payout settled.
- Use caseStablecoin merchant settlementPay each merchant’s settlement in stablecoins to the wallet and network it chose, on any day, and record the transaction against the settlement.
Work out who is owed from the chain
For a distribution or airdrop, pick the record or snapshot block, and decide which holders your rules leave out, such as unverified recipients or sybil wallets.
- Use caseToken distributions to holders and creditorsPay one asset out to thousands of holders, creditors or employees and prove each delivery.
- Use caseAirdrop eligibility lists and sybil filteringScore every address up to a snapshot block, remove sybil clusters and publish the list people claim against.
- GuideBuild a corporate-actions distributorSnapshot token holders at a record block with a one-time Turbo Pipelines job, then pay each holder its share from a Compose task without paying anyone twice.
- DocsTurbo job mode: one-time backfills and batch pipelinesRun a Turbo pipeline once over a bounded block range and let it exit, for backfills and data migrations.
Screen the recipient wallet before paying
Choose the lists and screening provider each wallet is checked against, and whether a hit holds the payout for your compliance team to review or stops it.
- Use caseScreen the recipient wallet before a payoutCheck a recipient wallet before a payout is sent to it.
- Use caseCrypto wallet screening and sanctions dataFlag transfers that touch sanctioned or high-risk addresses.
- Use caseSelf-hosted wallet checks for the Travel RuleSpot transfers to and from wallets no regulated firm runs, collect the details yourself and check that your customer controls the wallet.
Decide what builds each payout and who signs it
Decide whether a Compose task or your own systems send each payout, and where the signing keys stay.
- Use caseHow to pay contractors in stablecoinsA TypeScript task that you write and Goldsky hosts takes an approved pay run, screens each contractor’s wallet, sends each payout to your signer and waits for it to confirm.
- Use caseHow to settle merchants in stablecoinsA TypeScript task that you write and Goldsky hosts takes each merchant’s approved settlement, screens the merchant’s wallet, sends the payout to your signer and waits for it to confirm.
- DocsCompose EVM walletsSend transactions from a Compose task with a Goldsky smart wallet, a private key you store as a secret, or a signing endpoint you host.
Mark a payout paid only once it’s confirmed
Set how many blocks each payout waits before you mark it paid, and whether one the chain later reverses is sent again, logged or handed to a task of your own.
Make every payout safe to retry
A restart or retry can run a payout step twice, so check whether each recipient is already paid before sending again.
- GuideBuild a corporate-actions distributorSnapshot token holders at a record block with a one-time Turbo Pipelines job, then pay each holder its share from a Compose task without paying anyone twice.
- DocsCompose task triggers: cron, HTTP, and onchainRun a Compose task on a schedule, from an HTTP call or when an onchain event lands, and set how it retries when a run fails.
Flag payouts that stall
Decide how long a payout can go unconfirmed before a scheduled check alerts your team.
- Use caseHow to pay sellers and creators in stablecoinsA TypeScript task that you write and Goldsky hosts takes each payout request, screens the seller’s wallet, sends the payout to your signer and waits for it to confirm.
- DocsCompose task triggers: cron, HTTP, and onchainRun a Compose task on a schedule, from an HTTP call or when an onchain event lands, and set how it retries when a run fails.
Tie each payout to what it paid
Record each confirmed transaction hash against the payslip, seller payout, settlement or distribution it paid, so your records and the chain agree.
- Use casePost onchain transfers to your ledgerPost each confirmed onchain transfer to the fintech’s own ledger, corrected for reorgs.
- Use caseRun token distributions with an automated payout taskA TypeScript task that you write and Goldsky hosts takes a distribution from record date to final payment: it snapshots who is owed, pays each recipient, waits for each payment to confirm and logs every step.
Trace program and aid payments after they land
Choose which program and recipient wallets you follow, and what your reports to auditors and donors need to show about where the money went.
- Use caseStablecoin disbursements for public-sector programsTrack government benefit or grant payments made in stablecoins, from issue to spend.
- Use caseHumanitarian aid paid in stablecoinsPay cash assistance as stablecoins into recipients’ phone wallets, let them cash out locally, and trace every payment for donor reporting.
Settle with cash-out agents
Decide how often you settle with each agent, and tie each settlement transfer to that agent’s balance for the cycle.
Turn this plan into a working build
We can help you work through each decision and get the first stage into production.
Robinhood
HyperEVM
Arc
Solana
Ethereum
Polymarket
Base
Tempo
Bitcoin