Connecting a Trader
Connecting a trader takes two things: a trader configured in Core, and a trader gateway in the merchant settings that lists them.
Trader settings in Core
Section titled “Trader settings in Core”Currency
Section titled “Currency”The operation currency the trader is selected for. It is set when the trader is created.
All of the trader’s requisite limits are expressed in this currency as well.
During selection the trader’s currency has to match the currency of the merchant’s request — regardless of the convert_to setting.
Convert to USDT
Section titled “Convert to USDT”Marks the trader as working in USDT. With the setting on, the trader’s wallet balances are kept in USDT.
Minimum limit / Maximum limit
Section titled “Minimum limit / Maximum limit”The general amount limits. They are set in the trader’s currency.
Payout hold period
Section titled “Payout hold period”How long, in hours, crediting a payout is deferred. Once the period is over, the payout amount and the commission are moved to the trader’s wallets.
Main/Deposit address
Section titled “Main/Deposit address”The crypto wallets tied to the trader’s main and deposit balances.
With Address from the Tron system enabled, the wallet takes part in periodic deposit scanning: when a transfer to it is found, the trader is credited a deposit for the amount received.
Only works for traders with Convert to USDT enabled.
Supported banks
Section titled “Supported banks”The banks available to the trader. A profile can only be created for a bank from this list.
Merchant gateway settings
Section titled “Merchant gateway settings”There are two kinds of settings: with conversion and without. If the trader has Convert to USDT enabled, the merchant needs settings with conversion to USDT; if not, settings in the currency the trader was created with.
With conversion:
{ "USDT": { "gateways": { "pay": { "providers": [{ "trader": "trader" }] }, "payout": { "providers": [{ "trader": "trader" }] } } }, "convert_to": "USDT", "gateways": { "allow_host2host": true, "trader": { "list": [1111], "private_key": "1ccca8894bf0baabb47ef6695c0f0f18", "pay_expired_minutes": 15 } }}Without conversion (the trader’s currency has to match the currency in the settings):
{ "RUB": { "gateways": { "pay": { "providers": [{ "trader": "trader" }] }, "payout": { "providers": [{ "trader": "trader" }] } } }, "gateways": { "allow_host2host": true, "trader": { "list": [1111], "private_key": "1ccca8894bf0baabb47ef6695c0f0f18", "pay_expired_minutes": 15 } }}| Setting | Purpose |
|---|---|
list |
IDs of the traders taking part in selection for a transaction |
private_key |
key used to sign the incoming callback to Business |
Other gateway options are documented in Settings, including the amount randomizer — which keeps two open payins on the same device from carrying the same amount.
What the trader has to prepare
Section titled “What the trader has to prepare”Core settings alone do not produce a requisite. In the trader app there must be:
- a device with the
activestatus; - a bank profile bound to that device, not blocked;
- an
activerequisite of the requested type under that profile, with an amount range and limits that admit the payment.
See Requisite selection for the exact order these are checked in.
