Bitcoin Recurring Payment Solutions Compared

Bitcoin Recurring Payment Solutions Overview

Recurring payments are the backbone of subscription businesses, SaaS platforms, and membership services. Traditional payment rails like Visa and ACH make this straightforward: the customer authorizes once, and the merchant pulls funds on a schedule. Bitcoin works differently. As a push-payment system, Bitcoin requires the payer to sign every transaction. No merchant can unilaterally debit a Bitcoin wallet.

This fundamental constraint has led to several creative approaches for enabling recurring Bitcoin payments: credit balance pre-funding, delegated wallet authorization via Nostr Wallet Connect, custodial invoice scheduling, and protocol-level support through BOLT 12 offers. Each approach makes different tradeoffs between automation, custody, and user experience.

The following table provides a high-level comparison of the major solutions available today. Each is explored in detail throughout this guide.

For a broader comparison of Bitcoin payment processors beyond recurring billing, see our payment gateway comparison tool.

Push vs Pull: Why Bitcoin Subscriptions Are Different

The core challenge with Bitcoin recurring payments stems from a fundamental architectural difference between Bitcoin and traditional payment rails.

In a pull-payment system like credit cards or direct debit, the customer provides credentials once (a card number or bank mandate), and the merchant initiates all subsequent charges. The bank trusts the merchant's authorization and debits the customer's account on each billing cycle. This creates seamless subscription experiences but introduces chargeback risk, fraud exposure, and the possibility of unauthorized charges from compromised credentials.

Bitcoin inverts this model. Every transaction requires the payer to cryptographically sign a transfer with their private key. No merchant, payment processor, or third party can move funds without the wallet holder's explicit action. This eliminates chargebacks and unauthorized debits entirely, but it means every recurring payment cycle requires some form of customer interaction or delegated authorization.

Several technical factors compound this challenge:

• BOLT 11 invoices are single-use by default, requiring a new invoice for each payment cycle
• Bitcoin price volatility makes fixed-BTC amounts impractical for fiat-denominated services
• On-chain fee variability creates unpredictable costs per billing cycle
• No native "standing order" primitive exists in Bitcoin Script

For a deeper look at how programmable money and smart payments address these limitations, see our research coverage.

Solution Deep Dives

BTCPay Server: Self-Hosted Subscription Management

BTCPay Server introduced native subscription support in v2.3.0 (December 2025), making it the most feature-complete self-hosted option. It operates in two modes: manual reminders, where customers receive email notifications at each billing interval and pay on their own; and credit balance auto-deduct, where customers pre-fund a balance on the merchant's BTCPay instance, and the system automatically deducts payments each cycle.

The credit balance model is the closest any Bitcoin-native solution comes to simulating pull payments without requiring custody of private keys. Merchants configure billing intervals (daily, weekly, monthly, or lifetime), trial periods, and grace periods. The software is free and open-source under the MIT license with zero processing fees. Merchants pay only server hosting costs, typically $8 to $30 per month for a VPS.

BTCPay also offers a separate Pull Payments feature designed for refunds, payroll, and patronage scenarios where a merchant creates a payment with a spending limit and shares a claim link.

BitPay: Custodial Invoice Scheduling

BitPay offers a dedicated Subscriptions API that automates the invoice lifecycle. Merchants create a subscription template specifying the customer, amount, currency, and schedule. BitPay then generates and emails invoices to the customer on each billing date. The customer must still click through and pay each invoice manually, but BitPay handles retry logic and can convert incoming Bitcoin to fiat or stablecoins.

BitPay supports on-chain Bitcoin, Lightning, and 15+ other cryptocurrencies with settlement in USD, EUR, GBP, or crypto. Processing fees range from 1% to 2% per transaction plus a $0.25 fixed fee, with rates tiered by monthly volume.

Alby and Nostr Wallet Connect: Delegated Authorization

