Skip to main content

Tokens and Networks

The Tokens and Networks admin page is where operators manage the terminals that TrexWallet exposes to users and payment pages. A terminal can represent a blockchain network, a card acquiring provider, an internal wallet method, a P2P provider, or a merchant continuation flow.

Add Terminal

Use the separate Add terminal page at /TrexAdmin/AddTokenNetwork; the /TrexAdmin/TokenNetworks list is for browsing existing terminals.

The page has two creation modes:

  • Token contract — select a blockchain network, contract address, and existing ledger currency. The configured scanner is authoritative for the canonical contract address, token standard, name, symbol, and on-chain decimals. The network must already have its Base terminal.
  • Manual — create a Base coin, bank, acquiring, P2P, internal-transfer, or other off-chain terminal. The operator supplies the processing type, ledger currency or multicurrency flag, and descriptive metadata.

Only one Base terminal is allowed per network. A newly created terminal is treated as disabled setup in contract mode. Manual mode allows availability flags at creation, but configure the system wallet/hot address on the routing page and add the tariff before exposing the terminal to users.

Main Fields

FieldPurpose
CurrencyAsset served by the terminal.
Contract typeTerminal category: blockchain, card acquiring, P2P, internal, and so on.
Network typeConcrete provider or network used by the terminal.
Display nameHuman-readable label shown to users.
Icon codeOptional UI icon hint.
InstructionsFree-form text shown to the payer.
CapabilitiesTerminal-specific tags used by merchant applications for labels, icons, or filters.
CountriesOptional ISO country restrictions. Empty means global.
Flow pathEmpty for built-in handlers; non-empty redirects /pay to a merchant continuation page.
FlagsPer-terminal behavior switches.

Country Restrictions

Use Countries when a payment terminal is available only to payers from specific countries. Enter space-separated ISO country codes, for example GE AM KZ.

Behavior:

  • Empty Countries means the terminal is global.
  • A non-empty list is treated as a payer-country allowlist on the public /pay flow.
  • The deployment must supply the payer country to the public payment flow.
  • If the payer country is unknown, country-restricted terminals are not shown and cannot be started by a direct API call.

Merchant integrations can enforce additional provider country rules separately. The terminal Countries field controls only TrexWallet terminal availability for the universal payment page.

Important Flags

FlagEffect
Allow Payment OrderMakes the terminal available for merchant payment orders.
Require Partner InfoRequires sender/payer metadata for this terminal.

Continuation Path

Leave Flow path empty for built-in handlers: crypto, built-in card acquiring, and internal wallet balance. Set a relative path only when the terminal is owned by a merchant continuation flow.

The flow path must not collide with reserved platform prefixes such as /pay, /pay-auth, /payment/v1, /payorders/v1, /auth/v1, or /acquiring/v1.

Withdrawal Setup

For crypto withdrawals, configure a default hot address for the network. Create the hot address via System Addresses and select it on this page.

Operator Workflow Examples

GoalSteps
Activate Stripe Checkout for EUR ordersCreate or enable a built-in card terminal, allow payment orders, leave flow path empty, configure the tariff.
Activate T-Bank acquiring for RUB ordersUse the built-in card terminal shape, configure provider credentials for built-in card acquiring, and configure the tariff.
Add a custom P2P terminalCreate a P2P terminal, set terminal tags, set a merchant continuation flow path, and configure the tariff.
Restrict a terminal to selected countriesFill Countries with ISO codes and verify that payer-country detection is enabled for the public payment flow.
Disable a terminal temporarilyDisable top-up/payment-order availability; keep the terminal record for ledger continuity.