Apple Pay not working
The one-tap checkout became a zero-tap checkout.
Apple Pay is the closest thing e-commerce has to frictionless — the customer who'd abandon a card form will tap once and buy. When the button vanishes or errors, those exact customers leave silently. And because the button only shows on Apple devices with wallets set up, owners on desktops can go months without noticing.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
Apple Pay on the web is deliberately fussy: Apple demands proof of domain control and a spotless HTTPS setup before the button may appear. Your payment processor (Stripe, Square, PayPal) hosts a verification file at /.well-known/apple-developer-merchantid-domain-association — and anything that blocks, redirects, or 404s that path silently disqualifies the domain. Security plugins, WAF rules, and migrations break that path constantly, which is why the button's most common failure is simply vanishing after some unrelated-seeming change.
The other failure family is conditional display logic. The button legitimately hides when prerequisites aren't met — non-Safari browsers, devices without wallet cards, certain cart contents (subscriptions and some shipping setups, depending on gateway support). That's why diagnosis starts by separating 'broken for everyone' from 'hidden for this viewer': half of reported Apple Pay outages are an owner testing in Chrome on Windows, and the other half are genuinely broken verification, HTTPS hiccups, or gateway config that a migration or renewal quietly damaged.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
The domain-verification file unreachable
Security rules or redirects blocking /.well-known/ — Apple re-checks, fails, and pulls the button. The leading silent killer, especially post-migration.
HTTPS imperfections
Expired certificates, mixed content, or redirect quirks — Apple's bar is stricter than a browser padlock.
Gateway configuration drift
Express-checkout settings toggled off, API keys rotated, or the gateway's Apple Pay registration lapsed.
It was never broken — just conditional
Testing from a non-Apple browser or a device without a wallet. The button is working exactly as designed, invisibly.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Test where the button can exist
Safari, on an iPhone with a card in Wallet, real product, real checkout. Only that context can confirm an outage — anything else is checking for daylight at midnight.
- 2
Fetch the verification file yourself
Visit yourdomain.com/.well-known/apple-developer-merchantid-domain-association. A 404 or a redirect is your diagnosis in one request.
- 3
Check the gateway dashboard's Apple Pay panel
Stripe and friends show domain verification status explicitly. 'Failed' or a missing domain there means re-registration is the fix.
Stop and call when…
- The verification path is blocked by rules you can't safely rewrite — precision allowlisting territory
- Multiple express options (Apple Pay, Google Pay, PayPal) interact — changing one can hide another
- Revenue is actively leaking — express checkouts convert too well to debug at leisure
From there it’s our job: same-day look, flat quote, and the $389 flat repair covers most cases of exactly this.
Form & Email Rescue — buy it now, skip the hunt.
Contact forms delivering again, order and notification emails reaching inboxes.
Covers form and site-email failure on one site: broken submissions, vanishing notifications, spam-folder exile. Includes deliverability setup (SPF/DKIM) where the fix needs it.
Questions we hear a lot.
How much does a missing Apple Pay button actually cost?
It's your highest-intent mobile buyers paying the price: express-checkout users convert at multiples of card-form users because friction is the main cart killer. When the button dies, they don't switch to typing a card — a meaningful share just leaves. The leak is invisible in any error log; it only shows in mobile conversion rates drifting down.
Apple Pay worked for months. Nothing changed. Why is it gone?
Something changed — just not visibly. Certificate renewals, a security plugin update tightening rules around /.well-known/, a host migration, a gateway re-registration lapsing: Apple re-verifies continuously, and the first failed check removes the button without a single notification to you. 'Nothing changed' is the classic prologue to finding which of these did.
What does the $389 fix include?
The full path: verification file reachable and valid, HTTPS brought to Apple's bar, gateway registration repaired, conflicts between express options resolved — then a real transaction tested on a real device, refunded, and documented. It's priced with the form-and-checkout rescues because that's what it is: money-path repair.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
One tap, working again. Tested on real hardware.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.