Payouts

A payout sends funds from one of your vaults to an external address. You pick the vault, the asset, the network, and the destination — Stridge funds the gas, signs from the non-custodial vault wallet, broadcasts, and tracks the transaction to a terminal state.

Every payout is a durable record you can fetch forever via GET /v1/transfer/payout/{id}, and every state change fires a webhook.

Why payouts

Disbursing crypto yourself means running hot wallets, holding native gas on every chain, signing transactions safely, and reconciling on-chain state against your ledger. Payouts collapse that into one authenticated call:

• No key custody. Vault keys live in Turnkey or dfns; Stridge orchestrates signing without ever exporting a private key.
• No gas management. Every payout needs native gas on its network. If the vault wallet is short, Stridge auto-refills it from a gas station before executing — you never pre-fund gas.
• Idempotent by design. A reference_id you own deduplicates retries, so a dropped connection never double-pays.
• Fully tracked. Each payout has a lifecycle and a webhook for every terminal state, so your ledger stays in sync without polling.

How a payout works

Creating a payout

The minimum request identifies the vault, the asset and network to send on, the destination, your reference, and an amount.

{
  "vault_id": "550e8400-e29b-41d4-a716-446655440001",
  "asset": "USDT",
  "network_symbol": "ethereum",
  "to_address": "0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B",
  "reference_id": "order-12345",
  "amount": "100.50",
  "remark": "Payment for order #12345",
  "type": "normal",
  "expired_at": "2026-01-01T01:00:00Z"
}

Payouts are idempotent by (vault_id, reference_id): re-submitting the same reference_id returns 409 Conflict instead of sending twice. Use an id you already own — an order id, an invoice id, a ledger row id.

Response

{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "vault_id": "550e8400-e29b-41d4-a716-446655440001",
    "asset": "USDT",
    "network_symbol": "ethereum",
    "amount": "100.50",
    "usd_amount": "100.50",
    "rate": "1.0001",
    "to_address": "0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B",
    "reference_id": "order-12345",
    "remark": "Payment for order #12345",
    "type": "normal",
    "status": "confirmed",
    "tx_id": "0xabc123def456789",
    "error": "",
    "created_at": "2026-01-01T00:00:00Z",
    "confirmed_at": "2026-01-01T00:05:00Z",
    "expired_at": "2026-01-01T01:00:00Z"
  },
  "message": "operation completed successfully",
  "success": true
}

Full request and response schemas live in the API reference.

Payout type

Every payout carries a type that controls how Stridge handles a vault that can't immediately cover the transfer.

Both types refill gas when the vault is short and then send the payout — type only changes retry behavior. normal keeps retrying the refill and the transfer until the payout confirms or reaches expired_at. forceful is single-attempt: the refill and the transfer are each tried once, and if either can't complete the payout fails immediately (it carries no expired_at). Use forceful when an immediate failure is preferable to Stridge retrying.

Lifecycle

Rejecting a pending payout

A payout still in the queue can be cancelled with POST /v1/transfer/payout/{id}/reject. Stridge stops retrying it and it transitions to expired through the normal flow — a payout.expired webhook fires when it does.

curl -X POST 'https://api.stridge.com/v1/transfer/payout/{id}/reject' \
  -H 'X-API-Key: '"$STRIDGE_API_KEY"''

Rejecting is only valid while the payout is pending. A payout that has already reached a terminal state (or moved past pending) returns 409 Conflict.

Webhooks

Three events cover the terminal states of a payout:

All payout webhooks use the standard signed envelope. Full payloads are in Payout webhook events.

API surface

See the API reference for full schemas and error codes.

Next

• Payout Quickstart — send your first payout end-to-end in a few minutes.
• Vaults — the non-custodial vault model, addresses, balances, and regions.
• Gas station — how native gas is auto-refilled for every payout.
• Payout webhook events — payloads for payout.confirmed, payout.failed, payout.expired.