An OTC desk in Brazil is a counterparty that quotes you one price for a block of reais against USDC or USDT, then settles that trade directly with you, usually after a chat or a request for quote. A stablecoin API does the same conversion programmatically, one transaction at a time. Ticket size, how often you trade and how much you need automated decide which one fits.
This guide is for a business in Brazil, or paying into or out of Brazil, that moves BRL and dollar stablecoins. Pricing a very large single block is a separate topic, covered in large BRL to USDC conversions. Here the question is the channel.
What is an OTC desk in Brazil?
OTC means over the counter: the trade is agreed between two parties instead of being matched on a public order book. A desk is the team that makes those prices. In Brazil it typically sits inside a bank, a broker, an exchange or a virtual asset service provider, and it quotes reais against a dollar stablecoin for clients who want a price on a size that would move a screen.
The model is old and it works. A treasurer who needs to convert a large amount once a month does not want to watch a book fill. They want one person to name a number, hold it for a minute and take the risk of the move while it stands.
What the desk is, legally, matters more than what it calls itself. Under Law 14.478/2022 and the Central Bank of Brazil (BCB) resolutions that followed, virtual asset services must be provided by an authorized company, and the foreign exchange market has its own rules. When you pick a desk, ask which entity trades with you and under which authorization it does so. Brazil's stablecoin rules in 2026 lays out the framework.
How does an OTC desk quote and settle a trade?
The sequence is similar across desks, and the differences are in the details you should ask about. Onboarding is KYB (know your business, the verification of a company and its owners). Funding is usually a Pix (Brazil's instant payment system, run by the Central Bank) or a TED (Brazil's same-day bank transfer, business hours only).
Onboarding. The desk runs KYB on your company, often with paper documents and a relationship manager. Approval can take days.
Request for quote. You send a size and a direction, by chat, email or a desk portal. The desk answers with a firm price, valid for a short window.
Acceptance. You accept inside the window. A good desk states in writing that it cannot reprice after that.
Funding. You send the reais from your corporate bank account, usually by Pix or TED, to an account the desk names.
Delivery. The desk sends USDC or USDT to the blockchain address you gave it, or credits an account it holds for you.
Confirmation. You get a trade confirmation, and your accountant gets the documents for the books.
Typical OTC desk trade, step by step, and what to ask at each step
Step | What happens | Question to ask |
Quote | Firm price for the whole block | How long does it hold, and can it change after I accept? |
Funding | Reais move to the desk's bank account | Which bank, and which entity owns the account? |
Delivery | Stablecoin lands at your address | On which network, and what happens if the address is wrong? |
Records | Confirmation and invoice | Which document supports my accounting and my bank? |
Nothing in this flow is automated by default. That is the point of a desk, and also its limit.
What does a stablecoin API do differently?
A stablecoin API exposes the same conversion as calls your software makes. It does not replace price discovery on a very large block, but it changes everything around the price.
Quotes are programmatic. Your system asks for a rate for an exact amount and gets a base rate, a final rate and a final amount, so the fee is visible in the numbers. Accounts are named: the payer sees your customer's name on the receiving details, not a pooled account. Every conversion is its own transaction with its own status, and your system hears about each status change through webhooks instead of waiting for a confirmation email. The ideas behind this are in what a stablecoin API is and in the comparison of indicative and binding quotes.
The trade-off is that an API prices a standard flow with a standard engine. There is no one to call and negotiate with, and your per-transaction ceiling is a hard number.
OTC desk and stablecoin API compared
Side-by-side comparison for a business moving BRL and dollar stablecoins
Dimension | OTC desk | Stablecoin API |
Who prices | A trader, per block | A pricing engine, per request |
Quote | Negotiated, firm for a short window | Requested for an exact amount, floating or locked |
Best ticket | Rare and very large | Anything from routine to large, within your limits |
Frequency | A few trades a month | Many trades, every day |
Automation | Manual by default | Built for it: requests, statuses, webhooks |
Records per trade | A confirmation and an invoice | A transaction object with status history |
Accounts | A deposit account the desk names | Named accounts in your customer's name |
Onboarding | Relationship, documents, days | KYB through the same API |
Cost visibility | Spread inside the quote | Base rate against final rate in the response |
Neither column wins in the abstract. Each wins for a given payment pattern, and the next section sorts those patterns.
When does each one fit?
Start from the pattern, not the channel.
Choose the desk when the tickets are rare and very large, when a human relationship adds value, or when you want a negotiated price on a block that would strain any standard engine. A company converting one large amount a quarter for an acquisition or a dividend is the textbook case.
Choose the API when payments are frequent, when they come from a product instead of a treasurer, or when each payment has to reach a specific beneficiary. A marketplace paying sellers in dollars, a platform collecting reais from customers and holding USDC, a payroll provider: these cannot wait for a chat window. The reasoning for the treasury side is in BRL to USDC for corporate treasury.
Choose both when you have a steady flow and an occasional block. Many companies run the daily flow through an API and keep a desk contact for the day a transfer is too large for the standard path. Lumx works that way too: it has OTC for operations far above what fits the API.
Our recommendation: if you can describe the payment as a recurring event, start with the API and add a desk only when a ticket outgrows it. Starting with a desk and automating later means rebuilding the process around the trades you already made.
Which channel fits which payment pattern
Payment pattern | Usual fit |
One very large block, a few times a year | OTC desk |
Daily collections converted to USDC | API |
Payouts to many beneficiaries | API |
Steady flow plus a rare large block | API for the flow, desk for the block |
A product that needs status per payment | API |
Counterparty and compliance differences
With a desk you take a counterparty: you send reais to an account and wait for the stablecoin. Before the first trade, check who owns the bank account you pay into, which entity sends the stablecoin and whether it is authorized for the activity. If the trade is large, your own bank will ask what the money is for, and a desk that cannot give you documents makes that conversation harder.
With an API, the question is the same but the answers are structured. Every on-ramp and off-ramp on Lumx carries a purpose field, the end use of the funds, such as TRADE_TRANSACTIONS for a supplier invoice. Banking partners use it for screening and reporting, and a value that does not match the real use can hold the transaction or trigger an RFI (request for information, a compliance hold that asks for a document before a transaction clears).
Lumx's position is that converting BRL to USDC falls under BCB Resolution 521 as an operation of the foreign exchange market that is not itself foreign exchange, and that no IOF (the Brazilian tax on financial operations) applies, because a stablecoin is not foreign currency. That is Lumx's reading, not a quotation of the resolution. Ask any provider, desk or API, to describe its position in writing.
What happens to a payment on each side
A desk trade is a single event. You hold a quote, you pay, you receive. If something is wrong, you call.
An API payment is a lifecycle. A BRL to stablecoin on-ramp on Lumx moves through awaiting funds, transferring fiat, trading, transferring stablecoin and success, and each step fires a webhook. A rate can be floating or locked for 30 seconds, 1 minute or 5 minutes. The 30-second lock has no fee, and a locked on-ramp expires with its quote. If a Pix lands after the on-ramp expired, Lumx does not process it and refunds the sender on the same rail. Floating Pix on-ramps stay open for a day.
That behavior is useful when you build around it. When you do not, a late Pix means a new quote and a lost afternoon. A treasurer whose bank needs three approvals should use the floating rate, and a developer should expect an expired webhook as a normal outcome.
I think the most common mistake is choosing the channel by the headline price. A desk quote and an API quote look comparable on a screen, but the desk price assumes the size you named and the API price assumes the process you built. The comparison that holds up is the USDC you receive for the same reais, at the size you will really send, including any step your team does by hand.
When each one is the wrong tool
An OTC desk is the wrong tool for a flow that repeats daily. Every trade needs a person on both sides, and your reconciliation then depends on emails and spreadsheets. The cost does not show in the spread, it shows in the finance team's week.
An API is the wrong tool when the ticket is far above your per-transaction ceiling and you want a negotiated price on the whole block. Limits are published per verification tier, and a business customer on enhanced KYB has a daily and monthly ceiling that starts at US$100,000 and is set to fit the financial capacity shown in its documents. Splitting a block to fit under a ceiling is not a workaround, because daily and monthly limits still count every piece. Ask for a higher limit or move the block to a desk.
Neither tool is a hedge. A quote fixes one price for a short window, and forwards or options come from your bank or an FX broker.
What a BRL and USDC flow 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.
For BRL, each leg has its own operator. A banking partner issues the BRL account, in your customer's name. Lumx's Brazilian entity, Lumx SPSAV Ltda, runs the stablecoin leg while it operates under the Article 88 transition of Resolution 520/2025, and the wallets are held in custody by BitGo. A Brazilian company that also wants a USD account contracts both Lumx entities: the SPSAV for BRL and stablecoin, and Lumx US OP LLC for USD.
BRL runs on Pix only. TED and boleto (a Brazilian bank slip payable at any bank or app) are not live. The platform requests a rate for an amount, creates the on-ramp with the rate's id and a purpose, and shows the payer a Pix payment code for that amount. The stablecoin credits to a custodial wallet within about five minutes of the Pix, and webhooks report each status. The sequence is in on-ramping BRL, MXN and COP, and the payout direction is in what a stablecoin off-ramp is. For a business that pays out, the choice between a desk, an exchange and an API is also in the types of crypto off-ramps.
Live rates are on the BRL to USDC converter and the USDC to BRL page. How the legs fit by country is in global payments.
For limits, a KYB customer starts with a US$100,000 daily and monthly ceiling, and the customer's read endpoint returns what is used and what remains. Lumx also has OTC for operations well beyond what fits inside the API, so the same provider can cover both patterns.
Methodology and sources
Statements about Lumx come from the public documentation read on November 17, 2026: Exchange Rates, Transactions, Accounts, Transaction Limits, Webhooks and Payment rail cut-off times. The description of how an OTC desk works is general market practice, not a claim about any one desk. BCB Resolutions 520 and 521 are cited by number and year without a link, because the BCB normative database did not return readable text on the date of writing.
Verified on November 17, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Miha Meglic on Unsplash.
What is an OTC desk in Brazil?
An OTC desk in Brazil is a counterparty that gives you a negotiated price for a block of reais against USDC or USDT and settles that trade with you directly. It usually sits inside a bank, a broker, an exchange or a virtual asset service provider. Check which entity trades with you and under which authorization.
When should a business use an OTC desk instead of a stablecoin API?
Use a desk when tickets are rare and very large, or when a negotiated price on a whole block matters more than automation. Use an API when payments repeat, come from a product, or need a status per transaction. Many businesses use the API for the flow and a desk for the occasional block.
Does a stablecoin API replace an OTC desk?
Not for every ticket. An API prices routine and large flows within your limits, with quotes, named accounts and webhooks. A very large block above your ceiling may still be better negotiated with a desk. On Lumx, OTC exists for operations well beyond what fits inside the API.
How does an OTC trade settle compared with an API payment?
An OTC trade settles in one pass: you accept the quote, send the reais to the account the desk names and receive the stablecoin. An API payment moves through statuses and sends a webhook at each one. On Lumx, a BRL on-ramp pays by Pix and credits the stablecoin to a custodial wallet within about five minutes.
What should I ask a provider before moving BRL and USDC?
Ask which entity trades with you, who owns each account in the flow, how long a quote holds and whether it can change after you accept. Ask what happens when funds arrive late or are held for review, and which documents you receive for your records. A provider that answers in writing is easier to audit.





