How to Connect Stripe to Webflow Memberships for Recurring Paid Subscriptions

Why Stripe Plus Webflow Memberships Is a Real Business Stack in 2026

A client reached out last month wanting to launch a paid newsletter with premium case studies behind a paywall. Her budget was thin, her tech stack already included Webflow, and Substack did not offer the design flexibility she wanted. Webflow Memberships with Stripe for billing gave her a production-ready paid subscription site for under $60 per month all-in, and she shipped it in three weeks.

This combination has quietly become a serious alternative to Memberful, Patreon, and Ghost for founders who already use Webflow. According to Webflow's November 2025 product update, Memberships usage more than tripled year-over-year, driven largely by small publishers and creators moving off WordPress and Substack. Stripe reports over 4 million active merchants using their platform as of 2025, making it the default payments layer for most modern subscription businesses.

This tutorial covers how to connect Stripe to Webflow Memberships for recurring subscriptions specifically, including pricing plan setup, webhook configuration, gated content logic, and the common pitfalls that trip up first-time setups.

What Do Webflow Memberships and Stripe Each Actually Handle?

Webflow Memberships handles user accounts, authentication, access groups, and gated content visibility rules. Stripe handles payment processing, subscription billing, tax calculation, invoicing, and refunds. The two platforms connect through webhooks so that a successful Stripe payment grants a user membership access on Webflow, and a canceled Stripe subscription revokes it.

Webflow Memberships is built into Webflow's CMS and Business plans. Users can sign up, log in, reset passwords, and manage their profile inside your Webflow site without leaving it. Access groups let you tag members into tiers like Free, Basic, and Premium, and CMS items and pages can be restricted to specific access groups.

Stripe covers the money side. It issues invoices, handles card updates, manages failed payments with retry logic, computes and remits sales tax or VAT where required, and gives you a dashboard to see revenue and churn. For any serious subscription business, Stripe is effectively non-negotiable because no other payments platform matches its breadth of features.

What Are the Prerequisites Before You Start the Integration?

You need a Webflow site on at least the CMS or Business plan with Memberships enabled, a verified Stripe account with your bank details connected, and a clear plan for your pricing tiers before you touch any code or settings. Skipping the pricing planning step causes the most common mistake: building the wrong access group structure and having to rebuild it.

Webflow's Memberships feature is part of the CMS and Business site plans, not the Basic plan. As of 2026, the CMS plan runs $29 per month billed annually, and the Business plan runs $49 per month billed annually. Both include Memberships with unlimited members on paid subscriptions. Confirm your site is on one of these tiers before proceeding.

Your Stripe account needs to be fully activated with your bank details, business verification, and tax settings complete. If your Stripe account is in test mode only, you can integrate and test the flow, but you cannot accept real payments until you switch to live mode. My broader tutorial on setting up Webflow Memberships for gated content covers the general Memberships configuration that precedes this specific Stripe integration.

How Do You Create the Pricing Plans in Stripe First?

Create your pricing plans in Stripe before touching Webflow, because the plan IDs from Stripe are what you reference in the Webflow integration. Go to Stripe Dashboard, click Products, create a product for each membership tier, and add a recurring price with your chosen amount and billing interval.

For a typical paid newsletter setup, you might create two products in Stripe. One called Basic with a $10 per month recurring price. One called Premium with a $25 per month recurring price. Each price gets a unique ID starting with "price_" that you will copy into Webflow later. Write these IDs down or keep the Stripe tab open, because you need them in the next step.

Stripe also lets you create annual pricing alongside monthly. If you want to offer both $10 per month and $100 per year for your Basic tier, create two prices inside the same Basic product in Stripe. Each price ID is referenced separately in Webflow, so annual and monthly versions appear as separate plan options to your members.

How Do You Configure the Plans Inside Webflow Memberships?

Inside Webflow Site Settings, navigate to the Memberships tab, then Paid Plans, and click Add Paid Plan. Webflow prompts you to connect your Stripe account via OAuth, then lists all active Stripe products so you can map them to Webflow access groups. This is where Stripe pricing meets Webflow access control.

When you add a Paid Plan in Webflow, you pick which Stripe product and price to connect, then pick which Webflow access group the successful subscriber is added to. For example, you might set up Basic Monthly connected to your Stripe price_ABC123 which adds the member to your Webflow access group called Basic Members. Repeat for each plan combination.

The access group is the key mechanism for gating content. Once a member is in the Basic Members access group, they get access to every CMS item and every page where you have set Basic Members as the permitted group. This lets you control exactly what Basic subscribers can see versus Premium.

