Currencies & Exchange Directions
Currencies and directions are the foundation of the exchanger: they are what the client sees on the homepage and in the widget. This page covers enabling currencies, creating directions, and configuring additional order fields.
Currencies
In the admin panel, open the currencies section. The platform provides a catalog of supported currencies and networks; you don’t need to set them up technically — just enable and configure them.
Currency parameters:
code = USDT # short currency code
network = TRC20 # network/standard (TRC20, ERC20, BEP20, …)
decimals = 2 # display precision for amounts
min_confirmations = 1 # network confirmations before crediting
is_enabled = true # currency available for directions
Recommendations:
- Enable only the networks you are actually ready to accept and pay out on. USDT on TRC20 and ERC20 are different currencies in terms of directions, reserves, and merchants.
- Check min_confirmations: a lowered value speeds up exchanges but raises risk on large amounts.
Exchange directions
A direction is a “you send → you receive” pair (e.g. BTC → USDT TRC20). Each direction is configured with:
direction = BTC -> USDT.TRC20
rate_source = on_demand # rate calculated at the moment of request
partner_markup = 0.005 # partner markup 0.5% (see “Rate Formation”)
min_amount = 0.002 BTC
max_amount = 2 BTC
reserve = 150000 USDT # direction reserve (see “Reserves”)
merchant_in = btc_wallet_1 # intake merchant
merchant_out = usdt_trc20_1 # payout merchant/wallet
status = active # active | paused | hidden
Practical notes:
- Minimum amount must cover payout network fees — otherwise small orders run at a loss.
- paused status lets you quickly disable a direction without deleting it (zero reserve, merchant issues, network maintenance).
- A direction appears on the site and in the monitoring export only if it is active, has a reserve, and both merchants are operational.
Additional order fields
For directions that require extra client data, add order fields:
field_name = memo # system field name
label = “Memo / Tag” # client-facing label
required = true
validation = “^[0-9]{6,12}$” # validation regular expression
hint = “Enter the memo from your wallet”
Typical cases:
- memo/tag — for XRP, XLM, TON, and other networks with an additional payment identifier;
- card number — for fiat directions, with format validation;
- recipient full name — for directions requiring personalized payouts.
Regex validation rejects clearly incorrect details before payment and reduces operator workload.
Display order on the site
Directions can be sorted: pin top pairs first, rare ones below. The order and column composition of the direction table drive homepage conversion (see White-label Customization).
See also