Lorixen.
EN

Apple Pay Button Not Showing on Your Website Checkout

Short answer: Apple's payment button only appears when every condition is met at once: a supported Apple device and browser, a card in that device's Wallet, a page served over HTTPS, a domain registered for Apple Pay with your payment provider, and Apple Pay enabled in the provider's payment method settings. Most "missing button" reports come down to an unregistered domain (often www versus the bare domain, or a new checkout subdomain), a checkout embedded in a frame hosted elsewhere, or a tester whose device has no card added to Wallet. Work through the conditions on a real iPhone or Mac, fix the domain registration, and the button normally appears without code changes.

Why the button is designed to hide

Unlike a normal "Pay" button, Apple Pay buttons are shown only when the browser confirms Apple Pay can actually be used. The site's script asks the browser something like "can this customer pay with Apple Pay here?", and if the answer is no, the button is never rendered. That is good for shoppers but confusing for owners, because there is no error message, just an absent button. Apple's Apple Pay on the Web documentation describes these availability checks.

So the job is to find which condition is failing.

Device and browser conditions

Test the shopper's side first, because many reports come from staff testing on unsuitable devices.

  • Safari on iPhone, iPad or Mac is the reliable baseline. Recent versions of iOS have added Apple Pay support in some third-party browsers, but behavior varies, so always start with Safari.
  • A payment card added to Wallet. On iPhone, open the Wallet app and check that at least one supported debit or credit card is added. On a Mac, check Wallet & Apple Pay in System Settings, or use a Mac with Touch ID or a paired iPhone or Apple Watch.
  • Region and card type. The issuing bank has to take part in Apple Pay, and the payment must be in a supported region.
  • Private browsing and content blockers. Some content blockers stop the payment provider's script from loading. Test with them turned off.
  • Windows and Android devices will not show Apple Pay at all; they may show Google Pay instead if you have it enabled.

If the button appears on your own iPhone but customers say it is missing, ask what device and browser they use before changing anything.

HTTPS and the domain association file

Apple Pay on the web requires the checkout page to be served over HTTPS with a valid certificate. Beyond that, every hostname displaying it has to be registered.

With most providers, registration works like this:

  1. In the payment provider's dashboard, add the domain under the Apple Pay or payment method domains section.
  2. The provider gives you a file called apple-developer-merchantid-domain-association, or hosts it for you on platforms that handle this automatically.
  3. The file must be reachable at https://yourdomain.com/.well-known/apple-developer-merchantid-domain-association, returning the file contents with a 200 status, not a redirect to a login page or a 404.
  4. Click verify in the dashboard.

Check the file in a browser yourself. Common failures:

  • The web server blocks paths starting with a dot, so /.well-known/ returns 403 or 404.
  • A security plugin or firewall redirects unknown files.
  • The site forces a redirect from the bare domain to www (or the reverse) before serving the file, and the domain being verified is the one that redirects.

www, root domains and subdomains

Registration is per exact hostname. oakandthread.com, www.oakandthread.com and shop.oakandthread.com are three separate registrations. Typical situations:

  • The bare domain was verified, but customers browse on www. because that is your canonical address.
  • You launched a new checkout on checkout.oakandthread.com or a booking subdomain and never registered it.
  • A staging domain shows the button but the live domain does not, because only staging was added.

List every hostname on which a payment form appears and make sure each is registered and verified with your provider.

Iframes and embedded checkouts

If your payment form runs inside an iframe served from a different domain, such as an embedded booking widget, a third-party donation form or a page builder's payment block, the Apple Pay check happens on the iframe's domain. In that case:

  • The domain that must be registered is the iframe's domain, which the third party controls.
  • Some embedded tools do not support Apple Pay at all inside an iframe.
  • Cross-origin iframes may need specific permissions to allow payment.

Ask the provider of the embedded tool whether Apple Pay is supported when embedded. If not, linking to their hosted payment page in a new tab is often the fix.

Payment provider settings

Even with a verified domain, the provider has to offer Apple Pay on that checkout:

  • Stripe: In the Dashboard's payment method settings, confirm Apple Pay is enabled for the payment method configuration your checkout uses, and that the domain appears under payment method domains. Stripe's Apple Pay guide covers both, plus the Express Checkout Element and Payment Element options.
  • Test and live modes: Domain registration and settings may need doing in live mode, not just test mode.
  • Platform checkouts: On hosted platforms like Shopify or Squarespace, Apple Pay is switched on in the platform's payment settings, and domain verification happens automatically for the main domain. Custom domains added later may need time to propagate.
  • Checkout code: Older custom integrations may use a separate Payment Request Button. If your developer built it years ago, check it still matches the provider's current recommended approach.

Testing on real devices

Simulators and desktop browsers on Windows tell you little. A reliable test routine:

  1. Take an iPhone that holds a real Wallet card, open Safari, and stay connected to mobile data rather than office Wi-Fi.
  2. Visit each hostname where checkout appears, including www and non-www.
  3. Add a low-cost item and go to checkout. Confirm the button appears and the Apple Pay sheet opens.
  4. Complete a small real purchase in live mode, then refund it.
  5. Repeat the run in Safari on a Mac.

Keep the results in a short checklist so the test can be rerun whenever the theme, domain or checkout changes.

FAQ

Apple Pay shows on product pages but not in the cart. What is going on?

The two pages may load different payment components or sit on different subdomains. Check that the same provider script runs on both and that both hostnames are registered.

Is an Apple developer membership required?

Usually not when using Stripe or a hosted e-commerce platform; they register the merchant identity for you. Direct integrations without a provider are a different matter.

Will Apple Pay show on Chrome on a Mac?

Support outside Safari depends on the browser and OS versions. Treat Safari as the main target and anything else as a bonus.

If the button is still missing after these checks, send us your checkout URL and we will help track down which condition fails.

Sources

WhatsAppBook a call