How Do Webhooks Keep Webflow and Stripe Synchronized?

Webhooks are automatic messages Stripe sends to Webflow whenever a subscription event happens: new signup, renewal, cancellation, payment failure. Webflow listens for these webhooks and updates the member's access group accordingly. Without webhooks, your Webflow site would not know when a member cancels or when their card is declined.

When you connect Stripe to Webflow Memberships via the native OAuth connection, Webflow automatically registers the required webhooks in your Stripe account. You do not need to configure webhooks manually. You can verify they exist by going to Stripe Dashboard, Developers, Webhooks, and confirming the Webflow endpoint is present and active.

If webhooks fail or you disconnect and reconnect Stripe, access group assignments can drift. Stripe sends webhook delivery reports showing success and failure rates per endpoint, which is useful to check monthly if you are running a live paid membership site.

How Do You Restrict Content to Specific Paid Members?

Restrict content to specific paid members by setting Access Permissions on individual pages or CMS items. Inside a page or CMS collection item in the Webflow Designer, click the gear icon for settings, scroll to Access, and select which access groups can view this content. Only members belonging to the selected groups see the page.

This works for both static pages and CMS-driven content. If you have a blog collection where some posts are Free and some are Premium, you can add an Access Group reference field to the collection and set each post's access per item. Webflow's CMS then renders the post only to members with the matching access group, and non-members see a locked preview with a sign-up prompt.

For the preview experience on locked content, Webflow lets you define what members see when they try to access something they have not paid for. The common pattern is a teaser first paragraph followed by a "Subscribe to continue reading" message linking to your pricing page.

What Tax and VAT Settings Do You Need to Configure?

Enable Stripe Tax inside your Stripe Dashboard to automatically calculate, collect, and remit sales tax or VAT based on your customer's location. Stripe Tax launched in 2021 and now supports more than 60 countries. Skipping this step creates legal exposure in any jurisdiction where you cross the tax registration threshold.

For a US-based creator selling digital memberships, Stripe Tax will calculate sales tax based on the customer's billing address and charge the correct amount on top of your subscription price. For an EU-based creator, Stripe Tax handles VAT including reverse-charge for B2B customers with valid VAT IDs. Stripe Tax charges a small fee per transaction, typically 0.5 percent in the US, which is far cheaper than hiring an accountant to handle multi-jurisdiction filings manually.

The key setting to verify is that your Stripe product is set to the correct tax category. Digital memberships are usually classified as "Digital services - general" or similar. The wrong category leads to incorrect tax rates for some customers, which you will only notice when a customer emails you about a surprising tax line.

How Do You Test the End-to-End Flow Before Going Live?

Test the end-to-end flow using Stripe Test Mode and a Webflow staging environment before accepting real payments. Stripe provides test card numbers that simulate successful payments, failed payments, and various edge cases without charging real money. Run through every subscription path including signup, tier upgrade, cancellation, and resubscription.

Stripe's documentation lists specific test card numbers for different scenarios. Card number 4242 4242 4242 4242 simulates a successful Visa charge. Card 4000 0000 0000 0002 simulates a declined card. Card 4000 0027 6000 3184 simulates a 3D Secure authentication flow. Use these in test mode to verify your Webflow site handles each case gracefully, with the correct access group state after each event.

Before switching to live mode, audit your member-only pages by logging in as a test user at each access tier and verifying they see exactly what they should. Common bugs at this stage include forgetting to restrict one page, mislabeling an access group, or having stale cached pages showing premium content to free members. Check in an incognito browser to rule out caching artifacts.

How Do You Launch and What Should You Monitor in the First Month?

Switch Stripe from test mode to live mode, publish your Webflow site, and announce the membership launch to your audience. In the first month, monitor Stripe churn rate, Stripe webhook delivery success rate, Webflow Memberships signup funnel, and any customer support tickets about access issues. These four signals catch most integration problems early.

Stripe Sigma or the standard Stripe Dashboard will show you churn rate and monthly recurring revenue. Target less than 10 percent monthly churn for a paid newsletter or membership community. Stripe webhook delivery should be at 99 percent or higher. Anything lower suggests connectivity issues that will eventually cause access group drift on Webflow.

For the adjacent business side of running a paid content site on Webflow, my post on how to price retainers for ongoing Webflow work covers some of the financial considerations that apply equally to running a subscription membership versus a client retainer model.

If you want help setting up Webflow Memberships with Stripe for your own paid site or migrating from Substack, Ghost, or Memberful, I am happy to walk through it. Let's chat.