Should you use Stripe Payment Links or embedded Checkout?
Use Stripe Payment Links if you sell a small number of fixed products or plans and want to launch without backend code. Use embedded Checkout if payment has to happen inside your own page, after signup, or with prices and details your code decides at the moment of purchase. Most marketing sites should start with Payment Links.
Both options run on Stripe Checkout, so card handling, wallets and security are Stripe's job either way. The difference is who creates the checkout, where it appears and how much code you maintain. The choice sits downstream of your plans and pricing page; if those aren't settled, start with our SaaS pricing page guide. For the wider set of Stripe surfaces, including the Buy Button and the embeddable pricing table, see our Stripe integration page.
What's the difference between Payment Links and an embedded Stripe Checkout page?
A Payment Link is a URL to a Stripe-hosted payment page that you create in the Stripe Dashboard. An embedded Stripe Checkout page is a payment form that appears inside your own page, created by your server for each visitor. One is configured once and shared; the other is generated per purchase.
With a Payment Link, you pick the product and price in the Dashboard, set what happens after payment, and paste the link on a button. Stripe's docs say Payment Links can sell one-off products or subscriptions, and support promotion codes, adjustable quantities, upsells and letting customers choose what to pay.
With embedded Checkout, your server calls Stripe's API to create a Checkout Session when the visitor is ready to pay, passes a client secret to the page, and the page mounts Stripe's form. Stripe's current docs call this the full embedded page and list it alongside a full hosted page, an embedded form and Elements, so check which variant fits before you build. After payment, the customer returns to a URL you set.
How do Payment Links and embedded Checkout compare?
Payment Links win on setup effort and maintenance; embedded Checkout wins on control and on keeping the visitor on your site. The table compares them on the points that matter for a marketing site.
Payment Links | Embedded Checkout | |
|---|---|---|
Setup | Dashboard only, no code | Server endpoint plus front-end code |
Where the visitor pays | A Stripe-hosted page | Inside your page, on your domain |
Design control | Limited branding options | Your page around Stripe's branded form |
Prices and details | Fixed when the link is created | Set by your code for each session |
Signup before payment | Awkward to enforce | Natural: create the session after signup |
Tracking | UTM codes and a reference ID in the URL | Your own analytics plus session metadata |
Framer and Webflow | Works from any button | Needs a separate server endpoint |
Maintenance | Edit in the Dashboard | Code to update and test |
Neither option removes the need for fulfilment. Whichever you choose, something has to grant access, send the onboarding email or notify your team after Stripe confirms the payment, and that part is code or an automation tool.
How much design control does each option give you?
Payment Links give you limited branding on a page Stripe controls; embedded Checkout gives you the whole page around Stripe's form. Neither lets you redesign the payment fields themselves, which is part of why Stripe can handle wallets, validation and authentication for you.
Stripe's docs describe Payment Links branding as limited customization: 20 preset fonts, three border radius options, and your logo, background and button colors. That's enough to look consistent with your brand, but the page layout is Stripe's. Stripe's docs say you can serve Payment Links from your own subdomain, such as pay.example.com, but the page is still Stripe's, so the visitor leaves your site to pay.
Embedded Checkout uses the branding settings in your Stripe Dashboard for the form, while everything around it is your design: the plan summary, reassurance copy, FAQ and support details. That surrounding content is where conversion work happens, because it answers the last questions before someone pays. If you're designing that page in a builder, our Framer landing page examples show the layout patterns that carry over.
How do you track conversions with each Stripe option?
With Payment Links, you track by adding parameters to the link; with embedded Checkout, your own analytics already sees the visitor on your page. In both cases, the reliable conversion is Stripe's checkout.session.completed event, not the button click.
Stripe's Payment Links docs support the UTM codes utm_source, utm_medium, utm_campaign, utm_term and utm_content, and pass them to your redirect URL when the confirmation behavior is set to redirect. You can also add a client_reference_id of up to 200 letters, numbers, dashes or underscores, which Stripe includes in the checkout.session.completed webhook. That's how you tie a payment back to a campaign or a visitor.
Embedded Checkout keeps the visitor on your domain, so page views, scroll and experiments work as on any page, and you can attach your own metadata when the server creates the session. If you're testing pricing or checkout copy, our guide to A/B testing in Framer, Webflow and Next.js covers the setup, and scroll depth explains what engagement data can tell you.
How do you add a Stripe checkout page to Framer or Webflow?
On Framer or Webflow, a Payment Link is the simple path: paste the link on any button and you're live. Embedded Checkout needs a server endpoint that creates the Checkout Session with your secret key, and neither builder runs that code for you, so it has to live somewhere else.
That usually means a small serverless function on a separate host, plus a webhook endpoint for fulfilment. It works, but you now maintain backend code next to a no-code site, with secret keys to protect. If checkout logic keeps growing, that's often the point where a team moves the site to code; our guide to rebuilding a Framer site in Next.js covers that path, and our comparison of landing page builders shows what each builder handles natively.
Hypothetical example: one product, two Stripe setups
This example is hypothetical and illustrates the decision, not a real company.
For example, suppose a founder sells a $400 setup workshop and a $49-a-month community plan from a Framer site. Both are fixed prices with no account needed before payment, so two Payment Links, each on its own button with a redirect to a thank-you page, cover it in an afternoon. A client_reference_id on each link marks which landing page sent the buyer.
Now suppose the same founder adds software that needs an account first, with seat counts chosen at signup. The pricing page still shows the plans, but the button now leads to signup, and after signup the app's server creates an embedded Checkout Session with the chosen seats. The webhook switches the account to paid. The products in Stripe barely change; the requirement for an account first is what moved the setup to embedded Checkout.
Which Stripe option fits your business?
Choose by your most demanding requirement, not your average sale. If any product needs signup before payment or a price your code calculates, that product needs embedded Checkout or another code-based integration; everything else can stay on Payment Links.
Business type | Recommended | Why |
|---|---|---|
Consultant, agency or service deposit | Payment Links | Fixed amounts, no account needed |
Course, template or digital product | Payment Links | Fixed prices; fulfil from the webhook |
Early SaaS with flat monthly plans | Payment Links or the pricing table | Fast launch; switch later if needed |
SaaS that needs an account first | Embedded Checkout | Create the session after signup |
Seat, usage or quote-based prices | Embedded Checkout | Price set in code per buyer |
Checkout must stay on your own page | Embedded Checkout | The form mounts inside your page |
