Bitcoin for US Subscription Businesses: Recurring Payment Challenges

Subscription billing looks simple on paper: charge the customer the same amount on the same date every month, and the software handles the rest. Credit cards, ACH transfers, and even PayPal all support that model because they use a pull payment system, where the merchant is authorized to reach into the customer's account and collect funds automatically.

Bitcoin does not work that way. The protocol is designed around push payments: the person who holds the coins decides when, and to whom, those coins move. No third party can pull funds from a Bitcoin wallet without the private key. That single architectural fact reshapes how a US business can offer subscription-style services when customers want to pay in bitcoin.

Why the Push-Only Model Breaks Traditional Subscriptions

When a customer pays by credit card, they hand your processor a standing authorization. Your billing software fires a charge on the renewal date, the card network processes it, and funds appear in your account. The customer does nothing after the first setup.

With bitcoin, that standing authorization cannot exist. Every transaction requires a fresh digital signature from the payer's private key. A business cannot store a customer's private key (and should not, for security and liability reasons). Even if the customer uses a custodial wallet where an exchange holds the key on their behalf, that exchange will not honor external billing instructions.

The practical result: a subscription business accepting bitcoin must either accept that customers will initiate payments themselves each period, or build workflows that prompt and guide that action reliably.

This is not a bug that will be patched away. It is a property of how Bitcoin's security model works, and it is part of why some businesses view bitcoin as a poor fit for recurring revenue, while others see it as an opportunity to attract customers who actively prefer non-custodial, privacy-respecting payment options.

Workarounds US Businesses Are Using Today

Several approaches have emerged to make recurring billing workable in a Bitcoin context. None of them replicate the seamlessness of a credit card autorenewal, but they each reduce friction in different ways.

Scheduled invoice reminders. The most straightforward approach is to treat bitcoin subscriptions as manual renewals and automate the notification layer. A few days before the renewal date, the business sends the customer an invoice with a fresh payment address and a payment deadline. Invoicing clients in bitcoin covers the mechanics in detail, but the key point here is that most Bitcoin-capable invoicing tools can be configured to send these reminders automatically based on a recurring schedule. The customer still pushes the payment, but they receive a clear prompt and a specific address to send to.

BTCPay Server recurring payment templates. BTCPay Server, the open-source self-hosted payment processor, includes a "Pull Payments" feature and a subscription-style invoicing module. These let a merchant create a recurring invoice template that generates a new invoice and notifies the customer on a set schedule. The customer still initiates each payment, but the process is structured enough that it resembles a subscription from the customer's perspective. Because BTCPay Server runs on your own infrastructure, you control the cadence, the reminders, and the grace period logic. BTCPay also supports Lightning Network payments, which can reduce fees for smaller subscription amounts.

Strike's recurring invoice features. Strike, a US-based Lightning-enabled payments platform, has added tooling for recurring Lightning invoices aimed at creators and small businesses. The flow varies from BTCPay in that Strike is a hosted service rather than self-hosted software, which trades some control for easier setup. Recurring Lightning invoices can be sent to customers via email or a shareable link, and Strike handles the reminder logic. One caveat: because Strike is a custodial service, the business's funds are held by Strike until withdrawn, which introduces counterparty considerations that a self-hosted setup does not.

Stablecoin subscriptions as a hybrid. Some businesses that want predictable recurring revenue in crypto use stablecoins (USDC, for example) rather than bitcoin for their subscription layer, since some stablecoin protocols support smart-contract-based pull payment authorizations on certain chains. That is outside the scope of pure Bitcoin, but it is worth knowing that the workaround sometimes involves moving the subscription component off Bitcoin entirely.

None of these solutions match the zero-friction renewal of a card-on-file. Businesses that have made recurring bitcoin billing work tend to report higher voluntary churn because some customers simply forget to pay or let their subscription lapse between periods. Building in clear grace periods, well-timed reminders, and a simple renewal link reduces that attrition meaningfully.

Pricing Volatility and Recurring Amounts

If you charge a fixed amount in bitcoin each period, the USD value of that subscription will fluctuate with bitcoin's price. A monthly subscription priced at 0.001 BTC might be worth $70 one month and $110 the next.

