How to Connect Stripe to Framer and Start Selling Today

A Framer site can take Stripe payments today, and it can do it through four practical routes. The missing native one-click Stripe app is a limitation, but it’s not a reason to switch platforms.

The reason no one-click Stripe app exists is structural. Stripe’s own App Marketplace lists Webflow, Squarespace, Shopify, Adobe Commerce, and PrestaShop under its Commerce category, but there’s no Framer app. Framer itself offers no native ecommerce and no native Stripe integration. Every payment route connects Framer to Stripe directly, or it runs through a Stripe-powered tool.

Framer Forms handles lead capture only. It can’t process a payment or trigger a payment flow, and there’s no built-in order system: after a customer pays, nothing happens automatically from Framer’s side. No confirmation email, no receipt, no fulfillment notification.

What Framer does have is a marketplace of third-party ecommerce plugins. Frameshop, FramerFlo, Framer Commerce, StripeKit, and Stripe Payment Gateway all appear there, alongside a free Checkout Page plugin published on 30 July 2026. These aren’t official Stripe apps, but they close the gap in different ways.

The real question isn’t whether you can connect Stripe to Framer. It’s which route fits what you’re selling. We’ll cover four routes. Stripe Payment Links is the fastest option. Stripe Checkout gives you a hosted redirect and an embedded Buy Button. Stripe-powered Framer plugins live inside the canvas. Full ecommerce layers like Frameshop, FramerFlo, Framer Commerce, and Foxy come in when your needs outgrow a simple checkout.

Each route trades simplicity against control. A digital download, a subscription, a booking, and a physical product all point to different answers.

Stripe Payment Links: The Fastest Way to Sell on Framer

Stripe Payment Links gives you the shortest route from a Framer site to taking payments. You don’t need a plugin, code, or canvas editing. You create a link in the Stripe Dashboard, paste it into a button’s Link property in Framer, and you’re live. Setup takes under five minutes, which makes it the fastest way to start selling on Framer.

Here’s the setup:

1. In the Stripe Dashboard, create a Payment Link. Choose one-time or recurring pricing, set the amount, or let customers choose their own.

2. Copy the Payment Link URL Stripe generates.

3. In Framer, select the button that will act as your buy button and paste the URL into its Link property.

It supports both one-time and recurring payments, and it works for goods, services, subscriptions, tips, and donations. Stripe also automatically shows the most relevant payment methods per visitor, including Apple Pay and Google Pay, so mobile buyers get a friction-free checkout without you configuring anything.

The trade-off is that you’re selling through Stripe’s checkout, not yours. The limits are worth knowing before you commit:

• The checkout opens on a generic Stripe-hosted page with Stripe’s branding, not yours

• No custom design for the checkout experience

• No embed option to keep buyers on your site

• No pop-up checkout

• No upsells or order bumps after the initial purchase

• No cart recovery for abandoned checkouts

• No inventory management or product browsing

Payment Links is a transaction tool rather than a storefront. It answers whether they can pay you, and leaves everything else to you.

Getting buyers back to your site afterward is a two-minute job. Create a /thank-you page in Framer, then open the Payment Link’s “After payment” settings and set it to redirect customers to that URL. If you’re managing multiple products, add a Link field to a CMS Collection and bind the CTA button’s Link property to that field, so each product card pulls the right payment URL automatically.

It’s the right call for a digital download, a simple service, a tip jar, or a donation page. Where it falls short is any scenario that needs control over the post-purchase experience, inventory, or the checkout itself. The other routes in this article cover those needs.

Stripe Checkout on Framer: Hosted Redirect and Embedded Buy Button

Stripe Checkout is the next step up from Payment Links. It’s a low-code integration that works in one of two ways: it redirects the customer to a Stripe-hosted page, or it embeds the checkout form directly into your Framer site. One thing to keep in mind: Stripe Checkout still needs a backend or server to initiate a checkout session. Low-code doesn’t mean no code, and that distinction matters if you’re a solo founder who wants to avoid touching a server altogether.

