How to Enable Apple Pay in Stripe, Add & Setup Easily 2026

Start at the Stripe sign-in page and log in with the account that actually processes your live payments — not a personal test account you spun up to try something. If your organisation uses Google or SSO, use those buttons rather than a password, because Apple Pay settings sit behind account-level permissions and a second, disconnected account will send you round in circles later when the domain won't verify.

Once you're in, check the account switcher at the top-left of the dashboard: Stripe keeps a sandbox and a live account side by side, and Apple Pay has to be configured separately in each. Enabling it in the sandbox is the sensible place to start, but remember to repeat the domain step on the live account before you announce anything.

Apple Pay isn't a top-level menu item. It lives in Settings under Payment methods, which opens a long table of every method Stripe can offer you: card networks, bank debits, buy-now-pay-later options, and a Wallet group that includes Apple Pay, Google Pay, Cash App Pay, Link, and several region-specific wallets.

Each row shows the method's type, the regions it's popular in, and a status on the right — either a green Active tick or a Turn on button. Scroll to the Wallet rows and look at Apple Pay's status honestly: if it already says Active, your remaining problem is almost certainly domain registration, not the toggle.

Click Turn on in the Apple Pay row. Stripe enables it at the account level immediately — there's no application or approval queue for the web version, and no extra fee, since Apple Pay transactions settle at your normal card processing rate.

What the toggle does not do is make the button appear on your site. Stripe will only serve the Apple Pay button to a domain it has verified, so a freshly toggled account still shows nothing on the storefront. While you're in this table, it's worth turning on Google Pay in the same pass: it's the Android-side equivalent, the setup cost is the same click, and offering only one wallet leaves half your mobile traffic typing card numbers.

This is the step that catches everyone. From the Apple Pay settings page, open the web domains area and add the exact domain your checkout is served from — including the subdomain, so `shop.example.com` and `example.com` are two separate registrations.

Stripe then needs to prove you control it, which means downloading the association file it gives you and hosting it at `/.well-known/apple-developer-merchantid-domain-association` on that domain, reachable over HTTPS with no redirect. If you use Stripe Checkout or Payment Links, Stripe hosts the page itself and this is handled for you; the manual file only applies when you're embedding Elements or the Payment Request button on your own pages. Verify, and the domain flips to a verified state in the list.

The Apple Pay settings page has a second section, iOS certificates, and it exists for a completely different purpose than the domain list above it. Adding one starts with downloading a Certificate Signing Request from Stripe, which you exchange for a certificate on Apple's developer site and upload back — that's the flow that genuinely requires an Apple Developer account.

You only need this if you're taking Apple Pay inside an iOS app you publish. If your store is a website, the section will simply say there are no iOS applications, and that's the correct end state — leave it alone rather than working through a certificate you don't need.

Apple Pay will not 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 very little. Open your checkout on an iPhone in Safari, signed into an Apple ID with at least one card added to Wallet, and confirm the black Pay button renders above the card fields.

Run the transaction in your sandbox first, then repeat the whole check on the live account, because the domain registration doesn't carry over between them. Finally, look at the payment in the Transactions list and confirm it's recorded as a wallet payment — that's how you'll later tell how much of your revenue the button is actually earning.