Turning off card payments also removed express checkout

A display preference can conflict with a payment dependency

Wanting fewer fields on screen and turning off the card method are different configuration decisions. WooCommerce's Stripe documentation says express methods generally depend on the credit/debit card method being enabled. If the buttons disappeared when that method was disabled, the documented dependency is a concrete explanation to compare with your settings.

Record which card setting changed, its prior value, the time of the change and which express buttons disappeared at which locations. Establish that this is the WooCommerce Stripe extension, including its installed version. A plugin from another vendor, WooPayments or a separate hosted checkout needs its own documentation; a Stripe logo does not identify the software implementing the page.

Read every condition of the Link exception

The exception has three named parts: Optimized Checkout Suite is in use, Link by Stripe is enabled, and the button is on the checkout page. The documentation states that Link will show there even with card payments disabled. Confirm the active mode in the installed extension rather than assuming a recent version or a saved setting means the suite is in use.

Apply that sentence only to the arrangement it describes. It does not say that enabling Link makes Apple Pay or Google Pay independent of the card setting. It also does not say that Link remains on a product or cart page with cards off. A request for Link on checkout is therefore a different request from keeping all express methods everywhere while removing cards.

The documented presentation exception does not waive Link's applicable account requirements or establish provider permission for the business. Keep the desired appearance, extension support and the account's approved methods as separate entries in the decision.

Use the settings to choose the next action

If the required presentation includes express methods covered by the general dependency, a cards-disabled configuration does not meet the documented requirements. Where card processing remains authorized, the merchant can consider restoring the necessary card setting through its normal change process. If cards were disabled because the provider limited the account, restoring the setting is not a way to resolve that limit. The provider must determine which arrangement is permitted.

If the desired arrangement is specifically checkout-page Link under the documented suite, compare each prerequisite with the installation. Mark an unknown mode or unsupported version as unresolved rather than declaring the exception available. Do not switch suites merely to make the worksheet read yes; a mode change has its own checkout dependencies and needs an agreed scope.

Where the settings already satisfy the documented dependency but a button is absent, this card-setting explanation is incomplete. Record the affected method, location and the extension's displayed requirement information for a separate visibility investigation. Repeatedly toggling cards cannot establish which other display condition is unmet.

Define what an authorized change must preserve

Write the desired result in terms of named methods and named locations. After an authorized change, compare the actual page with that statement and the saved configuration. A button preview or a rendered button establishes presentation only; it does not establish payment success or merchant approval. Preserve required checkout information and acknowledgments when evaluating a shorter presentation.

For a Prism checkout consultation, summarize the extension version, whether Optimized Checkout Suite is active, the card setting and the methods and locations you want. That is enough to frame a configuration question without sharing access credentials. Confirm the scope, responsible maintainer, fees and terms before implementation work begins.

Payment-presentation dependency

Use one installed checkout configuration. The general dependency applies unless the complete documented Link exception matches. An unknown mode or account permission remains unresolved; a visible button cannot fill that gap.

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.