A promised promotion has no entry point on the hosted payment page

Locate the promised entry point

Save the public offer's URL, wording and publication period, including where it tells the buyer to enter the code. Then trace the route a buyer actually follows from that offer through the cart, store checkout and hosted page. Record whether a coupon input is visible, available behind a labeled control, absent, or simply unobserved at each step. An administrator preview of a different checkout page cannot answer this question.

Separate a missing input from a rejected code and from a discount that was already applied before the redirect. If the code can be entered but produces an error, preserve that error for a coupon-rule investigation. If the summary already shows a discount, establish which system applied it. Neither finding proves that the entry route promised in the offer is available.

Compare the two configuration owners

WooCommerce documents that the Coupon Form can be removed from the Checkout block. It also requires the checkout page to be assigned in Advanced settings. Have the store administrator compare that assigned page's block structure with the page the buyer reached. Finding a coupon form on an unused page does not resolve its absence on the active route. This particular removal behavior describes the Checkout block; a classic or customized checkout needs its own configuration evidence.

Stripe's hosted Checkout guide identifies applying discounts as a customizable feature, and describes the Checkout Session as the representation of the payment page. That establishes a separate configuration surface to investigate. It does not show that a WooCommerce coupon automatically becomes a Stripe promotion or that the installed connector exposes every hosted feature.

Record the integration name, installed version and whether the hosted session comes from a connector or merchant-maintained code. Ask its owner to identify the documented setting or session configuration that supplies buyer-entered promotions for that exact integration. Record unsupported or unconfirmed where appropriate instead of guessing an API parameter or changing an unrelated coupon rule.

Choose a correction that restores an honest route

If the intended entry point is the store and the assigned block has lost its Coupon Form, the next action is an authorized page-configuration correction, followed by a check of the buyer's actual route. If the intended entry point is hosted, the integration owner must establish whether that route supports code entry and how its configuration reaches the session. Restoring a store field alone does not answer a promise to enter the code later on the hosted page.

A supported store-side redemption route can be considered when the hosted input is unavailable, but first establish that its resulting discount reaches the hosted total and the store's order record consistently. Do not create a second independent discount merely to make both pages look discounted. If the advertised route cannot currently be supported, the promotion owner should approve accurate instructions or a change to the offer, and separately decide how existing promises will be handled. This worksheet does not determine a buyer's contractual remedy.

Close the finding with the visible path

The useful completion record names the changed setting, the responsible person, the release date, and what a buyer now sees between the offer and the payment summary. Inspect the actual entry surface without making a diagnostic charge. Use existing genuine order and provider records, where available, to establish whether the discount carried through; leave payment reconciliation unconfirmed when those records do not exist.

For a Prism checkout-review consultation, bring the offer URL, the observed missing step and the integration details. Ask for a scope that covers the mismatch between the promotion and checkout. Configuration work, implementation responsibilities, fees and terms must be agreed before work begins; a working promotion does not establish provider eligibility.

Promotion-entry route map

Complete this for one real published promotion and its actual checkout route. Mark each surface observed, absent or unconfirmed. A complete entry route still needs a separate record showing the correct discount reached the order; do not enter private checkout URLs 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.

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.