Look up results and resolve specific failures

Recharge lookup step by step

Open /recharge → 查詢進度. Paste the original recharge verification value without labels or added spaces, then select 查詢充值狀態. Compare the returned account, amount, channel, order ID, merchant/channel order numbers, timestamps and allocation result. For a deposit, also inspect the chain details and actual-versus-expected amount.

Transfer lookup step by step

Open /transfer → 查詢進度. Enter the 8-digit application ID and its matching verification value, then select 查詢申請狀態. Check verification status, current processing/review state, expiry and freeze/cooldown details. A correct ID with another request's token cannot retrieve this request.

Errors and the next concrete check

Account not found / multiple matches — Check: Provider, registration/association, exact ID. Next step: Use the UIN/UID and verify again

Minimum amount / arrears — Check: Effective minimum and debt in the latest result. Next step: Adjust the recharge input and repeat verification

Preview mismatch / expired — Check: Whether account, amount or channel changed. Next step: Generate a fresh preview

Payment pending after sending — Check: Order, exact asset/network/amount, transaction or receipt. Next step: Query the original order; give evidence to support

Combined code invalid — Check: Same request, newest pair, A before B, expiry. Next step: Correct the pair or resend when allowed

Pending transfer exists / account busy — Check: Original application state. Next step: Continue it or ask support; do not submit duplicates

Source frozen / final amount rejected — Check: Settlement readiness and full current remaining credit. Next step: Wait or re-preview the permitted final transfer

SMS cancel disabled / refund uncertain — Check: Task state, cancellation timer and provider response. Next step: Wait for permission, then verify the returned result

If the verification value is missing

Check your saved operation record and the result you copied. Transfer emails also carry the verification value; check both recipients' relevant messages. Browser-retained data may help with the same session, but is not a guaranteed recovery method. If still missing, ask support for the appropriate recovery process; an account ID alone is not a lookup credential.

Prepare a useful support request

State whether the issue is invitation, recharge, transfer, settlement or SMS. Include provider/account ID, order/application/task ID, requested and actual amount, relevant time, current status and full error text with secrets removed. For an already-made payment, include the channel receipt or transaction hash. Send a verification value only privately to the confirmed support contact if needed for lookup.

Escalate without repeating the financial action

For paid-but-failed allocation, interrupted transfer execution or uncertain refund, ask support to inspect the original operation before making another payment or transfer. Administrative review and provider failures can require manual handling. A FAILED label alone does not prove that no money or credit moved.