The Link agreement is different from the store’s own terms
Map each visible agreement to the product that renders it and the party whose terms it links to. Stripe documents that the Payment Element terms option cannot remove the Link legal agreement. Keep that provider agreement intact, and configure the merchant's terms through the store's own documented controls. On WooCommerce, the classic shortcode checkout presents terms with an acceptance checkbox, while the Checkout block presents an agreement message with links. The Link agreement does not substitute for identifying and configuring the store's own policy presentation.
For: A research-only merchant reviewing agreement text beside a payment form and deciding which wording or controls may be changed.
Identify each agreement by its destination and owner
Record the visible text, where it appears and the destination of each public policy link. Distinguish an agreement for using a provider's payment service from the merchant's terms for the order. Two sentences beside the same payment button can have different owners and purposes. Their physical proximity does not make them a single piece of merchant copy.
Then identify the integration actually installed: the payment component, the store's checkout type and the extension or custom integration responsible for connecting them. Stripe's Payment Element documentation describes supported options, but it does not prove which options a particular store extension exposes. A payment provider's name on the page is not enough to identify its integration or the setting that controls a sentence.
Keep the scope narrow enough to answer the observed problem. If the merchant policy link is wrong, record that destination. If the request is to change Link text, identify it as provider-owned. If an acceptance control is absent, identify the actual checkout type before deciding that the absence is a defect.
The Payment Element terms option has a specific limit
Stripe explicitly says the Link legal agreement cannot be removed through the Payment Element terms option. A request to remove all legal text through that option therefore includes a result the documented option cannot deliver. Preserve the provider agreement and revise the change request to identify the merchant-owned wording that actually needs attention.
Do not turn a styling change into a way to hide the provider agreement, cover its links or replace it with a merchant-written paraphrase. That would not establish a supported agreement configuration. If the installed extension does not document how it exposes a needed option, the open question is its supported configuration for the installed version, not which visual workaround makes the text disappear.
This boundary concerns the Payment Element's Link agreement. It does not describe every Stripe-hosted page or every payment extension. It also does not decide whether Link or any payment method is available or approved for this merchant. Technical display and the provider's eligibility decision remain separate.
Configure merchant terms on the checkout the store uses
WooCommerce's advanced settings documentation describes selecting the store's terms and conditions page. With the classic shortcode checkout, the terms can be opened inline and the buyer ticks an acceptance checkbox. With the Checkout block, the documented presentation is an agreement message with terms and privacy links, and the message can be edited in the block editor. A demand for the classic checkbox cannot be assumed to describe the block's documented presentation.
Compare the configured destination with the live public terms page and the text the buyer sees. Record the policy version the merchant intended to present. A correctly titled link that opens an obsolete page is still a mismatch, and a provider agreement beside it does not repair that mismatch. Conversely, finding the merchant's linked message on a block checkout is not evidence that the classic checkbox was accidentally removed.
If the merchant requires an additional research-only acknowledgment, state its purpose and required behavior separately. Identify the documented configuration for that control and what evidence, if any, the installed integration retains. Do not claim that the Link agreement, a merchant terms link or a checkbox verifies a buyer's identity or research status. The need for a particular legal control must be resolved for the business; these software documents do not settle that question.
Close the configuration question with visible evidence
For the affected checkout, compare three things: the provider agreement remains readable and its links accessible; the merchant links open the intended public policies; and the merchant control matches the documented checkout configuration and approved requirement. Record what was actually observed without submitting a payment merely to inspect text. A screenshot can show wording and placement, but cannot by itself prove that an acceptance result was stored.
Decide the next action from the ownership map. Correct a merchant destination through its documented setting, return provider-text changes as a supported-configuration question, or keep an undocumented required control unresolved until the installed product's behavior is established. Do not switch checkout type solely to imitate another checkout's appearance without first assessing its dependencies.
For a PRISM checkout-review consultation, provide the website, research-only products, checkout type and the specific agreement mismatch. Confirm any configuration or implementation assistance, responsibilities, fees and terms before work. The public inquiry receives email follow-up and does not book an appointment, buy a change or apply for processing. Leave out credentials and customer records.
Agreement ownership map
Use one copy for each distinct agreement or required control. Fill it from the current checkout and its installed product documentation. An unknown owner or undocumented control remains an open configuration question; do not resolve it by hiding text.
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.
Agreement ownership map. The last column is for temporary notes.
Ownership item
What to record
Decision it supports
Your mapping
Visible agreement text
What to recordThe short text needed to identify the agreement, its checkout location and its public link destination.
Decision it supportsEstablish which particular agreement is being discussed before changing it.
Provider or merchant owner
What to recordThe party named by the agreement and the product rendering it.
Decision it supportsPreserve provider-owned agreement text; assign merchant copy to its authorized owner.
Supported configuration
What to recordInstalled checkout type, extension or integration version and the documented setting for this text.
Decision it supportsFor Stripe Payment Element, terms cannot remove the Link legal agreement.
Merchant policy destination
What to recordThe selected public policy URL, intended version and actual page reached from checkout.
Decision it supportsCorrect a destination mismatch independently of the provider agreement.
Required store control
What to recordThe approved purpose, required buyer action and supported behavior for the installed checkout.
Decision it supportsDistinguish WooCommerce's classic checkbox from its block agreement message; leave additional controls unverified without documentation.
Retained acceptance evidence
What to recordOnly the storage behavior established by the integration documentation and the existing record available to the merchant.
Decision it supportsVisible text alone does not establish a stored acceptance result.
Open scope question
What to recordAny undocumented setting, unclear owner or unresolved requirement, plus the party who can answer it.
Decision it supportsHold that change for clarification while retaining the supported provider agreement.
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
Payment Element's Link restriction and WooCommerce's terms presentations are product-specific. They do not establish the behavior of an unseen extension or another platform.
This ownership map does not determine legal sufficiency, buyer verification or eligibility for Stripe or another payment provider.
Keep card data, authentication codes, private payment-link tokens, credentials and customer records out of the worksheet and public consultation form.
Stripe Payment Element — checked 2026-09-29. The Payment Element terms option cannot remove the Link legal agreement. Documented options do not establish a particular installed integration or merchant eligibility.
WooCommerce advanced settings — checked 2026-09-21. The classic shortcode checkout shows inline terms with an acceptance checkbox. The Checkout block shows an agreement message with links that can be edited in the block editor.
Prism solutions — checked 2026-09-21. Published help includes storefront review and provider website questions; scope, fees and terms are discussed before work. The provider decides eligibility and account terms.
Prism contact — checked 2026-09-21. The form requests website, products and question without card details, passwords or customer records. Email follow-up does not make an inquiry an appointment, purchase or processing application.