A Chinese bank TT request is more than an account number. The beneficiary identity, bank details, payment purpose, commercial record, and expected RMB need to describe the same payment.
The beneficiary block
Prepare the beneficiary’s complete name in the requested form, account number, bank name, branch information, and any requested city, province, address, telephone, or routing field. Whether every field is required depends on the actual route, but missing or inconsistent information can delay review.
Bank of China’s public remittance pages illustrate the range of information that may matter: payee name and account, beneficiary bank, bank address, SWIFT information for relevant international routes, and remittance purpose in some services. An ExtentExchange RMB-side instruction is transaction-specific, so do not copy a generic form into the request without confirmation.
The payment-purpose line should make sense
A useful purpose describes the real reason for the transfer in plain language and agrees with the invoice or supporting context. “Goods payment,” “service invoice,” or another description may still require more detail. Never relabel a payment to make it appear simpler, and never split an amount to avoid questions.
For a supplier payment, compare the purpose with the supplier name, invoice issuer, goods or services, order reference, and amount. If the beneficiary is not the invoicing party, explain the relationship before funds move.
Fields that deserve a second-person check
| Field | What to compare |
|---|---|
| Beneficiary name | Exact provided name, company or individual status, and invoice relationship |
| Account number | Every digit, spacing removed only when instructed |
| Bank and branch | Full institution and location information requested |
| RMB amount | Expected recipient amount in the current quote |
| Purpose/reference | Truthful commercial reason and matching order or invoice record |
For business payments, have someone who did not type the fields compare them with the supplier’s authoritative record. This is particularly valuable when details arrived through several messages.
Common exceptions
- The beneficiary name is abbreviated while the account uses a registered name.
- The supplier asks for a personal account after issuing a company invoice.
- The branch or location field is missing.
- The account changed after the quote was confirmed.
- The requested purpose conflicts with the underlying payment.
- The recipient reports a different RMB amount than the current instruction.
Pause on any exception. The recipient-mismatch guide explains why substitutions should be reviewed as new information.
Before approving USDT
Join the bank details to the rest of the transaction: exact USDT amount, current rate, expected RMB, receiving wallet, supported network, beneficiary, bank route, validity window, and timing limitations. Use the wallet and quote checklist immediately before approval.
After RMB is sent
Retain the quote, beneficiary record, purpose, invoice reference, transaction hash, and available RMB completion reference. Ask the beneficiary to check the intended bank account and reconcile the amount. Do not publish bank evidence or personal information.
Primary background sources
- Bank of China’s domestic transfer and remittance overview.
- Bank of China Singapore’s published international remittance fields.
These sources show why accurate beneficiary and bank data matters; they do not define the fields for every ExtentExchange request.
Questions about bank TT fields
Is a SWIFT code always required?
Not necessarily. The required routing fields depend on the actual bank route. Provide only the fields requested for the current transaction.
Can I correct one digit after USDT is sent?
Contact the desk immediately. Do not assume a beneficiary field can be changed or that completion is possible.
Can the purpose be shortened?
Only if the resulting description remains accurate and meets the current request. Never conceal the real purpose.
Use the official contact page and provide the complete bank record, RMB amount, purpose, and invoice context.
