WooCommerce express checkout compatibility depends on more than whether a payment method has been enabled in the store settings. The option shown to a customer can depend on the exact payment implementation, product type, browser and device, merchant and customer location, transaction currency, stock, order value, tax configuration, checkout fields and site security requirements. As a result, a missing express checkout option is not automatically evidence of a theme, plugin or display failure.
The first step is to identify whether the store uses WooPayments or the Stripe extension and which method is being tested. Their documentation describes different method sets and eligibility rules. Apple Pay, Google Pay, Amazon Pay, WooPay and Link by Stripe also behave differently at checkout. Separating these cases makes troubleshooting more precise and helps avoid changes that could affect tax calculation, required customer data or order processing.
What WooCommerce Express Checkout Includes
WooPayments documents five express payment methods: Amazon Pay, Apple Pay, Google Pay, Link by Stripe and WooPay. They should not be treated as interchangeable. Apple Pay, Google Pay and Amazon Pay appear as payment buttons. WooPay has a separate button, while Link by Stripe is presented inside the checkout form as an autofill method rather than as a standalone button.
The Stripe extension documentation covers Amazon Pay, Apple Pay, Google Pay and Link by Stripe, with its own site, account, product and currency requirements. Therefore, a store owner should record the exact extension and method before comparing expected behavior with documentation. A rule described for WooPayments should not automatically be presented as a universal rule for every Stripe-based checkout implementation.
Buttons versus checkout autofill
When checking whether express checkout is available, first decide what should actually be visible. A missing Apple Pay, Google Pay or WooPay button is a different diagnostic case from Link by Stripe not appearing as a separate control. Link is intended to appear within the checkout form and autofill checkout information, so looking only for a dedicated button can lead to a false diagnosis.
Also test the location where the payment method is expected to appear. The relevant page may be a product page, cart or checkout, depending on the implementation and configuration. Record the method, page, product and browser used for the test rather than comparing different conditions as if they were identical.
Compatibility by Product Type
Product compatibility is method-specific. WooPayments documents Apple Pay and Google Pay for simple and variable products, subscriptions, bookable products, bundled products, composite products and Mix and Match products, subject to additional conditions. WooPay supports the listed categories except bookable products in the WooPayments documentation. This is a documented comparison, not a guarantee that every product extension or configuration will qualify.
WooPayments product comparison
For Apple Pay and Google Pay in WooPayments, the documented product list includes:
- Simple and variable products.
- Subscriptions.
- Bookable products.
- Bundled and composite products.
- Mix and Match products.
WooPay has the same listed scope except for bookable products. Additional conditions can still affect whether a method is displayed. The exact product configuration, stock status, order value and checkout context matter. The product name alone is not enough to establish compatibility, particularly when another extension adds uploads, pre-orders, custom options or a non-default product flow.
Product and order conditions that hide methods
The Stripe documentation identifies situations in which express methods may be hidden. These include non-default product types, certain pre-orders, composite products, file-upload fields, free products and variable subscriptions with an out-of-stock variation. WooPayments also documents unsupported product types, zero-value orders and out-of-stock products as causes of disabled express buttons.
Check these conditions before investigating a theme or optimization plugin:
- Confirm that the product and selected variation are in stock.
- Check whether the order total is zero or the product is free.
- Review pre-orders, composite products, file-upload fields and other non-default product types.
- Check the exact subscription or variation configuration.
A hidden method can therefore be an eligibility outcome rather than a display malfunction. Compatibility should be assessed against the payment extension and the complete product configuration.
Regional, Currency, Browser and Site Requirements
Express checkout availability can also depend on the merchant account, customer location, currency, browser and device. WooPayments documents Link by Stripe as requiring a U.S.-based account with the customer paying in USD in the described compatibility context. WooPay is limited there to U.S.-based merchants and U.S. customers. Amazon Pay has method-specific restrictions involving supported merchant countries, tax setups and currencies.
The Stripe extension documentation separately describes account-country and currency requirements for Link by Stripe and Amazon Pay. This means there is no single regional or currency rule for every express method. The exact extension, merchant country, customer location and transaction currency must be checked together.
A pre-troubleshooting eligibility checklist
For Stripe express checkouts, the entire site must use HTTPS and have a valid SSL certificate. Apple Pay additionally requires port 443, TLS 1.2 or later, and the domain enabled in Stripe’s payment method domains. Google Pay also requires the domain to be enabled there.
Before testing conflicts, verify the following:
- The whole site uses HTTPS and the SSL certificate is valid.
- The required domain settings are completed for Apple Pay or Google Pay where Stripe requires them.
- The merchant country, customer location and currency meet the rule for the exact method.
- The test uses the relevant browser and device combination.
- The account and payment settings do not disable the method.
Apple Pay, Google Pay and Amazon Pay are enabled or disabled together in both the WooPayments and Stripe documentation. In WooPayments, Link by Stripe and WooPay cannot be enabled at the same time. These configuration states should be checked before assuming that a button has failed to render.
Custom Checkout Fields and Express Payments
Custom fields are a frequent source of confusion because some express methods bypass the normal checkout form. In WooPayments, Apple Pay, Google Pay and Amazon Pay do not collect fields added through Checkout Field Editor. WooPay is also documented as incompatible with Checkout Field Editor. Link by Stripe behaves differently: it autofills the checkout form and remains compatible with those fields according to the WooPayments documentation.
Bypassed fields versus autofilled fields
A wallet method that bypasses the normal form cannot be evaluated in the same way as an autofill method. If a store requires a custom delivery instruction, registration value or other field, verify whether the chosen payment method actually presents and collects it. Do not assume that a field visible in the standard checkout will also be included in a wallet flow.
Before changing a field from required to optional, identify how the value is used. Omitting a required field can affect order processing, tax, fulfillment or other store workflows. The supplied documentation does not establish compatibility for every third-party checkout-field extension, page builder or theme, so each implementation requires its own test.
Block and classic checkout differences
The Stripe documentation distinguishes custom fields registered for the Checkout block from fields added through the classic checkout fields filter. Fields available on the checkout page may be collected, and block express checkout can save entered values. However, a required field that is unavailable on the product or cart page can block payment after the wallet sheet has been approved.
Test the field in each relevant location: product page, cart, classic checkout and Checkout block. Record whether it is required, where it is registered and whether the express flow reaches the payment step. Do not generalize the behavior of one field implementation to every checkout configuration.
Why the Express Checkout Button Is Missing
A missing button should be investigated as an eligibility question first. Confirm that the selected method is expected to appear as a button, then check the product, order and account conditions. For non-shippable products, Apple Pay and Google Pay may be hidden when prices exclude tax and tax is calculated from the customer’s billing address. The billing address is not known before checkout, so the method may be intentionally unavailable.
Eligibility before conflict testing
Use this order of checks:
- Identify the exact payment method and extension.
- Confirm that the method is enabled and note any mutual-exclusion rule, including the WooPayments Link by Stripe and WooPay restriction.
- Check product type, variation, stock status, order total and whether the product is shippable.
- Review free products, pre-orders, file uploads, composite configurations and subscription conditions.
- Verify HTTPS, SSL, port and domain settings where applicable.
- Check merchant country, customer location, currency, browser and device.
- Review custom fields and the tax configuration for non-shippable products.
Only after these checks should you investigate theme behavior, caching, optimization or other third-party integrations. Do not force-enable an option hidden because billing-address-based tax calculation is unresolved. Any customization that overrides documented hiding behavior should be treated as advanced work, tested in a staging environment and reviewed for checkout and tax consequences.
The same process answers why a WooCommerce express checkout button is not showing without prematurely assigning blame to a plugin. A method can be unavailable because the customer is in an unsupported region, the currency does not qualify, the product is out of stock, the order has zero value or the required field cannot be collected.
Official Logging and Testing Workflow
For WooPayments, the documented troubleshooting path is to enable debug mode and logging where applicable, reload the page where the express option should appear and inspect the latest WooPayments log. Messages such as Express Checkout Element button disabled and WooPay Express button disabled can identify an eligibility failure.
Use the log together with a controlled test rather than changing several settings at once. The documentation does not verify compatibility with every third-party gateway, checkout-field extension, theme, cache layer, optimization plugin or page builder. A specific site-level cause therefore requires testing.
A controlled test record
For each test, record the exact payment method and extension. Also record the product type, selected variation, stock status, order value, browser, device, customer region and currency. Note whether the product is shippable, whether tax is calculated from the billing address and whether custom fields are required.
Compare results only when the relevant conditions are clear. If the button appears for one product but not another, compare product eligibility before changing the theme. If a wallet sheet approves payment but the order stops afterward, review required fields and their registration location. Test tax, checkout and field changes in a staging environment or controlled test order before applying them to production.
In summary, WooCommerce express checkout compatibility is a combination of payment-method rules, product eligibility, account and regional requirements, browser and device context, site security, tax settings and custom-field behavior. Start by distinguishing buttons from Link by Stripe autofill and by identifying WooPayments or the Stripe extension. Then verify product, stock, order value, currency, location, HTTPS and domain requirements. Test custom fields separately and inspect WooPayments logs when applicable. A missing option is often an intentional eligibility result, but the official documentation does not identify a specific cause without testing the affected site. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.