Pay the exact order and interpret payment states
Follow the selected channel's own checkout and distinguish payment confirmation from cloud-credit allocation.
Chapters · Pay the exact order and interpret payment states
1. Open the order's payment instructions
Use 打開支付頁 or 複製支付鏈接 from the generated order. Hosted channels such as Stripe, Binance Pay or Bybit Pay use their configured checkout. An enabled USDT(TRC20) deposit option uses the address and amount shown for that order. Available channels are configuration-dependent; a method named here is not a promise it is currently enabled.
2. For a chain deposit, match all four details
Check asset, network, destination address and exact pay amount. The deposit amount can include a small identifying decimal difference from the whole-number recharge input. Send the displayed amount, not a rounded amount, and do not reuse an old order or another network's address. After sending, keep the transaction hash and query the original order.
Recharge states and the action to take
PENDING_PAYMENT — Meaning: Waiting for payment or a matching payment amount. Your action: If not paid, use the active order; if already paid, inspect its details
PAY_CONFIRMING — Meaning: Payment detected, final/channel or block confirmation pending. Your action: Wait and query this order; do not pay again
ALLOCATING — Meaning: Payment confirmed; cloud credit is being allocated. Your action: Wait for allocation or give support the order if it stalls
SUCCESS — Meaning: Credit allocation succeeded. Your action: Check account and credited amount, then keep the record
PAY_CLOSED — Meaning: Payment order closed or expired. Your action: Do not pay the closed order; resolve any payment already made first
FAILED — Meaning: Processing failed; the error identifies the stage. Your action: Read the error and provide the original payment/order evidence
3. Underpayment, overpayment or wrong details
A detected amount mismatch may prevent automatic allocation. If an overpayment is recognized, the order still allocates according to its recorded amount; excess funds require administrator handling. Do not make an extra transfer to guess a correction. Provide the order, actual amount, network and transaction hash through the confirmed support channel.
4. Confirm the cloud-credit result
A checkout receipt or wallet success screen proves only that the payment provider reports a payment. Return to /recharge, open 查詢進度, enter the saved verification value and select 查詢充值狀態. Confirm SUCCESS and the allocated amount. Pending results refresh automatically while the query is active; the interface also enforces query cooldowns.
5. When the page or order expires
If the preview expires before creating an order, verify again. If a payment order expires, never reuse it for a fresh payment. If you already paid before or after expiry, retain the receipt and query/support record rather than creating another payment to compensate. Refunds depend on the recorded payment and administrator/channel processing, not just the FAILED label.