What we do
Tools
Industries
Department
How we workLet's talk →
Home/Stripe/Stripe Checkout
Stripe Checkout

Stripe Checkout: Choosing the Right Page, Then Getting the Order Out of Stripe

Stripe Checkout is a payment page Stripe builds and hosts, so you don't build a card form yourself. Payment Links are Checkout without code, and Link is something else again. Here's which to use for how you sell, what to decide before you share it, and where orders tend to go missing after someone pays.

Three names, three things

Landed on checkout.stripe.com? That's Stripe's hosted payment page, used by the business you're buying from. The business sets the price and handles your order. Questions or refunds go to them, not Stripe.

Checkout: a payment page your site opens for each purchase through the API, as a full page on Stripe or embedded in your own page. It handles cards, wallets, tax and subscriptions.

Payment Links: the same Checkout page, made in the Dashboard with no code. You get one buy.stripe.com URL to share anywhere, and every visitor gets their own checkout.

Link: Stripe's saved-details network. It fills in a returning customer's payment and shipping details so they don't type them again. It has nothing to do with Payment Links.

Which Stripe checkout matches how you sell

You sell Use Watch for
A few products shared in posts, emails, texts or a QR code A Payment Link per product or offer Each link works on its own. Nothing ties a sale to a customer record or order elsewhere unless you build it.
A website with a cart or a sign-up flow and a backend Hosted Checkout, with a Checkout Session per purchase The customer leaves your site to pay, then comes back to the page you set. Don't run fulfillment only from that page.
The same, but you want people to stay on your page Embedded Checkout Same Sessions and events as hosted Checkout, so everything after the payment works the same way.
Subscription plans shown side by side Checkout in subscription mode, or Stripe's embeddable pricing table This creates a Stripe Billing subscription. Renewals, pauses and plan changes then live on our Stripe Billing page.
A payment step that has to look and behave exactly your way Your own form with Stripe Elements More control, more code, and more edge cases on you. See our Stripe API page.

Decide these before you share the link

Each one changes what lands in Stripe, and so what your order system has to pick up.

  • Which payment methods will customers see?

    Cards confirm on the spot. Bank debits and some transfers confirm days later, so a finished checkout isn't yet a paid order.

  • What do we need to ask the customer?

    Checkout can collect a shipping address, a phone number and up to three custom fields, like a size or a delivery note. Those answers are stored on the Checkout Session, not in your order system.

  • Where does the customer go after paying?

    A Payment Link can show Stripe's confirmation page or redirect to yours with the session ID in the URL. A redirect lets your page show order details straight away.

  • Does the buyer need an invoice?

    Checkout can create a paid invoice after a one-time payment, which business buyers often ask for. Stripe charges 0.4% for it, capped at US$2 per invoice. Switch it on before launch, not after the first request.

  • How will we know which link or campaign sold it?

    Each Checkout Session records the Payment Link it came from. Give each link a clear name and metadata, then report sales by link instead of guessing from the Dashboard.

Where orders go missing after checkout.session.completed

Stripe's own fulfillment guide says watching the Dashboard is fine at low volume. Past that, these are the gaps.

Bank payments counted as sales before they clear

How you'll know: Orders ship the moment checkout finishes, then a bank debit fails three days later.

Fix: Check the Session's payment_status. For delayed methods, fulfill on checkout.session.async_payment_succeeded and handle async_payment_failed with a message to the customer.

The event says someone paid, not what they bought

How you'll know: Your handler gets checkout.session.completed but no products or quantities, so someone looks them up.

Fix: Retrieve the Session with line_items expanded. If customers can change quantities in Checkout, use the final quantities from there, not the ones you sent.

The customer's answers stay in Stripe

How you'll know: The shipping address, phone number and custom field answers are on the Session, and someone copies them into the shop, booking or CRM system.

Fix: Map every field into the order record as it's created. n-frames builds that mapping per form, so a new custom field doesn't silently get dropped.

One payment, two orders

How you'll know: A repeated event, or the landing page and the webhook running together, creates a duplicate order or a second shipment.

Fix: Record which Sessions you've fulfilled and skip repeats. Stripe warns this can run more than once, even at the same time.

Payment Link sales with no order anywhere

How you'll know: Sales from a link show up as Stripe emails, and fulfilment is a person reading them.

Fix: Turn each completed Session into an order, a stock change or a booking in the system you already run, tagged with the link it came from.

Questions people ask

What's the difference between Stripe Checkout and a Payment Link?

A Payment Link is Checkout set up in the Dashboard with no code: one reusable URL that opens a fresh checkout for each visitor. Checkout through the API creates a Session for each purchase from your own site, so you can set the cart, the customer and the return page every time.

What is Stripe Link, and is it the same as a Payment Link?

No. Link saves a customer's payment and shipping details and fills them in at any business that offers it, so a returning buyer pays in a couple of clicks. A Payment Link is a URL you create to sell something without code. Link can appear on a Payment Link page, but they're separate things.

What is checkout.stripe.com?

It's the address of Stripe's hosted Checkout page. Businesses send customers there to pay, so seeing it is normal when you buy from a business that uses Stripe. The order itself, and any refund, is handled by that business.

Do I need a developer to use Stripe Checkout?

Not for Payment Links, which you make in the Dashboard. Hosted or embedded Checkout needs a little server code to create Sessions. A developer earns their keep on what comes after: the webhook that turns a payment into an order, handled once, with bank payments treated properly.

Can I attach extra information to a Stripe Checkout session?

Yes. Add metadata key-value pairs when you create a Session or a Payment Link, such as your order ID or a campaign name, and read them back on the webhook. To ask the customer for information instead, use custom fields (up to three) or collect shipping and phone details.

Does Stripe Checkout handle subscriptions, or only one-time payments?

Both. In subscription mode, Checkout signs the customer up and creates the subscription in Stripe Billing, and the next renewals are billed by Billing, not Checkout. See Stripe subscriptions and billing.

How do I know when a Stripe Checkout payment is complete?

Listen for the checkout.session.completed webhook and check payment_status. For bank debits and other delayed methods, wait for checkout.session.async_payment_succeeded. Don't rely on the customer reaching your thank-you page, since they may close the tab. Our Stripe webhook setup page covers the endpoint.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.