> ## Documentation Index
> Fetch the complete documentation index at: https://docs-payment-merchant.keysecure.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Member List

## I. Feature Introduction

The module displays members’ basic identity information, asset status, and card usage, and supports permission management and security control actions for individual member accounts. It is an important entry point for daily risk control and user support.

## II. Page Description

| Information             | Description                                                               |
| ----------------------- | ------------------------------------------------------------------------- |
| User ID / Email         | Displays the member’s unique identifier and registration information      |
| Current Account Balance | Shows the remaining available digital asset balance in the user’s account |
| Card List               | Displays the status of all virtual cards under the user’s name            |
| Status Action Bar       | Includes account control buttons (e.g., Freeze Withdrawal, Freeze Login)  |

## III. Supported Operations

### Modify Withdrawal Limit (24 Hours)

Instructions: Enter a new maximum withdrawal limit within 24 hours. The change takes effect immediately.

Use case: Adjust withdrawal permissions based on risk level or business needs.

### Change Registered Email

Use case: The user requests an email change, or the original email is no longer accessible.

### Freeze Login Permission

Instructions: Once confirmed, the account will be unable to log in to the platform. It can be manually unfrozen in the admin console.

Use case: Suspected account compromise, or user-requested suspension.

### Freeze Withdrawal Permission

Instructions: Immediately restrict the user from withdrawing funds.

Use case: Suspicious identity, triggered risk models, etc.

### Unbind Google Authenticator (GA)

Instructions: This action requires manual administrator confirmation and the reason must be recorded. The user must rebind GA before performing restricted operations again.

Use case: Lost phone, unable to complete GA verification, etc.