dom4in.net
← All guides
Stripe

Verify your domain in Stripe for hosted checkout and wallets

Register your domain in Stripe settings and host one verification file (or DNS record) so Apple Pay and Link work on your site — five minutes.

~2 min read 0:00 on this page

The process

The whole path from the dashboard to a verified payment domain. Crumbs link to Directions.

Directions

1Open the Stripe Dashboard

Log in at dashboard.stripe.com. Make sure you're in the right mode — verify the domain in Live mode for production, and separately in Test mode if you test wallets.

2Go to payment method domains

Open Settings, then under Payments find Payment method domains (sometimes shown as Apple Pay / domains). Click Add a new domain.

3Enter the domain you check out on

Enter the exact domain that serves your checkout (e.g. shop.example.com). It must match where the payment button is rendered.

4Publish the verification file

Stripe gives you a hosted file to place at a well-known path. Upload it so it's reachable over HTTPS without a redirect.

https://shop.example.com/.well-known/apple-developer-merchantid-domain-association

5Click Verify

Back in Stripe press Verify. Once it passes, wallet buttons (Apple Pay, Google Pay, Link) appear automatically on your Stripe checkout for that domain.

Common issues & fixes

Verification file returns 404.

It must sit at the exact /.well-known/ path and be served as a static file. Some frameworks need an explicit route or public-folder placement.

File loads but verification fails.

A redirect (http→https or www→apex) is rewriting the path. Serve the file with a direct 200 on the canonical HTTPS host.

Apple Pay button still doesn't show.

The page domain must exactly match the verified domain, the device/browser must support Apple Pay, and you must be on HTTPS. Test on Safari.

Works in test but not live.

Domains verify per mode. Repeat the verification in Live mode.

Written and maintained by Ben McDaniel. Drafted with AI assistance and human-reviewed against each vendor's current setup flow. Vendor interfaces change — if a step looks different, the underlying record is what matters.