Stablecoin vs Card Fees and Settlement for Merchants

Stablecoin vs card fees compares two cost stacks. A card sale pays interchange, a network assessment and an acquirer markup. A stablecoin sale pays a conversion spread and a provider fee, with no interchange. The answer depends on card type and corridor: debit interchange is capped in Brazil and the United States, so credit and cross-border sales gain most.

What does a merchant pay on a card sale and on a stablecoin sale?

A card fee is three payments stacked: interchange to the bank that issued the card, an assessment to the network, and a markup to the acquirer (the merchant's bank or processor). A stablecoin sale has no issuing bank and no card network, so those two layers do not exist. What replaces them is the cost of turning the buyer's local currency into the stablecoin you settle in, and whatever your provider charges for the service.

The fee layers on each side, with the numbers that are public.

The US debit cap is narrower than most comparisons admit. The Federal Reserve's 2024 data puts the average debit interchange at 0.44% of value for Visa and 0.49% for Mastercard on transactions at covered issuers, against 1.46% and 1.30% on exempt transactions (the Fed's term for debit cards from issuers under $10B in assets, among other cases). The cap covers debit only, so a blanket "cards cost 1.5% to 3.5%" claim hides a spread of more than three to one inside the same network.

Lumx does not process, acquire or issue cards, and it does not price any card layer. On the stablecoin side, its pricing is "monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans". On a Lumx quote the base rate is the raw market rate with no FX margin built in, so the cost of the conversion is the Lumx fee plus any partner fee the platform adds.

What does a card cost in Brazil, and what does Pix cost?

