Easy Tech TutsHow to Enable Apple Pay in Stripe, Add & Setup Easily 2026
By Impran M NLast checked against official docs
Apple Pay is one of the cheapest conversion wins available on a checkout: the customer authenticates with Face ID instead of typing a card number, and drop-off between "add to cart" and "paid" tends to shrink. Stripe supports it natively, so there's nothing to install, but it won't render on your site until Stripe has registered the domain you serve checkout from.
This guide follows the order the dashboard imposes: sign in, turn on the wallet, register your domain, and only then test. It also covers the separate iOS certificate flow, needed only if you're taking Apple Pay inside a native app rather than a website.
01Sign in to the Stripe account that owns your checkout
Start at the Stripe sign-in page and log in with the account that processes your live payments, not a personal test account. If your organization uses Google or SSO, use those buttons instead of a password: Apple Pay settings sit behind account-level permissions, and a second, disconnected account will send you in circles later when the domain won't verify.
Once you're in, check the account switcher at the top left. Stripe keeps a sandbox and a live account side by side, and Apple Pay has to be registered separately in each.
02Turn on Apple Pay in payment methods
Apple Pay isn't a top-level menu item. It sits in Settings under Payment methods, in a Wallet group alongside Google Pay, Cash App Pay, Link, and several region-specific wallets.
Each row shows a status on the right, either a green Active tick or a Turn on button. Click Turn on for Apple Pay and Stripe enables it at the account level immediately: there's no application queue for the web version.
What the toggle doesn't do is make the button appear on your storefront. Stripe only serves it to a domain it has registered, so a freshly toggled account still shows nothing on the live site.
03Register your domain
If your checkout runs on Stripe Checkout or a Payment Link, skip this step: Stripe hosts that page itself, so Apple Pay works with no domain setup at all. If you're embedding Elements or a Payment Request button on your own pages, open the Payment method domains area (reachable from the Apple Pay settings screen or directly under Settings) and add the exact domain your checkout runs on, including the subdomain: shop.example.com and example.com count as two separate registrations.
Stripe's current process handles Apple's merchant validation for you: there's no Certificate Signing Request to generate and no association file to download and host yourself. Enter the domain, save, and it moves to a registered state in the list. This replaces the older manual well-known-file process some guides still describe.
04Add an iOS certificate only if you have a native app
The same settings area has a second section, iOS certificates, for a different purpose entirely. Adding one starts with downloading a Certificate Signing Request from Stripe, exchanging it for a certificate on Apple's developer site, then uploading it back.
That flow does require an Apple Developer account. You only need this if you're taking Apple Pay inside an iOS app you publish. For a website, leave this section alone; there is nothing to configure here.
05Test on a real Apple device before you announce it
Apple Pay won't appear in Chrome on Windows, in a desktop browser without a card in Wallet, or in most emulators, so a test that shows nothing tells you little. Open your checkout on an iPhone in Safari, signed into an Apple ID with at least one card in Wallet, and confirm the black Pay button renders above the card fields.
Run the transaction in your sandbox first, then repeat the check on the live account, since domain registration doesn't carry over between them. Afterward, look at the payment in the Transactions list and confirm it's recorded as a wallet payment.
When it doesn't work
Apple Pay is toggled on but the button never appears on the storefront
Why: The domain serving checkout isn't registered yet. This only matters for Elements or a self-hosted Payment Request button; Checkout and Payment Links don't need it.
Fix: Add the exact host, subdomain included, to the Payment method domains list and confirm it shows as registered.
The button works in the sandbox but not on the live site
Why: Sandbox and live are separate Stripe environments, and a domain registered in one doesn't carry over to the other.
Fix: Repeat the domain registration step on the live account before launch.
Testing shows nothing at all
Why: Apple Pay only renders on Apple hardware, in a supported browser, with a card already added to Wallet. It won't appear in Chrome on Windows, most emulators, or a browser with no saved card.
Fix: Test on a physical iPhone or Mac in Safari with a card in Wallet, and use Stripe's dedicated wallet test page if the button still won't render.
The iOS certificate section looks like it's required to launch
Why: It's easy to assume this step applies to every integration, but it only matters for a native iOS app.
Fix: If your checkout is a website, skip it entirely. An empty iOS certificates section is the expected state.
Frequently asked questions
Do I need an Apple Developer account to enable Apple Pay in Stripe?
Not for a website. Stripe handles Apple's merchant validation for web domains itself, so a normal Stripe account is enough. An Apple Developer account is only needed for the iOS certificate flow, which applies to a native iPhone app.
Why isn't the Apple Pay button showing on my site after I turned it on?
Almost always an unregistered domain. Stripe only serves the button to domains added under Payment method domains, and subdomains count separately. Checkout and Payment Links are the exception — they need no domain setup at all.
Do I have to host a verification file myself?
No, not with Stripe's current process. You register the domain in the dashboard and Stripe handles the Apple merchant validation behind the scenes. Older guides describing a manual .well-known file upload are describing a process Stripe has since simplified.
Can customers use Apple Pay on Android devices?
No. It appears only on Apple hardware with a card in Wallet, in a supported browser such as Safari. Google Pay is the equivalent for Android and sits in the same payment methods table.
Does domain registration carry over between sandbox and live?
No. Register the domain separately in each environment, and remember to repeat the step on the live account before launch even if it already works in the sandbox.
Sources and last check
Click path and screens come from a walkthrough recorded in 2025. Re-checked against Stripe's official documentation in September 2026, which corrected a real change in this guide: Stripe no longer asks merchants to download and host an apple-developer-merchantid-domain-association file for web domains. That verification now happens automatically when you register the domain in the dashboard. The no-extra-fee claim was confirmed against Stripe's own pricing support article.
About the author
Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.
