Checkout reliability

When a configured payment method stops appearing at checkout

A payment method can be missing because it is disabled, incompatible with the checkout, unavailable for the account, or hidden by its display requirements. Check the store settings and checkout type, then the method’s account and buyer requirements. A missing button alone does not identify the cause or establish whether the merchant is eligible.

For: An owner or administrator of a research-only store who configured a payment method that buyers no longer see at checkout.

Updated 2026-10-06

Get help with checkout

Identify which requirement is unmet

Account eligibility, checkout configuration and payment success are different questions. First establish whether the method should appear for this account, checkout and buyer. Then compare that expectation with the actual page and enabled settings. A method that never appears has not yet reached the buyer’s payment attempt.

The provider’s eligibility decision must reflect the store’s actual business and products. If the account is not eligible for a method, changing the public description to conceal that activity does not resolve the eligibility issue. Ask the provider which options, if any, support the actual business.

Work from the cheapest check to the one only the provider can answer: store settings first, then the checkout type, then the method's display conditions, then the account.

Store settings and the checkout type

On WooCommerce, the designated checkout page is assigned under WooCommerce, Settings, Advanced. If the wrong page is assigned, buyers may be reaching a page that was never the configured checkout at all.

WooCommerce’s Checkout block needs a compatible gateway. The blocks documentation warns that an incompatible gateway may be absent, and a checkout with no compatible enabled gateways may offer no payment method. Compare the active checkout type with the extension’s documented compatibility. A recent checkout change is a useful clue; the absence of a known change does not rule out a technical fault.

Confirm the method is still enabled in the store's payment settings before concluding anything about the provider. A disabled toggle and a withdrawn capability look identical to the buyer.

Wallets have their own display conditions

The WooCommerce Stripe extension documents separate prerequisites for express methods, including HTTPS, payment-method domain registration and supported account countries or currencies. Read the requirements for the particular method and installed extension rather than assuming that enabling cards also makes every wallet available.

The extension also lists product and configuration combinations in which express buttons are hidden. Check the affected product type, shipping and tax settings, and any required fields against that list. A method visible elsewhere in the store can still be unavailable on one product or checkout location.

Stripe's own Apple Pay documentation adds the buyer side: Stripe hides Apple Pay when device or integration requirements are not met, and Elements or embedded Checkout require each domain to be registered. A wallet that appears for you but not for a customer can be the customer's device, browser, or saved-card state, not your store.

What a missing method does not prove

A missing button alone does not prove an account restriction or a store fault. Record each mismatch separately; more than one can exist. The provider must resolve any uncertainty about account eligibility, while the site maintainer can inspect the checkout implementation.

Write down what you found at each layer before asking anyone: the checkout type in use, whether the method is enabled, which wallet requirements are met and which are missing, and the exact product the buyer was viewing. That note is what the provider's support, or the person who maintains the site, needs to answer the layer they own. Prism installs and repairs checkouts for platforms and payment arrangements it supports, and can trace which layer is failing before anything is changed; the provider's own record decides account eligibility.

Payment-method visibility matrix

Compare the affected checkout with the requirements for the missing method. Record what is established and what still needs the provider or site maintainer.

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.

Payment-method visibility matrix. The last column is for temporary notes.
Possible cause	Where to inspect	What to establish	Your finding
Method disabled	Store payment settings	Whether the method is enabled for the checkout buyers reach.	Method disabled: Your finding
Checkout compatibility	Assigned checkout page and gateway extension documentation	Whether the active gateway supports that checkout type and version.	Checkout compatibility: Your finding
Account or currency eligibility	Provider dashboard and current method requirements	Whether the actual account and transaction context can offer the method; unresolved eligibility goes to the provider.	Account or currency eligibility: Your finding
Buyer device or wallet conditions	The method’s supported browser, device and saved-payment requirements	Whether the missing button is specific to an affected buyer context.	Buyer device or wallet conditions: Your finding
Product or location restriction	Extension express-checkout requirements and affected product	Whether the product, required fields or button location prevents display.	Product or location restriction: Your finding
Connection mode mismatch	Extension connection status and provider mode indicator	Whether the account and environment shown are the ones the store is authorized to use.	Connection mode mismatch: Your finding

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

Do not change the store's stated business, products, or checkout wording to make a restricted method appear. Eligibility for a payment method belongs to the provider and must reflect what the store actually sells.
The WooCommerce block rules and the Stripe extension's express-checkout requirements apply only where those products are in use; other gateways and platforms use their own display conditions.
An inquiry does not establish account eligibility or authorize a checkout change. Keep API keys, account credentials, and card data out of any public form.

Related guides

Sources

WooCommerce: Checkout block — checked 2026-09-21. The Checkout block shows payment methods that are available and compatible with the block; the designated checkout page is set under WooCommerce, Settings, Advanced.
WooCommerce: Cart and Checkout blocks — checked 2026-09-21. An incompatible payment gateway may not appear on the block checkout; if only incompatible gateways are active, no payment method may be available. Compatibility is marked on the extension's product page.
WooCommerce: Advanced settings — checked 2026-09-21. Page setup in advanced settings assigns the Checkout page; the order-received endpoint is the confirmation route.
WooCommerce Stripe: Enabling express checkouts — checked 2026-09-29. Express methods require a valid SSL certificate and sitewide HTTPS; Apple Pay also needs port 443, TLS 1.2 or later, and a registered payment-method domain, as does Google Pay. Link and Amazon Pay are limited to listed account countries and currencies. Apple Pay and Google Pay cannot be enabled separately, the card method generally must be enabled, and the page lists product cases where buttons are not shown.
Stripe: Apple Pay — checked 2026-09-21. Stripe hides Apple Pay when device or integration requirements are not met; Elements and embedded Checkout require each domain to be registered.
Prism contact — checked 2026-09-21. The public form takes the website, products, and question, excludes card details, passwords, and customer records, and does not submit a processing application. Follow-up is by email.
Prism solutions — checked 2026-10-06. Prism's services are card-processing preparation, store builds and migrations, checkout installation and repair, store operations, and website review. Checkout work names the failing component before anything is changed, then installs or repairs the checkout within an agreed scope, for platforms and payment arrangements Prism supports. It does not decide the provider's account outcome.

Get help with checkout

Is this happening on your own store?

Get help with checkout All resources