An off-ramp rate differs from the Google rate because Google shows a mid-market reference, delayed by about three minutes, while an off-ramp quote is a price someone will trade at. It sits on the bid side of the market, carries the provider's fee, holds for a short window, and prices USDC, which is not always exactly one US dollar.
Best for: finance and payments teams that pasted a USDC to BRL quote next to a Google search and want to know which part of the difference is fair.
The question usually arrives as a support ticket: the payout was quoted at one rate, Google said another, and the recipient got fewer reais than the screenshot suggested. Nothing in that sequence is an error. The work is to split the gap into its parts. The cost lines of a payout are covered in how stablecoin payout pricing works, so this post stays on the rate.
What rate does Google show, and how late is it?
Google shows a mid-market rate: the midpoint between the price at which dealers buy a currency and the price at which they sell it. A midpoint is a calculation, not a quote.
Google states how fresh it is. Its finance data page lists currency prices as provided by Morningstar, with a delay of 3 minutes, and adds that it makes no promise the exchange rates displayed are accurate and that you should confirm current rates before making any transactions.
So the Google figure is a good map and a bad invoice. A basis point is 0.01%.
On Lumx, the floating rate plays the same role: a real-time reference with no price lock, meant for showing an estimated amount on screen. The docs say the rate applied at execution may vary slightly, so a floating rate is the estimate and a locked rate is the price.
Why an off-ramp quote sits below the Google rate
When you sell USDC for reais, you are the one selling, so you get the bid side of the market. The dealer on the other end buys dollars below the midpoint and sells them above it, and the difference between the two is the spread. Half of it lies between you and the Google midpoint on each trade.
Three more things sit between the bid and the amount that lands in the bank account:
The provider's fee, a percentage or a flat amount, folded into the rate or shown on its own line.
Any fee your own platform adds for its customers.
The window. A provider that holds a price for 30 seconds or five minutes carries market risk for that time, and a longer hold costs more.
A Lumx locked quote returns both a base rate and a final rate, with the fee lines in between. The fee object splits the cost into a Lumx share, a partner share and a total, and the final amount is what the recipient is quoted, so the fee part of the gap is visible before anything is sent.
How much of the gap is fair, and how do you measure it?
Measure it in basis points, against a reference captured in the same minute as the quote, on the amount that lands. The formula is the reference rate minus the effective rate, divided by the reference rate, times 10,000. The full method is in how to calculate FX spread. Here is one payout split into its parts.
The numbers are illustrative, chosen low for the arithmetic, and not a Lumx quote or price. The payout is 10,000 USDC into a Brazilian bank account over Pix (Brazil's instant payment system, run by the Central Bank), with the Google reading at 5.3000 reais per dollar.
An illustrative USDC to BRL payout of 10,000 USDC, from the Google reading to the amount that lands.
Step | Rate (BRL per USDC) | BRL lost at this step | Added gap at this step (bps) |
Google reading | 5.3000 | 0 | 0 |
Wholesale midpoint in the quote's minute (timing can move either way; here it happens to hurt) | 5.2995 | 5 | 0.9 |
Bid side of the market | 5.2980 | 15 | 2.8 |
After pricing USDC at 0.9998 dollars | 5.2969 | 11 | 2.1 |
After the provider's fee (final rate) | 5.2956 | 13 | 2.5 |
Cumulative | 5.2956 | 44 | 8.3 |
The second row is timing and belongs to nobody. The third is the dealer's half spread, the fourth is the gap between USDC and the dollar, explained below, and the last is the fee shown on the quote. In this example about a third of the 8.3 bps is the fee and the rest is the market-side price of the conversion. If a provider shows only the final rate, you can compute the total gap but not tell which row it came from.
The same split applies to USDC to MXN over SPEI (Mexico's interbank transfer system). The pairs are on USDC to BRL, BRL to USDC and USDC to MXN.
On a Lumx locked quote, the docs define the base rate as the rate before the fee lines and the final rate as the rate after them. Comparing each with the reference separates the two parts: base against reference is the gap before fees, final against reference is the total. The difference between base and final on a Lumx quote is the Lumx fee plus any partner fee, and a lock fee on the 1-minute and 5-minute locks, with no FX margin built in. The table above is generic and does not map to a Lumx quote.
Why on-ramp and off-ramp rates differ from each other
The same logic explains why buying USDC and selling it back are priced differently. Going in, you pay the ask side. Going out, you receive the bid side. Each leg crosses the spread in the direction that costs you, so the two rates are never mirror images around Google's midpoint, and a round trip is the sum of both legs.
An illustrative round trip, 10,000 USDC bought with reais and sold back, against the same Google reading of 5.3000.
Leg | Direction | All-in rate (BRL per USDC) | Gap vs Google (bps) |
Buy | BRL to USDC, you pay | 5.3040 | 7.5 above |
Sell | USDC to BRL, you receive | 5.2956 | 8.3 below |
Round trip | 53,040 BRL in, 52,956 BRL back | about 16 |
Fees as a separate subject are in on-ramp and off-ramp fees explained, and the two products are defined in what an on-ramp is and what an off-ramp is.
On Lumx, each direction is its own exchange rate request, and partner fees are configured separately for on-ramp and off-ramp. A deposit converted by an autoconversion rule is different: it converts at market and takes no locked quote.
USDC is not exactly one dollar, and the quote prices USDC
Google's number is the price of a US dollar. An off-ramp sells USDC, and USDC is a stablecoin that its issuer, Circle, says is redeemable one for one with US dollars. Circle's page says Circle Mint lets large institutions such as exchanges and banks redeem USDC 1:1 for USD, that Mint is not available to individuals or small businesses, and that smaller businesses reach USDC through providers in the Circle Alliance Program. Circle describes USDC as backed 100% by cash and cash-equivalent assets.
The price at which USDC trades for dollars is set by trading, not by the redemption promise, so it can sit a little above or below one dollar, and the quote prices that. It is the fourth row of the table above, and the 2 bps there is a conceptual placeholder, not a measured trading range: 2 bps is 0.0002 dollars per coin. So when you compare reais per USDC with a reference for the dollar, a few basis points may be the stablecoin and not the provider. The reserve is covered in what USDC is.
Lumx has its own mint account at Circle and also gets USDC through its strategic partner BTG, so it does not depend on the retail route. Lumx writes an off-ramp quote in the stablecoin: the source currency is USDC or USDT and the target is the fiat currency. The same pair works for dollars. The docs list USD as a supported target for USDC on Ethereum, Polygon and Base, and for USDT on Ethereum, Polygon and Tron, and the USDC to USD page has the pair.
When the gap is a red flag
A gap is fair when you can see where it comes from. Unexplained, it becomes the ticket from the top of this post. Three patterns deserve a second look.
An indicative rate that settles worse. A provider that shows a rate and settles at another adds a cost you never agreed to, usually called slippage, and on a binding quote used inside its window it should be zero. The two kinds of quote are in indicative versus binding quotes, and the window is in how long a payment quote lasts.
A "market rate" far from the public reference in the same minute. A few basis points is timing. A wide and persistent gap on a liquid pair means the rate may already carry margin.
No itemized fees. A provider that shows only a headline rate is hiding its margin, because you cannot separate margin from fees. Compare the amount that arrives in the recipient's account, captured in the same minute for the same size, not the headline rate.
A Lumx locked rate fixes the conversion for 30 seconds, 1 minute or 5 minutes, and the transaction refers to the quote to settle at it. If the window has closed, the API rejects it with EXCHANGE_RATE_EXPIRED (422), and a quote already used by another transaction returns EXCHANGE_RATE_ALREADY_USED (422). The answer to both is a new quote. Only the 30-second lock has no fee, and the longer ones include a fee that covers volatility.
Which reference rate to use for which job
Pick one reference per job and write it down. Google suits a sanity check and a rough estimate. The quote's own base rate suits the cost analysis of a single payout, because it is tied to one quote and one minute. A central bank fix suits a contract or accounting policy that names it, and is no use for pricing a payment sent at 15:00. The Brazilian fix is PTAX, which has its own post in PTAX versus a live quote.
I recommend that a finance team stores the quote's base rate, final rate and fee lines next to every payout, and never a screenshot of Google. A screenshot cannot be reproduced and a quote can, so when a recipient or an auditor asks why 10,000 USDC became a particular number of reais, the stored quote answers in one line.
When chasing the Google rate is the wrong goal
A small payout. On a few hundred dollars a flat fee outweighs the spread, so the effort belongs on the fee line, and shaving a basis point off the rate saves cents.
A very large amount. Beyond the depth of the cheapest liquidity, the average fill moves with size, and a price negotiated for the amount is the right question.
In both cases the goal is a known amount before the payout leaves, not a rate that matches a search result. A Lumx locked quote states the final amount before the payout is submitted, which is the number to hold the provider to.
What reading a USDC to BRL quote 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 payout starts with a quote. The company asks for a locked rate with USDC as the source, BRL as the target and the rail set to Pix, passing either the USDC to send or the reais to deliver. The response carries baseTargetAmount and baseExchangeRate, the fee lines for Lumx, for any partner fee and in total, then finalTargetAmount, finalExchangeRate and expiresAt. A platform that adds its own fee passes a partner fee on the quote request, so it can show finalTargetAmount before anything moves.
Submitting the off-ramp with the quote's id converts at the final rate, with webhooks on each status change through to SUCCESS. Pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. The end-to-end flow is on the global payments page. To see it on your own numbers, request a locked quote in the sandbox, open Google in the same minute and compare the two.
Methodology and sources
We read the Lumx documentation on November 1, 2026: Exchange rates, Partner fees, Transactions, the Get an exchange rate reference, Coverage and Errors. The delay and the disclaimer on currency prices come from Google's finance data page, and the redemption terms and reserve description from circle.com/usdc and circle.com/transparency, all read on November 1, 2026. Every number in the tables is illustrative, chosen for the arithmetic: none is a Lumx price, quote or forecast.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Jan Folwarczny on Unsplash.
Why does my off-ramp rate differ from Google?
Google shows a mid-market reference with a delay of about three minutes, while an off-ramp quote is a price you can execute. The quote sits on the bid side of the market, includes the provider's fee, holds for a window and prices USDC and not the dollar itself. On Lumx, a locked quote shows the rate before fees, the rate after fees and the fee lines, so each part of the gap can be read on the quote.
Is the Google exchange rate the real rate?
It is a real reference and not a price you can trade at. It is the midpoint between wholesale buy and sell prices, and Google itself says you should confirm current rates before transacting. On Lumx, the floating rate plays that reference role as an unlocked estimate, and a locked rate is the price that settles.
Can I get the Google rate when I off-ramp stablecoins?
Not as an executed price, because someone has to carry the spread and the fee, plus the risk of holding the price while you confirm. What you can do is compare the amount that arrives in the bank account, captured in the same minute as the reference. On Lumx, a locked quote returns the final target amount and the expiry, so the comparison is made before the payout is submitted.
Is USDC exactly one US dollar?
Circle says USDC is redeemable 1:1 for US dollars, but offers that redemption directly to institutions through Circle Mint, and everyone else goes through providers. The market price is set by trading, so it can sit slightly above or below one dollar, and a quote prices the stablecoin. On Lumx, the off-ramp source currency is USDC or USDT, and USD is a supported target alongside BRL, MXN, EUR and GBP.
How do I compare an off-ramp quote with the market rate?
Capture both in the same minute, then compute the reference minus the effective rate, divided by the reference, times 10,000, on the delivered amount. On Lumx, compare the base exchange rate in the locked quote with the reference, then the final exchange rate with the base rate, which shows how much of the gap the fee lines account for.
