The easiest way to support Apple Pay and Google Pay in a web checkout is to use a payment provider or hosted checkout that already supports both. They handle the wallet handshakes and give you the buttons. If you integrate directly, Apple Pay needs HTTPS, a verified domain and merchant validation, and Google Pay needs a payment token request through your payment gateway and approval for production.
Three ways to do it
- Use a hosted checkout. You send buyers to a page that already shows the wallets. Setup is mostly configuration. See checkout solutions with Apple Pay and Google Pay.
- Use your payment provider's prebuilt components. You embed their payment form, and the wallets appear when the device supports them. You still verify your domain for Apple Pay.
- Integrate each wallet directly. You use Apple's and Google's own APIs with your payment gateway. This gives the most control and the most work.
For most sites, route 2 is the practical choice. Route 3 is for teams that need custom behavior.
What Apple Pay needs on the web
From Apple's developer documentation for Apple Pay on the web:
- HTTPS on every page that includes Apple Pay, with a valid SSL certificate.
- TLS 1.2 or later on your server, with one of Apple's listed cipher suites.
- Your domain registered and verified with Apple. In practice you host a verification file at
/.well-known/apple-developer-merchantid-domain-association. Many providers handle this, or give you the file to host. - Merchant validation for each session, using Apple's servers. Your server must be able to reach Apple Pay's domains over port 443.
- A payment processor that can decrypt Apple Pay tokens, usually through your provider.
- A compatible device and browser. Safari on an Apple device is the reliable path. Check Apple's current docs for other browsers.
If you use a provider's components, they often take care of merchant validation, and you only host the domain file.
Add one-click upsells to your Whop
Install OneClick Upsell from the Whop App Store and offer a post-purchase upsell in a few minutes.
What Google Pay needs on the web
From Google's Google Pay API tutorial:
- Load the Google Pay JavaScript library.
- Define the API version, the card networks you accept and your payment tokenization method. With a payment gateway, you give Google the gateway name and your merchant ID at that gateway.
- Call the readiness check to see whether the buyer can pay with Google Pay.
- Show the Google Pay button when they can.
- Create a payment data request with the price and currency, and send the returned token to your gateway.
- Start in the test environment, then request production access. Google checks your integration against its checklist before you can use a production merchant ID.
Follow Google's brand guidelines for the button and its terms of service.
Mistakes that cause "the button does not show"
- The domain is not verified for Apple Pay, or the verification file is not served as plain text at the right path.
- The page is in an iframe without permission. A cross-origin iframe needs the payment permission, for example
allow="payment", and your site's headers must not block it. - The test device has no wallet set up. Add a test card to Apple Wallet or Google Wallet.
- The currency or country does not match your provider account.
- Testing on localhost or HTTP. Apple Pay needs a secure public domain.
- The browser or device is unsupported. Test on Safari with an iPhone and Chrome with an Android phone.
Test properly
- Use your provider's test mode and sandbox wallets where they exist.
- Check a real device with a real wallet, then place a small live payment before you launch.
- Test the full flow: button, payment sheet, confirmation, order record, refund.
- Check what happens when a buyer does not have a wallet. A normal card form should still show.
Shopify stores
On Shopify you do not build this. You tick Apple Pay and Google Pay in Settings, Payments, Manage, Wallets, if your provider supports them. See does Shopify accept Apple Pay.
If you sell on Whop
Apple Pay and Google Pay work on Whop-hosted checkout pages out of the box. If you embed Whop checkout on your own site, you verify your domain for Apple Pay by hosting a verification file and registering the domain with Whop. We walk through it in Whop checkout on GoHighLevel or your own site. OneClick Upsell then adds order bumps, one-click upsells and downsells to that checkout, from $19.95 per month plus Whop's processing fees. See pricing.
FAQ
How do I add Apple Pay and Google Pay to my website checkout?
Use a payment provider or hosted checkout that supports both, turn the wallets on, and verify your domain for Apple Pay. If you build it yourself, integrate Apple Pay on the web and the Google Pay API with your payment gateway.
Do I need an Apple Developer account to accept Apple Pay on the web?
If you use a provider's checkout, usually the provider's merchant setup covers it and you only verify your domain. If you integrate directly, you need an Apple Developer account, a merchant identifier and certificates.
Does Apple Pay work in Chrome or Firefox?
Safari on an Apple device is the dependable way to support Apple Pay. Apple has been adding support for other browsers, so check its current documentation before you rely on it.
Does Google Pay need approval to go live?
Yes. When you integrate it directly, you test in the test environment first, then request production access after Google reviews your integration.
Can I support both wallets with one integration?
With a payment provider or hosted checkout, usually yes. Direct integrations are separate for Apple Pay and Google Pay.
How much does it cost to support Apple Pay and Google Pay?
The wallets themselves do not add a separate charge on most platforms. You pay your provider's normal processing fee, and any monthly fee for the tool or platform.
Related reading
Ready to raise your order value?
Install OneClick Upsell on Whop and build your first upsell funnel today.
Some links to Whop on this site are affiliate links. If you sign up through them we may earn a commission, at no extra cost to you.