That’s where the Stripe Buy Button comes in. It’s Framer’s no-code path to the same Checkout engine, and it sidesteps the backend requirement entirely. The Buy Button generates a snippet you paste into your Framer site, and it gives you the choice between the hosted redirect and the embedded form.

The hosted redirect is what it sounds like: the customer clicks your buy button and leaves your site for a Stripe-hosted checkout page. The embedded form keeps the checkout on the page itself, so the buyer never leaves your Framer site. That difference matters in practice. An embedded form typically improves conversion rates because there’s no moment where the customer is pulled away to a different domain and has to decide whether to trust it and come back.

Here’s the Framer-specific setup for the Buy Button:

1. In the Stripe Dashboard, go to Payment Links → Buy button and generate a code snippet.

2. In Framer, paste the full snippet into an Embed component in HTML mode.

3. If you’re using the Buy Button across multiple pages, load the Stripe script once via Project Settings → Custom Code (end of body), then add only the button element per page’s Embed component. Adding the full snippet on every page creates duplicate script tags, which can break pages.

The Buy Button also supports a couple of useful attributes. client-reference-id lets you pass your own identifier through to Stripe for reconciliation or webhooks, and customer-email pre-fills the buyer’s email at checkout so returning customers don’t retype it.

The decision between Checkout and Payment Links comes down to whether you need the embedded form. If a hosted redirect is acceptable, Payment Links is simpler and requires zero configuration beyond pasting a URL, but if keeping customers on your Framer site matters for your conversion rate, the Buy Button’s embedded form is worth the extra setup. It’s the first route in this article that gives you a checkout that feels like part of your site.

Plugins That Connect Stripe to Framer Without a Server

If you want to skip the backend entirely, two Framer marketplace plugins connect your site to Stripe without a server: StripeKit and Stripe Payment Gateway. Both live inside the Framer canvas, both use Stripe’s API keys rather than OAuth, and both get you to a working checkout without writing code. Here’s how the two stack up side by side.

The difference between the two comes down to how deep the integration goes. StripeKit is the more ambitious plugin: it syncs your existing Stripe products into Framer automatically, keeps pricing and billing intervals in step, and even lets you create new products without leaving the canvas. The cached Payment Links are a small touch, but they matter if you’re editing a storefront repeatedly and don’t want to wait on Stripe’s API every time you preview a page. StripeKit is free, which makes it an easy starting point.

Stripe Payment Gateway takes a lighter approach. It’s essentially a polished “Pay with Stripe” button that you wire to a Payment Link you’ve already created in the Dashboard. Its strength is breadth: 46+ countries and 40+ payment methods covers an international audience, and the customizable button means you can match it to your site’s look. The catch is the free tier locks you to test keys, which is fine for development but useless for real sales. The Pro version costs a one-time $19 for live keys, with no subscription.

For most Framer builders, we’d lean toward StripeKit if you want products to stay in sync automatically and you don’t mind working with a restricted API key. Stripe Payment Gateway makes sense if you already have Payment Links set up and just need a flexible, well-styled button that reaches more payment methods. Both let you connect to Stripe without a server, which is a real advantage over the Checkout integration if you want to avoid the Dashboard as much as possible.

Full Ecommerce Layers: Frameshop, FramerFlo, and Framer Commerce

Everything so far gets you a checkout, but a checkout isn’t a store. If you need inventory tracking, shipping logic, tax calculation, or an order dashboard, you’ve outgrown Payment Links and even the plugins above. That’s where full ecommerce layers come in. These are Framer plugins and hosted services that plug into a Framer site and bring the store machinery along with them.

