# Stripe Recurring Payments: How to Set Them Up in 2026 > A practical 2026 guide to Stripe recurring payments: how to set up subscriptions, handle failed payments and dunning, manage tax, and when an MoR fits better. - **Author**: Aarthi Poonia - **Published**: 2026-06-26 - **Category**: Subscriptions, How-To - **URL**: https://dodopayments.com/blogs/stripe-recurring-payments --- Stripe recurring payments let you charge customers automatically on a schedule, which is the foundation of any subscription business. Setting them up is straightforward for a simple plan, but the details around failed payments, proration, and tax are where most teams hit friction. This guide walks through how Stripe recurring payments work, how to set them up correctly, and the operational edge cases that decide whether your recurring revenue is reliable or leaky. It also covers when a merchant of record is the better foundation. ## How Stripe recurring payments work Stripe handles recurring payments through three core objects: a Product, a Price (which defines the amount and billing interval), and a Subscription that ties a customer to a price. When a billing cycle ends, Stripe automatically attempts to charge the saved payment method and creates an invoice. This model supports fixed monthly and annual plans, free trials, and metered usage. The key thing to understand is that Stripe is a [payment processor](/glossary/payment-processor), not a [merchant of record](/blogs/merchant-of-record-services). You remain the seller of record, so tax and chargeback responsibility stay with you. ## How to set up Stripe recurring payments The setup splits into product configuration and integration. ### Step 1: Create products and prices In the Stripe Dashboard or via the API, create a Product for each thing you sell, then attach one or more Prices. A Price defines the amount, currency, and billing interval. For a $20/month plan, you create a recurring Price with a monthly interval. ### Step 2: Collect and save a payment method Use Stripe Checkout or Elements to collect card details and create a Customer with a saved payment method. Stripe stores the method so future cycles can charge it without re-prompting the customer. ### Step 3: Create the subscription Create a Subscription linking the Customer to the Price. Stripe then manages the billing cycle, generates invoices, and attempts charges automatically. You receive webhooks for events like successful payments, failures, and cancellations so your app can react. ### Step 4: Handle the lifecycle Subscriptions change. Customers upgrade, downgrade, pause, and cancel. Configure proration so mid-cycle plan changes are billed fairly, and decide your cancellation policy (immediate vs end-of-period). ```mermaid flowchart LR A["Create Product + Price"] --> B["Save payment method"] B --> C["Create Subscription"] C --> D["Stripe charges each cycle"] D --> E["Webhook updates your app"] E --> F["Handle upgrades + churn"] ``` ## The hard part: failed payments and dunning Setting up the happy path is easy. Keeping revenue when cards fail is the real challenge. Failed payments are a major source of churn. Across the SaaS industry, involuntary churn from failed or expired cards commonly accounts for 20% to 40% of total churn. Stripe offers Smart Retries and dunning emails, but you must configure and monitor them. For the strategy behind recovery, read [dunning management](/blogs/dunning-management). A solid setup retries failed charges on an intelligent schedule, emails customers to update expired cards, and gives a grace period before downgrading or canceling. Treat this as a core feature, not an afterthought. ## Tax: the gap in Stripe recurring payments Here is the limitation that surprises growing teams. Stripe processes the payment, but you are the seller of record. That means you are responsible for registering for, collecting, and remitting sales tax and VAT/GST in every jurisdiction where you have obligations. Stripe Tax can calculate the correct amount, but it does not register you or file returns. As you sell internationally, this becomes a real operational burden. For why this is hard, see [US sales tax for SaaS](/blogs/us-sales-tax-saas) and [top sales tax challenges for cross-border businesses](/blogs/top-sales-tax-challenges-for-cross-border-businesses). ## When a merchant of record beats Stripe for recurring payments If recurring revenue is increasingly global, a [merchant of record](/blogs/merchant-of-record-services) handles the tax layer that Stripe leaves to you. With an MoR, the platform becomes the legal seller and remits tax automatically, while still running subscriptions, retries, and reporting. Dodo Payments offers recurring billing as an MoR at 4% + 40c domestic US, +1.5% international, and +0.5% for subscriptions, with tax handling included. The trade-off is that ACH and SEPA direct debit are available for one-time payments only, not for recurring subscriptions, and BACS is not supported. For a structured comparison, see [Stripe vs merchant of record](/blogs/stripe-vs-merchant-of-records) and the [best Stripe alternative](/blogs/best-stripe-alternative) guide. If you are also evaluating consumer-grade options, compare [PayPal recurring payments](/blogs/paypal-recurring-payments) and dedicated [subscription billing platforms](/blogs/subscription-billing-platforms). ## Best practices for reliable recurring payments A few habits keep recurring revenue healthy regardless of platform. Use card account updater features so expired cards refresh automatically. Send proactive emails before renewals to reduce surprise cancellations. Monitor your failed-payment recovery rate as a first-class metric, because small improvements compound across the customer base. Finally, decide your tax architecture early. Switching from being the seller of record to a merchant of record is easier before you have thousands of active subscriptions than after. ## Common Stripe recurring payment mistakes A handful of mistakes account for most recurring-revenue pain on Stripe. Underinvesting in dunning is the biggest. Teams ship the happy path, then watch involuntary churn quietly drain revenue because retries and card-update prompts were never tuned. Treat recovery rate as a tracked metric from launch. Mishandling proration is the second. If upgrades and downgrades are not prorated correctly, customers see surprising charges and open support tickets, which erodes trust. Configure proration explicitly rather than relying on defaults you have not reviewed. Ignoring the tax obligation is the third and most expensive. Stripe processes the payment, but you are the seller of record. Many teams realize too late that they owed tax registration and remittance in markets they had been selling into for months. For the broader compliance picture, see [merchant of record services](/blogs/merchant-of-record-services). ## A simple model for recurring revenue health You can summarize the health of a recurring setup with three numbers: gross MRR, recovery rate on failed payments, and net revenue after fees and tax handling. Gross MRR tells you the topline. Recovery rate tells you how much of it you actually keep when cards fail, and moving it from 50% to 70% on a typical failure rate adds several percent to retained revenue. Net revenue after the full cost stack, including tax tooling and compliance time, tells you what the setup really earns. Comparing that net number across a processor plus add-ons versus an all-in MoR is the honest way to choose. ## FAQ ### How do I set up recurring payments in Stripe? Create a Product and a recurring Price with a billing interval, collect and save a customer payment method via Checkout or Elements, then create a Subscription linking the customer to the price. Stripe charges each cycle automatically and sends webhooks your app can act on. ### Does Stripe handle sales tax on recurring payments? Stripe Tax can calculate the correct tax, but Stripe does not register you or file returns. You remain the seller of record responsible for remitting tax. A merchant of record like Dodo Payments handles registration and remittance for you. ### How does Stripe handle failed recurring payments? Stripe offers Smart Retries and dunning emails, but you configure and monitor them. A good setup retries on an intelligent schedule, prompts customers to update expired cards, and applies a grace period before downgrading, which reduces involuntary churn. ### Can I migrate Stripe recurring payments to another platform? Yes, with a staged migration. Run the new platform in parallel for new customers, validate billing and webhooks, then move active subscriptions in batches so renewals are confirmed before all volume shifts. ### When should I use a merchant of record instead of Stripe for subscriptions? Use a merchant of record when a meaningful share of recurring revenue is international and managing tax registration and remittance in-house becomes costly or risky. An MoR runs subscriptions while taking on tax and chargeback liability as the legal seller. ## Conclusion Stripe recurring payments are powerful and well documented, and for a domestic business they are often all you need. The friction shows up around failed payments and, especially, global tax, where you remain the seller of record. If your recurring revenue is going global and you would rather not build a tax operation, compare an MoR setup using our [merchant of record services](/blogs/merchant-of-record-services) guide, then review [Pricing](https://dodopayments.com/pricing) and the [subscription documentation](https://docs.dodopayments.com/features/subscription). --- - [More Subscriptions articles](https://dodopayments.com/blogs/category/subscriptions) - [All articles](https://dodopayments.com/blogs)