Paying suppliers in Asia from Latin America with stablecoins means converting reais, Mexican pesos or Colombian pesos into USDC or USDT, then paying the supplier in US dollars over SWIFT. A Hong Kong company that agrees to it can instead receive USDT in its wallet. By default the supplier receives US dollars in its own bank account, never crypto.
Best for: importers and trading companies in Brazil, Mexico and Colombia that pay invoices to suppliers in Hong Kong, Singapore, Vietnam or India.
Mainland China is a separate case, covered in paying suppliers in China from Brazil.
How does a company in Latin America pay an Asian supplier with stablecoins?
In four legs, with one rail per leg. The company funds its account in local currency, the deposit converts into USDC or USDT, the stablecoin waits in a custodial wallet until the invoice is due, and a payout converts it into US dollars and sends it to the supplier's bank by SWIFT.
The four legs of a payment from Latin America to a supplier in Asia
Leg | What happens | Rail | Timing |
1. Local currency in | The company pays its own account from its bank (BRL to USDC) | Pix, SPEI, Bre-B or PSE | Instant on Pix and SPEI; Bre-B is capped at 1,000 UVB per transaction |
2. Convert | The deposit converts to USDC or USDT as it lands | None | Follows the deposit |
3. Hold | The stablecoin sits in the company's custodial wallet until the invoice date | None | Until you pay |
4. Pay out | The stablecoin converts to dollars and leaves as a wire (USDC to USD); a Hong Kong supplier can instead take USDT in its wallet | SWIFT in USD, or a USDT transfer | SWIFT: 1 to 5 business days; USDT: when the blockchain confirms |
Each pair of currencies and rails is a stablecoin corridor, and legs 1 to 3 match BRL to USDC for corporate treasury.
On Lumx, the Latin American company is one customer with a local account, a custodial wallet and one destination per supplier. Legs 1 and 2 run as an on-ramp, leg 4 runs as an off-ramp, and both sit behind the same API and the same webhooks.
Funding in reais, Mexican pesos or Colombian pesos
The company pays from its own bank account. In Brazil that is a Pix (Brazil's instant payment system, run by the Central Bank) transfer from the company's CNPJ (the Brazilian company taxpayer ID). In Mexico it is a SPEI (Mexico's interbank transfer system, run by Banxico) transfer. In Colombia it is a transfer to the company's Bre-B (Colombia's instant payment system) key, or a payment through PSE (Colombia's online bank-transfer network).
Bre-B has a regulatory ceiling of 1,000 UVB per transaction, about COP 12,110,000 or about USD 2,870 (Circular Reglamentaria Externa DSP-465 of the Banco de la Republica, Asunto 18, numeral 3.2, sheet of March 31, 2026). A USD 60,000 supplier invoice does not fit in one Bre-B transfer, so a Colombian importer funds a larger invoice through PSE, whose ceiling is set by each bank, or in several transfers within its limits.
Whether the company has to file anything at home to pay an import invoice this way is an origin-country question, covered by norm in our guides to stablecoin regulation in Brazil, stablecoin regulation in Mexico and stablecoin regulation in Colombia.
On Lumx, a standing autoconversion rule gives the company a Pix code or a CLABE (the 18-digit Mexican bank account number) to pay into, and every matching deposit converts to USDC or USDT at the market rate, with no per-payment call. The rule converts at the market rate; for a locked rate, quote the single payout. A BRL, MXN or COP account turns active right after the company's KYB (know your business, the verification of a company and its owners) is approved. Lumx targets one business day for KYB, so start there.
Which currency and rail reaches a supplier in each Asian country?
US dollars over SWIFT in all four, with USDT to a wallet as an extra option in Hong Kong only. Only two cases differ, so the table has two rows (Lumx docs, read November 1, 2026).
What the supplier receives and what to collect, by destination
Destination | Supplier receives | Rail | Timing | What to ask the supplier for |
Hong Kong | US dollars in a USD account, or USDT in its wallet | SWIFT in USD, or transfer to an external wallet | SWIFT 1 to 5 business days; USDT when the blockchain confirms | USD account and SWIFT code; or wallet address and network, in writing |
Singapore, Vietnam and India | US dollars in a USD account | SWIFT in USD | 1 to 5 business days | USD account number or IBAN, SWIFT code, bank name and address, and any intermediary bank the supplier's bank requires |
For all four, ask the supplier's bank one question in writing before the first invoice: will it credit an inbound USD wire from this sender for this kind of invoice, and does it need any document with it. We did not verify Vietnamese or Indian rules on inbound foreign-currency receipts, so for those two the answer comes from the supplier's bank, not from this guide. The Singapore and Hong Kong rules are covered in stablecoin regulation in Singapore under MAS and the HKMA stablecoin issuer regime.
SWIFT takes 1 to 5 business days because each intermediary bank adds time and may deduct a fee. The Lumx cut-off for USD over SWIFT is 3:00 PM Eastern (payment rail cut-off times), and an instruction sent after it waits for the next business day. The payer's clock is the one that matters: the documentation's example is that an off-ramp triggered at 4:00 PM in Sao Paulo lands well after the same 3:00 PM ET cut-off on FEDWIRE.
On Lumx, the destination carries the rail. A supplier in Singapore is a destination with the rail SWIFT, the currency USD, an account number or IBAN plus the BIC (the SWIFT code), the bank's name and address, and an optional intermediary bank. Every SWIFT payout returns UETR and MT103 confirmations, so the supplier's finance team can trace the wire on its side. The coverage page lists the rails by country.
Hong Kong: where USDT is an option, and where it stops
A Hong Kong company still receives USDT today: a transfer from the importer's wallet to a wallet the company controls, with no CNY settlement and no SWIFT leg, landing when the blockchain confirms. The Stablecoins Ordinance (Cap. 656) came into force on August 1, 2025, and the Hong Kong Monetary Authority now requires a licence to issue a fiat-referenced stablecoin there. That regime licenses issuers, not a company taking USDT for an invoice.
The test is the entity on the invoice. A Hong Kong trading company can take USDT. A mainland factory behind it cannot, because [Yinfa [2026] No. 42](https://www.pbc.gov.cn/tiaofasi/144941/3581332/2026020619591971323/index.html) of the People's Bank of China, dated February 6, 2026, bars foreign entities from providing virtual currency services to parties in mainland China. If the invoice names a mainland entity, pay the dollars to its bank instead. The USDT steps have their own guide on Hong Kong supplier payments in USDT.
For Singapore, Vietnam and India, this guide sends dollars to a bank account. Whether a company there may receive a stablecoin is a question for its own counsel and bank.
On Lumx, a USDT payout to a Hong Kong wallet is a transfer from the customer's wallet to the external address, on Ethereum, Polygon or Tron. A transfer to a wrong address or network cannot be recalled, so send a small test amount first.
What to collect from each supplier before the first payment
The legal name on the invoice, the name on the bank account and the tax ID have to describe the same entity. Ask for a USD account explicitly, and for a named person in finance who can read a SWIFT message when a wire is held.
I recommend paying the first invoice to every new Asian supplier in dollars by SWIFT, even when the supplier is in Hong Kong and offers USDT. The first payment tests the supplier's details, not the rail, and a wire to the wrong account can be traced by the banks, while a USDT transfer to the wrong address cannot. After one clean payment, I would move a Hong Kong supplier to USDT only once it confirms the wallet and network in writing.
On Lumx, each supplier is registered as a destination with the holder relationship SUPPLIER, and the payout carries the purpose TRADE_TRANSACTIONS. The destination goes through verification before it can be paid: destinations.under_verification marks the start, and destinations.approved or destinations.final_rejection reports the result. A payout to a destination that is not approved cannot run. The check includes sanctions screening and the name check (VoP or CoP) that the banking partners run, which counts toward the approval without a separate verdict coming back. The company pays its own suppliers from its own funds; a nested structure, where it pays parties Lumx has not onboarded, needs written approval from compliance first.
Limits, cut-offs and what a payment costs
Take a USD 60,000 invoice from a Singapore supplier. A business on standard verification has a per-transaction limit of USD 50,000, so that payment needs a higher limit before the invoice date.
When a SWIFT payout instructed from Latin America reaches the supplier (Lumx docs)
Instruction | When the SWIFT clock starts | Supplier has the dollars |
Before 3:00 PM Eastern on a US business day | Same day | 1 to 5 business days later |
After 3:00 PM Eastern, or on a weekend or US federal holiday | Next US business day | 2 to 6 business days after the instruction at most, counting the wait |
On Lumx, the limits apply to every customer from every country: USD 50,000 per transaction, USD 100,000 per day and USD 100,000 per month on KYB Standard, with higher figures after Enhanced verification. A payment over the limit is rejected with TRANSACTION_LIMIT_EXCEEDED, and the customer can request a higher limit from the dashboard or the API with a supporting document such as financial statements, which has a target review of one business day. The pricing model is "monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans". A locked rate for the dollar leg lasts 30 seconds, 1 minute or 5 minutes, and the 30-second lock has no fee.
What happens when a payment is held or returned?
Compliance can pause a transaction in an RFI (request for information, a hold that asks for a document before the transaction clears) when the purpose does not match the activity or the destination's details do not match the holder. The commercial invoice is the document to have ready.
A wire can also be held or returned by the supplier's bank or an intermediary for its own review, outside the sender's control. Three steps protect the payer when that happens: check the state of the transaction before resending, because a second instruction with a new reference pays the supplier twice; reuse the same Idempotency-Key if a resend is needed; and send the commercial invoice to answer any request for information. The UETR and the MT103 let the supplier's bank find the wire on its side.
On Lumx, a payout moves through offramp.transferring_stablecoin, offramp.trading, offramp.transferring_fiat and offramp.success, and offramp.failed reports a payout that did not complete. A retry that reuses the same Idempotency-Key does not create a second payment. Lumx considers the payout complete once the funds leave its banking partner.
When a stablecoin route is the wrong tool for an Asian supplier
When the supplier has to be paid in its own currency. This route ends in US dollars. A supplier that must receive local currency in its account needs a bank route that ends there.
When the invoices are rare or small. Intermediary deductions on a SWIFT wire can erase what the conversion saves.
When the payment may need to be recalled. A SWIFT wire can be recalled only if the supplier agrees to return it, and a USDT transfer cannot be recalled at all.
What an invoice paid to Asia 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.
Take a Brazilian importer with a supplier in Singapore. After KYB, it pays reais into a Pix code from an autoconversion rule, and each deposit converts to USDC in its custodial wallet. The supplier is registered once as a SUPPLIER destination on SWIFT in USD, a locked quote for the invoice amount goes to the off-ramp, and the payout carries the purpose TRADE_TRANSACTIONS. The supplier's finance team gets the UETR and the MT103. Mexican and Colombian companies run the same legs with SPEI, Bre-B or PSE first.
The global payments page lists the capabilities behind each leg, our explainer on stablecoins and SWIFT shows where the speed comes from, and the trade picture is in Latin America to Asia-Pacific corridors.
Methodology and sources
The Hong Kong regime was read on the HKMA page on the regulatory regime for stablecoin issuers on November 1, 2026. Yinfa [2026] No. 42 is cited by number and date, with a link to the People's Bank of China text. No Singapore, Indian or Vietnamese norm is cited, because the Monetary Authority of Singapore's site and the Indian financial intelligence unit's site did not load on the date of writing. Lumx onboards customers in the supported countries. Lumx rails, cut-offs, limits, destinations and webhook events were checked against the public documentation on November 1, 2026.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Scott Rodgerson on Unsplash.
How do you pay suppliers in Asia from Latin America?
Convert local currency into USDC or USDT through an account that holds the stablecoin, then pay each supplier in US dollars over SWIFT into its bank account. A Hong Kong supplier can instead receive USDT in its wallet. On Lumx, the company is one customer with a custodial wallet, each supplier is a destination, and the payout runs as an off-ramp with UETR and MT103 confirmations.
Which currency does an Asian supplier receive?
US dollars, in a USD account at its own bank, for suppliers in Hong Kong, Singapore, Vietnam and India. A Hong Kong company can take USDT in its wallet instead if it agrees. On Lumx, SWIFT runs in US dollars only, so the dollar amount is quoted before the payout and the destination carries the rail.
Does the supplier need a crypto wallet?
No. Only a Hong Kong supplier paid in USDT needs one, with the address and network given in writing. Every other supplier receives a dollar wire. On Lumx, a USDT payout is a transfer from the customer's wallet to the external address, on Ethereum, Polygon or Tron.
How long does a payment from Latin America to Asia take?
The funding leg is instant on Pix and SPEI; a Bre-B transfer is capped at 1,000 UVB, about USD 2,870. The SWIFT leg takes 1 to 5 business days, and an instruction sent after the 3:00 PM Eastern cut-off waits for the next business day. On Lumx, the cut-off for USD over SWIFT is 3:00 PM Eastern, which a payer in Sao Paulo or Mexico City converts to its own clock, and each status change of the payout arrives as a webhook event.
What is the largest single payment a company can send?
It depends on the company's verification level. On Lumx, a business customer on standard verification has a limit of USD 50,000 per transaction and USD 100,000 per day, and Enhanced verification with a supporting document raises it.
