Before a USDT-funded RMB payment is approved, the desk may request enough information to understand the sender, amount, source of funds, recipient, route, and payment purpose. The exact request depends on the transaction.
Start with the transaction outline
- The amount of USDT available or intended.
- The preferred or available blockchain network.
- The RMB amount the recipient needs.
- The requested recipient route: Alipay, WeChat Pay, or Chinese bank TT.
- The genuine timing requirement.
- The reason for the payment.
This initial outline lets the desk identify missing information. It is not an executable quote.
Sender and source context
Depending on the request, identity, location, wallet ownership, source-of-funds context, or supporting records may be requested. Information should be accurate and consistent with the transaction. Attempts to conceal the sender, split transactions to avoid review, or misstate the purpose can cause delay or refusal.
The transaction requirements page explains the review approach. Never send sensitive documents to an unverified account.
Recipient details by route
| Route | Information commonly prepared |
|---|---|
| Alipay | Recipient name, requested account details, amount, and purpose |
| WeChat Pay | Recipient identity, account details, suitability context, and purpose |
| Chinese bank TT | Exact beneficiary, bank, branch, account number, location fields, amount, and purpose |
The desk may request more or less depending on the recipient and current route. Use the dedicated services overview to reach the relevant route page.
Commercial and blockchain confirmation
After the request can be reviewed, the written confirmation should state the exact USDT amount, executable rate, expected RMB, wallet, supported network, recipient route, recipient details, validity window, and timing limitations. If any field changes, request a new confirmation.
The public rate information is indicative. It does not authorize transfer and should not be used to calculate a guaranteed recipient amount.
How to share information safely
- Begin from the official website contact page.
- Share only information relevant to the request.
- Do not publish identity, wallet, bank, or payment screenshots.
- Check unexpected requests through the established contact.
- Retain the final quote and transaction records securely.
If a document is requested, confirm why it is needed and the approved channel for providing it. Redaction should not remove information necessary to verify the transaction.
Why a request may stop
A request may be delayed or refused when information is incomplete, inconsistent, unsupported, or cannot be reviewed safely; when the recipient account is unsuitable; when the payment purpose is unclear; or when the network or route is unavailable. A refusal should not be bypassed by using another contact or changing the description.
Prepare information without oversharing
A clear request is not the same as sending every document you hold. Begin with the transaction outline and wait for the desk to explain what additional information is required. This reduces exposure of unrelated personal, wallet, or banking data while still supporting a meaningful review.
Check that documents and explanations refer to the same sender, recipient, amount, and purpose. If a record contains an error, disclose the correction instead of altering the context. Consistent information helps the desk understand the request; it does not create automatic eligibility.
Questions before review
Does every customer provide the same documents?
No. Requirements are transaction-specific and can vary by amount, sender, recipient, route, purpose, and risk indicators.
Can I request a quote without all bank details?
You may start a conversation, but a bank TT request cannot be fully reviewed without the beneficiary information the desk requires.
Does providing information guarantee settlement?
No. Eligibility, quote confirmation, blockchain transfer, recipient conditions, and third-party systems still affect the outcome.
Share the amount, network, recipient route, recipient information, and purpose through the official contact process.
