Choose a hosted or on-site payment page from the integration you run
Use the placement the integration you will actually run documents. Stripe's Checkout guide describes a full page the buyer can reach by a redirect to a Stripe-hosted page, or embedded on your site. It also describes an embedded form and a Payment Element built into your page. Those are different journeys. Stripe's hosted fulfillment document says you cannot rely on the buyer reaching the return page after a successful payment. The embedded lifecycle names the same completed-session event. Follow the fulfillment document for the layout you run. WooCommerce requires a cart and checkout page before buyers can pay, and its block checkout creates a draft order when the buyer clicks Place Order. You can choose among journeys your current documents describe. Your provider decides which integration it will enable. This page cannot see which one is installed. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner or authorized representative of a business that sells peptides for laboratory research use only and is deciding where the payment step on its store should happen.
Updated 2026-09-21
Stripe documents more than one place for the payment form
On the full hosted page, your application creates a Checkout Session, the session provides a URL, and the buyer is redirected to a Stripe-hosted payment page to enter payment details. On the full embedded page, your site mounts Checkout and the buyer enters payment details there, without that redirect. Stripe's comparison also lists an embedded form on your site, marked as a public preview, with a more limited order summary, and Elements as a customized payment page with no order summary in that table.
The hosted feature table lists responsive mobile design and PCI compliance as built-in for that hosted page. This page does not turn that label into an accessibility score or a statement of your remaining obligations. Custom domains for the hosted page are described as a paid feature. The price is on Stripe's pricing page and is not restated here. A full embedded page is not the same row as the public-preview embedded form. Do not mix their order summaries.
The buyer's return is not the fulfillment record
The hosted fulfillment document says a buyer can pay and then lose the connection before your landing page loads, so you cannot rely on that page alone. It says the completed-session event has to be able to fulfill the order. The full embedded lifecycle also names checkout.session.completed as the event that triggers fulfillment. The embedded page opened for this guide does not repeat the lost-connection example, so do not treat that example as a finding about every Stripe layout. Use the fulfillment document for the layout you run.
That is a Stripe Checkout statement. It does not say your store plugin creates the WooCommerce order at the same moment. If a plugin sits between Stripe and the store, the plugin's document has to say which event creates the order. Until you open it, that handoff is unknown.
The payment form does not choose the rail or the buyer control
Stripe's payment-method support table lists ACH Direct Debit as supported on Checkout and on the Payment Element, and unsupported on the Express Checkout Element. Cards are listed as supported on Checkout and the Payment Element. Support in that table is not the same as an enabled method on your account, and it is not a decision to use a card rather than a bank debit. The rail comparison is a separate question.
Buyer controls also follow the page you run. Stripe's hosted Checkout custom-fields document allows up to three fields and says not to collect sensitive data in them. That limit is for the hosted document. WooCommerce's terms checkbox and its block-checkout agreement message are store controls, documented on WooCommerce's settings pages, not on Stripe's hosted page. Do not specify a control the live page's document does not show.
A WooCommerce checkout is the store's checkout unless the gateway's document says otherwise
WooCommerce's advanced settings say buyers cannot buy and pay unless a cart page and a checkout page are assigned. On current block checkout, a draft order is a temporary record, and WooCommerce creates it when the buyer clicks Place Order. That is store order creation. It is not Stripe's description of a hosted payment page.
WooCommerce's payments settings let you enable an available payment provider and change the order in which methods appear. Enabling a provider there does not say whether that provider then redirects to its own page. If the gateway's current document does not say where the payment details are entered, leave that cell unknown. Do not infer a redirect from the fact that a provider is enabled.
What you can choose, and what the provider still decides
You can choose a documented journey that matches who should host the payment form, who must handle the completed-session event, and which order summary the buyer sees. You can refuse an integration whose document does not say what happens when the buyer never returns. You cannot decide that a provider has approved the hosted page, the embedded page, or the catalog.
Prism can discuss the website question and help connect a provider's questions to the pages involved. Scope and any fee are discussed before work. A review is informational. Implementation responsibilities must be agreed before any checkout change. Whether your live theme uses the shortcode, the block checkout, or a Stripe page is something you confirm in the admin. It is unknown from this guide.
Checkout placement comparison
Record the integration that is installed or proposed. Use Stripe's hosted and embedded documents only for a Stripe Checkout integration, and WooCommerce's documents only for the store checkout they describe. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Checkout placement comparison. The last column is for temporary notes.
Journey point
What the opened documents say
What remains specific to your integration
Your integration
Where payment details are entered
What the opened documents sayStripe full hosted Checkout redirects to a Stripe-hosted page. Stripe full embedded Checkout is mounted on your site. The embedded form and the Payment Element are separate on-site options in Stripe's comparison.
What remains specific to your integrationThe admin or proposal that names the option you would turn on.
What the buyer sees with the total
What the opened documents sayStripe's comparison gives the full page a full order summary, the embedded form a limited summary, and Elements no order summary. The hosted feature table lists responsive mobile design as built-in for that hosted page.
What remains specific to your integrationWhich of those rows matches the integration in the proposal.
What happens if the buyer does not return
What the opened documents sayThe hosted fulfillment document says a successful payment can still miss your return page, so that layout cannot depend on the return page alone. The embedded lifecycle names the same completed-session event and does not, on the page opened here, repeat that example.
What remains specific to your integrationThe webhook or plugin step your developer can show. Write unknown if nobody has identified it.
When the store order is created
What the opened documents sayWooCommerce block checkout creates a draft order when the buyer clicks Place Order. Stripe's fulfillment guide does not say a WooCommerce order is created at that click.
What remains specific to your integrationThe store or plugin record that shows the order was created, and the event that created it.
Which payment methods that page can show
What the opened documents sayStripe lists cards and ACH Direct Debit as supported on Checkout and the Payment Element, and lists ACH Direct Debit as unsupported on the Express Checkout Element. Support in the table is not an enabled method on your account.
What remains specific to your integrationThe methods enabled in the provider dashboard for this account.
Which buyer controls the page documents
What the opened documents sayHosted Checkout custom fields have a three-field limit, and Stripe says not to collect sensitive data in them. WooCommerce's shortcode and block checkouts present terms differently. Neither fact describes the other product.
What remains specific to your integrationThe control document for the page you will use. Mark support unverified if the current documentation or written vendor confirmation does not establish it.
Who has approved this placement
What the opened documents sayStripe's setup documents describe how to build the page. WooCommerce's enable control turns on an available provider in the store. Neither document is a provider's approval of this business.
What remains specific to your integrationThe written approval, or unknown if you do not have one.
These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.
Limits
A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
Hosted, embedded, and store-checkout statements on this page apply only to the Stripe or WooCommerce documents in the sources.
Choosing a page placement does not approve processing, select a card or bank rail, or set a fee.
Stripe Checkout comparison — checked 2026-09-21. Stripe documents a full page that can be hosted or embedded, an embedded form in public preview with a limited order summary, and Elements with no order summary in that comparison.
Stripe hosted Checkout lifecycle — checked 2026-09-21. The hosted flow redirects the buyer to a Stripe-hosted page, then uses checkout.session.completed for fulfillment. Its feature table lists responsive mobile design and PCI compliance as built-in.
Stripe embedded Checkout lifecycle — checked 2026-09-21. The full embedded flow mounts Checkout on the merchant site and uses checkout.session.completed for fulfillment.
Stripe Checkout fulfillment — checked 2026-09-21. Fulfillment cannot rely only on the return page, because the buyer may never reach it after a successful payment.
Stripe Payment Element — checked 2026-09-21. The Payment Element is an embeddable payment UI rendered in the merchant's front end.
Stripe hosted Checkout custom fields — checked 2026-09-21. Hosted Checkout allows up to three custom fields and says not to use them for personal, protected, or sensitive data, or information restricted by law.
Stripe payment method support — checked 2026-09-21. ACH Direct Debit is listed as supported on Checkout and the Payment Element and unsupported on the Express Checkout Element.
WooCommerce advanced settings — checked 2026-09-21. A cart page and a checkout page must be assigned or buyers cannot buy and pay.
WooCommerce order statuses — checked 2026-09-21. On block checkout, WooCommerce creates a draft order when the buyer clicks Place Order.
WooCommerce settings — checked 2026-09-21. The payments screen enables an available provider and can reorder how methods appear. That is a store setting.
Prism solutions — checked 2026-09-21. Prism can review website content or help connect a provider's website questions to the pages involved. The provider decides whether the account is available.
Prism features — checked 2026-09-21. A website review is informational. It is not a compliance certification, and it does not guarantee approval or continued processing.
Request a consultation
Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.