Webflow subscriptions not working? What changed, and what to use instead

What Webflow scheduled for January 29, 2026

Webflow's Subscriptions article lists User Accounts as a requirement for selling a subscription, and its purchase flow sends any buyer who isn't logged in to the sign up page before checkout. Webflow's sunset notice says User Accounts can't be added to any new or existing site and stop working on January 29, 2026, which leaves the Subscribe now button no account to send the buyer to. For a site that still had User Accounts on at that date, the notice lists the rest: members can no longer log in, User Accounts pages are migrated to regular static pages, content gates are removed, and the User Accounts APIs and webhooks go away.

The charges are a different matter. Webflow's sunset notice says that if you use paid subscriptions, "your subscriptions will still be available in your Stripe account, and subscribers will continue to be charged."

Where to start

Existing subscribers: still billed, with nowhere to manage it

A Webflow subscriber could see and cancel a subscription in one place, the subscriptions element on the User account page. Once User Accounts are off, that page becomes a static page and members can't log in, so a subscriber who wants to cancel or replace an expiring card has to email you. Stripe's no-code customer portal gives them that page back, without code:

1. In the Stripe Dashboard, open the customer portal settings and click Activate link.
2. Choose what subscribers may do. Updating payment methods and canceling are on by default. Updating a shipping address is off by default, so turn it on if you ship.
3. In Webflow, select a button or text link, open its link settings, choose the URL link type, and paste the portal link.

A subscriber enters their email and Stripe emails them a link that opens their portal. If someone says the email never came, the address they typed doesn't match a Stripe customer: search for it in the Stripe Dashboard. The portal shows invoices, not orders, and its subscription settings cover switching plans, changing quantities, and canceling. Skipping a single renewal is not one of them.

Signing up new subscribers

The right replacement depends on what the subscription is. A Stripe Payment Link and a Flint payment link both work as the URL of a Webflow button, with no custom code. A membership tool installs on the site itself.

Members-only content: a membership tool

If subscribers pay for access to pages, videos, or downloads, you need log-ins and gates, not only billing. Webflow's top recommended partners for gated content and memberships are Outseta and Memberstack. These install with a script on your site or a Webflow app rather than a link: Memberstack's Webflow guide has you paste its header script into Site settings > Custom code, which needs a Webflow plan that allows custom code, or install its app from the Webflow Apps Marketplace.

A simple recurring charge: a Stripe Payment Link

For a service, a donation, or a digital product with no gate, a Stripe Payment Link is the shortest path, and your Stripe account is already set up from Webflow Ecommerce. In the Stripe Dashboard, open Payment Links, click New, select or add a product with a recurring price, and click Create link. A link with a recurring price starts a subscription for each buyer. Paste the link into a Webflow button's URL field.

To show Stripe's own button on your Webflow page instead, open the link, click Buy button, and copy the embed code it generates:

<script async src="https://js.stripe.com/v3/buy-button.js"></script>
<stripe-buy-button
  buy-button-id="buy_btn_..."
  publishable-key="pk_live_..."
></stripe-buy-button>

Paste it into a Webflow Code Embed element. Code Embed needs a Core, Growth, Agency, or Freelancer Workspace, or an active Site plan. Each renewal then creates an invoice and a payment in Stripe, and subscribers manage the subscription in the portal above.

A subscription box: every renewal has to become a shipment

Webflow never handled this part. Its Subscriptions article says that when a subscription renews, "no new order is generated," and that a renewal needing a physical product sent out means you'll "manually track customers' renewal dates." The User Accounts sunset did not create that gap, and a replacement that only bills leaves it open.

A Stripe Payment Link with a recurring price can collect a shipping address at signup. Each renewal is still an invoice and a payment rather than an order to pack. Stripe documents shipping options for Checkout in payment mode only, and a Payment Link with a recurring price creates a subscription. Stripe doesn't document whether such a link accepts shipping rates or charges them on renewals, so test it in a sandbox before you rely on it. The packing list is something you assemble from Billing > Subscriptions each cycle, and a subscriber who wants to skip a month has to ask you. Shipping physical products on Stripe subscriptions covers the workarounds in detail.

Moving subscribers without charging them twice

Wherever subscribers go next, switch them at the end of the period they already paid for. In the Stripe Dashboard, open Subscriptions, click the overflow menu on a subscription, choose Cancel subscription, and pick the end of the period with no refund. The subscription runs until the paid time is used, then Stripe stops renewing it. Send that subscriber your new signup link to use on that date, so the new checkout charges once, when the old one would have.

• Deleting a subscription product in Webflow does not stop billing. Webflow's docs say it "won't automatically cancel any active customer subscriptions."
• Webflow won't let you disconnect Stripe while any customer subscription is active, so cancel the subscriptions first.

