Accepting crypto payments means routing a buyer's digital-asset balance through a settlement pipeline that leaves the merchant holding a chosen currency, usually a stablecoin like USDC or local fiat. The mechanics decompose cleanly into three structural models, a settlement choice, a volatility-shielding step, and a chargeback model that differs from card rails. This article walks through each piece, names the major payment networks operating in 2026 (Mesh, Coinbase Commerce, BitPay, PayPal Crypto, Stripe), and lays out a comparison table for product and finance teams evaluating an integration. The aim is mechanism clarity, not a recommendation of any one provider.
What "accepting crypto payments" actually means
Accepting crypto payments is the merchant-side process of taking digital-asset value from a buyer's wallet or exchange account, confirming it on a blockchain, and recording settlement in the merchant's chosen currency. The asset the buyer sends and the asset the merchant receives can be the same token, a different token, or fiat after conversion. The pipeline is the integration.
Three things distinguish a crypto payment from a card or ACH transaction. First, the funds move on a public blockchain rather than through a card network or bank rail, so the transaction settles when a block is finalized rather than when an issuer authorizes a charge. Second, the buyer does not hand over reusable account credentials; they sign a single transaction from a wallet or initiate a transfer from a custodial account. Third, the merchant chooses what currency lands in their ledger, which is what makes stablecoin settlement attractive even when the buyer pays in volatile assets. The BIS Quarterly Review tracks the rise of stablecoin payment volume across these flows.
The three structural models for accepting crypto
Crypto checkouts decompose into three structural models: direct wallet, hosted checkout, and network aggregator. The direct-wallet model has the merchant receive funds at a wallet they control. The hosted-checkout model delegates the front end to a processor. The network-aggregator model adds a layer that unifies many wallets and exchanges behind a single integration. Each shifts a different piece of the work.
In the direct-wallet model, the merchant publishes a deposit address and the buyer signs a transaction from their own wallet. There is no intermediary processor. The merchant handles confirmation, accounting, and any conversion to fiat themselves, usually via an exchange API or an OTC desk. Self-custody operators and DAOs commonly run this pattern. The cost is low; the integration work is high.
In the hosted-checkout model, a processor like Coinbase Commerce or BitPay renders a payment page, accepts the buyer's funds at an address it controls, and posts settlement to the merchant's wallet or bank account. The merchant integrates by embedding a button or redirect. The processor owns volatility shielding, confirmation logic, and refund tooling.
In the network-aggregator model, a layer like Mesh connects to many wallets and exchange accounts so a single integration covers a wide buyer base. Per Mesh's public material, the network supports 300+ wallets and exchanges and 120+ tokens across 24+ chains. The merchant integrates once; the aggregator handles the source-side routing.
How a network-aggregator like Mesh works
A network aggregator sits between many buyer-side fund sources (self-custody wallets, custodial exchange accounts, embedded wallets) and the merchant's settlement account. The integration exposes a single API. When a buyer pays, the aggregator authenticates the source, pulls the chosen asset, handles any on-chain transport or conversion, and lands a chosen stablecoin or fiat amount in the merchant's account.
Per Mesh's public material, the design decouples the customer's source asset from the merchant's settlement asset, a pattern Mesh calls SmartFunding. A buyer can pay from a Coinbase account in BTC or from a self-custody wallet in ETH while the merchant receives USDC. The aggregator covers source authentication (OAuth-style for custodial accounts, wallet signatures for self-custody), the source-side conversion, and on-chain delivery. Mesh's Series C release describes the network as enterprise-grade; the round was led by Dragonfly Capital with participation from Paradigm, Moderne Ventures, Coinbase Ventures, SBI Investment, and Liberty City Ventures.
Settlement: stablecoin or fiat at the merchant
Settlement is the moment the merchant's ledger records value. The merchant chooses what that value is denominated in. The common options in 2026 are USDC, PYUSD, USDT, RLUSD, and local fiat. Each carries a different operational profile around chain choice, banking integration, and conversion cost. The choice is a finance decision, not a buyer decision.
Stablecoin settlement keeps funds onchain. USDC, issued by Circle, is supported across most major chains and integrates with bank rails through Circle Mint. PYUSD, issued by PayPal and Paxos, runs on Ethereum and Solana and connects into PayPal's settlement layer. USDT, issued by Tether, has the deepest secondary-market liquidity. RLUSD, issued by Ripple, settles on Ethereum and the XRP Ledger. See the stablecoin pillar for issuer mechanics and chain footprints.
Fiat settlement converts at the processor or aggregator and transmits via ACH, SEPA, wire, or a card network. The conversion happens at a quoted rate, usually with a spread that the processor publishes. Mesh, Coinbase Commerce, and BitPay all offer fiat settlement in addition to stablecoin settlement, per their public material. The trade-off is straightforward: stablecoin settlement keeps optionality and lower cost; fiat settlement removes the operational lift of holding digital assets.
Volatility shielding mechanics
Volatility shielding is the step that protects the merchant from price movement between the moment a buyer commits and the moment funds settle. The shielding mechanism is either a quoted rate held open for a short window or an immediate conversion to a stable asset at receipt. Both eliminate exposure; they differ in who carries the inventory risk.
The quote-and-lock pattern works like an FX quote. The processor returns a rate good for a fixed window, typically 10 to 15 minutes. If the buyer's transaction confirms inside the window, the merchant receives the quoted amount. If not, the processor either re-quotes or rejects. Coinbase Commerce documents this pattern in its developer documentation.
The instant-conversion pattern converts the buyer's asset to a stablecoin (or fiat) at the moment of receipt. The processor takes the spread and posts a stable amount to the merchant. Network aggregators that route the source-side conversion implement a variant of this pattern. The merchant never holds the volatile asset.
Chargeback model and refund mechanics
The chargeback model for crypto payments is structurally different from card rails. Blockchain transactions are not reversible by the network. There is no equivalent of a Visa or Mastercard dispute that the merchant must defend. Refunds happen as separate outbound transactions that the merchant initiates. Disputes, when they occur, run through the processor's contract terms or off-chain mediation, not through a card scheme.
The trade-off is that fraud and consumer-protection burden shifts. The merchant cannot recover funds from a buyer who claims they were defrauded, and the buyer cannot reverse a payment they regret. Industry guidance from the FTC on payment apps offers parallel context on irreversible consumer payments.
Major crypto payment networks at a glance
The 2026 landscape includes five widely integrated networks. Mesh is a source-side aggregator covering 300+ wallets and exchanges. Coinbase Commerce is a hosted checkout backed by Coinbase. BitPay is a long-running hosted processor. PayPal Crypto integrates buying and paying inside PayPal accounts. Stripe re-entered crypto acceptance with stablecoin-first settlement in 2024. Each plays a different structural role.
Mesh raised a $75M Series C at a $1B valuation in 2026 per its PRNewswire release, and named Stellar and Tempo as integrations the same window. BitPay has operated since 2011. PayPal's stack is anchored by PYUSD per PayPal's launch release. Stripe's stablecoin payments product, per Stripe's public material, focuses on USDC settlement across multiple chains.
How do these networks compare?
The networks differ on structural model, asset coverage, settlement options, and integration shape. The table below summarizes the five at a glance. Coverage figures shift as integrations launch.
Network | Structural model | Buyer-side coverage | Settlement options |
Mesh | Source-side aggregator | 300+ wallets and exchanges, 120+ tokens across 24+ chains (per Mesh) | USDC, PYUSD, USDT, RLUSD, local fiat (per Mesh) |
Coinbase Commerce | Hosted checkout | Major chains and tokens; Coinbase account integration | USDC and other major assets; fiat via Coinbase |
BitPay | Hosted checkout | BTC, ETH, and a long tail of altcoins and stablecoins | Local fiat in 200+ countries (per BitPay) and stablecoin |
PayPal Crypto | Custodial account integration | PayPal account holders; PYUSD on Ethereum and Solana | PYUSD or USD inside PayPal balances |
Stripe | Hosted checkout, stablecoin-first | USDC across Ethereum, Solana, Polygon, Base (per Stripe) | USDC or local fiat via Stripe payouts |
Where stablecoin orchestration and cross-chain routing sit
Beyond the merchant-facing network, a second layer handles cross-chain transport and stablecoin routing. This is where projects like Circle's CCTP and intent routers fit. A payment that starts on one chain and settles on another passes through this layer. Most merchants do not see it directly, but it shapes which chains a network can credibly support.
Eco Routes is one example of an intent-routing layer that could compose with a payments network: it executes a stablecoin transfer intent across chains using a solver-based model. It is not a substitute for a payments network like Mesh; it is a transport layer that a network can call. For finance teams evaluating settlement chain choice, the cross-chain transport layer is the reason a merchant settling USDC on Base can receive payments originated from a wallet on Solana without manual bridging.
What to evaluate when picking an approach
The right approach depends on three things: where the merchant's buyers already hold funds, what currency the merchant wants to receive, and how much integration work the team can absorb. Each model fits a different combination. A consumer brand with global buyers benefits from aggregator-style coverage. A vertical with a known buyer wallet may do fine with direct receipt.
Practical evaluation factors include:
Source-side coverage: how many wallets and exchange accounts the buyer base actually uses.
Settlement coverage: whether the network supports the merchant's preferred stablecoin and fiat rails.
Chain support: which networks are live, which are announced, and which are required by buyer geography.
Pricing: the published fee plus any spread on conversion or fiat settlement.
Compliance posture: how the network handles KYC, sanctions screening, and travel-rule data.
Refund and dispute tooling: API coverage for outbound refunds and any mediation contracts.
Reconciliation: webhook reliability, settlement timing, and accounting integrations.
Related reading
Sources and methodology. Network claims drawn from each provider's public material as of June 2026: Mesh (meshpay.com and Series C PRNewswire release), Coinbase Commerce developer docs, BitPay site, PayPal newsroom, and Stripe stablecoin payments page. Figures refresh quarterly; coverage shifts as integrations launch.

