Checkout reliability

One-time and recurring items share the first checkout

Verify the price type of each line, the amount presented at the first checkout and which items the future billing record actually includes. Stripe Checkout supports mixed one-time and recurring items in subscription mode, so the mode alone does not mean every item repeats. Compare the merchant's intended offer with the actual line-item configuration and billing records before approving the presentation. The documented Stripe capability does not establish support in your store connector or approval for your business.

For: A research-only merchant reviewing an intentional cart that combines a recurring purchase with a separate one-time item.

Updated 2026-10-01

Subscription mode can contain different price types

Stripe's hosted Checkout guide distinguishes payment mode for one-time purchases from subscription mode, which can include recurring and one-time items together. Its mixed-cart flow supplies the line items through Price references or explicit price data. That makes each line's actual price definition central to the review: the name displayed to the buyer is not enough to establish the billing type.

Start by confirming that a mixed offer is what the merchant intended. If every item was meant to be a one-time purchase, investigate the purchase-mode mismatch separately. For an intentional mixed cart, do not reject subscription mode simply because one item is one-time. Identify that item's price type and its place in the initial purchase instead.

Trace each real item from the offer to the price record

Use the genuine catalog identity, selected option and quantity to connect each store line to the corresponding Price reference or price data supplied to Checkout. Record whether that configuration is one-time or recurring. If the store uses a connector, have its authorized maintainer identify the actual mapping and installed integration; the generic Checkout feature is not evidence that the connector implements it.

For a recurring line, compare the configured billing interval with the interval the offer describes. For the separate one-time line, compare the configuration with the merchant's intent that this purchase not repeat. Mark a missing price definition as unknown rather than inferring it from a label such as a product name or a cart heading.

Keep intended behavior and observed configuration in separate notes. An approved offer establishes what should happen. The supplied price data establishes what the integration requested. A real billing record, where one exists, establishes what was recorded for that purchase. None of those should silently replace the other.

Compare the first amount with the future billing picture

Read the initial checkout summary alongside the actual line quantities, currencies and amounts. Preserve any separately shown tax, shipping or discount entries instead of assuming that the total is just the sum of catalog prices. The purpose is to account for the displayed first amount using this cart's real records, not to supply a general formula for every subscription configuration.

Then inspect the corresponding subscription or future billing information available to the authorized team. List the items it contains and the amounts or timing it actually states. The one-time purchase should not be described to the buyer as a continuing purchase when that is not the offer. Conversely, the recurring portion needs a clear continuing-billing description; calling the whole cart a single one-time purchase would hide that part of the offer.

A correct first total does not establish that the later billing configuration is correct. Compare item membership and recurrence separately from the amount. If no later invoice exists, record that fact and distinguish configured future billing from completed billing history. Do not create an order or claim a renewal result to fill the gap. Any future amount or date absent from the real configuration stays unconfirmed.

Approve the presentation only to the extent the records agree

The merchant can approve the mixed-cart wording when the offer, the item mapping, the initial summary and the configured continuing purchase tell the same story. A mismatch should be precise: the wrong price type, an extra recurring item, an unexplained initial component or missing future-billing information. Give that mismatch to the owner of the relevant integration before approving a change. Do not fix an apparent recurrence issue merely by renaming the line.

Bring the public offer, integration name and non-sensitive summary of the mismatch to a scoped Prism checkout consultation. Prism's published help covers storefront review, processing preparation and provider website questions. Confirm the requested technical work and responsibilities, fees and terms before work begins. The provider separately decides eligibility and account terms for the actual research-only business and recurring arrangement. A contact request leads to email follow-up; it does not purchase implementation, book an appointment or submit a processing application.

Mixed-cart billing map

For each real mixed cart, identify every line separately within the input fields. Keep the intended offer, configured future billing and completed billing history distinct. Approval requires agreement across those records, not just a matching first total.

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.

Mixed-cart billing map. The last column is for temporary notes.
Billing checkActual record to compareMismatch to flagYour finding
Line item identityCatalog item and selected option, quantity and its corresponding Checkout line or Price reference.A line cannot be traced to the item the buyer selected.
One-time or recurring price typeActual price definition or supplied price data for each item, against the merchant's intended offer.A type is wrong or unknown; a display label does not establish recurrence.
Initial checkout amountFirst checkout summary with line amounts, currency and any separately shown tax, shipping or discounts.An unexplained component, missing line or total that cannot be tied to the real summary.
Intended future billingApproved recurring offer compared with the configured subscription items and any stated billing interval, amount or date.A separate one-time item appears to repeat, or the recurring item does not match the offer.
Observed billing historyAn existing initial invoice and later invoice if one genuinely exists, referenced without customer details.Future billing is being claimed as verified history when only configuration is available.
Buyer-facing explanationThe actual product, cart and checkout wording about the initial purchase and continuing commitment.The whole mixed cart is described as one-time, or the one-time portion is described as recurring.
Supported integration ownerInstalled connector or custom integration identity and the authorized maintainer responsible for the price mapping.Generic Stripe support is being substituted for evidence about the installed integration.

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.

Limits

  • Stripe Checkout's mixed-cart capability applies to the documented subscription-mode flow. It does not establish every plugin's capabilities or a provider's approval of this merchant.
  • This review does not predict later charge success, decide tax treatment or replace provider terms for recurring billing.
  • Use non-sensitive references only. Do not record private checkout URLs, payment-card details, authentication codes, API secrets or customer records in the worksheet or public inquiry.

Sources

  • Stripe hosted Checkout lifecycle — checked 2026-09-29. Checkout subscription mode supports recurring and one-time items in a mixed cart, with line items supplied through Price references or price data. This establishes the documented flow, not a merchant connector's support or an actual billing outcome.
  • Prism solutions — checked 2026-09-21. Prism's public support includes storefront review, processing preparation and provider website questions. Scope, fees and terms precede work; the provider decides eligibility and account terms.
  • Prism contact — checked 2026-09-21. The form requests the website, products and question, excludes card details, passwords and customer records, and receives email follow-up. It does not book an appointment, purchase a service or submit a processing application.

Get help with checkout

Is this happening on your own store?