PayOut Webhook

PayOut Webhook

PayOut webhooks are sent only when the payout order status changes and only after atomic execution steps are completed. Intermediate internal operations (gas refuel, partial transfers, retries) do not trigger webhooks individually.

PayOut status flow

The payout lifecycle differs slightly depending on the blockchain network.

BTC-based networks

queue
  -> in_mempool
  -> confirm_check
  -> paid
  • queue — payout accepted and queued for execution

  • in_mempool — transaction detected in the Bitcoin mempool

  • confirm_check — transaction confirmed on-chain, awaiting required confirmations

  • paid — payout successfully completed

Other networks (EVM, TRON, TON, etc.)

queue
  -> confirm_check
  -> paid
  • queue — payout accepted and queued for execution

  • confirm_check — transaction detected on-chain

  • paid — payout successfully completed

The in_mempool state is skipped on most non-BTC networks.

Webhook delivery rules

  • Webhooks are sent only on status transitions

  • A webhook is dispatched after all related on-chain actions are completed atomically

  • No webhooks are sent for:

    • individual internal transactions

    • service operations (e.g. gas refuel)

    • partial execution steps

Each webhook represents a consistent and finalized state of the payout at that stage.

Request Example

Last updated