Which codes could a wire to buy USDT carry?

A wire to buy USDT is a payment to a licensed firm in exchange for a digital asset. The UAE code list does not describe that in so many words, so the practical task is to pick the entry whose name is closest to the payment and then agree it with the desk. The table below uses code names exactly as one bank publishes them. It is a shortlist for the conversation, not a ruling. For the wire itself, including AED against USD handling, see our guide to buying USDT with a bank wire.

Source: NAB, United Arab Emirates purpose of payment codes, accessed 20 October 2026. Descriptions in the third column are our reading of the names, not text from the regulator.

We could not open the Central Bank of the UAE's own explanatory notes on the codes in a readable form, so we do not quote its definitions here. Read the full descriptions in the notes before you settle on a code; the HSBC UAE copy listed in Sources is one place to find them.

Is there a purpose-of-payment code for crypto?

In the bank-published list we checked, no entry is named for virtual assets or crypto. We did not confirm this against a Central Bank of the UAE page, so treat it as a finding about that list, not a statement about every version. Your own bank may show a different set or wording, so look at the list inside your bank's payment form.

The consequence is the same either way. With no dedicated entry, you cannot rely on a code that names the asset, and the code and the written payment reference have to tell one consistent story about a purchase from a licensed firm. Whichever code you and the desk agree, put the same description in the reference and keep the desk's written confirmation of it.

Why does OAT not fit a payment to a desk?

OAT reads as a transfer between your own accounts. It is tempting for a buyer because the USDT will end up in a wallet you control, but the wire does not go to yourself. It goes to the desk's account, and the desk is a separate legal person. A code that says own account while the beneficiary is a company is the kind of contradiction a bank screening team notices.

FAM and SAL fail for the same reason in a different direction. Family support and salary describe relationships that do not exist between you and a desk. Some senders pick them because they seem harmless or familiar. They are the codes most likely to clash with a reference such as a trade ID, and the clash is what draws attention.

Why can a wrong code get a wire held, queried or returned?

A purpose code is a field the bank reads alongside the beneficiary name and the payment reference. When the three disagree, a bank can ask questions before it releases the payment. We make no claim about how often this happens; it is a general risk of any mismatched wire. Two published points explain the mechanics.

• One UAE bank states on its help page that purpose codes are mandatory for domestic and cross-border payments where both banks are UAEFTS members, and that a missing or invalid code leads to automatic rejection (accessed 20 October 2026).
• The Central Bank of the UAE's technical notes on transaction codes include sample SWIFT message text in which the receiving side tells the sender the payment was executed for regulatory requirements and asks for the purpose of payment as a code (accessed 20 October 2026).

So a code can be rejected at entry, or queried after the money has left. The cheapest fix is to settle the code and the reference wording with the desk before you press send. For USD wires the route and cost side is covered in how SWIFT payments from the UAE work.

Where does the field sit in the Emirates NBD, FAB, ADCB and Mashreq apps?

We could not confirm menu paths or exact field labels for Emirates NBD, FAB, ADCB or Mashreq from those banks' own published pages, so we do not give any. Labels and positions change between app releases and between personal and business channels. The table lists what to look for instead.

If you cannot find the field, ask your relationship manager or the bank's support line to show you where the code is entered. Do not guess and leave a default selected, since a pre-filled value may not match the payment.

What changes when a company sends the wire?

The code still describes the payment, not the sender. What changes is the paper behind it. A company should be able to show who approved the purchase, which invoice or trade confirmation it settles, and why the treasury or investment code chosen matches. The approval and record-keeping steps are set out in our guide to how a UAE company buys USDT.

Business channels at UAE banks often ask for supporting documents at the payment step, and an attached agreement that says one thing while the code says another is as unhelpful as a wrong personal code. Keep the code, the reference and the document wording aligned, and keep the desk's written confirmation of the code in the same file.

What does the receiving bank see on a sell payout?

When you sell USDT, the desk pays you. Your bank sees an incoming credit with the sender's company name, a reference and the rail used. The purpose code on that payout is part of the desk's own payment instruction, and we have not published which code it uses, so ask for it in writing alongside the reference wording. How an incoming credit reads on the statement is covered in what the credit from a USDT sale looks like on your statement.

Whether your bank shows the code to you at all varies by bank and channel. If you need it for your records, ask the desk to include it in the written settlement confirmation, and keep that confirmation with the statement. Payouts go to an account in your own name; onboarding steps are in the onboarding section.

How do you confirm the code before you send?

1. Ask the desk by email or in the dealing chat which code it expects and what the reference should say.
2. Check that your bank's list offers that code under that name.
3. Make the reference describe the same thing, for example a purchase and the trade ID.
4. Save the desk's answer. If a query arrives later, quote it.

To start a purchase and get these details in writing, request a quote.

This guide is informational and is not legal, tax or investment advice, nor an invitation to buy or sell any virtual asset. Rules and figures are as of October 2026, re-check the sources before acting. Virtual assets may lose their value in full or in part and are subject to extreme volatility.