A large BRL to USDC conversion is one big enough that its price depends on the BRL liquidity behind the quote, so it is quoted and tested differently from a screen rate. Ask for a lockable price at your real size, learn where the reais are delivered, and measure depth with a ladder of quotes first.
The treasury side, meaning why a company holds dollars and where they sit afterwards, is in the guide to BRL to USDC for treasury.
What makes a conversion large
There is no universal threshold. A ticket that moves the price at one provider is noise at another. Any one of three things makes a ticket large for you.
Depth is the first. A ticket is large when the quote at full size is worse than the quote at a small size by more than you will pay. That gap is slippage, and it belongs to the liquidity behind the quote, not to the provider's marketing.
Limits are the second. Every account has a ceiling per transaction, per day and per month, and a ticket is large once it nears the first.
The payer's process is the third. A Pix (Brazil's instant payment system, run by the Central Bank) for a seven-figure amount often needs more than one approver at the sending bank, and approvals take minutes. If the quote expires first, the ticket is large for operational reasons.
Live rates sit on the BRL to USDC converter and the USDC to BRL page.
OTC quote or screen quote: which fits a large ticket?
A screen quote is the rate a provider returns through its API when you ask, from the same pricing logic at any size within your limits. An OTC quote (over the counter, meaning bilateral) is a price agreed for a specific block, usually with a desk that carries the market risk while the price stands.
Screen quote against negotiated OTC quote for a large BRL conversion
Question | Screen quote | Negotiated OTC quote |
Who sets the price | The provider's pricing engine | A desk, for your specific block |
How size is handled | Same logic at every size, up to your limits | Priced for the whole amount at once |
How long it holds | A lock of seconds to minutes, or no lock | Often a very short window, because the desk carries the move |
Best fit | Automated flows, repeatable sizes | Rare, very large, one-off blocks |
Ask two questions in writing whichever you take. Once you accept inside the window, can the provider still reject or reprice? And is the fee inside the rate or beside it? Compare quotes by the USDC that lands for the same reais.
Lumx also has OTC for operations far larger than a US$ 200,000 ticket. A ticket of that size fits inside the API, and it falls under enhanced verification. On the API side the quote is the locked rate from the exchange-rate endpoint, requested for the exact amount of the ticket. You can state the amount in BRL or the USDC you need, and the response returns the base rate, the final rate and the final amount, so the fee shows in the numbers.
Where onshore BRL liquidity actually sits
A conversion has two legs, and size hits each separately: the reais arriving and the dollar token leaving. A provider can be deep on one and thin on the other.
Onshore means the BRL leg settles inside Brazil. The reais move by Pix between Brazilian bank accounts, and the institution on the other side is authorized to operate in the foreign exchange market under Law 14.286 of December 29, 2021, which restricts these operations to institutions authorized by the Central Bank of Brazil (BCB). An onshore position gives you reais that can reach a supplier's bank account on a Monday morning.
The USDC leg is either minted directly through the issuer's channel or bought from a market maker, and a large buy behaves differently in each case. The token is explained in what USDC is, and the whole move from reais to a token in the on-ramp explainer.
We source conversion liquidity from our own balance and from institutional counterparties only, BTG Pactual among them, and we mint USDC directly through BTG, our strategic partner and investor. We do not take liquidity from just anyone, because delivery on a large ticket depends on who stands behind it.
How a lock window becomes basis points
A quote is a promise with an expiry. The longer the window, the more the market can move while you hold it, and someone carries that move. On a large ticket it is a budget line.
The arithmetic below is illustrative, not a published provider figure and not a Lumx price. It assumes a deliberately low 0.5% daily volatility in BRL and scales by the square root of time, the usual rough rule for a one-standard-deviation move. Change the assumption and the table scales linearly.
Illustrative rate drift inside a lock window, assuming 0.5% daily volatility
Lock window | Typical drift | On R$1,000,000 |
30 seconds | about 0.9 basis points | about R$93 |
1 minute | about 1.3 basis points | about R$132 |
5 minutes | about 2.9 basis points | about R$295 |
Next to a spread of tens of basis points, none of these is large: the window is a second-order cost and depth is the first-order one.
What the window does decide is whether your process can use it. On Lumx the lock and the payment window are one clock: with a locked rate the payment expires when the quote does, and a Pix that arrives afterwards is refunded to the sender on the same rail. A floating-rate Pix on-ramp stays open for a day, at whatever price the market gives at execution. The choice is between a price you lock and must pay inside the window, and a price you do not know until the money lands. A treasury whose bank needs three approvals should read that twice. The mirror case is in paying an exact local amount.
The 30-second lock carries no fee, the 1-minute and 5-minute locks include a volatility fee, and the floating rate has neither fee nor lock.
Test depth before you commit
Slippage is the one number a rate card cannot give you. You measure it with a quote ladder: the same pair quoted at rising sizes, with the effective rate recorded at each step.
Take the real ticket size and quote it at 1%, 5%, 10%, 25%, 50% and 100%. At each step record the BRL you would send, the USDC you would receive, and the effective rate from dividing the two. The distance from the smallest step, in basis points, is the cost of size.
Quote ladder template, one row per step, repeated at each time of day you test
Step | BRL sent | USDC received | Effective rate | Distance from step 1 (bps) | Quote returned in (s) | Error or hold |
1% | 0 | |||||
5% | ||||||
10% | ||||||
25% | ||||||
50% | ||||||
100% |
Run it at least three times at different hours, because a ladder describes one moment. Write the pass rule first, for instance that the 100% step must sit inside a tolerance you set in basis points of step 1. The same ladder works for MXN and COP with the rail changed.
I would run the ladder before the first large ticket and again whenever the ticket size doubles, once on a weekday afternoon and once on a Sunday night, because Pix is open at both times and the quote gives you a price, not whether the depth behind it changes. I would also decide in advance what result makes me cut the ticket in two, since a number chosen afterwards always seems to support the plan already in motion.
On Lumx the ladder costs nothing to run: a floating rate is free, and so is a 30-second lock, so every step can be quoted from the same endpoint. Each response carries the base rate, the final rate and the final amount, which fills the effective-rate column. A step the system cannot fill returns a 422 with NO_LIQUIDITY_PROVIDER, and an amount above your per-transaction limit returns TRANSACTION_LIMIT_EXCEEDED.
Limits, Pix and review on a large ticket
Three layers sit between a large quote and a credited wallet, and each belongs to a different party.
The first is the platform limit. Limits are in US dollars and attach to the customer by verification tier. On-ramp, off-ramp and transfer each have their own set, so a large on-ramp does not use up off-ramp headroom. The published defaults for a business customer apply to customers from any country.
Default limits for a business customer, in US dollars
Limit | KYB standard | KYB enhanced |
Per transaction | 50,000 | 50,000 and above |
Daily | 100,000 | 100,000 and above |
Monthly | 100,000 | 100,000 and above |
KYB (know your business, the verification of a company and its owners) enhanced is open-ended on purpose: the limit set fits the financial capacity shown in the submitted documents. To raise a limit, the customer requests it for one transaction type with a supporting document, such as a bank statement, financial statements or a tax return. The review targets one business day. Cut-offs per rail are in the guide to the Pix limit for a company.
The second layer is review. Transfers above standard thresholds can trigger extra risk review, typically adding up to two business hours. A transaction flagged by monitoring is held as an RFI (request for information, a compliance hold that asks for a document before a transaction clears), and without an answer in 24 hours it may be refunded to the sender. Every on-ramp also carries a purpose field, and a value that matches the real use of the funds, such as trade transactions for a supplier invoice, avoids the mismatch that turns a clean ticket into a question.
The third is the sending bank. The limit on a corporate Pix is agreed between your company and its bank, and no figure appears here because none was read from a primary source today. Ask the bank for it, and for what raising it takes, before the ticket exists.
On Lumx the first two layers are visible before you send. Reading the customer with transaction limits included returns the ceiling and the used and remaining amounts for the day and the month, and webhooks report each status. What a conversion costs, layer by layer, is in how payout pricing works.
When a large ticket is the wrong shape
Splitting a ticket to sit under a per-transaction ceiling is the wrong move. Daily and monthly limits still count every piece, a run of near-limit tickets is what monitoring reads, and a limit request meets the same need honestly. If the ceiling is the problem, ask for the ceiling.
A conversion is the wrong place to look for a hedge. A locked quote fixes one price for seconds or minutes, and Lumx offers no forward, NDF or option, so hedging instruments come from your bank or FX broker. A company that collects and pays in reais has a simpler route in the natural hedge with Pix.
A standing autoconversion rule is the wrong tool when price certainty matters more than automation. It converts every matching deposit at market and takes no locked quote, which suits recurring collection and not a single block you want priced in advance. For that block, use one on-ramp with a locked rate.
A lock is the wrong choice when the payer cannot pay inside the window. If approvals take longer than five minutes, the floating rate with a day to pay is the honest option, price risk included.
What a large BRL ticket 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.
Once KYB approves the customer, the BRL account activates right away, so there is no provisioning wait to plan around. The platform requests a locked rate for the amount, in BRL or in USDC, and creates the on-ramp with the rate's id and a purpose. The response carries a Pix payment code for that exact amount. The payer sends the Pix inside the lock window, and the on-ramp moves from awaiting funds to success, with a webhook at each status. USDC or USDT then credits to a custodial wallet in the customer's name.
A deposit that lands after the on-ramp expired returns to the sender, and a held transaction stays held until compliance gets its answer, so whoever can answer should know the ticket is coming.
Live pairs and rails are on the coverage page, and how the legs fit per country is in global payments. The BRL, MXN and COP on-ramp is walked through in on-ramping BRL, MXN and COP, the payout side in what a stablecoin off-ramp is, and the path between two currencies in what a stablecoin corridor is.
Methodology and sources
Statements about what Lumx does come from the public documentation read on November 1, 2026: Exchange Rates, Transactions, Transaction Limits, Limit Increase Requests, Payment rail cut-off times, Request for Information, Accounts, Autoconversion Rules and Errors.
Law 14.286 of December 29, 2021 is cited by name and date without a link, because planalto.gov.br did not respond on the date of writing. The drift table is our own illustrative arithmetic under the stated 0.5% assumption.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
What counts as a large BRL to USDC conversion?
A conversion is large when it changes the price you are quoted, nears your per-transaction limit, or needs bank approvals that outlast the quote. There is no single dollar figure, because depth varies by provider and by hour. On Lumx, a business customer on standard verification has a published per-transaction limit of 50,000 US dollars, a ticket of 200,000 fits inside the API under enhanced verification, and a quote ladder at your real size shows the depth.
Is an OTC quote better than a standard quote for a large BRL ticket?
Not by default. An OTC quote prices the whole block at once and suits rare, very large tickets, while a screen quote suits automated, repeatable flows. Compare them by the USDC received for the same reais, and ask whether the price can be repriced after you accept. On Lumx the quote is a locked rate requested for the exact amount, with a 30-second lock at no fee.
Where does the BRL liquidity for a large conversion come from?
Onshore: the reais move by Pix between Brazilian bank accounts, and the counterparty is authorized for foreign exchange in Brazil. The USDC leg comes from direct minting or a market maker, and the two legs can differ in depth. Lumx sources liquidity from its own balance and from institutional counterparties only, BTG Pactual among them, and mints USDC directly through BTG.
Can I lock the rate on a large Pix payment?
Yes, for 30 seconds, 1 minute or 5 minutes, and the Pix has to arrive inside that window or it is refunded to the sender. Match the window to how fast your bank approves payments. On Lumx the 30-second lock has no fee, the longer locks carry a fee for volatility risk, and a floating-rate on-ramp keeps the payment open for one day without a locked price.
How do I raise the limit before a large conversion?
Complete enhanced KYB, then submit a limit request for the transaction type with a bank statement, financial statements or a tax return that supports the amount. The review targets one business day. On Lumx the request goes through the dashboard or the API, and the new limits apply from the moment they are approved.
