Accepting cryptocurrency payments requires choosing a processor that matches your business volume, supported chains, and settlement preferences. The three most established names in this space — BitPay, Coinbase Commerce, and Stripe with its stablecoin integration — each take different approaches to custody, fees, and on-chain settlement. Understanding their structural differences helps avoid costly surprises when scaling from occasional crypto invoices to high-volume recurring billing.
For teams evaluating multiple options across the broader landscape, comparing crypto payment gateway processors bitpay coinbase through independent aggregators like crypto payment gateway processors bitpay coinbase provides an additional angle, especially for merchants who want non-custodial routing and multi-asset support beyond what any single processor offers.
Fee Structures Compared
Pricing models differ significantly across these platforms, and the gap widens as transaction volume grows.
| Processor | Platform Fee | Settlement Fee | Fiat Conversion Spread |
|---|---|---|---|
| BitPay | Free | 1% | ~0.5 – 1% |
| Coinbase Commerce | Free | 0% (on-chain only) | 1% if auto-converting |
| Stripe (stablecoin) | Free | 1.5% | Included in rate |
| NOWPayments | Free | 0.5% | Variable by asset |
BitPay charges a flat 1% per settled invoice and converts everything into your designated fiat currency automatically unless you opt for wallet withdrawal. This simplicity comes at the cost of custodial control — funds pass through BitPay’s accounts before reaching yours.
Coinbase Commerce charges no platform fee and no processing fee when you hold crypto. You pay nothing if you keep USDC or BTC in your dashboard. Auto-conversion to USD carries a 1% spread, which is competitive but adds up at scale.
Stripe stablecoin payments price inbound crypto at 1.5%, slightly above card processing rates for some tiers. The advantage lies in unified reporting — one dashboard handles cards, bank transfers, and stablecoins together. Settlement lands in your existing Stripe balance.
NOWPayments sits between custodial and non-custodial models with a flat 0.5% fee and support for 300+ assets. Their architecture routes transactions without holding user funds long-term, reducing counterparty risk compared to fully custodial alternatives.
Custody Models: Who Holds the Keys
Custody determines how much operational risk you accept and how quickly funds become spendable.
Fully Custodial: BitPay
BitPay operates as a registered money transmitter. Inbound crypto arrives at addresses they control, and balances appear in your merchant dashboard after blockchain confirmations. Withdrawals to your bank or personal wallet take moments to initiate but may face daily limits tied to your verification tier. This model works well for businesses that prioritize ease of use over self-custody.
Hybrid: Coinbase Commerce and Stripe
Coinbase Commerce generates deposit addresses you control through API keys, but the default flow routes funds to a Coinbase-hosted balance. You can configure payouts to external wallets, giving you partial custody flexibility. Stripe’s stablecoin product follows a similar pattern — funds settle to your Stripe balance, which acts as a custodial intermediary before bank transfer.
Non-Custodial Options
Platforms like NOWPayments offer non-custodial payout modes where payments go directly to merchant-controlled wallets. This eliminates platform counterparty risk entirely but requires more technical setup and personal responsibility for key management and reconciliation.
Supported Chains and Stablecoins
Chain coverage varies widely and directly impacts which customers can pay comfortably.
| Processor | Ethereum | Base | Polygon | Solana | Tron |
|---|---|---|---|---|---|
| BitPay | Yes | No | No | Limited | No |
| Coinbase Commerce | Yes | Yes | Yes | No | No |
| Stripe (stablecoin) | Yes | Yes | Yes | Yes | No |
| NOWPayments | Yes | Yes | Yes | Yes | Yes |
Stripe supports USDC across Ethereum, Solana, Polygon, Base, and Tempo networks — the broadest EVM-plus-Solana coverage among managed gateways. Coinbase Commerce covers Base, Ethereum, Polygon, and several other EVM chains but lacks Solana and Tron support.
BitPay offers the narrowest chain selection, primarily focused on Ethereum and Bitcoin. This limitation matters less for domestic US merchants and more for global B2B operations where customers prefer paying on low-fee networks like Base or Tron.
Stablecoin availability follows similar patterns. USDC is universally supported. USDT appears on most platforms except where EU regulations favor EURC under MiCA compliance. PYUSD and FDFD are emerging options available through Stripe and select partners.
Integration Complexity
Technical setup time ranges from minutes to weeks depending on the processor and integration depth.
BitPay provides REST APIs, hosted checkout pages, and plugins for WooCommerce, Shopify, and major e-commerce frameworks. Most merchants complete integration in under an hour using a hosted payment link. Webhooks notify your system of confirmed payments with status codes for pending, confirmed, and completed states.
Coinbase Commerce mirrors this approach with API-first design and plugin ecosystem. The webhook delivery model includes retry logic and signature verification for security. Custom checkout flows require minimal code since address generation and confirmation tracking happen server-side.
Stripe stablecoin payments integrate through the existing Stripe Payments API. If you already process cards through Stripe, adding stablecoin acceptance means enabling a new payment method in your dashboard and handling one additional payment_intent type. For developers already familiar with Stripe’s SDKs, this is the lowest-friction option.
Custom integrations requiring direct on-chain monitoring, multi-chain receiving, or cross-chain settlement demand engineering resources that none of these managed platforms provide out of the box. Teams building above $1 million monthly invoice volume typically evaluate treasury APIs or custom smart contract solutions instead.
Recurring Billing and Subscriptions
Not all processors handle subscription payments equally well.
BitPay supports recurring invoices through scheduled payment links generated via API. Each cycle creates a new address and invoice reference, which works reliably but lacks true subscription automation like automatic retries or proration.
Coinbase Commerce does not natively support recurring billing. Merchants must generate individual payment links per billing cycle or build external scheduling logic that calls the Coinbase API repeatedly.
Stripe handles subscriptions natively through its Subscription API. Adding stablecoin as a payment method for recurring invoices requires minimal configuration — the same customer portal and dunning management that processes credit cards also processes USDC on-chain.
Non-custodial platforms often implement recurring billing differently, using wallet pre-authorizations (EIP-2612 permits) or smart-contract-based pull payments. These approaches give subscribers granular control over authorization amounts while allowing merchants to collect payments automatically.
Which Processor Fits Your Business
Small freelancers and solopreneurs billing under $50,000 monthly benefit most from Coinbase Commerce’s zero platform fee combined with simple hosted checkout. Engineering overhead stays near zero and total costs rarely exceed 1% including conversion spreads.
Established e-commerce stores already using Stripe gain the most value from Stripe’s stablecoin integration. Unified reporting, single dashboard, and existing customer infrastructure make the marginal complexity negligible compared to managing a second processor.
Businesses serving global B2B clients across multiple regions should evaluate NOWPayments or similar multi-chain aggregators. Support for Tron, Solana, and 15+ EVM networks lets international customers pay using the network they already hold, improving conversion rates and reducing failed transactions.
High-volume merchants processing above $1 million monthly should consider whether managed gateways remain cost-effective. At that scale, even 0.5 – 1% fees represent significant monthly expenditure, and custom treasury API integrations with direct on-chain settlement become financially justified despite the 2 – 6 week development timeline.