13 posts tagged with "merchant"

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.

This article introduces the working principle, security design, and operational flow of the Pay Protocol Signer, aiming to help merchants understand how to achieve high-security on-chain asset management through an "offline signing + on-chain broadcasting separation" model.

To help merchants further reduce energy costs, we have added support for the ITRX platform. Merchants can now choose to automatically purchase energy from ITRX or Neee before on-chain operations, thereby reducing TRX consumption.

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