A crypto payment is one where a crypto asset passes from payer to payee, who keeps it and carries its price. A blockchain payment uses a blockchain only to move the value, usually as a dollar stablecoin: the payer can start with dollars and the payee can end with reais in a bank account.
Companies that ask for "crypto payments" usually mean the second case: an invoice settled abroad sooner, with no treasury left holding a coin that moves in price. This post walks one supplier payment from dollars to reais and says who needs an authorization in Brazil. The basics of the stablecoin are in what a stablecoin is, and the technology under the rail is in how blockchain works.
What does each side of the payment end up holding?
The difference is what the payee holds when the payment ends. In a crypto payment it is the asset, and the payee owns whatever the asset does next. In a blockchain payment the stablecoin is a vehicle that exists for part of the route, and the payee can end up with reais in a bank account.
Crypto payment and blockchain payment compared on what each party sends, receives and carries.
Crypto payment | Blockchain payment | |
What the payer sends | A crypto asset such as Bitcoin, Ether or a stablecoin | Bank money, or a stablecoin from a balance the payer already holds |
What the payee receives | The same asset | Local currency in a bank account, or a stablecoin if the payee asks for one |
Who carries price risk | The payee, from receipt until the asset is sold | A small stablecoin risk, not zero, that grows with how long a balance sits; the FX rate is fixed only if a locked quote is used |
Wallet on the payee side | Required | Not required when a provider runs the stablecoin leg |
Typical use | Paying a counterparty that wants the asset | Cross-border supplier invoices, payroll, marketplace payouts |
The two overlap in one case. A company that pays another in USDC, where the receiver keeps it, has made both a crypto payment (the asset changed hands) and a blockchain payment (it settled on a blockchain). It needs a wallet on both sides, which a provider-run blockchain payment does not. The wallet question has its own post.
Why the two terms get confused
Early crypto payments were Bitcoin checkout buttons, so the asset and the payment became one idea. Business volume then moved to stablecoins and to APIs that hide the network behind an account, a payout and a status, but the "crypto" label stuck. The useful test is what the payer sends, what the payee receives, and who is exposed to the asset in between.
A BRL supplier payment, step by step
A company pays a supplier in Brazil. It funds the payment in US dollars, the money crosses on a blockchain as USDC, and the supplier receives reais over Pix (Brazil's instant payment system, run by the Central Bank). The supplier never holds a stablecoin.
One supplier payment from dollars to reais, with the party that holds the money at each step. Deposit timings are processing targets from the Lumx payment rail documentation, read on November 1, 2026, and the documentation calls them targets, not guarantees.
Step | What happens | Who holds the money | Time |
1. Fund | The payer sends USD by ACH or FEDWIRE to its own USD account, a named account in the payer's name | The banking partner that issued the account to the payer | ACH: 1 to 2 business days. FEDWIRE: same business day, typically within hours. A new USD account can take up to 1 business day to activate |
2. Convert | The deposit becomes USDC in the payer's wallet, at the market rate | The payer's custodial wallet | Reported by webhook |
3. Quote | The payer asks for a USDC to BRL quote, optionally with the rate locked | Still the payer's wallet | A 30-second lock has no fee; 1 and 5 minutes carry a fee |
4. Settle | The USDC is sold for reais and sent to the supplier's registered bank details | The wallet is debited, then the reais move | Reported by webhook at each status |
5. Receive | Reais are credited by Pix | The supplier's bank | Pix runs 24/7/365 with no cut-off |
The slow step is the dollar leg, which runs on a bank's calendar, against the 1 to 5 business days the documentation gives for a SWIFT wire in USD. A payer who already holds USDC skips steps 1 and 2 and can pay on a Sunday. Step 2 always runs at the market rate, and only the USDC to BRL transaction in step 4 can use a locked rate. Step 4 is the off-ramp, covered in what a stablecoin off-ramp is. The BRL to USDC page covers the reverse direction and the USDC to BRL page the payout.
On Lumx the payer is a customer that has completed KYB (know your business, the verification of a company and its owners). A banking partner issues its USD account, an autoconversion rule turns each deposit into USDC, and an off-ramp to a destination registered with the relationship SUPPLIER sells the USDC for BRL. The off-ramp moves through TRANSFERRING_STABLECOIN, TRADING and TRANSFERRING_FIAT to SUCCESS, and a webhook fires at each change. The docs cut-offs (ACH 2:00 PM ET, FEDWIRE 3:00 PM ET) cover requests Lumx processes, not when a deposit lands, and US bank holidays follow the Federal Reserve calendar. A webhook marks every status. As of November 2026, the Pix payout reaches the supplier with the paying company's name, not Lumx.
Price risk and accounting are different problems
Crypto payments carry price risk because the payee holds the asset after the payment. A blockchain payment shrinks it without removing it. A dollar stablecoin is designed to hold one dollar and can still trade off that price, and the risk grows with how long a balance sits in a wallet. Holding it also exposes you to the issuer, who has to back each coin with reserves, and to the custodian of the wallet; see are stablecoin payments safe.
Accounting follows the same split: paying in an asset is usually a disposal at the price on the day, while a bank-to-bank blockchain payment shows as cash out, cash in and a conversion. Ask your accountant; for Bitcoin see stablecoins vs Bitcoin for business payments.
On Lumx the USDC to BRL transaction can use a locked quote of 30 seconds, 1 minute or 5 minutes, which covers the quote window. Cover for a longer exposure is a treasury decision with the company's own FX counterparty.
Which costs less, and what about taxes?
Neither label sets the cost. The conversions do, plus the fee on a 1 or 5 minute lock and the provider's own fees. A crypto payment that the payee keeps as an asset skips the second conversion and passes the price risk on. So compare quotes by the reais that land with the supplier. Lumx pricing is a monthly platform fee plus usage-based per-transaction fees, and nothing is taken from the Pix amount that arrives; only the supplier's bank can charge it.
On taxes, a conversion between BRL and USDC is regulated by Resolution BCB 521 of November 10, 2025. It is an operation of the exchange market, but it is not foreign exchange, and no IOF (Imposto sobre Operações de Crédito, Câmbio e Seguro, the federal tax on credit, foreign exchange and insurance operations) applies to it, because a stablecoin is not foreign currency. IOF still follows Decree 6.306 of December 14, 2007 for real foreign exchange operations, such as a dollar wire handled by a bank. Ask the accountant about the rest.
I recommend writing the payment policy around what the payee holds when the payment ends, not around whether a blockchain appears somewhere in the route. If the payer funded in dollars and the supplier ends with reais, I would treat it as an FX payment that happens to settle on a blockchain, and send it through the same approval and reconciliation steps as a wire. If anyone in the chain ends up holding a volatile token, I would want a separate policy for that, with its own limits and its own owner.
Who needs an authorization in Brazil
The law regulates the company that handles the asset, not the asset. A foreign exchange layer sits on top and decides how money may cross the border.
Law 14.478 of December 21, 2022 allows virtual asset services only from entities authorized by a federal body, and the Central Bank of Brazil (BCB) is the regulator. Article 3 puts a dollar stablecoin inside the definition of a virtual asset. Article 5 defines the provider as an entity that performs, for third parties, at least one of five services, among them exchange between virtual assets and currency. The company type is a PSAV (Prestadora de Serviços de Ativos Virtuais), the local form of a VASP (virtual asset service provider, the FATF term). Companies already operating had until October 30, 2026 to file under the transition regime of Resolution BCB 520 of November 10, 2025. The authorization is in the PSAV post.
Paying a supplier abroad also touches foreign exchange. Law 14.286 of December 29, 2021, Article 3, allows exchange operations only through institutions the BCB has authorized for that market, and turning dollars into reais for a supplier is one. From November 6, 2026, banks and payment institutions may not serve virtual asset providers the BCB has not authorized. Article numbers, resolution dates and the May 31, 2027 adjustment deadline for payment institutions are in Brazil's stablecoin rules for 2026.
The company paying the supplier is, as we read Article 5, the provider's client and not a provider, because it runs no service for third parties. The exception matters: a company that lets its own users hold or convert virtual assets may be inside Article 5, and that is a question for counsel before launch. For a company paying its own suppliers, the compliance question moves to the provider: which entity in the chain holds the authorization or is in transition, and how it identifies the payer and the payee.
Lumx applied for the SPSAV (Sociedade Prestadora de Serviços de Ativos Virtuais, the company type that holds a PSAV authorization) and operates under the Article 88 transition regime. It is not a bank, and it does not describe itself as one. KYB and KYC (know your customer, the verification of an individual) are built into onboarding, and Lumx screens wallets and transactions with Chainalysis and verifies individuals with Sumsub. The general idea of a provider is in what a VASP is.
When is a blockchain payment the wrong tool?
A blockchain payment adds a conversion at each end, and the route has to earn that back. A payment inside Brazil gains nothing from it, because Pix already settles instantly. A transfer on a blockchain is also final, so it gives no card-style chargeback. The cases that earn it back are cross-border flows, weekend settlement and bank routes with several intermediaries, called stablecoin corridors. If the counterparty wants the asset itself, it is a crypto payment and the question becomes who holds the keys.
What this looks like on Lumx for a Pix supplier payment
The supplier example above is the common shape of a Lumx flow: bank money in, a stablecoin in the middle, bank money out. 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 this payment, the BRL leg runs over Pix, and the example uses USDC, which runs on Ethereum, Polygon and Base for BRL. Each customer gets a wallet on each supported blockchain when it is created, enabled once the customer is approved, and the wallet keeps its balance between payments, so a payer can fund once and pay several suppliers from it. Every payout debits the customer's own wallet toward a destination registered under that customer.
A request over the customer's transaction limit is rejected with the TRANSACTION_LIMIT_EXCEEDED code, and a transaction flagged by monitoring is held as an RFI (request for information, a compliance hold that asks for a document before it clears). The global payments page describes the product, and the coverage page lists the rails and countries.
Methodology and sources
Product behavior was read in the Lumx documentation on November 1, 2026: the coverage, wallets, transactions, destinations, accounts, exchange rates, transaction limits, nested payments and payment rail cut-off pages. The Brazilian norms are cited by number and date, each with a link to the official text. The dates come from Lumx's own regulation posts, which checked them against the Diário Oficial text on September 25, 2026. The official sites did not serve the full text to the checking tool on November 1, 2026, so read the article text there before relying on a specific provision.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Teng Yuhong on Unsplash.
What is the difference between blockchain payments and crypto payments?
A crypto payment hands the payee a crypto asset, and the payee takes its price risk. A blockchain payment uses a blockchain as the settlement rail, usually with a dollar stablecoin, and often starts and ends in a bank account. The payer can send dollars and the payee can receive reais, so neither has to hold a volatile asset. On Lumx, the payer funds a USD account and a Brazilian supplier is paid in reais over Pix.
How long does a blockchain payment to a supplier in Brazil take?
It depends on the dollar leg, because Pix runs 24/7/365. The Lumx documentation gives ACH 1 to 2 business days and FEDWIRE the same business day as processing targets, not guarantees. A payer that already holds USDC skips that leg. On Lumx, a stablecoin balance can be paid out to Pix at any hour, with a webhook at each status.
Who needs an authorization to run a blockchain payment in Brazil?
The provider that handles the asset for clients. Law 14.478/2022 requires virtual asset services to be provided by entities authorized by a federal body, and the Central Bank of Brazil is the regulator. The company that sends the payment is the provider's client, and a dollar-to-real payment also falls under the foreign exchange framework of Law 14.286/2021. Lumx applied for the SPSAV authorization and operates under the Article 88 transition regime of BCB Resolution 520/2025.
Which is cheaper, a blockchain payment or a crypto payment?
Neither label sets the price. The conversions do, plus provider fees and a fee on a 1 or 5 minute rate lock, so compare quotes by the reais the supplier receives. A crypto payment that the payee keeps skips one conversion and passes the price risk on. Lumx charges a monthly platform fee plus usage-based per-transaction fees.
Is paying in USDC a crypto payment or a blockchain payment?
Both, when the receiver keeps the USDC: the asset changed hands, and it settled on a blockchain. It is only a blockchain payment, and not a crypto payment, when the receiver is paid in local currency and never holds the coin. On Lumx, a payer can hold USDC in its wallet and pay a destination registered under its account, so a Brazilian supplier receives reais over Pix.
