Telegram Bot Command Guide
This document compiles the currently available query commands, usage methods, and response examples for the backstage Telegram bot, for operations and customer service reference.
1. /pay
Purpose
Query detailed information for deposit or withdrawal orders. The order number can be a merchant order ID, platform order ID, or system-mapped ID.
Command Format
/pay <order_number>
<order_number>is a required parameter, maximum 32 characters, no spaces allowed.
Usage Example
/pay PM00012345
Response Example
Order [PM00012345] Query Result:
Order Type: Deposit
Merchant ID: PF0001
Order Time: 2024-06-01 10:15:03
Merchant Order ID: CL202406010001
Platform Order ID: PM00012345
Order Amount: 1000.00
Actual Amount: 995.00
Fee: 5.00
Credit Amount: 995.00
Order Status: Success
If the order does not belong to an authorized merchant or does not exist, the response will be
No payment or payout information available.
2. /balance
Purpose
Query wallet balance for authorized merchants. You can specify a single merchant, or omit the parameter to view all authorized merchants at once.
Command Format
/balance [PFxxxx]
- Parameter is optional; if provided, must be a valid merchant ID (e.g.,
PF0001).
Usage Example
/balance PF0001
Response Example
Merchant [PF0001] Example Merchant
Balance Query Result:
CNY Total: 12345.67
USD Total: 890.12
3. /daily
Purpose
Statistics for today's total deposits and withdrawals, displaying by currency: total count, successful count, in-progress count, and successful amount. Merchant ID is optional.
Command Format
/daily [PFxxxx]
- Parameter is optional; if provided, must be a valid merchant ID.
Usage Example
/daily
Response Example
Merchant [PF0001] Example Merchant
Today's Statistics:
📥 Deposit Statistics
──────────
💱 Chinese Yuan (CNY)
└ Total: 5 | Success: 4 | In Progress: 1
✅ Success Amount: 4,880.00
💱 US Dollar (USD)
└ Total: 2 | Success: 2 | In Progress: 0
✅ Success Amount: 300.00
──────────
📤 Withdrawal Statistics
──────────
💱 Chinese Yuan (CNY)
└ Total: 3 | Success: 2 | In Progress: 1
✅ Success Amount: 1,500.00
──────────
If the query result is empty, it will return
No deposit/withdrawal data; if the merchant does not exist, it will returnMerchant [PFxxxx] does not exist. Currency will be automatically converted to the corresponding name (e.g., CNY → Chinese Yuan, VND → Vietnamese Dong).
4. /okx
Purpose
Query OKX Exchange C2C market real-time USDT/CNY sell quotes (top 10). This command does not require group authorization.
Command Format
/okx [payment_method_code]
- Parameter is optional; if provided, must be one of the following valid codes:
0- Bank Card1- Alipay2- WeChat Pay
Usage Example
/okx
/okx 1
Response Example
OKX C2C USDT CNY Quote (All Payment Methods) Top 10:
──────────
1. 7.23 CNY | 5,000.00 USDT | Large Merchant A | Bank Card/Alipay
2. 7.24 CNY | 3,200.00 USDT | Preferred Merchant B | WeChat Pay
3. 7.24 CNY | 1,500.00 USDT | Verified Merchant C | Bank Card
...
If query fails or no data available, it will return
Failed to get OKX priceorNo OKX price information available. If payment method code is incorrect, it will return:Unsupported OKX payment method parameter, please enter 0 (Bank Card), 1 (Alipay), 2 (WeChat Pay).
5. Error and Permission Messages
- Unauthorized groups or merchants will receive:
No query permission. - When command format is incorrect, the bot will return:
Command error. - Please ensure the bot has been added to the target group and the corresponding merchant permissions have been bound in the backstage.
/okxcommand is public and can be used in any group without authorization.
6. Command Quick Reference
| Command | Purpose | Parameters | Auth Required |
|---|---|---|---|
/pay <order_id> | Query deposit/withdrawal order | Required, max 32 characters | ✅ |
/balance [merchant_id] | Query wallet balance | Optional, format PFxxxx | ✅ |
/daily [merchant_id] | Query today's deposit/withdrawal stats | Optional, format PFxxxx | ✅ |
/okx [payment_method] | Query OKX C2C quotes | Optional, 0/1/2 | ❌ |
If you need to add commands or adjust response formats, please confirm requirements with the backstage development team before creating a task.