Overview

The platform uses three types of wallets, each serving a strictly defined role in the payment-processing architecture.

Master Wallets (Liquidity Wallets)

A Master Wallet is the core liquidity pool within a network.

Used for:

  • accumulating funds received from transit wallets

  • sending payouts to cold wallets

  • covering all network fees

  • ensuring stable operation of automatic sweep mechanisms

Key Properties

  • Private keys are stored (encrypted on the platform side).

  • Used only for outgoing transactions.

  • Must always maintain a sufficient balance of the network’s native token (ETH for Ethereum, TRX for Tron, MATIC for Polygon, SOL for Solana, etc.).

Native tokens are mandatory

A Master Wallet must always hold enough native tokens to:

  • sign and send payouts

  • pay gas fees

  • initiate transfers from transit wallets

  • maintain the auto-sweep strategy

Without native tokens, even internal fund movements are impossible.

Transit Wallets (Payment Reception Wallets)

Transit wallets are designed to receive funds from end users.

Used as:

  • one-time deposit addresses

  • intermediate storage before the automatic transfer to the master wallet

Key Properties

  • Generated by the platform (individually or in bulk).

  • Have their own private keys.

  • Linked to a specific master wallet.

  • Not used for payouts.

Automatic Sweep (auto-sweep)

All funds received on transit wallets are automatically moved to the master wallet based on:

  • minimal balance (min_balance)

  • withdrawal percentage (sweep_percent)

  • check interval (interval_seconds)

  • or instantly upon deposit (event-driven sweep)

No need to generate many transit wallets in advance

The platform automatically creates new transit wallets as load increases.

This allows you to:

  • avoid storing thousands of unused addresses

  • evenly distribute incoming payments

  • handle large numbers of deposits in parallel

  • keep the system scalable

When the number of orders increases, new transit wallets are generated automatically without delays.

Cold Wallets (External Client Wallets)

Cold wallets are external customer or merchant addresses used for payouts.

Key Properties

  • The platform never has access to private keys of cold wallets.

  • Used only as payout destinations.

  • Cannot be sources of transactions.

Used for:

  • client payouts

  • merchant settl

  • refunds

  • external storage of funds

  • distribution of received assets

Private Key Logic

  • Master and Transit wallets store private keys (encrypted).

  • Cold wallets never store or submit private keys — only addresses.

  • When exporting, the private key is returned only in RSA-encrypted form.

Funds Flow

1. Transit → Master

All funds are regularly transferred from transit wallets to master wallets:

  • by auto-sweep rules

  • or manually via force sweep

2. Master → Cold

Payouts are executed only from master wallets.

The platform validates:

  • liquidity sufficiency

  • availability of the requested asset

  • adequate native token balance for gas

3. Payout in a different asset

If the requested asset differs, you can enable:

{ "auto_convert": true }

The system will:

  • convert the asset (DEX / internal routing)

  • send the required token to the cold wallet

Security Restrictions

  • Payouts cannot be made from transit wallets.

  • Cold wallets can never be transaction sources.

  • Transit → Cold transfers are forbidden.

  • Master wallets should not receive external deposits.

PreviousDecrypting the Private KeyNextRSA Key Management

Last updated