PayOut Webhook

PayOut Webhook

PayOut webhooks are sent only when the payout order reaches a final state (paid or system_fail). Intermediate internal operations (gas refuel, auto-topup, partial transfers, retries) do not trigger webhooks.

PayOut Status Flow

The payout lifecycle differs depending on the blockchain network.

EVM networks (ETH, BSC, Polygon, Arbitrum, Base, Optimism, Avalanche, etc.)

queue → sending → broadcasting → confirm_check → paid

With gas refuel (when source wallet lacks native currency for gas):

queue → refueling → refuel_confirmed → sending → broadcasting → confirm_check → paid
Status
Description

queue

Payout accepted and queued for processing.

refueling

Gas refuel transaction sent to prepare the source wallet.

refuel_confirmed

Gas refuel confirmed, payout transaction will be sent next.

sending

Payout transaction is being broadcast to the network.

broadcasting

Transaction is queued in the EVM pipeline, waiting to be broadcast to the network. The platform polls the pipeline until the transaction reaches the mempool.

confirm_check

Transaction detected on-chain, awaiting required confirmations.

paid

Payout successfully completed.

BTC-family networks (BTC, LTC, DOGE, BCH, DASH)

Status
Description

queue

Payout accepted and queued for processing.

sending

Payout transaction is being broadcast to the network.

in_mempool

Transaction visible in the mempool, waiting to be included in a block.

confirm_check

Transaction included in a block, awaiting required confirmations.

paid

Payout successfully completed.

Other networks (TRON, TON, SOL, XRP, etc.)

With gas refuel (when source wallet lacks native currency for gas):

Status
Description

queue

Payout accepted and queued for processing.

refueling

Gas refuel transaction sent to prepare the source wallet.

refuel_confirmed

Gas refuel confirmed, payout transaction will be sent next.

sending

Payout transaction is being broadcast to the network.

confirm_check

Transaction detected on-chain, awaiting required confirmations.

paid

Payout successfully completed.

Failure

Status
Description

system_fail

Payout failed after retries or timeout. See error_reason for details.

Webhook Delivery Rules

  • Webhooks are sent only on final states: paid or system_fail.

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

  • No webhooks are sent for:

    • intermediate status transitions (sending, refueling, broadcasting , in_mempool, etc.)

    • individual internal transactions

    • service operations (e.g. gas refuel)

    • partial execution steps or retries

Each webhook represents the final, consistent state of the payout.

Webhook Payload Example

Payload Field Reference

Field
Description

uuid

Unique payout operation identifier.

order_id

Your order identifier (as provided in the create request).

status

Final status: paid or system_fail.

amount_requested

Original requested payout amount.

amount_to_receive

Actual amount the recipient receives.

fee_info.total_fee_paid_fiat

Total fees paid in USD (payout gas + refuel gas combined).

sources

Array of source wallets used for the payout. Each entry includes the transaction hash (txid) and actual fees paid.

service_operations

Platform-performed operations (gas refuels). Only present when refueling was required.

created_at

When the payout was created.

completed_at

When the payout reached its final state. null for system_fail.

Last updated