To pay a Hong Kong supplier in USDT, check that the Hong Kong company named on the invoice is the one receiving the payment, get its wallet address and network in writing, send a small test, then send the balance. A mainland supplier should be paid in US dollars, not in USDT.
Goods made in Guangdong or Zhejiang are often sold by a Hong Kong trading company. The route works only when the invoice names the right entity. The reais leg and the mainland case for a Brazilian buyer are in paying suppliers in China from Brazil, and other Asian countries in suppliers across Asia.
Who should receive the USDT: the Hong Kong company or the factory?
The company on the invoice decides it. A Hong Kong trading company that sells you the goods can be the payee. The factory in the mainland that makes them is a different legal person under a different regime, and it should be paid in dollars to its bank account.
Who can be paid in USDT, by the entity on the invoice
Entity on the invoice | Pay in USDT? | Why |
Hong Kong trading company, with the invoice and the wallet in its own name | Yes, after the checks below and the buyer's own counsel review | The February 2026 notice is written for the mainland and does not address Hong Kong, which runs its own regime |
Mainland factory that ships the goods | No, pay US dollars to its bank | The notice treats USDT as a virtual currency that cannot circulate as money on the mainland |
Agent, sister company or any third party asking to be paid instead | No | The payee must be the entity on the invoice, and anything else breaks the audit trail |
Hong Kong company that will pass the money on to a mainland party | Ask its own adviser first | What it does next is its risk, and the buyer should not instruct it to pay a mainland party in USDT |
The mainland column of that table rests on one text. On February 6, 2026, the People's Bank of China and seven other agencies published the notice on further preventing and handling risks related to virtual currencies, Yinfa [2026] No. 42. It names Tether among the virtual currencies that have no legal tender status and must not circulate as money, and it says that foreign entities and individuals may not unlawfully provide virtual currency services to parties within the mainland in any form. The notice took effect on the day it was published and repealed Yinfa [2021] No. 237.
The supplier does not need to be a Lumx customer. A transfer goes from the buyer's wallet to a wallet address, so the payee is a Hong Kong company the buyer has already checked and nothing else. Lumx screens each transaction before it runs, in both directions, and monitors blockchain activity with Chainalysis KYT, which covers every kind of wallet, external ones included. Destination addresses are due to become destinations in the API, like fiat destinations, with no date yet. None of that replaces the buyer's own check that the address belongs to the supplier. A Hong Kong company that wanted to pay through Lumx itself would go through standard business verification, as a customer onboarded by reverse solicitation, with no local licence.
What the Hong Kong and mainland rules say
The mainland notice is about activity inside the mainland and about foreign parties who serve mainland parties. It does not mention Hong Kong. A Hong Kong company receiving USDT for goods it sold is not described in it, and this guide does not read it as a ban on that company. What it does tell a buyer is where not to send the money: to a party on the mainland.
The Hong Kong text is about issuers. The Hong Kong Monetary Authority states that since August 1, 2025, under the Stablecoins Ordinance (Cap. 656), issuing fiat-referenced stablecoins in Hong Kong is a regulated activity that needs a licence, and it keeps a register of licensed issuers. That page describes the issuer's licence. It does not describe a licence for a company that receives stablecoin as payment for goods, and this guide claims no licence status for the supplier. What the supplier's own bank or exchange accepts is a separate question for the supplier. The issuer regime is covered in Hong Kong's stablecoin issuer licence, and the three regimes side by side in three regimes compared.
Before the first payment, the buyer's counsel should confirm its own jurisdiction's rules on paying abroad in a stablecoin.
Checks on the Hong Kong company before the first payment
Three things have to be true before money moves: the company exists and is the one that sold you the goods, the people behind it are known, and the wallet really belongs to it.
Start with the entity. The name on the contract, the name on the invoice and the name on the company's own registry extract must be the same string. Ask for a current extract from the Hong Kong company registry, and for its directors and ultimate owners. This is what KYB (know your business, the verification of a company and its owners) does for a customer, covered in what KYB is, and a buyer can run a lighter version on a supplier.
Then the wallet. Ask the supplier's finance team for the address and the network, on company letterhead, and confirm both over a second channel, such as a call to a number you already held. The address alone is an incomplete instruction, because the same string can exist on more than one network, and a transfer on the wrong one can be lost.
Last, the commercial paper. Agree in the contract or the invoice that the price is in US dollars and settled in USDT at par, so the amount is not renegotiated after the goods ship. The invoice has to name the Hong Kong company as seller. If the invoice names another company, ask why before paying.
The buyer's side on Lumx is a verified business: a customer's wallet is enabled once it reaches APPROVED, and a standard KYB review targets one business day. The supported countries list shows where a buyer can be onboarded.
Which network to pay on
USDT lives on several networks, and the supplier's address belongs to exactly one of them. The network is the one the supplier's receiving account already takes, which the supplier's finance team knows, and cost comes second.
Where a USDT payment can go from a Lumx wallet, from the Lumx wallets and transfer docs read on November 1, 2026
Network | USDT in the wallet | What to check |
Ethereum | Yes | The supplier's address is an Ethereum address, and the receiving side accepts USDT there |
Polygon | Yes | The same check on Polygon, which is a separate network from Ethereum |
Tron | Yes | The address starts with T, which is a format check and not proof of ownership |
Base | USDC only | Not a route for USDT |
Stellar | USDC only, and on-ramp only | Not a route for a transfer to a supplier |
The Tron option is covered in USDT on Tron for business payouts, and the token in what USDT is.
In the Transfer call, the blockchain field sets the network. Leave it out and the project's default network is used, so name the network explicitly on a supplier payment and never rely on the default.
The payment, step by step
Agree the terms in writing: the Hong Kong company as seller, the amount in US dollars, USDT as the payment currency and the network.
Run the checks above and receive the address on letterhead, confirmed over a second channel.
Fund the buyer's wallet with USDT on that network. If the buyer holds local currency, that means converting it first, and the stablecoin corridor explains the usual routes.
Send a small test transfer to the address and ask the supplier to confirm it arrived.
Send the balance of the invoice.
Keep the invoice, the contract line that sets USDT as the payment currency, the supplier's confirmation and the transaction record in one file.
I recommend sending a small test amount and waiting for the supplier's finance team to confirm it before the first full payment, even though the test costs a little time. I also recommend putting USDT in the contract or the invoice itself, so the currency is agreed in writing and not granted over chat after the goods ship. A transfer to the wrong address or network cannot be recalled, and the test is the cheapest way to find out.
After the payment lands, what the Hong Kong company does with the USDT is its own treasury decision.
The buyer calls the Transfer endpoint with the currency, the sending customer, the supplier's address, the amount and the network, and can attach the invoice number in the metadata field. The transfer moves from TRANSFERRING_STABLECOIN to SUCCESS, and the transfer.success webhook carries a receipt with the transaction hash and a link to the block explorer, which is the record for step 6. A failed transfer arrives as transfer.failed.
What a payment costs and how long it takes
The cost that varies is getting USDT into the wallet, and it depends on where the buyer's money starts, so it is the one to compare between providers. On Lumx, the network fee on the transfer is subsidized, so the buyer does not need ETH or TRX in the wallet.
On time, a transfer takes as long as the network needs to confirm it, with no bank cut-off. An international bank wire takes one to five business days for SWIFT, per the Lumx coverage page. A receiving platform can still hold a deposit for review.
Four limits on Lumx can be checked before invoice day:
50,000 USD per transaction for a standard KYB customer.
100,000 USD per day and 100,000 USD per month.
A limit increase is reviewed in one business day.
A transfer above a limit is rejected with
TRANSACTION_LIMIT_EXCEEDED.
Illustrative example, with invented figures: a 62,000 US dollar invoice from a Hong Kong trading company
Step | Amount | Note |
Invoice, agreed at par in USDT | 62,000 USDT | Written into the contract before the goods ship |
Test transfer | 100 USDT | Confirmed by the supplier before the balance goes |
Balance transfer | 61,900 USDT | Above the 50,000 USD single-transaction limit of a standard KYB customer |
Limit headroom check |
| Before invoice day, on the customer read |
The balance here needs a higher limit, so ask for the increase before the due date.
Lumx's model is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans.
The stablecoin balance used for the transfer is the buyer's own wallet balance, held in custody with BitGo and segregated by customer, not a deposit, because Lumx is not a bank.
When paying in USDT is the wrong tool
When the supplier is a mainland entity, or its wallet is. Pay dollars to its bank, whatever discount it offers for USDT.
When the invoice names one company and the wallet belongs to another. A payment to a sister company or an agent leaves the buyer unable to show that the goods were paid for.
When the supplier cannot give the address and the network in writing, or will not confirm them over a second channel. Without both, the first payment is a guess.
When the buyer may need the money back. A bank wire can be recalled with the other bank's cooperation. A confirmed USDT transfer cannot be recalled by anyone, so a deposit that may be refunded is a worse fit than a bank payment.
When the supplier cannot turn USDT into usable money. The dollar route exists for this case: Lumx runs SWIFT in USD, with UETR and MT103 confirmations on every payout, and the comparison of stablecoins and SWIFT sets out when each wins.
What this payment looks like on Lumx
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
A payment to a Hong Kong supplier is the simplest thing the global payments API does: a transfer of USDT from the buyer's custodial wallet to an external address, with no conversion in between. The buyer, as a verified customer, funds the wallet by on-ramp, by an autoconversion rule on a local currency account, or by sending USDT in. Then it transfers to the address the supplier confirmed, on the network it named, and follows the status through webhooks.
Each payment should be the customer's own money paying the customer's own supplier. The nested payments rule in the Lumx documentation lists invoices that name an entity other than the account holder as a signal, so the invoice should name the buyer; any structure that pays through a third party needs written approval from compliance first. A mainland supplier is paid in USD by SWIFT, so the same buyer can run both routes from one integration.
Methodology and sources
Yinfa [2026] No. 42 was read in Chinese on pbc.gov.cn on November 1, 2026, and the provisions above are from that text. The Hong Kong issuer regime was read on the HKMA's page for stablecoin issuers on the same date. Lumx's wallet, transfer, limit and webhook pages were read at docs.lumx.io on November 1, 2026. That Lumx customers pay Hong Kong suppliers in USDT by transfer to an external wallet comes from our own operations.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: U. Storsberg on Unsplash.
How do you pay a Hong Kong supplier in USDT?
Confirm that the Hong Kong company on the invoice is the payee, get its wallet address and network in writing, and confirm them over a second channel. Send a small test, wait for the supplier to confirm, then send the balance and keep the invoice and the transaction record. In Lumx, the buyer makes a transfer from its wallet to the supplier's address on the named network, and the success webhook carries the receipt.
Who should be the payee when the goods are made on the mainland?
The Hong Kong company that issues the invoice and signed the contract, and no one else. The mainland factory behind it should be paid in dollars to its bank account, since the February 2026 notice from the People's Bank of China treats USDT as a virtual currency that cannot circulate as money there. Lumx pays a mainland supplier in USD by SWIFT and a Hong Kong supplier by a transfer to its wallet.
Which network should the supplier use?
The one its receiving account already supports, which the supplier's finance team should state in writing. Cost comes second, and the address only works on the network it was issued for. Lumx holds USDT on Ethereum, Polygon and Tron, and the transfer takes the network as a field.
Can a USDT payment to the wrong address be recovered?
Usually not. A confirmed transfer cannot be recalled by the sender, and recovery depends on whoever controls the receiving address. That is why a small test comes first and the address is confirmed over a second channel. With Lumx, a transfer that fails arrives as a transfer.failed webhook, and one that succeeds carries the transaction hash, so the record shows where the money went.
What should the buyer keep on file for a payment to a Hong Kong supplier?
The contract line that sets USDT as the payment currency, the invoice naming the Hong Kong company as seller, the address confirmation from the supplier, and the transaction record. Lumx lets the invoice number be attached to the transfer in its metadata field, and the receipt in the success webhook gives the transaction hash.
