Supplier Payouts
Disburse stablecoin payments to many recipients with batch approval, recipient pre-checks, and on-chain settlement — driven from a Studio UI or directly through the API.
Who this is for
| Persona | Typical inbound |
|---|---|
| Payroll provider | ”We pay 200 contractors a month in USDC and need to batch this.” |
| Affiliate or creator platform | ”Monthly KOL and creator payouts in stablecoins.” |
| Treasury desk | ”Disburse from a corporate fund pool with multi-step approval.” |
| B2B service settler | ”Net-30 supplier invoices paid out automatically when funds hit our pool.” |
Not a fit if you need payments coming in rather than going out (see Accept crypto payments or Invoice approval workflow), if you want self-service withdrawals where the recipient pulls funds (consider the White-Label Wallet instead), or if you need fiat off-ramp settlement (compose this with Crypto-to-bank off-ramp).
What you can ship today
Two modules that work together: a Fund Pool that holds your stablecoin liquidity, and a Payouts module that creates and approves disbursements drawing from that pool.
| Surface | Role |
|---|---|
| Fund Pool | A per-organisation stablecoin pool. Endpoints for status, credit, debit, transactions, batch listing, batch detail, batch approval, batch rejection. Defaults to USDT; supports USDC. |
| Payouts module | Endpoints for listing, creating, retrieving, updating, and cancelling payout intents, plus recipient resolution by email or user ID and address resolution per chain. |
| Recipient resolution | When a recipient is already in the KryptoGO ecosystem, resolve them by email or user ID and read their KYC-verified status before disbursing. When the recipient is a raw on-chain address, resolve the address per chain and read its risk signal. |
| Batch approval | Multi-step approval workflow — Maker creates the payout intent, Reviewer approves the batch, on-chain settlement fires. |
How it works
1. Load the Fund Pool with stablecoin (an on-chain transfer
into the organisation's pool address, then credited via
the API).
2. The Maker opens the Payouts page in Studio (or calls the
API directly):
- Enter the recipient — an individual, an organisation, or
a raw wallet address.
- resolve-recipient validates the email or user ID and
returns a kyc_verified boolean and the chains the
recipient supports.
- resolve-address checks the address on the target chain
and returns a risk signal — found, not_found, or
high_risk with a risk alert.
3. Create the payout intent. It enters a pending or
awaiting-approval state.
4. The Reviewer opens the batch and approves (or rejects).
5. On approval, the Fund Pool debits and the on-chain
transfer fires. The batch transitions: pending →
submitted → confirmed.The batch can also resolve to rejected or failed; the Fund Pool retains the funds in those cases.
Custody model
Funds in the Fund Pool sit in your KryptoGO-managed organisation address — see Custody Options. The Maker, Approver, and Signer roles are configured in Studio. KryptoGO does not unilaterally move funds; settlement only happens after the configured approval workflow completes.
Compliance posture
The payouts flow inherits the platform’s regulated posture: Taiwan VASP, ISO 27001 and ISO 27701, SOC 2 Type II, Cure53. Recipient address resolution returns a risk signal so that high-risk addresses can be blocked before approval. For recipients in the KryptoGO ecosystem, the resolved KYC status flows back to the merchant so that regulated payouts can enforce a verified-recipient-only policy. Full detail at Compliance & Certifications.
Chains and tokens supported today
| Chain | Tokens |
|---|---|
| Arbitrum | USDC, USDT |
| Base | USDC, USDT |
| Optimism | USDC, USDT |
| Solana | USDC, USDT |
| Tron | USDT |
The Fund Pool defaults to USDT and supports USDC; non-stablecoin payouts are not part of the platform.
Typical integration timeline
| Path | Bucket |
|---|---|
| Use Studio’s payouts and Fund Pool modules out of the box | Under one month — typically a few days once Maker and Approver roles are assigned and the Fund Pool is funded |
| Direct API integration for programmatic payouts | One to three months — recipient resolution, batch approval, and on-chain settlement reconciliation are the common time sinks |
| High-volume payouts (hundreds per batch) with multi-signature treasury setup | One to three months — multi-signature wallet configuration and batch-size validation drive the timeline |
Bucketed by the framework in Integration Timeline Framework.
Current scope
- The Studio payouts module and Fund Pool are in production.
- Configurable per-operator transfer limits prevent runaway disbursements; per-organisation and per-key limits are on the near-term roadmap.
- Recipient KYC verification is automatic for recipients in the KryptoGO ecosystem; raw-address recipients have no KYC, so merchants running regulated payouts must enforce that policy themselves.
- Batch sizes for very large disbursements should be confirmed during scoping; multi-signature wallet configuration affects throughput.
- A built-in scheduler for recurring payouts is not part of the platform today; merchants schedule disbursements from their own systems against the API.
- A CSV bulk-import path through Studio is on the near-term roadmap.
Talk to us
If you disburse stablecoins to recipients at scale and want a multi-step approval workflow with recipient pre-checks, reach our partnerships team via the address on www.kryptogo.tw . We will help you scope batch sizes, multi-signature setup, and reviewer assignment.
Where to go next
- Crypto-to-bank off-ramp — to settle payouts in fiat instead of stablecoin.
- White-Label Wallet — for self-service end-user wallets that hold the funds you disburse.
- Compliance & Certifications — for the controls that govern reviewer workflows.
- Architecture Overview — to see how the Fund Pool and payout intents fit into the broader platform.