Apple Pay on WooCommerce: how to add it, with or without Stripe

To add Apple Pay to WooCommerce, you need a payment gateway that supports it, a domain verified for Apple Pay with that gateway, and a checkout served over HTTPS. WooPayments and Stripe do it, and so does Whop if you’d rather not depend on Stripe: with the WhopForWoo plugin, Apple Pay and Google Pay appear inside the Whop payment form on your own checkout.

Your options

If you already run WooPayments or Stripe, follow their own guide. The rest of this page covers Whop, for stores that want Apple Pay without Stripe or as a second processor.

How Apple Pay works with Whop on WooCommerce

WhopForWoo loads Whop’s Checkout element inside the WooCommerce payment box. The plugin enables Apple Pay and Google Pay on every checkout configuration it creates, so the wallets appear in the form whenever the buyer’s device can use them.

There is one requirement Whop sets for any page you host yourself: Apple Pay must be ready on the domain. Whop’s own hosted checkout pages on whop.com are already approved, so this step only concerns your store’s domain.

One domain with Apple Pay ready clears both Apple Pay and Google Pay for every Whop element on it.

Step-by-step: Apple Pay on WooCommerce with Whop

1. Install and connect WhopForWoo

Install the plugin, then open WooCommerce → Settings → Payments → Whop. Paste your API key and Account ID (how to get the API key), add the webhook (webhook setup) and choose the Whop Elements on Checkout mode.

2. Download Whop’s Apple Pay verification file

Download it from Whop: https://whop.com/.well-known/apple-platform-integrator/apple-developer-merchantid-domain-association. Don’t edit it.

3. Host the file on your WordPress site

The file must be reachable at exactly:

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

On most WordPress hosts: connect with SFTP or the host’s file manager, create a .well-known folder in the site root (the folder that contains wp-config.php), and upload the file there without an extension.

Whop’s requirements: served over HTTPS, reachable without login, content unmodified.

4. Check the file opens

Open the URL in a private browser window. It should download or display the file. If you get a 404, a redirect, or your theme’s page, see troubleshooting below.

5. Register your domain in Whop

In the Whop dashboard, open Websites, select your domain, choose Fix Apple Pay, follow the steps, then Check now. Whop checks the file is reachable and registers the domain with Apple. Through the API, the domain’s apple_pay.state goes from pending to ready, or to action_required if Apple couldn’t fetch the file.

6. Test on a real device

Open your checkout over HTTPS in Safari on an iPhone or Mac with a card in Apple Wallet, add a product and go to checkout. The Apple Pay button appears in the Whop form. For Google Pay, use Chrome with a card saved in Google Pay.

Test with a real low-value order: Whop’s sandbox does not support Apple Pay or Google Pay yet.

Apple Pay button not showing on WooCommerce

Check these in order:

1. Device and browser. Apple Pay shows in Safari on a device with a card in Wallet. Desktop Chrome without Google Pay shows neither.
2. Domain not ready. In Whop, the domain must show Apple Pay as ready. www.yourstore.com and yourstore.com are different domains: register the one your checkout uses.
3. File blocked or redirected. Security plugins, “force trailing slash” rules or server rules that hide dotfiles can block /.well-known/. The URL must return the file directly, with no redirect.
4. Cached checkout. A cached checkout page serves a stale security token and the payment form won’t load properly. Exclude the checkout from page caching; WhopForWoo’s Status & Tools has a test that tells you whether it’s cached.
5. Sandbox. Wallets don’t work in Whop’s sandbox. Test live with a small order.
6. Checkout Block. If your store uses the WooCommerce Checkout Block, WhopForWoo uses the hosted redirect: the buyer pays on Whop’s page, where Apple Pay is already approved, so the domain step doesn’t apply there.
7. Other gateway’s button. If you also run Stripe or WooPayments, their express buttons are configured separately. A missing Stripe button is a Stripe setting, not a Whop one.

Fees and payouts

Whop lists cards and wallets under the same rate: 2.7% + $0.30 on US domestic cards, plus 1.5% for international cards and 1% when currency conversion applies. Apple Pay doesn’t add a surcharge. The full breakdown, including optional add-ons and payout fees, is on Whop fees.

Is Apple Pay through Whop secure?

Card and wallet details stay inside Whop’s iframe on Whop’s domain and never touch your server. WhopForWoo marks an order paid only after the payment is confirmed by Whop’s API or by an HMAC-signed webhook, with matching order, amount and currency. More on whether Whop checkout is safe.