This guide will walk you through configuring the auto-sweep, rebalance, and distribution strategies in the merchant admin console to automate your fund management.
This guide explains how to use the sub-wallet features of TronLink / MetaMask to manage multiple merchant accounts with 4 mnemonic groups (3 multisig admin groups + 1 treasurer group), each corresponding to 4 master wallets, and complete the following tasks:
Keep 4 mnemonic groups (3 multisig admin groups + 1 treasurer group) securely separated. Each mnemonic group can derive and manage multiple addresses through different derivation paths (a master wallet plus multiple sub-wallets), and the 4 branches together can be used to register and manage multiple merchants.
This guide is intended for merchant operations and fund security teams. It covers the full workflow for cold contract replacement, emergency sweep address setup, emergency withdrawal address setup, and high-risk fund handling.
You can execute the process in the following order:
This document describes how to rapidly batch-create TRON sub-contracts for payment business. The core approach is: first activate TRX currency in the admin console, then generate sub-contract addresses by creating payment orders, and finally deploy the contracts by transferring a small amount of TRX (approximately 1.277 TRX, valued at around 0.5 USDT) to complete batch initialization at minimal cost.
A cross-chain bridge is a protocol mechanism used to transfer assets between different blockchain networks. Because various public blockchains (such as TRON, Ethereum, BSC, etc.) are independent and use incompatible protocols, assets cannot be transferred directly. Cross-chain bridges enable equivalent circulation of the same asset across different chains through mechanisms like "lock → mint" or "swap → release".
This admin console already has built-in cross-chain swap functionality, allowing you to complete asset transfers between major blockchains without integrating an external bridge. It works similarly to "currency exchange": select the asset to sell, choose the destination chain for the asset to buy, enter the receiving address on the counterparty chain, and confirm to complete the cross-chain transfer.
| Feature | Description |
|---|---|
| Supported Assets | USDT and other mainstream stablecoins, native coins |
| Supported Chains | TRON (TRC20)、Ethereum (ERC20)、BSC (BEP20), etc. |
| Fund Source | Hot wallet (Finance) account balance |
| Settlement Time | Typically within minutes (subject to on-chain congestion) |
| Fees | Charged by the cross-chain bridge at real-time rates (included in the swap rate) |
A user's sub-contract can sometimes be contaminated by malicious transfers (e.g., receiving blacklisted USDT). If a normal sweep is performed, the blacklisted funds would be transferred into the cold contract, putting the merchant's main funds at risk. To prevent this, merchants should first blacklist the contaminated sub-contract to exclude it from the normal sweep flow, then use the emergency sweep feature to sweep the funds to a safe external address instead of the cold contract, achieving risk isolation.
The steps to use the emergency sweep feature are as follows:
Tag Address is used to categorize and manage wallet addresses.
When creating a payment order, merchants can specify tagId so the system automatically assigns a receiving address from the corresponding tagged address pool.
Address allocation rules:
This mechanism helps merchants achieve:
This mechanism is ideal for merchant scenarios that require managing a large number of receiving addresses.
This guide helps merchant administrators complete the following configurations:
This document demonstrates how to add the ETH chain for merchants who have already enabled the Tron chain. The operation process for BSC chain is exactly the same as ETH.
In traditional Web2 internet, when large merchants integrate with payment platforms, they often need to allocate independent payment sub-accounts for different business lines, stores, or even individual users (such as Alipay's PID or bank virtual accounts) to achieve fund allocation management and reconciliation.
In Pay Protocol's blockchain world, the core concept that realizes this functionality is Merchant Sub-Contract. It is not the merchant's sole payment address, but rather smart contract addresses that merchants can generate on-demand in batches, specifically serving particular scenarios (such as one user or one order). Due to its foundation on blockchain and smart contracts, the generation and management methods are more flexible, transparent, and secure.
Blockchain wallets are the "keychains" of the blockchain world, determining how you access and manage assets while impacting security and functionality. Wallet differences can be categorized by usage patterns or underlying protocol models. This article provides a comprehensive understanding of both classification methods, including security recommendations and a comparison table of common wallets.