Something shifted in 2025 that most retailers did not plan for. On-chain stablecoin settlement volume reached an estimated $33 trillion for the year, a figure that, according to analysis published by Spark citing public network data, surpassed the combined transaction volume of Visa and Mastercard. That number includes a large amount of trading and treasury movement rather than pure point-of-sale activity, so it overstates retail adoption. But the infrastructure that moved those trillions is now pointed squarely at merchant commerce, and the companies pointing it there are not fringe crypto startups. Stripe, PayPal, Shopify, Mastercard, and Circle all shipped merchant-facing stablecoin capabilities in the months around the turn of 2026.
For a payment team running an established card-based stack, that raises a practical question that has nothing to do with crypto ideology: does accepting stablecoins actually help the business, and if so, how does it fit alongside the cards, wallets, and local methods already in production? What follows is a merchant-side, rail-neutral look at how stablecoin payments work, the three ways to accept them, the real benefits and the real limitations, and where they fit in a modern payment architecture.
A stablecoin is a digital asset whose value is pegged to a reference currency, most commonly the US dollar, so that one unit is designed to always be worth approximately one dollar. USDC, USDT, PYUSD, and EURC are among the most widely used. Stablecoin payments move value as these dollar-pegged tokens over public blockchains, settling when a block is finalized rather than when an issuing bank authorizes a charge.
That single mechanical difference (settlement on a blockchain instead of authorization through a card network) is the source of nearly every benefit and every limitation that follows. There is no issuing bank in the loop, no interchange, no card network, and no multi-day settlement cycle. There is also no chargeback mechanism of the kind card holders expect, no built-in identity layer, and no established consumer habit of paying this way outside a small cohort of crypto holders.
Stablecoins sit apart from volatile cryptocurrencies like Bitcoin in the one respect that matters for payments: price stability. A merchant that accepts one USDC expects it to be worth roughly one dollar when it settles, which removes the exchange-rate risk that made earlier attempts at Bitcoin acceptance impractical for everyday commerce.
Three developments converged to move stablecoin acceptance from theoretical to practical, and understanding them explains why the topic became unavoidable for payment teams in 2026.
Regulation caught up. The GENIUS Act, signed into US law on 18 July 2025, gave stablecoins a federal regulatory framework for the first time, establishing rules for issuance and reserves. In parallel, the EU’s MiCA framework brought stablecoin issuers and certain service providers under supervision. Regulatory clarity is what allowed regulated financial institutions to build on stablecoin rails without the compliance uncertainty that had kept them out.
The major processors integrated it. Rather than requiring merchants to adopt crypto-native infrastructure, the established players folded stablecoin settlement into their existing merchant products. Since December 2025, according to Spark’s analysis, Stripe merchants have been able to accept USDC through standard checkout, with Stripe handling the blockchain interaction and converting to fiat automatically if the merchant prefers. PayPal extended PYUSD across dozens of markets. Mastercard added settlement support for regulated stablecoins including USDC and EURC. This is the development that matters most for existing merchants, because it means adding stablecoins no longer requires abandoning the card-based workflow.
The market reached meaningful scale. Total stablecoin circulating supply reached roughly $308 billion by early 2026 according to figures cited by industry trackers, large enough that consumer and institutional holdings can sustain a genuine payment network beyond its origins as a trading instrument.
Stablecoin acceptance is not a single thing. There are three structurally different models, and they have very different implications for which customers can pay, what the merchant ends up holding, and how much the existing checkout has to change.
The customer pays with stablecoins from a wallet, and a processor or gateway converts the payment to the merchant’s local currency before it lands in the merchant’s account. The merchant never holds a crypto asset. This is the model that most closely resembles ordinary card processing from the merchant’s point of view: funds arrive in dollars (or euros, or the relevant currency), reconciliation looks familiar, and the volatility question never arises because conversion happens at the moment of payment.
The limitation is on the customer side. Only customers who already hold stablecoins in a wallet can pay this way, which today is a small share of online shoppers. Industry estimates commonly put crypto ownership at roughly 3 to 5 percent of online shoppers, which caps the immediate addressable base for this model.
The inverse model. The customer pays with a familiar instrument (Visa, Mastercard, Apple Pay, Google Pay), and the merchant receives settlement in stablecoins instead of waiting on the traditional multi-day bank settlement cycle. This model preserves the full customer base, because customers pay exactly as they always have, while giving the merchant faster settlement and the treasury benefits of holding a dollar-pegged digital asset. It is particularly relevant for merchants with cross-border operations, fragmented settlement timelines, or treasury teams that want faster access to funds.
The merchant accepts stablecoins directly into its own wallet with no processor in between. The customer scans a QR code or clicks a payment link, sends stablecoins from their wallet to the merchant’s, and the transaction settles on-chain in seconds for the cost of a network fee. There is no processor markup and no percentage fee, only the network transaction cost. The trade is that the merchant takes on wallet management, key security, on-chain operations, volatility exposure if it holds the asset, and the compliance work of handling crypto directly. This model suits crypto-native businesses more than established retailers.
The practical takeaway for most existing merchants: Model 1 and Model 2 are the ones that fit an existing card stack, because they preserve familiar reconciliation and either shield the merchant from holding crypto (Model 1) or preserve the existing customer experience (Model 2). Model 3 is powerful but built for a different kind of business.
Stablecoin payments carry real advantages, and it is worth being precise about which are meaningful for an established merchant versus which are mostly relevant to crypto-native operations.
Faster settlement. On-chain settlement finalizes in seconds to minutes rather than the two-to-seven business days typical of card settlement. For businesses with cash-flow sensitivity or long settlement cycles, this is a genuine operational benefit.
Lower cost per transaction, in some models. Direct on-chain payments avoid interchange, assessment fees, and processor markup, carrying only a network fee. Even the processor-mediated models can, in some cases, cost less than the three fee layers of a card transaction. The size of the saving depends heavily on the model and the provider.
Cross-border efficiency. Stablecoins move the same way regardless of borders, avoiding the intermediary fees, FX spreads, and cut-off-time delays that make traditional cross-border settlement slow and expensive. This is the single strongest use case for most enterprises: not domestic checkout, but cross-border settlement, supplier payouts, and treasury movement.
No rolling reserve or fund-freeze risk in self-custody models. When a merchant holds funds in its own wallet, no intermediary can freeze them or impose a rolling reserve. This matters most to businesses that have struggled with payment processor holds.
Reaching crypto-holding customers. Studies cited across the industry suggest that crypto owners often prefer merchants that accept crypto, so acceptance can attract a specific, growing customer segment even while that segment remains a minority.
The crypto-native content on this topic tends to bury the limitations. For a payment team making a real decision, they matter as much as the benefits.
Small customer base for direct crypto payment. If customers must pay in stablecoins (Model 1 or Model 3), only the minority who hold crypto can transact. For most consumer merchants, this makes direct stablecoin acceptance a supplementary option well short of a primary rail, at least for now.
No native chargeback mechanism. On-chain transactions are final. This eliminates chargeback fraud and the associated fees, which is a benefit, but it also removes the consumer-protection mechanism that card holders expect. For consumer commerce, the absence of a familiar dispute path is a real consideration, and it shifts the burden of dispute resolution onto the merchant’s own policies.
Volatility shielding requires deliberate design. Although stablecoins are pegged, merchants that choose to hold them rather than convert immediately take on peg risk and must design their settlement and treasury handling accordingly. Most merchants that are not crypto-native settle to fiat immediately for exactly this reason.
Accounting, tax, and compliance complexity. Handling stablecoins introduces KYB and KYC considerations, transaction monitoring, and accounting treatment that differ from card payments. Merchants that hold stablecoins rather than converting immediately face additional accounting and tax questions.
Operational maturity. Wallet operations, key management, and on-chain error handling are unfamiliar to most payment teams. Poor wallet operations create losses and disputes that card-based teams are not set up to handle, which is why the processor-mediated models are the pragmatic entry point for established merchants.
The framing that serves an established merchant best treats stablecoins as one more payment rail, with a distinct cost, speed, and customer profile, sitting alongside cards, wallets, account-to-account payments, and local methods in the payment stack. The useful question is where that rail earns its place across the stack.
That framing is exactly what a payment orchestration layer is built to handle. Orchestration connects a merchant to many payment providers and methods through a single integration and routes each transaction across them based on cost, geography, and other factors. Adding a stablecoin rail to an orchestrated stack is a matter of connecting a provider and configuring the rules that decide when it is used, without re-architecting the checkout.
Several patterns emerge when stablecoins are treated as an orchestrated rail:
For the broader picture of how routing across multiple providers and methods works, Gr4vy’s guide on intelligent payment routing covers the underlying mechanism, and the guide on alternative payment methods situates stablecoins among the wider set of non-card options merchants are adding.
A side-by-side view of the two, from the merchant’s perspective:
| Dimension | Card payments | Stablecoin payments |
|---|---|---|
| Settlement speed | 2-7 business days | Seconds to minutes |
| Settlement finality | Reversible (chargebacks) | Final (no chargebacks) |
| Cost structure | Interchange + assessment + processor markup | Network fee, plus processor fee in mediated models |
| Customer base | Nearly universal | Small for direct crypto payment; universal in card-in/stablecoin-out model |
| Chargeback protection | Built in for consumers | None natively |
| Cross-border efficiency | FX spreads, intermediary fees, delays | Borderless, minimal intermediaries |
| Volatility risk | None | None if settled to fiat immediately; peg risk if held |
| Consumer familiarity | Universal | Low outside crypto holders |
| Regulatory framework | Mature | Maturing (GENIUS Act, MiCA) |
| Operational maturity required | Standard | Higher for self-custody; standard for processor-mediated |
The comparison makes the strategic point clear. In consumer checkout, stablecoins work best today as an added rail with specific strengths (cross-border settlement, speed, cost in some models) and specific weaknesses (customer base, dispute handling, operational demands), which makes them a valuable addition to a multi-rail stack well before they become a wholesale substitute for cards.
A stablecoin payment moves value as a dollar-pegged (or other currency-pegged) digital token over a public blockchain, settling when the blockchain confirms the transaction rather than when a bank authorizes a charge. Common stablecoins used in payments include USDC, USDT, PYUSD, and EURC. Because the token’s value is pegged, the merchant is not exposed to the price volatility associated with cryptocurrencies like Bitcoin.
There are three models. In the first, the customer pays in stablecoins and a processor converts to fiat so the merchant receives local currency. In the second, the customer pays with a card and the merchant receives settlement in stablecoins. In the third, the merchant accepts stablecoins directly into its own wallet with no processor. Most established merchants use one of the first two, because they preserve familiar reconciliation and either avoid holding crypto or preserve the existing customer experience.
They can be, depending on the model. Direct on-chain payments avoid interchange, assessment fees, and processor markup, carrying only a network fee, which can be significantly cheaper than a card transaction. Processor-mediated stablecoin acceptance carries a provider fee that reduces but may not eliminate the saving. The cost advantage is real but varies widely by model and provider.
No. On-chain stablecoin transactions are final and cannot be reversed the way card transactions can. This eliminates chargeback fraud and the associated fees, which benefits the merchant, but it also removes the dispute-resolution mechanism that card-paying consumers expect. Merchants accepting stablecoins for consumer purchases need their own policies for handling disputes and refunds.
Holding stablecoins introduces peg risk (the small chance the token deviates from its pegged value) and accounting, tax, and treasury considerations that differ from holding fiat. Most merchants that are not crypto-native avoid this by settling stablecoin payments to fiat immediately, which removes the holding risk. Merchants that choose to hold stablecoins usually do so for a specific treasury or cross-border reason and design their operations accordingly.
The most widely used in merchant contexts are USDC (issued by Circle), USDT (Tether), PYUSD (PayPal’s dollar-backed stablecoin), and EURC (a euro-pegged stablecoin). Card networks and processors have added settlement support for specific regulated stablecoins, so the practical set available to a given merchant depends on which providers it works with.
Increasingly yes. Major processors have integrated stablecoin acceptance into their existing merchant products, so in some cases stablecoins can be enabled with little or no code change. In an orchestrated payment stack, adding a stablecoin rail is a matter of connecting a provider and configuring routing rules, instead of rebuilding the checkout.
Stablecoins gained a US federal regulatory framework with the GENIUS Act signed in July 2025, and the EU regulates them under the MiCA framework. Regulation continues to develop, and the specific compliance obligations depend on the merchant’s jurisdiction, whether it holds stablecoins, and which providers it uses. The regulatory picture is far clearer than it was even a year earlier, which is part of why established payment companies entered the space.
The strongest cases today are cross-border settlement, supplier payouts, treasury efficiency, and reaching crypto-holding customers, well ahead of any case for replacing domestic card checkout. Businesses with significant cross-border volume, slow or fragmented settlement, or high cross-border costs benefit most. For a purely domestic consumer merchant with no settlement pain, the immediate case is weaker, though the option is worth evaluating as adoption grows.
The most workable approach treats stablecoins as one rail among several, added alongside cards, wallets, and local methods instead of replacing them. A payment orchestration layer can route transactions across all of these based on cost, geography, and customer preference, so a merchant can use stablecoins where they are strongest (often cross-border) while keeping cards for the bulk of consumer checkout.
The honest read on stablecoin payments in 2026 is that they crossed from speculative to practical, but practical does not mean universal. For an established merchant, the technology now works, the regulation exists, and the major processors have made acceptance accessible without a crypto-native rebuild. What has not changed is that most consumers still pay with cards and wallets, that direct stablecoin payment reaches only a small slice of shoppers today, and that the clearest wins are in cross-border settlement and treasury rather than domestic checkout.
That points to a measured strategy. Treat stablecoins as an additional rail with a specific and real set of strengths, add them where those strengths apply, settle to fiat unless there is a deliberate reason to hold, and keep the whole thing unified with the rest of the payment stack so the finance team is not managing a separate silo. Merchants that already route transactions across multiple providers are best positioned to do this, because adding a stablecoin rail becomes a configuration decision instead of an architectural one.
Gr4vy’s cloud-native payment orchestration platform connects merchants to a wide range of payment providers and methods through a single integration, with routing, unified reporting, and the flexibility to add new rails as they mature. If stablecoins are on your roadmap and you want to understand how they would sit alongside your existing card and local-method stack, reach out to our team for a walkthrough.
Payments are shifting beneath the surface. Not through a single innovation, but through the steady…
A customer sees a charge on their card statement they do not recognize, or a…
Payment orchestration sits at the intersection of two fast-moving trends: the shift of nearly all…
San Mateo, July 28: Wizlo, the operating system powering end-to-end telehealth infrastructure for modern e-commerce…
Picture a large retailer on the busiest sales day of its year. Its single acquiring…
Every time a customer pays with a card, an invisible piece of infrastructure does the…