A payment form replaced the order summary

Name the component before assigning the missing work

Stripe’s Checkout comparison distinguishes a full page, hosted or embedded, from an embedded form and an Elements integration. In the comparison checked on September 21, 2026, the full page has a full order summary, the embedded form has a limited summary and is marked public preview, and Elements has no order summary. A proposal that says only “embedded checkout” does not identify which of those responsibilities the provider supplies.

Ask the maintainer to identify the actual component, the integration behind it, and the surrounding store page. The missing summary may be a piece of merchant-owned page content that was removed when the payment interface changed. Its absence does not establish that the payment provider lost the order, or that changing where payment fields appear requires removing item review.

Separate checkout calculations from their display

Stripe’s Payment Element documentation, checked on September 29, 2026, supports both Checkout Sessions and Payment Intents. Sessions includes checkout features; Payment Intents models the payment step, with tax, shipping and discount checkout logic belonging to the implementer. Identify which integration is installed before deciding who should calculate each amount. Do not infer that choice from the appearance of the card fields.

Calculation and display need separate owners. A total can exist in the payment record while the buyer has no visible item breakdown. Conversely, a store summary can display values that have not been reconciled with the payment amount. In the responsibility map, name both the record supplying each value and the page element displaying it. A statement that “Stripe handles payment” leaves the summary question unanswered.

This is a review of presentation and responsibility. It does not determine whether a tax amount is legally due or whether a shipping rule is commercially appropriate. Compare the displayed values with the merchant’s actual configured order calculation and flag any unresolved calculation separately.

Follow the review point through the real buyer journey

Use the actual checkout page and any retained evidence for real affected orders. Record where the buyer can review the selected product or option, quantity, item amounts, shipping selection or charge, tax treatment as displayed, and final amount with currency. Mark each item as visible, absent or not yet observed. If review is on an earlier step, record how the buyer reaches it and returns to payment.

Check the sequence of the actual journey: whether shipping, tax, discounts or quantities can change after that earlier review, and where the resulting total is shown before payment. An earlier cart screen cannot establish what was displayed after a later change. A receipt issued afterward can help reconcile the amount charged, but it cannot demonstrate that the buyer had a chance to review it beforehand.

A blank line is not evidence that shipping or tax is zero. Record how the interface distinguishes an amount that does not apply, an amount included elsewhere, and a value still awaiting calculation. Where the available evidence does not establish that distinction, leave a specific display question for the maintainer instead of entering a guessed amount.

Accept a defined order-review responsibility

The deliverable should identify who supplies the item list, who supplies the shipping and tax display, which record controls the final amount, and where the customer reviews them before payment. Attach the observed page locations and unresolved differences to the agreed checkout scope. If a required part has no owner or cannot be demonstrated on the installed journey, keep that part open rather than signing off the payment form as the whole checkout.

For a Prism checkout-review consultation, describe the website, research-only products, the component named by the maintainer, and the summary information that disappeared. Prism’s published support includes storefront review and help with provider website questions; confirm any implementation, responsibilities, fees and terms before work begins. The public inquiry should contain the question, not customer records or payment credentials. Follow-up is by email, and submitting it does not book an appointment, purchase work or submit a processing application.

Order-review responsibility map

Complete this for the checkout that is installed or proposed. In the blank column record the system, responsible person and observed page location. An empty owner or an unobserved review point is an open acceptance item. Use references to private records, not customer details or private checkout URLs.

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.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.