Here’s how we see the decision: do you want the store inside Framer, or do you want a proven backend running the commerce while Framer handles the look? Frameshop and FramerFlo sit on the first side. Frameshop is the most Framer-native option of the lot, since your products live in the Framer CMS and sync to Stripe, which means you never leave the canvas to run your store. FramerFlo has the same plugin-native feel but adds operational features like an order dashboard and inventory management, which matter once sales start coming in.

Framer Commerce and Foxy take the opposite approach. Framer Commerce is really a Shopify store wearing a Framer front end. Shopify quietly handles inventory, shipping, tax, and multi-currency, while Framer makes the storefront look good. Foxy is similar in spirit, a hosted cart and checkout layer that plugs into your Framer site, with the bonus that receipts and subscription billing come standard. If you’re already running or planning a Shopify store, Framer Commerce is the natural fit. If you want a hosted layer without committing to Shopify’s whole ecosystem, Foxy handles those tasks for you.

The plugin-native options keep everything in one place and feel lighter to manage, but they lean on you to stay on top of the operational details. The hosted options hand that off to a dedicated commerce platform, at the cost of a subscription and a bit of distance between your storefront and the system running it. Our Framer ecommerce vs Shopify comparison weighs that same split in more depth.

How to Handle Subscriptions and Recurring Payments on Framer

Stripe handles the actual charging, and the third-party tools that connect to it handle the membership logic. That split means the hard part, reliably billing a customer every month, is never something you build yourself.

Here’s what’s available:

• Stripe Payment Links support recurring payments out of the box, so a simple subscription can be a single link on a Framer button. You set the billing interval in the Dashboard, paste the link, and Stripe handles the rest. One caveat: the “Customers choose what to pay” option works for donations and tips, but it doesn’t support recurring, so it can’t power a subscription where the customer picks their own amount.

• Outseta and Thenty are the membership tools for gated sites. Both connect to Stripe and handle authentication, page gating, and recurring billing on Framer. Outseta is the broader platform, bundling billing with CRM and auth in one place. Thenty is lighter, focused on digital product delivery with gated access rather than a full business-operations suite.

• FrameAuth V2 gates pages or content sections and accepts payments via Stripe or Lemon Squeezy. It manages members, subscriptions, and access tiers, with overrides like ShowIfSignedIn, ShowIfWithTag, and ShowIfWithoutTag so you can tailor what each visitor sees. It also supports Stripe test mode, which lets you validate the whole flow before taking a real payment.

• Stripe Checkout’s embedded form and Buy Button also support recurring pricing, so if you’re already using either of those routes for one-time sales, a subscription is just a pricing configuration change, and if you’re on Foxy’s hosted checkout layer, subscription billing comes standard there too.

Our take on choosing between these comes down to what your subscription actually protects. If you’re selling access to a single product, a course, or a newsletter, a Payment Link on a button is enough. You don’t need a membership platform to gate content you’re not really gating. But the moment you have member-only pages, tiered access, or the need to know who’s logged in and what they’re entitled to see, a Payment Link stops being the answer. That’s when Outseta or FrameAuth becomes necessary, because the value isn’t in the billing, it’s in the access control wrapped around it.

What Happens After Payment: Delivery, Receipts, and Redirects

Framer has no order system. When a customer pays, nothing happens automatically on your side: no confirmation email, no receipt, no fulfillment notification. The payment goes through, and then it’s on you to make the post-purchase experience happen with an external automation.

The tools to fill that gap are straightforward, and each of the routes in this article has a way to hand off to them:

• For Payment Links, open the link’s “After payment” settings and set it to redirect to a /thank-you Framer page. That brings the buyer back to your site instead of leaving them stranded on Stripe’s checkout confirmation.

• Connect Stripe to Zapier or Make to trigger post-payment delivery or emails. You can route events to Mailchimp for a welcome sequence, Google Sheets for a simple order log, Slack for a team notification, or your delivery tool for the actual digital product.

• For the Stripe Buy Button, use the client-reference-id attribute so you can reconcile payments in webhooks, then automate access or delivery based on that reference.

