Accepting cryptocurrency for recurring revenue has evolved from a niche experiment into a legitimate billing infrastructure layer. Businesses that sell SaaS access, memberships, content subscriptions, or ongoing services now have multiple paths to charge customers in digital assets without relying on traditional card networks. The landscape splits into three distinct approaches: hosted payment gateways, self-hosted open-source platforms, and on-chain streaming protocols. Understanding where each fits prevents costly integration mistakes.
Why Recurring Crypto Billing Matters
Subscription models generate predictable cash flow. Traditional processors still dominate this space, but they carry friction that crypto solves natively: cross-border fees, chargeback risk, settlement delays, and geographic restrictions. A crypto-native subscription removes the card network entirely. Payments settle on-chain, merchants face zero dispute reversals, and international customers pay without currency conversion layers.
The tradeoff involves user experience and price volatility management. Customers must hold crypto, and merchants need strategies to handle fluctuating token values. The right platform addresses both concerns through stablecoin support, oracle-based pricing, or instant fiat conversion. For businesses evaluating crypto recurring billing subscriptions coinbase commerce, the decision comes down to custody preferences, technical resources, and whether continuous streaming or periodic billing aligns with the product model.
Hosted Payment Gateways
Hosted gateways handle everything on behalf of the merchant. They manage wallet infrastructure, price feeds, compliance checks, and payouts. This model suits teams that want to start accepting crypto subscriptions within hours rather than weeks.
Coinbase Commerce
Coinbase Commerce operates as a hosted payment processor focused on simplicity. Merchants integrate via API or plugins, receive a unique deposit address per invoice, and get settled in their chosen cryptocurrency. The platform supports Bitcoin, Ethereum, Litecoin, USDC, Dai, and several other assets.
For recurring billing specifically, Coinbase Commerce does not provide native subscription automation. Merchants build recurring logic externally using webhooks that detect incoming payments and trigger account upgrades. This works well for straightforward renewal flows but requires custom development for proration, tier changes, or dunning management.
The primary advantage sits in brand recognition and ease of setup. The Coinbase name reduces customer hesitation at checkout. Settlement lands directly in the merchant’s custodial Coinbase account, which connects to bank transfers for fiat off-ramping. Processing fees apply per transaction, and the platform handles all wallet security and key management.
Limitations of Hosted Solutions
Hosted gateways introduce third-party custody risk. If the processor suspends an account or changes terms, merchant funds and subscriber data become dependent on that provider’s policies. Price volatility during the confirmation window also creates reconciliation complexity. Some merchants accept the tradeoff for speed; others prefer full control over their payment rails.
Self-Hosted Open-Source Platforms
Self-hosted solutions give merchants complete ownership of their billing infrastructure. The software runs on the merchant’s own server, funds never touch an intermediary wallet, and no processing fees exist beyond network costs.
BTCPay Server Subscriptions
BTCPay Server introduced native subscription management in version 2.3, fundamentally changing what the platform could handle. Before this release, recurring payments required manual invoice generation or external cron jobs. Now the built-in Subscriptions app supports two renewal modes.
Manual recurring payments send email reminders before each billing period expires. Customers receive a new invoice and pay independently each cycle. Automatic recurring payments use a credit balance model where subscribers preload funds upfront, and the system deducts the plan cost at each interval without requiring additional customer action.
The platform supports defining offerings with multiple pricing tiers, trial periods, and feature-based entitlements. It integrates with Lightning Network for instant low-fee renewals and on-chain confirmations for larger settlements. Merchants pay only VPS hosting costs, typically between $10 and $30 monthly, plus any applicable network fees.
BTCPay Server demands technical comfort. Setting up and maintaining the server requires Linux administration skills, and the merchant bears full responsibility for security, backups, and uptime. The reward is total autonomy over customer data, fund custody, and billing logic customization.
BTCPay vs Hosted Comparison
| Feature | BTCPay Server | Coinbase Commerce |
|---|---|---|
| Custody | Self-custodied | Platform-managed |
| Monthly cost | Hosting only ($10 –$30) | Per-transaction fees |
| Subscription automation | Native (manual + credit balance) | Webhook-dependent |
| Technical requirement | High (self-hosted server) | Low (API integration) |
| Fiat off-ramp | Manual | Built-in bank connection |
On-Chain Streaming Protocols
Streaming represents a fundamentally different approach to recurring revenue. Instead of charging customers at fixed intervals, money flows continuously by the second from sender to receiver. This eliminates billing cycles, reduces churn from forgotten renewals, and enables granular usage-based pricing.
How Superfluid Works
Superfluid operates as an open-source token streaming protocol across EVM-compatible blockchains including Ethereum, Polygon, Base, Arbitrum, and Optimism. It introduces the Super Token standard, which wraps any ERC-20 asset into a streamable format. When a customer initiates a subscription, tokens convert to their streaming variant, and value transfers occur through protocol-level accounting rather than individual transactions.
The economic advantage is significant. Once a stream starts, no additional gas fees accumulate for maintaining it. Balance updates happen continuously through smart contract state changes, not repeated on-chain transfers. A $50-per-month subscription running at $0.0005787 per second requires exactly one transaction to create and one to stop.
Superfluid also released a dedicated Subscriptions toolkit that provides customizable checkout widgets, subscriber dashboards, and automated stream management. Teams can host the widget themselves, export configuration as JSON, or deploy it to IPFS. The system is non-custodial, free to use, and designed for direct integration into existing platforms.
Use cases extend beyond simple subscriptions. DAOs stream contributor salaries and grant distributions. Content platforms meter access by the second. Developers implement dollar-cost averaging bots that continuously transfer fixed amounts. The protocol treats every recurring payment pattern as a variation of the same streaming primitive.
Loop Crypto: Pull-Based Recurring Payments
Loop Crypto takes a middle path between streaming and traditional periodic billing. Rather than continuous flow or manual renewal invoices, Loop implements pull-based autopay through smart contract allowances. Customers authorize their wallets once, and Loop’s smart contracts withdraw the specified amount at each billing interval automatically.
The system mirrors how credit card autopay functions. A customer subscribes to a $100/month plan in ETH, and Loop queries a pricing oracle each cycle to determine the equivalent token amount. The actual withdrawal executes on-chain without requiring customer interaction. This approach avoids the fund-lockup requirements of credit balance models while eliminating the non-payment risk of manual reminders.
Loop supports Ethereum, Solana, Polygon, Base, Optimism, and Arbitrum. It integrates directly with Stripe and Chargebee, allowing merchants to manage subscription logic, coupon codes, trials, and customer portals in familiar tools while offloading crypto payment execution to Loop’s infrastructure. A 0.75% fee applies to processed volume.
Streaming vs Pull Payments
| Aspect | Superfluid Streaming | Loop Crypto Autopay |
|---|---|---|
| Payment model | Continuous per-second flow | Scheduled pull withdrawals |
| Gas efficiency | Single tx for lifetime of stream | One tx per billing cycle |
| Customer action | Initial stream creation only | Initial wallet authorization |
| Best for | Usage-based, salary, vesting | Fixed-price subscriptions |
| Supported chains | 11+ EVM networks | EVM + Solana |
Choosing the Right Infrastructure
The optimal choice depends on three factors: custody preference, technical capacity, and billing model.
Merchants who want zero technical overhead and don’t mind third-party custody should start with a hosted gateway like Coinbase Commerce. Integration takes minimal effort, and the platform handles compliance, security, and payout routing. Recurring logic requires external development but the foundation is solid.
Teams comfortable managing servers and wanting full financial autonomy should evaluate BTCPay Server. The native subscription system eliminates the previous workaround requirements, and the credit balance model provides automatic renewals without custodial risk. Lightning integration makes micro-subscriptions economically viable.
Web3-native businesses selling to on-chain audiences benefit most from streaming or pull-based systems. Superfluid eliminates recurring gas costs entirely and supports flexible pricing structures that periodic billing cannot replicate. Loop bridges the gap for merchants already using Stripe or Chargebee, adding crypto autopay without disrupting existing workflows.
Many operations combine multiple approaches. A SaaS company might offer BTCPay Server for self-hosted crypto payments through one channel, Superfluid streams for DAO treasury disbursements, and Coinbase Commerce as a fallback for customers who prefer settled fiat balances. The infrastructure exists to support whatever model the business requires.