System Overview

I. System Overview

This guide details the full back-office operational workflow for cryptocurrency deposit services, covering record generation, query and tracking, exception handling, cancellation operations, and refund processes, to ensure standardized operations by back-office personnel and to safeguard regulatory compliance and fund security.

Prerequisites

• Back-office operators must log in to the WBO back-office system using their assigned account credentials and navigate to the "Virtual Asset Management - Deposit/Withdrawal - Deposit" module.
• Confirm that the account has the required permissions for "Deposit Application", "Deposit Records", "Cancel", and "Refund". If permissions are lacking, contact an administrator to request access.

II. Operational Instructions

Cryptocurrency Configuration

Prior to customer deposits, configure the supported deposit cryptocurrencies.

Customer Wallet Address

Completing wallet address verification before deposits is a critical prerequisite to ensure asset security.

Deposit Operations

Request Reception and Record Generation

📍

Menu path: WBO - VA Clearing Management - Deposits & Withdrawals - Deposit Application

• After the client submits a deposit request, the system automatically receives the request information and generates a unique deposit record (including record number, client securities account, deposit currency, amount, destination address, transaction hash (TXID), request time, status, and other core information).
• If an abnormal or problematic deposit application is encountered, back-office operators may delete it directly within the system.

Deposit Record Query and Tracking

📍

Menu path: WBO - Virtual Asset Management - Deposit/Withdrawal - Deposit Records

• Multi-condition search: Supports filtering by record number, customer number, creation time, status, and other criteria to quickly locate target records.
• Detail tracking: Click a single record to view details, including address verification and the block confirmation progress corresponding to the transaction hash, enabling real-time tracking of the entire deposit process.

Cancellation of Non-Deposited Records

• Prerequisite: Applicable only to records with the status "Wallet Address Under Verification" (i.e., deposit requests for which the blockchain network has not begun confirmations and the assets have not been transferred). Records in other statuses cannot be cancelled.
• Steps:
  1. In the deposit records list, locate the target record to be cancelled and click the "Cancel" button;
  2. A confirmation dialog will appear; enter operation remarks (e.g., "Duplicate user request", "Incorrect address"), then confirm the cancellation again;
  3. Upon successful cancellation, the record status will be updated to "Cancelled", and the system will automatically retain a cancellation operation log (including operator, operation time, and remarks) to support subsequent traceability.

Refund Process After Successful Deposit

• Prerequisite: Applicable only to records with the status "Credited" (i.e., assets have been successfully credited to the platform and the user requests a refund or the system requires a forced refund). Verify the user's identity and the legitimacy of the refund request.
• Steps:
  1. Navigate to the "Deposit" module, search for the target credited record, and click the "Request Refund" button;
  2. Complete the refund information: enter the user's specified refund address (must match the user's identity verification information), select the corresponding network (consistent with the deposit network), and verify the refund amount (defaulted to the deposit amount; adjustments are allowed but must state the reason for adjustment);
  3. Execute the refund: the back office clicks "Execute Refund", the system generates a refund transaction hash and broadcasts it to the blockchain network;
  4. Track the refund status: monitor the block confirmation progress of the refund record in real time; upon confirmation completion, update the deposit record status to "Refunded" and retain a full refund process log;
  5. Notify the user: once the refund succeeds, notify the customer offline.