Alby pioneered the most innovative non-custodial approach through the Nostr Wallet Connect (NWC) protocol (NIP-47). NWC enables a customer to connect their Lightning wallet to a service and grant it permission to request payments. The customer sets spending caps and frequency limits on the wallet side, maintaining full control over their funds.

ZapPlanner, built on NWC, takes this further: the customer connects their NWC-enabled wallet, specifies a Lightning Address to pay, sets the amount and interval (daily, weekly, monthly, yearly), and ZapPlanner automatically triggers payments. This is technically still a push payment initiated by the payer's wallet, but it simulates pull behavior because payments happen automatically once authorized.

ZapPlanner is free and open-source. Alby Hub can be self-hosted at no cost or used via Alby Hub Cloud at approximately $12.90 per month. The only variable cost is standard Lightning routing fees (typically under 0.5%).

BOLT 12 Offers: Protocol-Level Recurring Payments

BOLT 12 introduces offers: reusable payment codes that natively support recurring payment schedules at the protocol level. A merchant publishes an offer specifying a payment schedule, and the payer's wallet can automatically generate and pay invoices at the defined interval.

BOLT 12 was officially merged into the Lightning specification, and implementations exist in Core Lightning (CLN) and LDK. OCEAN Mining Pool uses BOLT 12 for payouts. However, wallet support remains limited compared to BOLT 11, and widespread adoption for subscription billing has not yet materialized. For developers building future-proof subscription infrastructure, BOLT 12 represents the most promising long-term direction.

OpenNode, Speed, and CoinGate: API-Based Approaches

OpenNode, Speed, and CoinGate do not offer dedicated subscription billing products comparable to BTCPay Server or BitPay. Instead, they provide APIs that let merchants build recurring billing logic themselves by generating invoices on a schedule and sending them to customers.

OpenNode charges a flat 1% processing fee with no setup or monthly costs. Speed claims 0% processing fees and uniquely supports USDC and USDT on the Lightning Network, enabling stablecoin-denominated recurring payments. CoinGate charges 1% per transaction and supports 70+ cryptocurrencies with settlement in EUR or crypto, making it particularly relevant for European merchants.

Stablecoins and Recurring Payments

Bitcoin price volatility is one of the biggest obstacles to recurring payment adoption. A subscription priced at 100,000 sats per month could cost $30 one month and $50 the next. Stablecoins solve this by providing dollar-denominated value on Bitcoin-compatible rails.

Speed supports USDC and USDT on Lightning for merchant payments, though it lacks a dedicated subscription billing product for stablecoins. On Spark, USDB enables instant, near-zero-fee dollar transfers natively on Bitcoin without bridging to other chains. Spark's support for streaming payments (continuous sub-second settlement) offers a foundation for recurring payment primitives in the Bitcoin ecosystem.

Outside the Bitcoin ecosystem, Stripe launched stablecoin subscription billing in late 2025 using smart contract auto-debit patterns on Base and Polygon. This approach uses EVM-based approval patterns where customers authorize recurring wallet debits via smart contracts, effectively creating true pull payments with stablecoins. Native Bitcoin (L1) lacks this smart contract functionality, and Lightning-based stablecoins inherit the same push-payment constraints as regular Lightning payments.

Feature and Fee Comparison

The following table provides a detailed comparison of capabilities and costs across all major solutions.

How to Choose a Recurring Payment Solution

The right solution depends on your technical requirements, budget, and how much control you need over the payment flow.

If you want full control and zero processing fees: BTCPay Server is the strongest option. Its subscription feature is mature, the API is well-documented, and you avoid all third-party dependencies. The tradeoff is server administration and the operational overhead of self-hosting.

If you need a managed service with fiat settlement: BitPay provides the most complete custodial subscription API with automated invoice scheduling, retry logic, and settlement in multiple fiat currencies. You pay 1-2% per transaction for the convenience.

