Off-ramping USDT in Latin America means sending the token to a provider that converts it and pays local currency over Pix (Brazil), SPEI (Mexico) or Bre-B (Colombia's instant payment system) and ACH (Colombia). A Colombian business can also receive USDT from clients and pay suppliers in US dollars by ACH, FEDWIRE or SWIFT from the same wallet.
The country changes the rail, and the network changes what can go wrong before it. This guide covers BRL, MXN and COP, then the dollar leg for a Colombian business, and the coverage page lists the other countries. The token and its issuer are covered in what USDT is, and the conversion in what a stablecoin off-ramp is.
Which networks can you send USDT on?
USDT is not deployed on every network that carries USDC. On Lumx, as of November 2026, it runs on three; the other two networks are USDC only.
USDT networks accepted for BRL, MXN and COP payouts, per the Lumx wallets and coverage documentation.
Network | USDT | What it means for a payout |
Ethereum | Yes | The network fee varies with congestion, which matters less on a large invoice than on a payroll run |
Polygon | Yes | The network fee is paid by whoever sends the USDT |
Tron | Yes | The address starts with T and a send from your own wallet needs TRX for Energy, both covered in the TRC20 explainer |
Base | No, USDC only | Not an option for a USDT payout |
Stellar | No, USDC only | Only for the BRL to USDC on-ramp |
I recommend choosing the network by where the sender's USDT already sits, not by which chain is cheapest on paper. For payouts into Mexico my default is USDT on Tron, because the balances businesses pay from tend to have arrived there, and a bridge to Polygon to save on the network fee adds a step that can fail. For a few large invoices paid from an Ethereum balance, I would leave it there, since a network fee is small next to a large invoice.
On Lumx every customer gets a wallet on each supported blockchain, enabled once the customer is approved. An off-ramp debits the wallet on the network named in the request, or on the project's default network when none is named.
Which rail pays out in each country?
Each country has a domestic rail that credits the recipient's bank. Brazil and Mexico have one each. Colombia has two, and the choice limits the size of the payout.
Payout rails for USDT off-ramps to BRL, MXN and COP, as of November 2026.
Country | Rail | What you register for the recipient | Speed | Live rate |
Brazil (BRL) | Pix | A Pix key: CPF (the Brazilian individual taxpayer ID), CNPJ (the Brazilian company taxpayer ID), email, phone number or a random key | Instant, every day of the year | |
Mexico (MXN) | SPEI | A CLABE (the 18-digit Mexican bank account number) | Instant, every day of the year | |
Colombia (COP) | Bre-B | The recipient's Bre-B key | Instant, up to 1,000 UVB per payment | |
Colombia (COP) | ACH Colombia | Name, document type and number, email, bank, account number and account type | Confirm with a small first payment |
In Brazil the tax ID has to belong to the holder of the account behind the Pix key, or the bank rejects the credit, as the Brazil USDT guide shows step by step. In Mexico the Mexico guide walks through a CLABE (the 18-digit Mexican bank account number) payout with USDC, and the token is the only difference.
In Colombia the rail is chosen when the recipient is registered, not when the payment is made. Bre-B credits a registered key and is capped per operation by the Banco de la República at 1,000 UVB (the basic value unit, revalued each year): COP 12,110,000 for 2026, about USD 2,870 at the rate on November 1, 2026, under Circular Reglamentaria Externa DSP-465, Asunto 18, section 3.2. It applies to every provider. A recipient who invoices above it needs bank details on ACH Colombia, as the Colombia guide explains.
On Lumx the rail is a property of the destination, so the recipient's rail is fixed at registration and every payout to that destination goes out on it. In Brazil and Mexico the payout lands under the paying customer's own name. A larger Colombian invoice goes to a recipient on ACH Colombia.
How can a Colombian business receive USDT from clients and pay suppliers in dollars?
It takes one provider that holds both legs. The client sends USDT on Ethereum, Polygon or Tron to the business's wallet address on that network. The balance then stays as USDT, converts to COP and pays out over Bre-B or ACH Colombia, or converts to US dollars and pays a supplier by ACH, FEDWIRE or SWIFT.
For the dollar leg the business registers each supplier as a destination, with the relationship set to supplier, and creates an off-ramp from the USDT balance.
Dollar payout rails from a USDT balance, per the Lumx cut-off and POBO and COBO pages, read November 18, 2026.
Rail | Settlement | Cut-off | What you can trace |
ACH | 1 to 2 business days | 2:00 PM ET | The bank's booking reference, when available. ACH runs as credits (push) |
FEDWIRE | Same business day | 3:00 PM ET | The IMAD, the identifier Fedwire assigns |
SWIFT | 1 to 5 business days | 3:00 PM ET | UETR on every SWIFT payout and the MT103 on request |
Each leg has a different operator. The USD account is issued by a banking partner, with a sponsor bank behind it, and the customer asks for it when it is created, with a target of up to one business day. The COP leg runs through a sponsored program of a banking partner, under that partner's licence. The COP account is in the customer's own name when the customer is Colombian, and the banking partner's name shows for everyone else. Suspicious-activity reports to the UIAF (Colombia's financial intelligence unit) belong to the banking partner, and a Bre-B payout stays under the 1,000 UVB cap above.
Colombia has no stablecoin law, and the Banco de la República does not treat crypto-assets as foreign currency. The DIAN still expects an invoice behind each payment. Our Colombia regulation guide lists what each authority says, and counsel in Colombia can say whether an arrangement needs an exchange declaration.
The steps from a USDT balance to a bank credit
Get the business approved through KYB (know your business). It runs once.
Put USDT in the wallet on the network you chose, a small amount first.
Register the recipient as a destination, with the rail, the account details or key, and the relationship between your business and the account holder, such as supplier or employee.
Wait for the destination to clear verification, then create the off-ramp with the destination, the amount, the purpose and an idempotency key, so that a retry cannot pay twice.
Follow the payout to the end: the stablecoin transfer, the trade, the fiat transfer, then success, with an event at each stage.
Declare the relationship to the account holder truthfully, because it is a compliance field and not a label. A purpose that does not match what the funds are for can trigger an RFI (request for information, a compliance hold that asks for a document before a transaction clears).
What delays the USDT leg is network confirmation and, on Tron, a sending wallet without TRX for Energy. Lumx covers the network fee on its own legs, so the off-ramp itself needs no ETH or TRX. Time a first send in the sandbox, since there is no single figure from deposit to bank credit.
On Lumx each of those is an API call or a webhook, described on the global payments API page. The KYB (know your business) target is one business day, the destination is verified at registration, so a tax ID the bank rejects surfaces before any payment, and a payout whose RFI stays unanswered for 24 hours may be refunded to the sender.
What an off-ramp costs, line by line
A USDT off-ramp has three costs, and most quotes show one. The spread between the rate you receive and the mid-market rate is usually the largest and is often folded into the rate. The rail adds a per-payment fee where the provider charges one. The network adds the blockchain fee on the transfer that puts the USDT in the wallet, paid by whoever sends it. How the layers combine is in how stablecoin payout pricing works, and the providers side by side in best stablecoin off-ramp APIs.
A locked rate is the defense against a hidden spread, because a floating rate can move before execution.
On Lumx the pricing model is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. A locked rate is available for 30 seconds without a fee, or for one or five minutes with one, and the response returns the base rate and the final rate side by side. Lumx does not deduct a fee from the amount that reaches the recipient on a Pix, SPEI or Bre-B payout. Only the recipient's own bank can charge the recipient.
Limits, timing and cut-offs
Three things cap a payout: the customer's limits, the rail's own cap and the hours the rail runs. A payout over a limit is rejected, not queued, so ask for higher limits before a payroll run. The rail's cap exists in Colombia and not in Brazil or Mexico. Pix and SPEI have no cut-off, so a Saturday night payout lands on Saturday night, and the cut-offs in this region belong to the dollar rails, covered in payout limits and cut-offs by rail.
On Lumx a business customer on KYB Standard starts at a per-transaction limit (see the transaction limits in the Lumx docs) and USD 100,000 per day or month, and the limits are global, so they do not change with the destination country. Enhanced verification sets limits that fit the customer's documents, and a payout over a limit returns a 422 with the code TRANSACTION_LIMIT_EXCEEDED.
Why a USDT off-ramp fails, and when it is the wrong tool
A wrong network is the failure that costs money: a transfer to the address of another blockchain goes to an address nobody is watching. Store the network with the address.
A tax ID or name that does not match the account holder is why a Pix payout bounces. A Bre-B payout above the cap fails, as does an expired lock or a payout bigger than the balance. The broader set, across rails and providers, is in why stablecoin payouts get rejected.
On Lumx these arrive as error codes to match on: INSUFFICIENT_BALANCE, EXCHANGE_RATE_EXPIRED, INVALID_TAX_ID, TRANSACTION_LIMIT_EXCEEDED, and the offramp.failed event when a payout does not complete.
How is a USDT off-ramp regulated in Brazil?
In Brazil, converting USDT into reais is an operation of the exchange market but not foreign exchange, and no IOF applies, because a stablecoin is not foreign currency. Article 76-A of Resolution BCB 277 of 2022, inserted by Resolution BCB 521 of November 10, 2025, defines the activity as a payment or transfer in virtual assets, and Law 14.478 of December 21, 2022 sets the framework for the providers.
Lumx filed its SPSAV (Sociedade Prestadora de Serviços de Ativos Virtuais) application and operates under the transition of Resolution BCB 520 of 2025, Article 88.
When the sender holds USDC, swapping into USDT only to off-ramp adds a conversion for no gain, and USDC vs USDT for payments sets out when each fits. When the recipient wants to keep the stablecoin, the payment is a transfer to their wallet.
What a USDT off-ramp 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.
The customer's custodial wallet holds the USDT on Ethereum, Polygon or Tron, and an off-ramp from that wallet to a registered destination pays out over Pix, SPEI, Bre-B or ACH Colombia, depending on how the recipient was registered. USDC and USDT are separate balances in the same wallet. The COP corridor runs through a sponsored program with a banking partner, under the partner's licence.
KYB, destination verification and the conversion to local currency are inside the API, so the steps above are calls and not a project.
Methodology and sources
Product behavior was read on docs.lumx.io on November 1 and November 18, 2026, in the wallets, coverage, accounts, POBO and COBO, exchange rates, transactions, destinations, transaction limits, RFI and cut-off times pages, and the off-ramp integration prompt. The COP payout rails, the networks for COP, the refusal of Bre-B payouts above the cap and the KYB target of one business day were confirmed by Lumx on October 29 and November 1, 2026.
The Bre-B cap comes from the Banco de la República's Circular Reglamentaria Externa DSP-465, Asunto 18, section 3.2, in the sheet of March 31, 2026, and the 2026 peso value of COP 12,110,000 from its Bre-B page. Those pages did not serve text to automated requests, so confirm the value there before you build a limit.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Barrett Ward on Unsplash.
How do I off-ramp USDT in Latin America?
Send the USDT on a supported network to a wallet your provider controls, register the recipient's bank details, and accept or lock a quote. The provider converts it and pays local currency over Pix in Brazil, SPEI in Mexico, or Bre-B or ACH Colombia in Colombia. On Lumx you send USDT to the customer's wallet, register a destination, and create an off-ramp naming the destination, the amount and the purpose.
Which networks can I send USDT on for payouts to Brazil, Mexico and Colombia?
USDT is accepted on Ethereum, Polygon and Tron for all three currencies. Base and Stellar carry USDC only. On Lumx each customer has a wallet on every supported network.
How can a Colombian business receive USDT from clients and pay suppliers in dollars?
The client sends USDT on Ethereum, Polygon or Tron to the business's wallet address, and the business converts the balance to US dollars and pays the supplier by ACH, FEDWIRE or SWIFT, or converts to COP and pays over Bre-B or ACH Colombia. On Lumx the COP leg runs through a banking partner's sponsored program, the USD account has a sponsor bank behind it, and tracking is a UETR on every SWIFT payout and the MT103 on request.
How much USDT can I off-ramp in one payment?
It depends on the customer's verification level and, in Colombia, on the rail. A Bre-B payout is capped at 1,000 UVB, COP 12,110,000 in 2026, and ACH Colombia has no per-payment cap on Lumx. Higher limits come with Enhanced verification.
What does a business need before its first USDT off-ramp?
An approved customer, a wallet with USDT on a supported network and a verified destination for each recipient. On Lumx the KYB target is one business day, and the destination is verified at registration, so bank details are checked before the first payment.





