A prior agreement value carried into a new checkout

Identify the agreement before tracing the value

Record the exact label and linked wording, including its version or effective date if available. Establish whether the control concerns store terms, a research-only acknowledgment, or permission to save and reuse a payment method. These purposes need separate evidence. The presence of a saved payment method does not explain why a store acknowledgment is selected.

WooCommerce documents different terms presentations: the classic shortcode uses an acceptance checkbox, while the Checkout block presents an agreement message with links. Identify the assigned checkout and any extension responsible for the observed control. Neither description identifies the cause of a custom checkbox’s preselection.

Separate the first display from the order record

Preserve the observation before clearing or changing the field: page address, time, checkout type, whether the buyer was returning, and whether this was a new order or a return to an unfinished checkout. Keep customer information out of shared screenshots and consultation messages.

Ask the maintainer to trace the initial value through the installed configuration or code. A field default, stored account preference, session value or restored browser state are possibilities to investigate, not findings about your store. A difference between observed visits is a clue; it does not by itself identify which layer supplied the value. Record the actual setting or code reference that establishes the source.

Compare the first-display observation with the value retained on an actual completed order, where one exists. A stored affirmative value may show what the system saved without showing whether the buyer selected it during that order. Record whether evidence of an action, a time and the wording version exists, or whether only a value is kept. Do not add a fresh acceptance time to an old order to fill a missing record.

Compare continuing permission with the requirement for this order

Have the merchant’s requirement owner identify the written rule: acknowledgment for each order, agreement to a named version, or continuing permission with a defined scope. Where the rule requires a fresh action, a carried value without evidence of that action does not demonstrate that the rule was met. Where continuing agreement is intended, compare the original record and its scope with the current wording and use.

Stripe’s saved-payment guidance illustrates this scope distinction for Stripe payment methods: setup can save details without charging, and later use must stay within what the customer agreed to. Future reuse and offline charges require specific consent and a retained record. That guidance does not authorize reuse of every store acknowledgment or determine the legal effect of this checkbox.

Choose a correction that preserves the intended control

If a traced retention rule matches the merchant’s requirement and its supporting record is retrievable, document that finding and its limits. If it conflicts with a per-order requirement, assign a precise correction: the intended initial state, buyer action and evidence to retain. Keep the required control enforced while resolving its behavior. An unknown source stays unresolved; changing the requirement to fit the screen does not explain the value.

For a Prism checkout consultation, describe the page, acknowledgment purpose, initial state and missing evidence. Scope, responsibilities, fees and terms are confirmed before work. Send the website, research-only products and question without customer records, card details or passwords. Follow-up is by email; an inquiry does not book an appointment, purchase implementation or submit a processing application.

Acknowledgment-state trace

Use the observed checkout, installed control and actual requirement. Intentional retention needs both a traced source and a matching rule. Use internal references without customer information; leave unavailable evidence unresolved.

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.