Most subscription businesses avoid this by invoicing in USD and requesting the current bitcoin equivalent at the time of payment. The customer sees "Your renewal: $49.00, payable as approximately 0.00047 BTC at today's rate." The invoice system calculates the BTC amount dynamically using an exchange rate feed, and the customer pays in bitcoin. This approach keeps subscription revenue predictable in USD terms. How to price your products when you accept bitcoin covers the mechanics of dynamic pricing and rate feeds in more depth.

IRS Rules: Each Payment Is a Separate Taxable Event

This is where recurring bitcoin billing has a significant compliance dimension that credit card subscriptions do not.

Under IRS guidance, bitcoin is classified as property, not currency. That classification has been in place since Notice 2014-21 and was reinforced in subsequent IRS FAQs and Rev. Rul. 2023-14. When a customer pays a recurring bitcoin subscription, they are disposing of property. If the bitcoin they spend has appreciated since they acquired it, that disposal is a taxable event for the customer, and they may owe capital gains tax on the difference between their cost basis and the fair market value at the time of payment.

For US customers, this means a monthly bitcoin subscription can generate twelve separate taxable events per year, each requiring them to track the cost basis of the specific bitcoin units spent. Most customers using tax software or a crypto tax tool can handle this, but it is a material difference from paying by credit card. Some customers choose to pay subscriptions from bitcoin they acquired at a higher price (so there is no gain, or even a loss to harvest), while others prefer to pay from recently purchased coins to minimize the accounting complexity.

For the business on the receiving end, the IRS treatment is also property-based. When you receive bitcoin as payment, the fair market value of that bitcoin at the time of receipt is ordinary income, reported the same way as any other business revenue. If you later sell or convert that bitcoin, any change in value from receipt to sale is a separate capital gain or loss event for your business. How you denominate and track incoming subscription payments in your accounting system affects both your income recognition and your subsequent gain or loss calculations.

These rules can change, and individual situations vary considerably. A tax professional familiar with digital asset reporting can help a subscription business set up a compliant workflow. The IRS website at irs.gov/businesses/small-businesses-self-employed/virtual-currencies is the primary source for current guidance.

For subscription businesses that also hit the $10,000 threshold in a single transaction or series of related transactions, Form 8300 reporting rules may apply. The FinCEN and IRS jointly administer those requirements, which apply regardless of payment method.

If your subscription business operates across state lines, state money-transmitter licensing rules can also come into play depending on your specific model. This is an area where requirements vary significantly by state and have been evolving, so confirming current requirements with a qualified professional is prudent before launching a bitcoin subscription product. It is also worth reading up on handling refunds and chargebacks with bitcoin before you set cancellation and refund policies for your subscribers.

Frequently Asked Questions

Can I set up a true automatic bitcoin charge that does not require the customer to act each period? No. Bitcoin's architecture requires the coin holder to sign every transaction. There is no mechanism that allows a merchant to pull funds from a customer's wallet automatically. Every recurring bitcoin payment requires the customer to initiate the transfer, either manually or by responding to a system-generated invoice prompt.

Is BTCPay Server free to use for recurring invoices? BTCPay Server is open-source and free to use as software, but you do need to host it somewhere, which involves server costs. Many businesses run it on a VPS starting around $5 to $10 per month. The recurring invoice and pull payment features are included in the core BTCPay Server installation at no additional license cost.

Do my customers owe taxes every time they pay a bitcoin subscription? Under current IRS rules, yes, if the bitcoin they spend has appreciated since they acquired it, that payment is a taxable disposal of property. Each subscription renewal can be a separate taxable event. Customers who have held bitcoin with an unrealized gain will want to factor this into their decision to pay in bitcoin versus another method. This is a factual description of how the current rules work, not tax advice. Customers should consult a tax professional or verify current IRS guidance for their specific situation.

What happens if a customer misses a bitcoin subscription renewal? Unlike a credit card that simply declines at renewal, a bitcoin subscription just does not receive payment by the due date. Your system needs to handle this explicitly: define a grace period, automate a follow-up invoice or reminder, and decide when to suspend access. This lapse-and-reinstate logic has to be built into your subscription management workflow, since there is no underlying payment network to flag a missed payment the way a card processor would.

Can Lightning Network payments make bitcoin subscriptions easier? Lightning can reduce fees on small recurring payments and allows near-instant settlement, which makes the payment experience faster once the customer initiates it. Some tools like BTCPay Server's Lightning integration and Strike support Lightning-based recurring invoices. But Lightning does not change the push-payment model: the customer still has to act each period. It makes the act of paying easier, not unnecessary.