The client-reference-id is your hook for tying a payment to a specific customer or order in your own systems. Without it, a webhook tells you someone paid, but not who or for what. With it, you can automatically grant access to a gated page, trigger a digital download email, or log the sale to your CRM.

Getting Stripe connected is the easy half. The delivery, the receipts, and the follow-up are where the business actually runs, and they need a small automation layer to handle them.

Tax and VAT: Who Is the Seller of Record on a Framer and Stripe Setup?

The seller-of-record question quietly decides how much tax work lands on your desk, and it’s easy to miss when you’re focused on getting a checkout working. Standard Stripe is a payment processor, not a merchant of record. That means you remain the seller of record on every transaction: tax registration, VAT filing, PCI compliance, fraud, and chargebacks all sit with you. Stripe moves the money; you own the legal obligations that come with selling.

The middle column is where most Framer sellers land. Stripe Tax is genuinely useful because it saves you the guesswork of figuring out what to charge a buyer in another country, but it doesn’t change who you are in the transaction. Stripe’s own documentation is explicit: you must register with the tax authority in a location to collect taxes there. The tool calculates the number; you still file the return.

Stripe Managed Payments is the notable shift here. Introduced on February 25, 2026 and generally available, it grew out of Stripe’s 2024 acquisition of Lemon Squeezy. Under this model, Stripe becomes the legal seller, taking on tax calculation, collection, registration, filing, fraud, disputes, and buyer support across 80+ countries. It applies at the transaction level rather than the whole account, so you can run some sales through it and keep others on standard Stripe.

Our assessment is that Managed Payments is the right call if you’re selling to customers across many jurisdictions and don’t want to build a tax-compliance operation alongside your store. The trade-offs are real, though: Stripe takes a share of each sale, and it sits between you and your customer data, which means less control over the checkout, refunds, and how the sale appears to the buyer. In countries where Managed Payments can’t take on responsibility, you’re back to registering and filing yourself.

The seller-of-record distinction matters most for anyone selling across borders, because VAT and sales tax obligations attach to the seller, not the payment processor. Whether you use Stripe directly, add Stripe Tax, or hand the whole thing to Managed Payments, knowing who the legal seller is on each transaction is the difference between a clean tax season and an expensive surprise.

Which Framer Payment Route Should You Pick for What You Sell?

The right Framer Stripe integration depends entirely on what you’re actually selling. A digital download, a subscription, a booking, and a physical product each point to a different route, and the table below lays out which one to reach for.

For a digital download, Payment Links is the whole answer. Create the link, bind it to a buy button, and let Zapier or Make pick up the payment event and email the file. No store system needed for a product that doesn’t ship.

If the subscription is really just a recurring charge, Payment Links with recurring pricing is enough. The moment you need member-only pages, tiered access, or to know who’s logged in, Outseta, Thenty, or FrameAuth V2 earns its place, because the value shifts from billing to access control.

Bookings are the case that needs the most assembly. A Payment Link handles the money, but it can’t capture the appointment details, so you pair it with a scheduling tool through Zapier or Make. If you’re invoicing a client with line items or taking a deposit followed by a balance, the webhook-to-Stripe-invoice route through a Framer form is the cleaner path.

Physical products are where we’d steer you away from Payment Links unless you’re selling exactly one thing. Inventory, shipping, and tax are the unglamorous work that a real store system like Frameshop, FramerFlo, or Framer Commerce already does, and rebuilding that with automations gets painful fast. For a single product, Payment Links plus a fulfillment automation is fine, but it’s not a system you want to grow into.

Our verdict after walking through all four routes: there’s no one-size-fits-all answer, but Payment Links is the easiest starting point for most builders. It’s free, it takes minutes to set up, and it covers digital goods, simple subscriptions, and bookings with the right automations around it. Start there, and you can upgrade to a full ecommerce layer when your sales justify the overhead.