What are the parts of a stablecoin payout flow?
- Licensed provider. Holds the licences to convert fiat to stablecoins and back, and usually holds the funds. If you have your own licence, this can be you.
- Wallet layer. Where the stablecoins sit before they leave: the provider's wallets, an MPC wallet service, or your own keys in an HSM.
- Ledger integration. Your platform's balances, fees and payout records, linked to every on-chain transfer.
- Screening. Checks on the receiving wallet and the transaction before sending, plus travel rule data where the rules require it.
- Reconciliation. A daily match of on-chain transfers, provider reports and ledger entries, with alerts for every mismatch.
- Payout request
- Quote
- Screening
- Provider or wallet
- Blockchain
- Webhook
- Ledger entry
- Reconciliation
Which provider model fits you?
| Model | Who holds funds and licences | What you build | Fits when | Examples |
|---|---|---|---|---|
| Fully managed, fiat in and fiat out | Provider | Payout API integration, ledger, reconciliation | You want stablecoin speed but never touch crypto | Circle CPN Managed Payments (launched April 2026; partners work only in fiat) |
| Payout API with conversion | Provider | Integration, ledger, screening flow, reconciliation | You pay out in stablecoins or local currency through one API | BVNK, Bridge (Stripe), Stripe stablecoin payouts for Connect platforms |
| Wallet infrastructure, your licence | You | Most of the flow, policies, screening, reconciliation | You hold a licence and want control over wallets and flows | Fireblocks, Turnkey, Dfns, Fordefi |
| Self-hosted keys | You | Everything, including key management | You have a strong security team and a reason not to rent keys | MPC library or HSM in your infrastructure |
The custody models guide explains the custody choices behind these models, and how to choose an MPC wallet provider compares the wallet infrastructure options. If you serve EU clients, read MiCA for payment companies first.
Which chain should payouts run on?
The chain follows the receiver. Contractors and partners in many emerging markets already hold USDT on TRON; enterprise and European flows lean to USDC and EURC on Ethereum, its layer-2 networks and Solana.
- TRON. The default rail for USDT in many corridors. Fees are paid in energy and bandwidth; renting energy instead of burning TRX lowers the cost of each transfer.
- Ethereum layer-2 networks and Solana. Low fees and wide USDC support.
- Ethereum mainnet. Highest fees; mostly for large treasury moves, not payouts.
Use one chain per corridor, not one chain for all. Sending USDT to a TRON address on the wrong network is one of the most common ways to lose a payout.
What do you have to build yourself?
- A payout state machine. created → screened → submitted → confirmed → reconciled, with held, failed and returned states.
- Idempotency. Every payout request carries a key, so a retry never sends twice.
- Ledger entries. Double-entry records for the payout, the network fee and the provider fee, in the token's own precision (USDT and USDC use 6 decimals).
- Screening and travel rule. Calls to your KYT provider before sending, and the data exchange your regulator requires.
- Reconciliation. A daily job that matches chain data, provider reports and ledger entries, and opens a case for each mismatch.
- Operations. Alerts for stuck transfers, low energy or gas balances and webhook gaps, and a runbook for each.
What do we put in each part, and why?
For a payment platform without a crypto licence, our default stack is a payout API with conversion (BVNK or Bridge), the provider's wallets, one chain per corridor, a double-entry ledger with idempotency keys, screening before signing and a daily reconciliation job.
| Part | What we put there | Why | We choose otherwise when |
|---|---|---|---|
| Licensed provider | A payout API with conversion: BVNK or Bridge | The provider holds the licence and the funds, so your platform can usually add stablecoin payouts without a crypto authorisation of its own | You hold an EMI or CASP licence and want control of wallets: wallet infrastructure. You never want to touch crypto: a fully managed fiat-in, fiat-out service such as Circle CPN Managed Payments |
| Wallet layer | The provider's wallets. With your own licence: MPC wallet infrastructure with signing policies (Fireblocks, Turnkey, Dfns or Fordefi) behind one internal interface | Policies and approval rules sit before every transfer, and one interface means the wallet provider can be replaced later | Data residency rules or no third party in the signing path: self-hosted MPC or an HSM |
| Chain | One chain per corridor. USDT on TRON with rented energy; USDC and EURC on an Ethereum layer-2 network or Solana | The chain follows the receiver, and renting energy costs less per transfer than burning TRX | Large treasury moves: Ethereum mainnet |
| Ledger integration | A payout state machine, an idempotency key on every request, double-entry records in the token's smallest unit | A retry never sends twice, and the ledger does not drift by cents | We do not vary this |
| Screening | A call to your KYT provider before signing, and travel rule data sent through the provider's API | A flagged address is stopped before the money leaves; a payout without travel rule data is blocked or held | You are the regulated party: a travel rule protocol instead of the provider's API |
| Reconciliation | A daily job that matches chain data, provider reports and ledger entries, with polling as a fallback for webhooks | A missed webhook otherwise leaves a payout pending forever; every mismatch opens a case | We do not vary this |
How long does it take?
With a provider chosen and sandbox access, about four weeks to live-ready: architecture and test list in week 1, the payout flow in week 2, screening and reconciliation in week 3, production configuration and small-value mainnet tests in week 4. Going live also depends on the provider's onboarding and your compliance sign-off, so start both in week 1.
What usually goes wrong?
| Failure | Effect | Fix |
|---|---|---|
| Wrong network for the address | Payout lost or stuck | Validate address format per chain; ask for chain explicitly |
| Retry without idempotency | Double payout | Idempotency key on every request |
| Webhook missed | Ledger shows pending forever | Poll as a fallback; reconcile daily |
| Not enough energy or gas | Transfers fail in batches | Monitor balances; top up automatically |
| Rounding across decimals | Ledger drifts by cents | Store amounts in the token's smallest unit |
| Frozen tokens | Funds blocked by the issuer | Screen before sending; document the procedure |
What have we built?
Our founders built Transatron, non-custodial TRON infrastructure that lowers transaction fees for wallets, exchanges and apps; its public site states savings of 60% or more. Since 2021 we have also led a digital-asset programme for a bank: a feasibility phase for a bank-issued stablecoin and the integration of our AssetBridge asset-management layer with several blockchains. The phase was accepted; the next one waits for regulatory approval. That is why we start provider onboarding and the compliance review in week 1, not week 4.
FAQ
Q01What stack does Vareger use for stablecoin payouts?
For a payment platform without a crypto licence, our default stack is a payout API with conversion (BVNK or Bridge), the provider's wallets, one chain per corridor, a double-entry ledger with idempotency keys, screening before signing and a daily reconciliation job.
Q02Do we need a crypto licence to pay out in stablecoins?
Not if a licensed provider holds the funds and does the conversion. If you hold stablecoins for customers yourself, you will usually need one, for example a MiCA authorisation in the EU. Check with your counsel.
Q03Can recipients get local currency instead of stablecoins?
Yes, through providers with local payout corridors. The stablecoin then only moves the money between the provider's accounts.
Q04USDT or USDC?
Follow the receiver. USDT is widespread in emerging markets, especially on TRON; USDC and EURC are more common in regulated European and US flows.
Q05Who holds the keys?
In the managed and payout-API models, the provider. In the wallet-infrastructure model, you, through MPC or an HSM.
Q06How much does a payout cost?
Network fee plus provider fee plus FX spread. The network fee depends on the chain; the payout cost calculator estimates all three for your corridors, and the chain selector compares networks.
Disclosure: Vareger builds payout integrations on these providers. We hold no licence and receive no fees from any provider named here; if that changes, we say so on this page. Our founders built Transatron, the TRON fee infrastructure named on this page.
