3 posts tagged with "fund"

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:

This tutorial will guide you on how to repair orders where users have overpaid or underpaid through the backend management system.

Prerequisites​

Before starting to repair orders, please ensure you have the following information:

1. Order Number: The order number or payment number that needs to be repaired.
2. Transaction Hash: The transaction hash of the user's payment (can be obtained through a blockchain explorer or payment platform).

According to the operating mode of Pay Protocol, the funds paid or recharged by customers will be stored in the merchant's sub-contract. Merchants can extract the funds to their own wallets through the "Sweep"-"Rebalance"-"Transfer" process.

For ease of expression, this article uses "hot wallet" to refer to the hot contract address of the Pro version.