A stablecoin off-ramp is the service that takes a dollar stablecoin such as USDC or USDT and delivers local currency to a bank account: reais over Pix (Brazil's instant payment system, run by the Central Bank), pesos over SPEI (Mexico's interbank transfer system, run by Banxico), dollars over ACH or FEDWIRE, euros over SEPA. The token goes in on a blockchain; ordinary money comes out on an ordinary rail. The on-ramp is the same road in the other direction, and it has its own explainer.
For a business, the off-ramp is where a stablecoin stops being an abstraction and becomes a supplier paid, a contractor's salary, a seller's settlement. It is also where most of the operational risk sits, because it is the leg that touches the banking system. This post walks through the steps, the costs, the failure modes and the cases where an off-ramp is not the answer. If the token itself is new to you, what a stablecoin is comes first.
The five steps between a token and a bank credit
Every off-ramp, whatever the provider calls it, runs the same sequence.
Quote. The sender asks how much local currency a given amount of stablecoin will produce. The answer includes the exchange rate, the fee and an expiry, usually a few minutes for a floating quote or longer for a locked one. This is the moment the cost is visible, and a provider that shows it only after execution is charging a spread the client cannot audit.
Deposit. The sender transfers the stablecoin to the provider's address on an agreed network. Confirmation takes seconds on Tron or Solana, a minute or two on Ethereum or Polygon. From here the tokens are the provider's problem.
Conversion. The provider sells the stablecoin for local currency at the quoted rate, from its own inventory or through a liquidity partner. The client never sees this step, which is the point.
Compliance. The destination is checked: does the account holder's tax ID match the name on the account, is the recipient on a sanctions list, does the transaction fit the customer's declared purpose and history. This is where a payout can pause with an RFI (request for information, a compliance hold that asks for a document before a transaction clears).
Payout. Local currency leaves the provider's bank account over the local rail and lands in the recipient's account. On Pix and SPEI that is seconds, around the clock. On ACH it is a business day; on SEPA, the same day or the next; on SWIFT, one to three days.
Three of the five steps are fast by construction. The two that can slow a payout are conversion, when liquidity is thin for a pair, and compliance, when the destination is new or the data is wrong.
What an off-ramp costs
The visible price is the spread between the quoted rate and the mid-market rate, plus a fee that is either a percentage or a fixed amount per payout. In Latin American corridors the spread on a stablecoin off-ramp is typically a fraction of what a correspondent-banking wire costs once the intermediary fees and the receiving bank's conversion are counted, which is the reason the flow exists. We do not publish a single number because it depends on the pair, the volume and the network, and any provider who quotes one number for all corridors is quoting the best case.
The invisible price is the network fee on the deposit leg, which the sender pays. On Ethereum during congestion it can be dollars per transfer; on Tron, Polygon or Base it is cents. For a payroll of hundreds of payouts, the network decides whether the fee line is noticeable. The USDC to BRL corridor page and the USDT to MXN corridor page show the live rate for the most common pairs we run and the networks accepted for each.
Where off-ramps fail, and what the failure looks like
The blockchain leg almost never fails. The bank leg does, for reasons that have nothing to do with stablecoins.
Name and tax-ID mismatch. Pix rejects a payout when the recipient's CPF (the Brazilian individual taxpayer ID) or CNPJ (the Brazilian company taxpayer ID) does not match the holder of the destination account. SPEI does the same with the CLABE (the 18-digit Mexican bank account number) and the beneficiary name. The funds return to the sender's balance; the fix is data, and the good providers validate before accepting the payout rather than after the bank bounces it.
Compliance hold. A first payout to a new recipient, an amount out of pattern, a recipient in a higher-risk category. The provider asks for a document, the payout waits, and the sender needs to know that it is waiting and why. Silence here is the single most common complaint about off-ramp providers.
Rail maintenance and limits. Pix has scheduled maintenance windows and per-transaction limits set by each bank; SPEI has a nightly window; ACH has cut-off times. A provider that knows the rails routes around them; one that does not leaves the payout pending until morning.
Wrong network. The sender puts USDC on a network the provider does not accept for that pair. Recovery depends on whether the provider controls the address on that network. The prevention is reading the pair list before sending, and a provider that publishes it per pair.
The failure that taught me the most was not a rejection. It was a Pix payout that succeeded, to the right CPF, on a Saturday, and the recipient did not see it until Monday, because their bank showed weekend credits with a delay in its app. The client escalated, we pulled the Pix end-to-end identifier, the receiving bank confirmed the credit had settled Saturday morning, and everyone was right and nobody was happy. We now include the Pix end-to-end ID in the payout event so the client can hand it to the recipient's bank directly. An off-ramp is judged on the last screen the recipient looks at, and we do not control that screen.
Who is licensed to pay out local currency
The off-ramp is a regulated activity on the fiat side, and the licence sits with the provider, not with the client. In Brazil the framework is Law 14.478 of December 21, 2022, which set the rules for virtual asset service providers, with the Central Bank's Resolutions 519, 520 and 521 of 2025 supplying the authorization and conduct requirements. In the United States the equivalent baseline is a money services business registration with FinCEN. Mexico, Colombia and the European Union each have their own answer, and a provider that cannot name its entity and its authorization per country is asking the client to carry that risk.
One consequence is worth knowing before the first payout. Whether an off-ramp may pay someone other than the sender, an employee or a supplier, depends on the provider's authorization and on the destination country's rules. In Brazil a provider operating as an authorized virtual asset service provider can pay validated third parties with a purpose code. Get that answer per corridor in writing, rather than discovering it at the first rejection.
When an off-ramp is not the answer
When the money never needed to be a stablecoin. A Brazilian company paying a Brazilian supplier should send Pix; converting reais to USDC and back adds two spreads and a counterparty.
When the recipient wants to hold dollars. If a contractor in Buenos Aires prefers USDT to pesos, an off-ramp destroys the value they asked for. Pay them the token; the off-ramp is their decision, later.
When the payment must be recallable. The stablecoin leg is final, and the Pix or SPEI leg is final the moment it settles. A payment sent to the wrong validated account is recovered by asking the recipient, not by a chargeback.
When the destination country has no local rail the provider operates. A SWIFT off-ramp is possible and sometimes the only option, but it inherits SWIFT's timing and fees, and the case for using a stablecoin at all becomes weaker.
What an 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, 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.
An off-ramp on our global payments API is a transaction from a custodial wallet holding USDC or USDT to a validated destination in BRL, MXN, COP, USD, EUR or GBP. Before the payout is accepted we validate the destination against the holder's tax ID, so the bank bounce described above happens at request time, with a reason, rather than after the funds have left. Every step emits a webhook event: quote accepted, funds received, compliance cleared or held with a reason, payout settled with the rail's own reference, or rejected with the bank's return code. On Pix and SPEI the recipient's credit normally lands within minutes of the blockchain confirmation, at any hour.
We only pay out on rails we operate directly with a local banking partner, which is why the country list is six and not sixty. Where there is no local rail, we say so and offer SWIFT with SWIFT's timing, rather than calling a two-day wire a stablecoin payout.
Verified on September 18, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Michael Myers on Unsplash.
How long does a stablecoin off-ramp take?
On instant rails such as Pix and SPEI, minutes from blockchain confirmation to bank credit, including compliance checks, at any hour. On ACH, one business day; on SEPA, same or next day; on SWIFT, one to three business days.
Can an off-ramp pay a third party, such as a supplier or employee?
It depends on the provider's authorization and the destination country's rules. In Brazil, a provider operating under Law 14.478/2022 and the 2025 Central Bank resolutions can pay validated third parties with a purpose code. Get the answer per corridor in writing before the first payout.
What is the difference between an off-ramp and selling stablecoins on an exchange?
An exchange sells the token for local currency into the seller's own exchange account, and withdrawal to a bank is a separate step with its own limits. An off-ramp quotes in fiat, runs compliance on the destination, and delivers straight to the recipient's bank account in one transaction, which is what a payroll or supplier flow needs.
Why did my off-ramp payout get rejected?
The most common reason is a mismatch between the recipient's tax ID and the destination account holder, followed by a compliance hold on a new recipient and a rail limit or maintenance window. A good provider returns the bank's own return code and a plain reason with the rejection.
