Skip to main content

Operation Management Overview

The Operation Management feature provides various operational tools for test order creation, manual operations, and data queries.

Feature Overview

Operation Management includes the following features:

  • Create Deposit Order: Manually create a test deposit order
  • Create Payout Order: Manually create a test payout order
  • Order Query: Quickly query order status
  • Manual Operations: Handle orders in special situations

Main Features

Create Deposit Order (CreatePayment)

Path: OperationCreatePayment

Used to manually create deposit orders, primarily for testing channels and debugging.

Steps:

  1. Select Merchant

    • If you have global permissions, you need to select a merchant first
    • Regular users automatically use the currently logged-in merchant
  2. Select Service

    • Choose from the merchant's activated services
    • Displays service limit ranges
  3. Select Channel

    • Automatically filters available channels based on the service
    • Displays channel limits and current balance
  4. Fill in Deposit Information

    • Deposit Amount (required): Fill in according to the selected channel and service limits
    • Payer Name: Required for some services
    • Payer Card Number: Required for some services
    • Bank Code: Required for Thai / Vietnamese / Indonesian bank services
    • Phone Number: Required for some services
    • ID Number: Required for some services
  5. Submit Order

    • After the system creates the order, a payment page will pop up
    • The payment information can be viewed in a new window

[!TIP] Amount Limit Hint: Hover the mouse over the amount input field to see the currently available limit range. The limit is determined by the intersection of the channel limit and the service limit.

Required Fields by Service Type:

Service TypeRequired FieldsNotes
CNY Bank CardAmount, Name, Card Number, Remark CodeRemark code must be filled in manually
CNY Alipay / WeChatAmount, Name
Thai ServiceAmount, Name, Card Number, Bank CodeSelect a Thai bank
Vietnamese ServiceAmount, Name, Bank CodeSelect a Vietnamese bank
Indonesian ServiceAmount, Name, Bank Code
Brazilian ServiceAmount, Name, Card Number, Phone, ID Number
USDTAmountGenerates dedicated address or fixed amount

Create Payout Order (CreatePayout)

Path: OperationCreatePayout

Used to manually create payout orders, typically for testing payout channels.

Steps:

  1. Select Merchant (if authorized)
  2. Select Service
  3. Select Channel
  4. Fill in recipient information:
    • Payout Amount
    • Recipient Name
    • Recipient Bank Account
    • Bank Code
    • Other required information (based on service type)
  5. Submit Order

[!WARNING] Creating a payout order will actually deduct channel balance and send a payout request to the upstream. Please use a test environment or small amounts for testing.

Permission Details

Operation Permission Categories

1. OPERATION_PAYMENT_WRITE (1014)

  • Can create deposit orders for the currently logged-in merchant
  • Can only see their own merchant's data

2. OPERATION_PAYMENT_GLOBAL_WRITE (1021)

  • Can create deposit orders for any merchant
  • Must select the target merchant first
  • Usually assigned to operations administrators

[!NOTE] Permissions are configured in User Management. If you cannot access operation features, please contact an administrator to check permissions.

Amount Limit Logic

The system calculates the final available limit based on the following rules:

Limit Sources

  1. Channel Limit

    • payment_lower_bound / payment_upper_bound
    • Per-transaction limit for each channel
  2. Service Limit

    • single_limit_lower_bound / single_limit_upper_bound
    • Limit configured for the merchant's service
  3. Channel Service Boundary

    • service_bounds (limit for a specific service per wallet)
    • Highest priority

Calculation Rules

Final Lower Bound = max(Channel Lower, Service Lower, Service Boundary Lower)
Final Upper Bound = min(Channel Upper, Service Upper, Service Boundary Upper)

Special Cases:

  • 0 means no limit
  • Upper Bound < Lower Bound means no available range

Limit Examples

Example 1: Normal Case

Channel Limit: 100 - 50,000
Service Limit: 500 - 20,000
Available Limit: 500 - 20,000 (intersection)

Example 2: No Upper Limit

Channel Limit: 100 - 0 (no upper limit)
Service Limit: 500 - 20,000
Available Limit: 500 - 20,000

Example 3: No Available Range

Channel Limit: 10,000 - 50,000
Service Limit: 100 - 5,000
Available Limit: Invalid (upper bound < lower bound)

FAQ

Q: Why can't I see certain services?

A: Possible reasons:

  1. The merchant has not activated the corresponding service
  2. The service status is disabled
  3. The service has no available channels bound to it

Q: Why can't I see channels after selecting a service?

A: Possible reasons:

  1. The service has no channels bound to it
  2. Bound channels are disabled
  3. Insufficient channel balance (for payouts)

Q: What to do when amount validation fails?

A: Check the following:

  1. Is the amount within the available limit range?
  2. Review the limit hint information
  3. Try adjusting the amount or switching channels

Q: Can created orders be cancelled?

A:

  • Deposit orders: Can be closed before payment
  • Payout orders: Orders already submitted to upstream generally cannot be cancelled

Q: Do test orders affect statistical data?

A: Yes, all orders created through the backstage are included in statistics. Recommendations:

  1. Use a dedicated test merchant
  2. Use a test environment
  3. Tag test orders for later identification

Use Cases

1. Channel Testing

Before launching a new channel, create small test orders to verify:

  • Order creation is normal
  • Callback notifications are correct
  • Amounts are accurate

2. Issue Reproduction

When a merchant reports an issue, reproduce it through operation tools:

  • Create an order with the same parameters
  • Observe system behavior
  • Identify the root cause

3. Limit Verification

Verify that limit configurations are correct:

  • Test boundary values
  • Confirm limit calculation logic
  • Verify error messages