WooCommerce · Stripe · Help

WooCommerce Stripe: Apple Pay missing after domain verification?

Check the gateway, display location and eligible wallet environment before rebuilding domain registration or payment settings.

Source date: 5 November 2026Editorial team: KAN KAI WORKSEditorially updated:

Quick answer

A verified Stripe domain alone does not guarantee an Apple Pay button at every location or on every device. Check the installed gateway, exact domain and enabled express locations. Compare the same page in a supported environment with a configured wallet. If the button remains absent, use the first browser finding to distinguish output never created, a hidden area and a blocked script request.

Source basis: Q1 · Q2 · Q3

Applies to
Official WooCommerce Stripe extension with Apple Pay; not interchangeable with WooPayments or other Stripe plugins. Domain, display location and customer environment need a consistent comparison.
How to verify the result
Apple Pay appears in the previously affected eligible device and page context, and an agreed test completion confirms the correct amount and order mapping.
Your first check

Is Apple Pay absent everywhere, or only on one device or page type?

Confirm the installed Stripe plugin, exact domain and enabled button locations. Then compare the same page using an eligible device with a configured wallet.

Stripe shows the domain as verified and Google Pay appears, but Apple Pay is absent from the product page or checkout. The reviewed report describes this pattern. Domain verification is only one requirement; it does not establish that every customer environment and page area must display the button. Q1

Identify the integration first

This guide concerns the official WooCommerce Stripe extension. WooPayments and other Stripe plugins can have different settings and workflows. Record the plugin name, version, connected Stripe account and test or live environment before combining instructions.

WooCommerce documents requirements including HTTPS and domain registration, together with configurable locations for express methods. The exact domain used for the visit matters; a different subdomain is not an identical comparison. Q2

Compare three independent dimensions

  1. Page location: Check whether express buttons are enabled for the product page, cart or checkout concerned. A button absent from a disabled location is not a loading failure. Record where other express methods appear.
  2. Customer environment: Use a currently supported device and browser context with an eligible wallet actually configured. Compare a direct browser visit with any embedded in-app visit. A device without a suitable wallet is not a useful positive control.
  3. Product and session: On staging, compare a simple supported product with the affected cart. Keep currency, login and environment consistent. This helps separate product conditions from a general failure to render the integration.

When the requirements appear satisfied

Open the console and network panel before loading the page. Distinguish a button never created, a created but hidden area and a blocked payment-script request. Investigate the first error rather than only the subsequent failures. Re-registering a domain is not a targeted correction for a theme CSS problem.

Compare saved gateway settings with the actual display location. The official settings include the relevant express options. Q3 Test script optimisation or consent-integration changes individually on a copy, so you can identify which condition alters the result.

After correction, repeat the original device and page combination with a fresh session. Record the state that now works, including the checkout type, rather than relying only on a screenshot of a button from another page.

Example: Apple Pay appears at checkout but not on a product

Constructed diagnostic example: In an assumed test setup, Apple Pay appears at checkout but not on the product page. The domain, eligible device, browser and configured wallet remain the same. This is not a report of a test we performed.

  1. Read the display settings: Open express-checkout settings in the WooCommerce Stripe extension actually installed. Compare the saved selections for checkout and product pages. If product pages are not selected, the different display is initially explained.
  2. Change one condition: If both locations are enabled, compare the product page and its checkout using the same device. Changing domain, browser and product together would make the observation ambiguous.
  3. Classify the missing output: If a button container exists but is hidden, investigate presentation. If a payment script fails, preserve its first error. If the container is absent, inspect integration and location settings first.

Expected observation: Record each location's saved configuration beside its visible result. Only then add a comparison with another eligible device.

Success check: The button appears after reloading the intended eligible page context. This establishes display only. A complete payment flow needs a separate supported test mode and an order check. Do not initiate a real payment for this display comparison.

Technical references: WooCommerce: Enabling express checkouts.

Frequently asked questions

Does visible Google Pay mean Apple Pay must also appear?

No. It establishes availability of a different express route in that environment. Each wallet’s requirements still need checking.

Must I upload my own Apple certificates?

Not speculatively. Follow the installed gateway’s supported setup. The official Stripe extension handles its required domain file; unrelated manual integrations can complicate the diagnosis.

Does a visible button prove a successful payment flow?

No. Rendering and completing payment are separate checks. Complete a test only in the agreed test environment, then inspect its order mapping.

Information for assistance

Provide the plugin and version, display location, exact domain, device and browser, wallet readiness and first script error. Do not send card data or wallet secrets.

KAN KAI WORKS can investigate express configuration and the missing button output. Get help with this case.

Support with this issue

KAN KAI WORKS can investigate express configuration and the missing button output.

Describe your case →Related service: Shops & e-commerce

Sources and scope

Sources checked: 5 November 2026. The original incident has not been independently reproduced.