19 posts tagged with "merchant"

This document outlines a comprehensive security validation process, covering transaction operations, signature verification, payment flow, and the enhancement of service security and stability, with the goal of ensuring the security of transactions and the high availability of the system.

1. What is the Guardian?​

The Guardian (also known as a "Guardian") is a security service component deployed in the backend or on an independent server. It is used to perform secondary validation and permission review for on-chain transfer requests or other critical multi-signature operations originating from the merchant system.

Its core mechanism is:

After the merchant system completes the initial signature, the Guardian independently generates a signature using the same parameters and compares it with the original signature. Only when the content matches and the permissions are valid is the on-chain execution allowed.

This mechanism effectively prevents data tampering, forged signatures, and unauthorized operations.

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).

This tutorial will guide you on how to buy energy through the TG mini program to reduce transaction fees when performing functions such as sweeping and rebalancing on the Tron network.

This tutorial will guide you on how to replace the batch transfer contract address and display the balance information of the address in the admin console. After the replacement, any administrator can perform the transfer-in operation, while only the owner of the batch transfer contract has the authority to perform the transfer-out operation.

To help merchants reduce network fees, we have introduced the TRON automatic energy purchase feature. With the help of a third-party platform, merchants can automatically purchase energy before performing on-chain operations, thereby reducing TRX consumption.

If you need to use this feature, please follow the steps below:

When customers make payments using Pay Protocol, merchants may encounter issues such as payment failure, overpayment, wrong address, or wrong currency. Merchants need to handle these issues based on the information provided by the customers.

TRON is a decentralized platform based on blockchain, aimed at establishing a global free content entertainment system. In the TRON network, bandwidth and energy are two important resources that are crucial for executing transactions and smart contracts.

The operation of Pay Protocol is based on smart contracts, and each operation by merchants requires a certain amount of bandwidth and energy. This article will introduce the concepts of bandwidth and energy, as well as how to save on network fees by purchasing energy on the TRON network.

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.

PRO and STD merchants use a contract with multi-signature functionality to manage members, merchant configurations, and transfer operations. This article will explain how to use the multi-signature contract to manage your organization and funds.