If non-custodial automation matters: Alby with NWC is the only solution that enables automated recurring payments without requiring the customer to take action each cycle or pre-fund a balance. The customer remains in control of their wallet and spending limits at all times.

If you are building for the long term: consider integrating BOLT 12 offer support now. While wallet adoption is still early, protocol-level recurring payment support will eventually become the standard for Lightning-based subscriptions.

If stablecoin-denominated billing is important: Speed supports USDC and USDT on Lightning. For Bitcoin-native stablecoin payments, Spark with USDB provides dollar-denominated value without leaving the Bitcoin ecosystem. As the stablecoin-on-Bitcoin infrastructure matures, expect more dedicated recurring billing products to emerge in this space.

Frequently Asked Questions

Can Bitcoin handle recurring payments and subscriptions?

Yes, but not the same way as credit cards or direct debit. Bitcoin is a push-payment system, meaning the payer must authorize every transaction. Solutions like BTCPay Server's credit balance model, Alby's NWC delegation, and BitPay's invoice scheduling all work around this constraint to enable subscription billing. None of them give the merchant the ability to unilaterally debit a customer's wallet.

What is the difference between push and pull payments for subscriptions?

In a pull-payment system (credit cards, ACH), the merchant initiates charges against the customer's stored credentials. In a push-payment system (Bitcoin), the customer must initiate every transfer. Pull payments enable frictionless subscriptions but create chargeback and fraud risk. Push payments eliminate unauthorized charges but require additional tooling to automate recurring billing cycles.

Which Bitcoin recurring payment solution has the lowest fees?

BTCPay Server and Alby (with ZapPlanner) have zero processing fees. BTCPay Server is open-source and self-hosted, so you only pay server costs ($8 to $30 per month) plus network fees. Alby Hub can also be self-hosted at no cost. Speed claims 0% processing fees as a hosted service. Among custodial providers, OpenNode and CoinGate charge 1%, while BitPay charges 1-2% plus $0.25 per transaction.

How do stablecoins help with Bitcoin recurring payments?

Bitcoin price volatility makes fixed-BTC subscription amounts impractical for fiat-denominated services. Stablecoins like USDC, USDT, and USDB provide dollar-pegged value on Bitcoin-compatible rails. Speed supports USDC and USDT on the Lightning Network for merchant payments. USDB operates natively on Bitcoin through Spark, enabling instant dollar-denominated transfers without bridging to Ethereum or Solana.

What is BOLT 12 and how does it enable recurring payments?

BOLT 12 is a Lightning Network protocol specification that introduces "offers": reusable payment codes with native support for recurring schedules. Unlike BOLT 11 invoices, which are single-use, a BOLT 12 offer lets a merchant define a payment schedule that the payer's wallet can fulfill automatically. BOLT 12 has been merged into the Lightning specification and is implemented in Core Lightning and LDK, but wallet support is still growing.

Is BTCPay Server good for subscription businesses?

BTCPay Server v2.3.0 introduced a comprehensive subscription system with configurable billing intervals, trial periods, grace periods, and a credit balance model for automated payments. It is the most feature-rich self-hosted option for Bitcoin subscriptions. The main tradeoff is operational responsibility: you manage your own server, handle backups, and configure your own Lightning channels. For teams comfortable with server administration, BTCPay Server eliminates processing fees entirely.

Can I accept recurring stablecoin payments on Bitcoin?

Stablecoin recurring payments on Bitcoin are still nascent. Speed supports USDC and USDT on Lightning for one-time merchant payments but does not offer a dedicated subscription billing product for stablecoins. On Spark, USDB enables dollar transfers natively on Bitcoin with support for streaming payments. True delegated-spending subscription billing (where the merchant can auto-debit) currently requires EVM-based smart contract patterns and is not available on Bitcoin L1 or Lightning.

This tool is for informational purposes only and does not constitute financial advice. Data is approximate and based on publicly available information as of mid-2026. Pricing, features, and availability change frequently. Always verify current details on each provider's website before making decisions.