Subscription boxes on Flint, without code

Flint is a payments API with commerce built in, and its dashboard sets up a subscription box without code. Each renewal is an order with the subscriber's address, a shipping charge, tax for that address, and a fulfillment you ship like any other order. Flint has no Webflow app; your Webflow site links to Flint's hosted checkout.

1. Add the box to your catalog as a product with shipping set up.
2. In the Flint dashboard, open Subscriptions > Plans and click New plan. Set the box, the price, how often it ships, and the delivery options subscribers can choose.
3. Open the plan and click Create payment link. Copy the link's URL.
4. In Webflow, set a button's URL link to that address.

The checkout collects the shipping address, shows the plan's delivery methods with their prices, and makes the signup order the first shipment. Before each renewal (three days ahead for a monthly box), Flint emails the subscriber what is shipping, where, and the estimated total, with links to skip, change the address, or pause. Subscribers sign in to their Flint account with a six-digit code sent to their email, and can skip, pause, change the address, or cancel there; you decide whether skipping, pausing, and address changes are allowed, and canceling always is. Subscriptions > Upcoming shipments projects the renewals due to ship, so you know what to pack.

Flint's hosted checkout can't be shown inside an iframe, so on Webflow it is a link. Putting the form on your own page is embedded checkout, which takes code. The subscriptions features page shows the subscriber's side.

The same link from the API

If someone on your team writes code, the link is one request with the plan's ID. This is optional; the dashboard steps above make the same link.

curl -X POST https://api.withflintpay.com/v1/payment-links \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Idempotency-Key: payment-link-coffee-box-001" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Monthly coffee box",
    "subscription_plan_id": "plan_1kmn0aExample",
    "customer_collection": {"require_email": true}
  }'

The response carries url, the address to put behind the Webflow button. Every completed checkout creates a subscription for the buyer's email.

Importing subscribers who already have a card on Flint

Flint can take over a subscription partway through a period the buyer already paid for. An imported billing start continues that period without charging, and the first charge is at its end:

curl -X POST https://api.withflintpay.com/v1/subscriptions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Idempotency-Key: import-sub-ada-001" \
  -H "Content-Type: application/json" \
  -d '{
    "subscription_plan_id": "plan_1kmn0aExample",
    "customer_id": "cus_1kmn0aExample",
    "payment_method_id": "pm_1kmn0aExample",
    "billing_start": {
      "type": "imported",
      "period_started_at": "2026-10-01T00:00:00Z",
      "completed_cycles": 7
    },
    "delivery": {
      "type": "shipment",
      "delivery_method_id": "dmet_1kmn0aExample",
      "destination": {"type": "customer_address", "customer_address_id": "caddr_1kmn0aExample"}
    }
  }'

completed_cycles carries the shipment count over, so a subscriber on their eighth box doesn't get a first-box insert. Subscriptions > Import subscriptions in the dashboard does the same from a CSV, checking every row before it creates anything. Both need the customer and a saved card already in Flint, and cards saved in your Stripe account aren't moved. For Webflow subscribers, that makes the period-end switch above the no-code route.

A Stripe subscription link and a Flint plan link, side by side

Questions, answered

Sources

All sources accessed October 9, 2026.

• Webflow Updates: Deprecating Logic and User Accounts (December 11, 2024)
• Webflow Help Center: User Accounts sunset
• Webflow Help Center: Subscriptions
• Webflow Help Center: Webflow User Accounts overview
• Webflow Help Center: Link settings
• Webflow Help Center: Custom code embed
• Memberstack Help Center: Webflow Installation Gotchas
• Webflow Integrations: Memberstack
• Stripe docs: Create a payment link
• Stripe docs: Create an embeddable buy button
• Stripe docs: Customize checkout for Payment Links
• Stripe docs: Charge for shipping
• Stripe docs: How subscriptions work
• Stripe docs: Activate the no-code customer portal
• Stripe docs: Configure the customer portal
• Stripe docs: Cancel subscriptions

Related

• Shipping physical products on Stripe subscriptions: shipping charges, addresses, and fulfillment when renewals are invoices.
• Order history in the Stripe customer portal: what subscribers see in the portal you link from Webflow, and what it leaves out.
• Does Stripe track inventory?: for boxes with a limited run, how to stop selling once the stock is gone.
• Flint subscriptions: plans, renewals as orders, and the subscriber's account.
• Ship physical products on a subscription: plans with delivery methods, renewal reminders, and delivery holds.
• Subscription signup links: the hosted signup page behind the Webflow button.
• Customer accounts: the subscriber's account, your branding and domain on it, and what subscribers may change.