Hosted checkout page or custom payment form? How to choose
Short answer: For most small businesses, a prebuilt checkout (a Stripe-hosted page or Stripe's embedded checkout form) is the better starting point: it's quicker to build, handles payment methods, tax and discounts for you, and needs less maintenance. A fully custom payment form built with Stripe Elements makes sense when the payment step must sit inside a bespoke flow, such as a multi-step booking app or a platform with its own pricing logic, and you have developers to maintain it.
When founders brief a developer on "taking card payments", the first technical fork is usually between a ready-made checkout and a custom one. Using Stripe's current options as the example, here's how they compare and which suits which business.
The options Stripe currently describes
Stripe's online payments overview groups its approaches roughly by effort:
- Payment Links: no code; a shareable link to a Stripe payment page.
- Full page checkout: a prebuilt payment page, either embedded on your site or reached by redirecting to a Stripe-hosted page.
- Embedded form: a prebuilt payment form placed on your own page, without redirection.
- Custom payment flow: a payment page you design yourself using Stripe Elements.
- Mobile apps: a Mobile Payment Element for iOS, Android and React Native.
Behind the prebuilt options sits the Checkout Sessions API, which Stripe says it recommends for most integrations, covering both basic payment collection and complex checkouts with line items, tax, discounts, shipping and subscriptions. The lower-level Payment Intents API lets you build everything yourself, but Stripe notes that this means manually building discount logic, tax calculation and currency conversion, with significantly more code and ongoing maintenance. Some features, Adaptive Pricing among them, are only available with Checkout Sessions, according to the same page.
The Payment Element itself, per Stripe's docs, is an embeddable UI component that can accept more than 100 payment methods, validates input and handles errors, with an Appearance API for styling and dynamic payment methods managed from the Dashboard.
Comparison
| Hosted or embedded prebuilt checkout | Custom flow with Elements | |
|---|---|---|
| Build effort | Low | Medium to high |
| Look and feel | Your branding within Stripe's layout | Fully your design |
| Customer stays on your site | Embedded options: yes; hosted: redirect | Yes |
| Tax, discounts, shipping, subscriptions | Configured through Checkout Sessions | Built by your developers if using lower-level APIs |
| New payment methods | Often switched on in the Dashboard | Often also Dashboard-driven via dynamic payment methods, but test in your UI |
| Ongoing maintenance | Lower | Higher; you own more code |
| Fits | Shops, bookings, services, subscriptions | Bespoke apps, platforms, unusual flows |
Verdicts by situation
A small online shop or service business
Prebuilt checkout. Whether you redirect to the hosted page or embed the form, you get a well-tested checkout with less to build. Many e-commerce platforms handle this for you anyway; this choice mainly applies to custom-built sites.
A booking or quoting web app with a multi-step flow
Embedded prebuilt form first, Elements if needed. If payment is the last step after choosing a time, extras and details, an embedded form usually fits fine. Move to Elements if the payment step must be interleaved with other inputs or styled in ways the embedded form can't support.
A subscription product (SaaS, memberships)
Prebuilt checkout, plus Stripe's subscription tools. Recurring billing involves proration, trials and failed payments. Building that on lower-level APIs is real work; Stripe's own guidance points towards Checkout Sessions for subscriptions.
A platform with its own pricing engine
Elements, with care. If you calculate prices, discounts and currency conversions yourself, you'll likely be building custom flows anyway. Budget for the extra code and maintenance that Stripe's overview warns about.
A mobile app selling physical goods or services
Mobile Payment Element (or a prebuilt flow opened in the app). Check each app store's rules on which payments must go through in-app purchase; this depends on what you sell.
Questions to ask before deciding
- Does the customer need to stay on our page, or is a redirect acceptable?
- How closely must the payment step match our design?
- Do we need tax calculation, discounts, shipping or subscriptions, and who will build them?
- Who maintains the integration after launch?
- Which payment methods do Australian customers expect from us? Check what's available for your account in Stripe's settings.
- How will we test failures: declined cards, authentication steps, timeouts?
Things that matter either way
- Webhooks: whichever option you choose, rely on server-side events to confirm payment before fulfilling orders, not only on the customer reaching a "thank you" page.
- Receipts and emails: decide whether Stripe or your app sends them, so customers don't get two.
- Testing: use test mode thoroughly, including authentication challenges and declines.
- Accessibility and mobile: test the payment step on small screens and with keyboard navigation.
FAQ
Is an embedded checkout the same as building with Elements?
No. The embedded form is Stripe's prebuilt checkout placed on your page. Elements are components you assemble into your own payment page with more control and more responsibility.
Does a hosted checkout page hurt conversion?
It depends on your customers and flow. A redirect to a familiar, well-built payment page often works well; if you're concerned, the embedded form keeps customers on your site while still being prebuilt.
Can I switch from hosted to custom later?
Yes. Many businesses start with a prebuilt checkout and move specific flows to Elements when needs grow. Keep your order and fulfilment logic separate from the payment UI to make switching easier.
Which is more secure?
Both are built to keep card data off your servers when implemented as Stripe documents. Custom builds have more of your own code around payments, so more to get right.
Do I need a developer for a prebuilt checkout?
For the hosted page, often only a little: your site creates a checkout session and redirects to it. Platforms such as Shopify or WooCommerce handle payments through their own integrations, so the question mainly arises with custom-built sites and apps.
Planning a booking or ordering app and unsure how deep the payment integration needs to go? Describe your checkout flow and we'll recommend the lightest option that fits.