Skip to main content

Auto-Refund Configuration & Operation Guide

ยท 5 min read
Pay Protocol Support
Pay Protocol Support
Pay Protocol BD & Support Team

Auto-refund automatically returns eligible funds to user addresses. This document covers configuration, prepaid account setup, strategy configuration, and the complete refund creation workflow.

Auto-refund involves on-chain operations that incur Gas Fees. The platform can configure refund fees based on business requirements.

Tutorial Objectivesโ€‹

This tutorial guides you through the complete auto-refund workflow: prerequisite verification, configuring the refund batch transfer contract, enabling the prepaid account, configuring withdrawal strategies, creating auto-refunds, and verifying refund results.

Prerequisitesโ€‹

Before using auto-refund, please confirm:

  • The backend Strategy Platform is enabled
  • The Signer Machine has been configured with the project team
  • The project team has provided the refund batch transfer contract address for the corresponding network
  • At least two admin wallets with multi-signature permissions are prepared
Important

Admin wallets must be Web3 decentralized wallets, not exchange wallets. They must be able to connect and sign transactions.

Overall Workflowโ€‹

  1. Configure the refund batch transfer contract
  2. Enable the prepaid account
  3. Configure the fund withdrawal (distribution) strategy
  4. Create auto-refund
  5. Verify refund results

Part 1: Basic Configurationโ€‹

1. Configure the Refund Batch Transfer Contractโ€‹

First, you need to configure the batch transfer contract address provided by the project team as the hot wallet for refunds through the multi-signature mechanism.

1.1 Initiate Hot Wallet Address Modificationโ€‹

Log in to the backend using Admin Wallet A, navigate to:

System Configuration โ†’ Multi-Signature Management โ†’ Modify

Multi-signature management modify entry

On the modification page:

  • Category: Select Modify Standard Hot Wallet Address
  • Address: Enter the batch transfer contract address provided by the project team
  • Click Submit

Modify form

Submit modification

Note

After submission, the proposal will enter a pending approval state and require another administrator to complete multi-signature approval.


1.2 Multi-Signature Approvalโ€‹

Log out and log back in using Admin Wallet B.

Navigate to:

System Configuration โ†’ Multi-Signature Management

Multi-signature management list

Find the Modify Standard Hot Wallet Address proposal you just submitted and click Approve.

Approve proposal

When the wallet prompts a signature request, confirm the transaction information and click Sign.

Wallet signature

After the signature and on-chain transaction confirmation are complete, the batch transfer contract is configured as the hot wallet for refunds.

Tip

The multi-signature mechanism ensures that critical configuration changes require confirmation from multiple administrators, enhancing fund security.


2. Enable the Prepaid Accountโ€‹

The prepaid account is the foundation for automatic strategy execution and must be enabled and funded first.

Instructionsโ€‹

Log in to the backend using an admin wallet and navigate to:

System Configuration โ†’ Strategy Configuration โ†’ Prepaid Account

Enable the Prepaid function.

Prepaid switch

Click Deposit, select the corresponding network and USDT, and send funds to the address provided on the page.

Prepaid deposit entry

Deposit address

Please maintain sufficient prepaid account balance to avoid affecting strategy execution.

Note

The prepaid account must be enabled and funded before configuring any automatic strategies.


3. Configure the Fund Withdrawal (Distribution) Strategyโ€‹

The withdrawal strategy controls the automatic fund distribution process from the hot wallet to user addresses.

Instructionsโ€‹

Navigate to:

System Configuration โ†’ Strategy Configuration โ†’ Strategy Settings โ†’ Fund Withdrawal (Distribution) Strategy

Configure:

  • Strategy Status: Enabled
  • Maximum Withdrawal (Distribution) Wallets per Transaction: 1

Click Save Fund Withdrawal (Distribution) Strategy.

Withdrawal strategy configuration

Important

The fund withdrawal (distribution) strategy must be enabled, otherwise the final step of auto-refund cannot execute normally.


Part 2: Create Auto-Refundโ€‹

4. Create Auto-Refundโ€‹

After completing the basic configuration, you can create auto-refund tasks.

Instructionsโ€‹

Navigate to:

Asset Management โ†’ Refund โ†’ Auto-Refund

Auto-refund list

Click Add.

New refund form

Fill in the refund information:

FieldDescription
Original Transaction HashEnter the TxHash of the original transaction to be refunded
Refund AddressIf left empty, defaults to the original payment address
Refund AmountEnter the refund amount
CurrencySelect the corresponding refund currency
Fee Type / Fee ValueConfigure platform refund fees based on business requirements

After confirming the information is correct, click Submit.

Submit success

Note
  • If the refund address is left empty, funds will be returned to the original payment address
  • Fee type and fee value are used to configure platform fees and can be set based on business requirements

5. Auto-Refund Fund Flowโ€‹

After successful submission, the system automatically executes the refund according to the configured strategy:

Sweeping, withdrawal, and refund are on-chain operations that incur corresponding Gas Fees.

If the platform needs to charge users refund fees, they can be configured via Fee Type / Fee Value when creating the auto-refund.

Tip

On-chain transactions require block confirmation, and the backend may not update the status immediately. Please wait patiently or refresh the page to view the latest results.


Part 3: Key Remindersโ€‹

  • The prepaid account must be enabled and funded before configuring any automatic strategies
  • Admin wallets must be Web3 decentralized wallets
  • On-chain transactions require block confirmation; the backend may not update immediately
  • Refund fees can be configured based on business requirements when creating refunds
  • Ensure sufficient prepaid account balance to avoid affecting strategy execution

Part 4: Completion Checklistโ€‹

  • Strategy Platform enabled
  • Signer Machine configured
  • Batch transfer contract configured as hot wallet
  • Prepaid account enabled and funded
  • Fund withdrawal (distribution) strategy enabled
  • Withdrawal wallet count set to 1
  • Auto-refund information filled correctly
  • Refund results verified