How do you add Stripe to a Framer site?
You add Stripe to a Framer site by connecting your buttons to Stripe-hosted payment pages, either through a link or an embed. Framer doesn't ship a built-in Stripe checkout, and a Framer site doesn't run your own server code, so every option is one of three things: a link out, an embed of Stripe's code, or a code component that talks to a backend you host elsewhere.
The payment button is a call to action like any other, so the basics in our call to action guide still apply: one clear action per offer, with a label that names what the buyer gets. This guide covers the plumbing behind that button. For the strategic choice between hosted and embedded checkout on any platform, read Payment Links vs embedded Checkout on a marketing site.
Which Stripe and Framer integration option should you use?
Use the lightest option that supports your pricing. A single product or deposit needs only a Payment Link, a small plan grid fits Stripe's pricing table, and anything involving accounts, usage or custom logic needs embedded or server-created Checkout.
Option | Backend needed? | Best for | Main limit |
|---|---|---|---|
Payment Link on a button | No | One product, event, deposit or service | Buyer leaves your site to pay |
Buy Button embed | No | A single product card on the page | Styling set in Stripe, not Framer |
Pricing table embed | No | A few flat or per-seat plans | Stripe's layout, plus documented limits |
Embedded Checkout via code component | Yes | Checkout inside your page design | You host and maintain an endpoint |
Third-party Framer plugin | Depends on the plugin | Carts or product sync | Another vendor in your payment path |
Stripe's pricing table has documented limits on how many products, prices and intervals one table can show, and Stripe's docs say it doesn't support every pricing model, so check the current limits before you design around it. If your plans don't fit, design the plan cards in Framer and send each button to its own Payment Link.
How do you set up a Stripe Payment Link in Framer?
A Payment Link is the fastest way to sell on Framer: create the link in the Stripe Dashboard, then paste it into the link setting of any Framer button. Card details are handled on Stripe's hosted page, so there's nothing to secure on your site.
Create the product and price in Stripe
Set the name, price and billing interval in the Dashboard. Add the image and description buyers will see on the payment page.
Create the Payment Link
Choose whether to collect addresses, phone numbers, tax IDs or promotion codes. Collect only what you need to fulfil the order.
Set the after-payment page
Redirect buyers to a page on your Framer site instead of Stripe's default confirmation. Design it as a real thank-you page that says what happens next.
Paste the link into your Framer button
Select the button, add the Payment Link URL as its link and decide whether it opens in a new tab. Same tab usually feels more natural for checkout.
Publish and test in test mode
Use a test-mode link and Stripe's test cards on the published site, then swap in the live link. Check the redirect, the receipt email and the Dashboard entry.
Payment Links also accept URL parameters documented by Stripe, such as a prefilled email or a client_reference_id you can use to match the payment to a lead later. Check Stripe's Payment Links docs for the current list before relying on one.
How do you embed a Stripe Buy Button or pricing table in Framer?
To embed a Buy Button or pricing table, create it in the Stripe Dashboard, copy Stripe's embed code (a script tag plus a Stripe web component) and paste it into a Framer Embed set to HTML. The Buy Button is built on Payment Links and the pricing table sends buyers to Stripe Checkout, so neither needs a backend.
Three things to check. First, size the Embed so the table isn't clipped on mobile; give it enough height for the tallest plan card, or the layout will jump. Second, test on the published domain, not only in the editor preview. Stripe's docs note the pricing table can't send visitors to checkout when it's sandboxed in an iframe that blocks top-level navigation, and an editor preview can behave differently from the live site. Third, if you've added a Content Security Policy to your site, Stripe's Buy Button and pricing table docs list the script and frame sources they must allow.
The trade-off is design control. Fonts, spacing and card layout are set in Stripe's settings, not Framer, so an embedded pricing table often looks like a different site from the page around it. For a pricing page that has to match your brand, design the cards in Framer and link each one to a Payment Link. Our roundup of Framer landing page examples shows how polished Framer pages usually handle this.
When do you need a backend for Stripe on Framer?
You need a backend as soon as Stripe has to create something on demand or tell your systems about a payment. Framer publishes your site but doesn't run your server code, so that logic lives in a separate endpoint, typically a serverless function on a host such as Vercel or Cloudflare.
- Embedded Checkout: Stripe's docs require the Checkout Session to be created on a server with your secret key. The page then mounts Checkout with the session's client secret.
- Signup before payment: if buyers need an account first, your backend creates the session for that account and links the two.
- Automatic fulfilment: granting access, sending licences or updating a CRM should run from a verified Stripe webhook, which needs an endpoint that receives and checks it.
- Dynamic prices: usage, quotes or custom bundles have to be calculated on a server, never trusted from the browser.
In Framer, the front end of embedded Checkout is a code component: a React component that loads Stripe.js, asks your endpoint for a client secret and mounts Checkout in the page. Keep the secret key only on the server. For simple automations, such as emailing a buyer or adding a row to a sheet, an automation tool listening to Stripe events can stand in for a custom endpoint.
Hypothetical example: a course creator moving from Payment Links to embedded Checkout
For example, suppose a designer sells a video course from a Framer site. Version one is a single Payment Link on the hero button, with a redirect to a thank-you page and the course access sent by hand. It works on day one.
As sales grow, sending access by hand stops scaling, and the designer wants checkout inside the page. Version two adds a small serverless function with two jobs: create an embedded Checkout Session when the Framer code component asks for one, and receive the checkout.session.completed webhook, verify its signature and send the course invite. The Framer site barely changes; the new work is the endpoint and its tests.
Should you use a Framer plugin for Stripe payments?
A third-party Framer plugin can make sense for carts or product catalogs synced to Stripe, but treat it as a payment vendor, not a design asset. It sits between your buyer and Stripe, so vet it the way you would any payment provider.
Check who maintains it, what data it stores, whether it uses your own Stripe account, what it costs at your volume and what happens to checkout if the plugin breaks or shuts down. For one product or a few plans, Stripe's own Payment Links and embeds are usually more durable because there's nothing in between. If you're selling a full catalog with inventory and shipping, a dedicated store platform is usually the better tool than a marketing site builder.
Our Stripe integration page explains how we handle webhooks and testing across platforms, and our Framer development service covers Framer builds more broadly.
How do you test and track Stripe payments on Framer?
Test every payment path in Stripe's test mode on the published Framer site, then track purchases as a conversion event. A payment button that works in the editor can still fail live because of embeds, redirects or cookie settings.
- Paths: a successful card, a declined card, an abandoned checkout and, if used, a promotion code.
- Devices: mobile Safari and Chrome, since embeds and redirects behave differently there.
- After payment: the redirect page, the receipt email and the record in the Dashboard.
- Tracking: fire a purchase event from the thank-you page or, more reliably, from the webhook into your analytics.
Once payments work, test the page around them. Button copy, plan order and the explanation above the price all affect how many people reach checkout, and our guide to A/B testing in Framer covers how to run those tests. If your payment logic outgrows Framer, rebuilding a Framer site in Next.js puts the site and the backend in one codebase.