Brazil caps debit and prepaid interchange by rule, which moves the break-even for Pix (Brazil's instant payment system, run by the Central Bank) against cards. Resolução BCB nº 246, of September 26, 2022, in force since April 1, 2023, sets a ceiling on interchange of 0.5% on any debit transaction and 0.7% on any prepaid transaction. It replaced Circular nº 3.887 of March 26, 2018, which had capped debit as a weighted average of 0.5% with 0.8% per transaction.

Brazilian card and Pix cost layers, from the text of the norm.

A merchant discount rate quoted by an acquirer adds the assessment and the acquirer markup on top of the 0.5%, so a stablecoin path has to beat the whole stack. Ask your acquirer for the rate by card type and your payment service provider for the charge per Pix receipt, then put both next to the stablecoin quote. Mexico works the same way, with SPEI (Mexico's interbank transfer system, run by Banxico) in place of Pix.

A worked example with your own inputs

Take $10,000 of sales in a month. These inputs are illustrative, not provider quotes; replace them with the lines from your own contracts.

Interchange alone, from the Federal Reserve's 2024 averages, against a hypothetical stablecoin cost.

The card rows leave out the assessment, the acquirer markup and dispute losses, so the real card cost is higher. The 0.20% inputs are placeholders, not a Lumx price.

The break-even rule is short. Stablecoin wins on a sale when its spread plus provider cut is lower than interchange plus assessment plus acquirer markup plus expected dispute losses. For a debit sale at a capped issuer, in the United States or Brazil, that bar is low, and the stablecoin path may lose. For credit, which has no cap in either source above, or for a cross-border sale that triggers a currency markup, the bar is higher, but how much higher depends on your own card mix and quotes. Run it per corridor, with same-day quotes for the same amount.

How settlement timing differs

Fees decide the margin. Timing decides the working capital. Mastercard's stablecoin settlement changes how banks settle with the network, not when the merchant is paid. A card payout reaches the merchant on the acquirer's schedule, batched by day, at a date set in the merchant agreement. No public figure applies to every merchant.

A stablecoin sale has two clocks. The first is the rail the buyer pays through, and it does not depend on the stablecoin. The second is the wallet credit: after the deposit, the on-ramp runs conversion and delivery steps before it reaches success. After a Pix or SPEI payment, the stablecoin credit is instant, about 5 minutes. Webhook onramp.success marks the credit.

Settlement of the rails a merchant can collect on, from the Lumx docs read on November 1, 2026. This is the rail only, not the wallet credit.

A compliance hold, called an RFI (request for information), can pause a transaction.

For a merchant selling into Brazil or Mexico that holds dollars, the card path waits on the acquirer, converts through its FX markup and waits for a cross-border payout. The Pix or SPEI path swaps that for an instant rail and one conversion. The SWIFT comparison is in stablecoins vs SWIFT.

What about converting back to local currency and holding a balance?

A merchant that needs reais at the end pays a second leg. The stablecoin it holds goes through an off-ramp to a local bank account, and that conversion has its own spread and fee, on top of the collection cost above. How stablecoin payout pricing works breaks that second leg down. At Lumx, the off-ramp is a transaction from the wallet to a bank account in the merchant's name, and Lumx does not take a fee out of the amount that reaches the recipient on a Pix or SPEI payout; only the recipient's bank can.

Holding the balance adds a risk cards do not have: the stablecoin can trade below its peg while it sits in the wallet. The longer the merchant waits to convert, the more exposure it carries. Stablecoin depeg risk for payment companies covers how to size it. With Lumx, an autoconversion rule converts each fiat deposit to stablecoin at the market rate, and the merchant chooses when to run the off-ramp.

What the buyer and the merchant each carry

Cards put risk on the merchant that stablecoin payments move elsewhere, and the reverse holds too.

The merchant carries card disputes: a buyer can contest a sale after the goods shipped, and the network's rules decide the outcome. A confirmed stablecoin transfer is not pulled back by a network, so refunds become a new payment under the merchant's own policy. See are stablecoin payments reversible.

The buyer carries the currency. A Brazilian buyer who pays in reais through Pix never touches USDC; the conversion happens behind the checkout. A buyer who must hold the stablecoin first carries the cost of getting it, which is why stablecoin works best as one more way to pay.

Licensing is a separate question, covered in license to accept stablecoins. Cross-border merchant payments without pre-funding covers why a stablecoin balance can replace a prefunded account abroad.

What to ask both providers for

I recommend that a merchant never accept a single blended percentage from either side, and ask for the fee as separate lines: on cards, the interchange, the assessment and the acquirer markup; on stablecoin, the conversion spread and the provider cut. I would also run both quotes on the same day, for the same amount and corridor, because a low headline rate on one leg can be recovered on the other. And I would keep cards at checkout for buyers who want them, and add the stablecoin path where the cross-border cost is the largest line.

A fair comparison holds four things equal: the sale amount, the day (the conversion rate moves), the corridor (a Pix receipt and a SPEI receipt price differently) and the itemization of fees.

When stablecoin is the wrong tool for a merchant

Keep cards when the buyer will not pay in anything but a card, or when the purchase relies on consumer credit at checkout. Keep them for small domestic sales on capped debit, in Brazil or at a covered US issuer, where the stablecoin spread plus provider cut can easily cost more. And keep them when your accounting cannot yet record a conversion and a stablecoin balance.

What this looks like with Lumx for a merchant selling into Brazil and Mexico

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 a sale, the merchant's platform creates an on-ramp transaction: the buyer pays in BRL over Pix or in MXN over SPEI, and the response returns a Pix code or a CLABE (the 18-digit Mexican bank account number) to show at checkout. When the amount arrives, Lumx converts the fiat to USDC (see what USDC is) or USDT and credits the merchant's wallet. Expiry depends on the rate type. A floating-rate on-ramp on Pix or SPEI expires after 1 day. A locked one expires with its quote: 30 seconds with no fee, or 1 or 5 minutes with a fee. A deposit that lands after expiry is refunded to the sender on the same rail. A foreign company can collect through a named virtual account (a local account number in the customer's own name) in BRL or MXN, with no local entity in Brazil or Mexico; see named virtual accounts.

On cost, the quote returns the base amount and the final amount after fees, with the base and final exchange rates. The gap between the two is the Lumx fee plus the partner fee, plus the lock fee on a 1 or 5 minute quote, and the quote shows those pieces separately. Your platform adds the partner fee as a rate in basis points, a flat dollar amount, or both, sent to a wallet you choose, and on a locked quote the fee is part of the quote. The Brazilian how-to is accepting stablecoin payments in Brazil. The conversion pages are BRL to USDC and MXN to USDC, and coverage by country lists the rails.

Methodology and sources

Checked on November 1, 2026. Nothing here is a quote from a provider.

• Federal Reserve Board, Regulation II average debit card interchange fee by network, 2024 data (read on November 1, 2026)

• Electronic Code of Federal Regulations, 12 CFR 235.3, reasonable and proportional interchange transaction fees, text current to October 29, 2026

• Banco Central do Brasil, Resolução BCB nº 246, of September 26, 2022, articles 1 to 3, 5 and 6 (text read on November 1, 2026)

• Banco Central do Brasil, Estudo Especial nº 106, results of the debit card interchange cap, for Circular nº 3.887 of March 26, 2018 (0.5% weighted average, 0.8% per transaction, in force October 1, 2018)

• Lumx docs: Transactions, Exchange rates, Partner fees, Payment rail cut-off times, Coverage, Webhooks

Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Mike Enerio on Unsplash.