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

Connecting Merchants

A merchant is the platform’s link to your payment details: a crypto wallet, a payment system account, or a payment gateway. The exchanger accepts client funds and makes payouts through merchants. This page covers connecting merchants and verifying their operation.

What a merchant is in the platform

A merchant binds specific details (your own wallets and accounts) to a currency and a role in the exchange:

  • Fund intake (merchant_in) — addresses/accounts to which clients send payment for orders.
  • Payout (merchant_out) — wallets/accounts from which client payouts are made (manually or via auto-payout).

The same wallet can be an intake merchant for some directions and a payout merchant for others.

Connecting: step by step

  1. In the admin panel, go to the “Merchants” section.
  2. Click “Add merchant” and choose the type: crypto wallet, payment system, gateway.
  3. Fill in the details:

merchant_type   = crypto_wallet
currency        = USDT
network         = TRC20
address         = TXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
api_key         = …            # if the merchant is managed via a gateway API
role            = in | out | both

  1. Bind the merchant to the currencies and directions where it will be used.
  2. Save and run diagnostics (see below).

Recommendations:

  • Use dedicated wallets for the platform, not personal ones (see Security Basics).
  • You can connect several merchants per currency — to separate flows and add redundancy.
  • For directions with auto-payout, the payout merchant must support API-based sending.

Diagnostics

After connecting, verify the merchant:

  • Balance — the panel shows the current balance of the details; reconcile with the actual one.
  • Transaction journal — the merchant’s incoming and outgoing operations, statuses, transaction hashes.
  • Test payment — send a small amount to the intake address and make sure the platform saw the credit (currency, network, confirmations).
  • Error statuses — typical failure causes:

invalid_address      # details entered incorrectly / wrong network
insufficient_balance # not enough funds for the payout
api_unauthorized     # API key rejected (permissions, expiry)
network_mismatch     # payment arrived on the wrong network
low_confirmations    # transaction exists but has fewer confirmations than the threshold

Operations

  • Watch payout merchant balances: when they drop below the working volume, directions stall or fall back to manual mode.
  • Set up notifications for low balances and transaction errors (see Notifications).
  • Periodically reconcile the merchant journal against the exchanger’s financial statistics.

See also