Skip to main content
Every merchant gets one free scheduled payout per day — Tribridge covers the network gas. Need funds sooner? Request an additional payout any time; only the network gas is deducted from your balance. Tribridge never charges a withdrawal fee. All payouts are confirmed with a one-time email code, and executed from the Tribridge vault on-chain.

How it works

1

Balance settles

Collected payments are confirmed and settled into your available balance (net of prior payouts).
2

Check context

Call GET /payouts/context to see per-chain available and pending balances plus your linked payout wallets.
3

Request a code

Call POST /payouts/request-otp. Tribridge emails a 6-digit confirmation code to your account. A destination wallet is required before a code is issued — either a linked payout wallet or an explicit destination_address.
4

Execute the payout

Call POST /payouts with the code. The payout is executed on-chain from the vault to your destination.

Get payout context

GET /payouts/context — Everything the payout UI needs in one call: available balance per chain (net of prior payouts), pending balance, and your linked payout wallets. Add ?mode=live|test to scope it.
Example response

Request a confirmation code

POST /payouts/request-otp — Emails a payout confirmation code to your account. Call this before POST /payouts.
cURL
Dashboard sessions use your login JWT (Authorization: Bearer) for payout endpoints — not the x-api-key. API keys authenticate merchant server integrations; payouts are a dashboard-level money movement, hence the extra email-code step.

Execute a payout

POST /payouts — Creates and executes a payout. Requires the confirmation code from the previous step.
cURL

List payouts

GET /payouts — Lists your payouts, newest first, with status, amount, destination, and transaction hash.