Skip to content

Interface and navigation

After signing in you see the admin panel. The menu on the left is split into two groups:

🏢 My organization ▾

Wallets — balances and withdrawals.
Addresses — one-time addresses and residual balance scan.
Transactions — withdrawal history.
AML whitelist — addresses without AML checks.
Organizations — list and settings for your organizations.
Users — team members and IP whitelist for sign-in.

Additional UI elements:

  • Organization switcher — dropdown in the top-left corner. Wallets, Addresses, and Transactions always show data for the selected organization.
  • Language (e.g. ENG) — interface language switcher in the top-right corner.
  • Theme — light/dark mode toggle (moon icon).
  • Profile menu — click your username in the top-right corner: profile settings, change password, and 2FA setup.

How a payment works: full cycle

Here is the path of a typical incoming payment in a configurable network:

1 You (or your integration) create a one-time address for an order.
▼
2 The client sends funds to that address.
▼
3 The platform records the deposit and runs an AML check.
◢ AML check result ◣
AML passed risk within limits
4a. Funds are automatically transferred to the main wallet. A webhook notification is sent.
AML failed risk above threshold
4b. Funds remain on the one-time address. You handle it manually: refund, manual withdrawal, or private key access. A webhook notification is sent.

For Coins, deposits go directly to the Coins wallet, are converted, and shown in the organization balance in USDT. An integration gets that address when POST /generate-disposable-address sends a known payout_token_ticker: the deposit is credited to the virtual USDT balance, and a payout with the same source_order_id spends it. Without that field, and when the ticker is unknown, hot-wallet stables stay on-chain.

Once funds are on the main wallet (or on Coins), you can withdraw them in Wallets, and each withdrawal appears in Transactions.