Skip to content
Request a demoGet in touch
Get in touch
← Back to documentation

Auto-payouts

An auto-payout is the automatic sending of funds to the client after their incoming payment is confirmed. It is the exchanger’s main accelerator: most orders close without an operator. But automatically sending money is also the main source of risk — so configure it carefully.

How it works

  1. The client creates an order and pays it.
  2. The payment passes AML screening (see AML Transaction Screening) and receives the required number of network confirmations.
  3. The platform automatically builds an outgoing transaction from the payout merchant to the details from the order.
  4. The order moves to the “Paid out” status, and the client receives a notification.

Configuration

Auto-payouts are enabled at the direction level. In the admin panel, open the direction and configure the payout block:

auto_payout        = true
payout_merchant    = usdt_trc20_1      # merchant from which payouts are sent
auto_payout_max    = 5000 USDT         # above this amount — manual moderation
min_confirmations  = 1                 # incoming payment confirmations before payout
Step by step:

  1. Make sure the payout merchant is connected, passed diagnostics, and supports API-based sending (see Connecting Merchants).
  2. Enable auto_payout on the direction.
  3. Set auto_payout_max — the ceiling for automatic payouts. Larger orders go to the manual processing queue.
  4. Run a test order for a small amount and confirm the payout went out automatically.

⚠️ Risk warning

An auto-payout is irreversible: a mistakenly sent blockchain transaction cannot be undone. Mandatory measures:

  • Limits.auto_payout_max should be an amount whose loss you can absorb. Large payouts — manual only, after review.
  • Minimum funds on the hot wallet. Keep only the working volume (the direction’s daily turnover) on the auto-payout merchant; sweep the excess to cold storage.
  • API key permissions. The merchant key should have only the permissions needed for payouts. If the key is compromised, the attacker gets exactly those capabilities.
  • Detail verification. Order details don’t change after payment; client requests to “send to a different wallet” are a typical fraud scenario — such orders are refunded, not redirected.
  • Error monitoring. A wrong payout address, a double payout on one order, a payout on the wrong network — all of this happens in practice. Set up notifications for every outgoing transaction and review failures daily.
  • AML before payout. The payout must go out only after the incoming payment is screened: paying “dirty” money onward means taking the risk onto yourself.

Manual moderation

Orders above the limit, with AML flags, or after auto-payout errors go to the operator queue. The operator reviews the order and confirms the payout manually. Set up notifications for new orders in the queue (see Notifications) so the manual contour doesn’t become a speed bottleneck.

See also