Apple Pay or Google Pay Missing in WooCommerce After a Domain Move?

In this guide

If Apple Pay or Google Pay disappeared from WooCommerce after a domain move, check the exact new hostname in the connected Stripe account’s payment-method domains, then verify HTTPS and wallet eligibility. For Apple Pay, also check that the domain association file is reachable. A working card form does not prove the new domain is ready to display wallets.

This guide covers the official WooCommerce Stripe extension. Other Stripe plugins can expose different settings or handle verification differently, so identify the installed gateway before following menu instructions or replacing files.

Record what changed and what is missing

Note the old and new domain, whether www changed, whether checkout moved to a subdomain, and when DNS and HTTPS were switched. Record the Stripe extension version, connected account and active environment. Confirm whether wallets disappeared from product pages, the cart, checkout or all three.

Test the same product and customer environment that previously worked. A new test involving a different browser, unsupported product or empty wallet can make a successful migration look broken. Keep payment secrets and customer wallet details out of screenshots shared with support.

Check the domain in the right Stripe account

Stripe’s domain-registration guidance requires registration of domains and subdomains displaying relevant payment methods in supported embedded integrations. The old domain’s registration does not stand in for a different hostname. Check the account actually connected to the store, not another Stripe account used by the same business.

1. Confirm the browser’s final hostname. Follow the normal redirect to checkout and record where the wallet interface is displayed.
2. Find that hostname in payment-method domains. Check that it is enabled and any reported verification issue is resolved.
3. Check the intended environment. Review the live or sandbox configuration used by that checkout rather than assuming a successful test covers production.
4. Identify embedded or platform arrangements. If checkout is inside an iframe or uses connected accounts, have the integration developer confirm all relevant domain and account requirements.

Owners with authorized Stripe access can review these settings. A developer should investigate custom checkout embedding or account routing. Do not reconnect the store to a different Stripe account simply to make a button appear; that can change where transactions and records belong.

Verify HTTPS and the Apple association file

The WooCommerce Stripe express-checkout documentation requires a valid SSL certificate and HTTPS throughout the site. It also documents the Apple Pay association file, which the extension creates automatically. After migration, confirm the new host can serve that file through the intended public hostname.

Ask the developer or host to check the expected well-known file route and response. Password protection, security challenges, routing errors or an absent file can prevent verification. Avoid copying an arbitrary file from another store or disabling the firewall globally. Correct the specific response and complete verification through the supported gateway process.

Check the certificate for the final hostname and ensure the moved site does not send payment pages back to an old or insecure URL. A certificate installed for the apex domain may not cover every new subdomain. Use the migration DNS checklist to coordinate hosting changes without disturbing unrelated services.

Separate domain failure from ordinary wallet eligibility

Next, compare the affected device with Stripe’s wallet-rendering test guidance. Use a compatible device and browser with an appropriate wallet setup, allowed payment-method detection and supported region. Private browsing can change the result. Stripe’s demos can help distinguish a device issue from a store integration issue.

If the wallet does not appear in the appropriate Stripe demo, resolve the test environment first. If it appears there but not on the store, focus on the integration, domain configuration and product being tested. A screenshot from one device cannot establish what every customer should see.

In WooCommerce, verify that express checkout is enabled and configured to appear at the intended locations. Review the gateway’s eligibility information. Some product types and combinations are excluded; the official guide lists examples including free products, certain pre-orders and file-upload fields. A virtual product can also be affected by the configured tax-address behavior.

Use a simple, supported paid product as a diagnostic comparison, then test the real catalogue item. Do not remove required fields or change tax settings just to force a wallet button into view. Those changes can alter the information needed to complete a valid order.

Test rendering and purchase as separate steps

Once the button appears, use the gateway’s supported sandbox process to complete the intended journey. Confirm the wallet approval, WooCommerce order, Stripe transaction state, shipping and tax totals, and expected notifications. Test the product-page and checkout entry points if the business offers both.

Check custom required fields and the actual checkout design. A button rendering correctly does not prove that all order requirements are collected. If the customer was charged during an earlier failed attempt, reconcile that transaction before asking them to retry; the charged-but-error guide covers that separate situation.

After a targeted configuration change, clear relevant cached pages and retest the new hostname on the affected wallet environment. Record the domain entry, account, environment, device, product and result so the business has a repeatable acceptance check for its next migration.

FAQs

Why do cards work when Apple Pay is missing?

Wallet rendering has additional domain and environment requirements. Verify the exact hostname, Apple association file and supported device rather than assuming the entire gateway connection has failed.

Does registering the old domain cover a new shop subdomain?

Do not assume it does. Review Stripe’s payment-method domains for the exact new hostname and the account and environment used by the store.

Should the wallet button appear on every product and browser?

No. Device, browser, region, wallet setup, product eligibility and checkout configuration influence whether it appears. Compare a supported test product and wallet environment before diagnosing a migration fault.

Prepared for website owners by Nithu / Suthakaran Nithursan. Dated advisory facts link to primary sources. Examples are illustrative and are not client results or guarantees.