What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To accept Apple Pay on a WordPress store, you need a WooCommerce-compatible payment gateway, a complete HTTPS site, a supported merchant account, and domain verification for every hostname used during checkout. The gateway then displays an Apple Pay button only when a shopper is using a compatible Apple device and browser with an eligible card in Apple Wallet.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
For most WooCommerce stores, WooPayments is the shortest setup: enable Apple Pay and Google Pay in Payments > Settings > Express Checkouts, and its extension creates the verification file and communicates readiness to Apple. Stripe is usually the cleanest alternative for stores already processing cards through Stripe; PayPal Payments fits merchants who already operate through PayPal.
As an Amazon Associate I earn from qualifying purchases.
What Apple Pay on WordPress actually involves
Apple Pay is not a standalone WordPress plugin that deposits money into your bank account. It is an express-checkout method exposed by a payment provider. WooCommerce sends the order and amount to that provider, the provider presents Apple’s payment sheet, and the provider handles authorization and settlement.
That arrangement creates three separate jobs:
- Payment processing: Open an account with a gateway that supports Apple Pay in your country or region.
- Website security: Serve the entire store, not just the checkout page, over HTTPS with a valid certificate. The payment connection must use TLS 1.2 or later; Stripe’s express-checkout requirements also call for port 443 to be open.
- Domain authorization: Prove to Apple, through the gateway, that each hostname where the button can appear is controlled by you.
The Apple Pay button is conditional. A desktop visitor on an unsupported browser, or a shopper using an Apple device without a usable Wallet card, will not see it. This is normal and is not evidence that the integration failed.
#1 Best Overall
- Use the, easy-to-use, and customizable POS to get started.
- Accept contactless payments, chip cards, Apple Pay, and Google Pay from anywhere, with improved connectivity, extended battery life, and enhanced security. Pay one low rate for every tap or dip.
- No long-term commitments or contracts, no monthly fees- and with offline payments, keep taking payments for up to 24 hours.
- Safely and securely accepts payments anywhere. Plus, get data security, 24/7 fraud prevention, and payment-dispute management at no extra cost.
- Use the, easy-to-use, and customizable POS to get started.
Apple Pay and Google Pay are enabled together in WooPayments. If you only want Apple Pay visible, the gateway’s device and browser rules still determine when the Apple Pay option appears; you cannot force it to display for every visitor.
Requirements checklist before you configure anything
- WordPress, WooCommerce, PHP, and your payment extension are on currently supported versions.
- The entire site is served over HTTPS with a valid SSL certificate, including cart, checkout, account, and product URLs.
- Your server accepts secure traffic on port 443 and supports TLS 1.2 or later.
- Your payment provider account is in a country or region that the provider supports for Apple Pay, with the currencies and business type you need.
- Every checkout hostname is identified: the apex domain (for example,
example.com), awwwhostname, staging domains, and any checkout subdomain are separate names for verification purposes. - Apple’s domain-association verification has completed for each production hostname.
- Customers who test the button have a compatible Apple device and browser, such as Safari where required, and an active payment card in Apple Wallet.
Make a list of the exact hostnames your store uses before registering a domain. A redirect from www.example.com to example.com does not make them the same registration when a provider asks you to verify both.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteChoose the gateway that matches your store
The best route depends less on the Apple Pay label and more on the payment account you already maintain. The following comparison uses the setup and capability differences documented for WooCommerce-compatible integrations.
| Route | Verification and certificate work | Best fit | WooCommerce Subscriptions | Button placement |
|---|---|---|---|---|
| WooPayments | Extension creates the Apple verification file and communicates readiness automatically. | Most WooCommerce stores, especially those without an existing processor. | Supported. | Controls can place the button on checkout, cart, or product pages. |
| Stripe for WooCommerce | Extension creates the association file automatically, but you must enable each hostname on Stripe’s payment-method domains page and meet Stripe’s HTTPS, port 443, and TLS requirements. | Stores already using Stripe for cards or wanting Stripe’s other express and local methods. | Supported. | Uses the placement controls provided by the Stripe extension and its express-checkout settings. |
| PayPal Payments | PayPal presents the association file, but every hostname still has to be registered in the PayPal account. | Stores that already manage payments through PayPal. | Not established for Apple Pay in the documented route; verify your account’s current capability before promising recurring Apple Pay payments. | Uses the PayPal Payments extension’s supported locations. |
| Other gateways | Usually manual: HTTPS/TLS checks, merchant identity and payment certificates, an association or verification file, and gateway-specific settings. | Merchants committed to Authorize.Net, CyberSource, Moneris, or another supported processor. | Most listed alternatives are limited to one-time transactions. | Depends on the gateway’s extension and filters. |
WooCommerce describes WooPayments as the best option for most stores. That recommendation is primarily about automation: it removes the manual certificate and association-file steps that make other routes easy to misconfigure.
Rank #2
- Get your money as soon as the next business day.
- Get set up quickly with no long-term commitments. Download the Square Point of Sale app for free, create an account, and start taking payments anywhere.
- Run your business all in one place with the free Square Point of Sale app. Track your sales, manage inventory, accept tips, send receipts digitally, and more.
- Works with Apple devices with a Lightning connector.
Set up Apple Pay with WooPayments
Use this path when you are comfortable opening a WooPayments account or want the fewest domain-verification tasks.
- Install and connect WooPayments. In WordPress, install the WooPayments extension, connect the store to a WooPayments account, and finish the account’s identity, business, and payout requirements. Apple Pay availability still depends on the account’s country and other provider rules.
- Open the express-checkout settings. Go to Payments > Settings in WordPress, then open Express Checkouts.
- Enable the combined wallet option. Check Apple Pay / Google Pay and save. WooCommerce requires these two wallets to be enabled together in this integration.
- Allow the extension to verify the site. WooPayments creates the Apple verification file and communicates the site’s readiness to Apple. Do not replace that file with a manually uploaded copy unless WooPayments support specifically instructs you to do so.
- Choose where the button appears. Use the customization controls to enable supported locations such as checkout, cart, and product pages. Start with checkout and cart if you want to minimize visual changes, then add product pages after testing the theme layout.
- Test as a real Apple Pay shopper. On a compatible Apple device and browser, open each enabled location, select Apple Pay, authorize with the Wallet card, and confirm that WooCommerce creates the order and the payment appears in the WooPayments account.
If verification does not complete, first check that the public site is HTTPS on every page and that no maintenance mode, password protection, security plugin, or CDN rule blocks the gateway’s verification request.
Set up Apple Pay with Stripe for WooCommerce
Stripe is a practical choice when Stripe already processes your card payments. It keeps your payment reporting and payout relationship in one provider, but the domain must be enabled in Stripe’s own dashboard as well as configured in WordPress.
- Install the official Stripe extension. Activate it in WordPress and connect the store to a Stripe account in a Stripe-supported country.
- Confirm transport security. Install a valid SSL certificate, force the whole site to HTTPS, leave port 443 reachable, and verify that the server supports TLS 1.2 or later. Mixed content or a checkout that falls back to HTTP can prevent express checkout from loading.
- Connect the account and enable express checkout. Complete the Stripe connection in the extension, then turn on Apple Pay in its express-checkout or payment-method settings.
- Enable the payment-method domain in Stripe. In the Stripe dashboard, open the payment-method domains page and add every exact hostname that can display Apple Pay. Register
wwwseparately from the apex domain and include any checkout subdomain. - Let the extension publish the association file. The official extension creates the Apple Pay domain-association file automatically. Keep the extension active and avoid a second plugin that tries to serve a different Apple validation file.
- Test on a supported Apple environment. Use Safari or another environment supported by the current Stripe integration, with a Wallet card available. Test each domain and each button location you enabled.
If Stripe shows the domain as unverified, the most useful check is the exact hostname in Stripe’s payment-method domains page. A certificate that works on the apex domain does not prove that a subdomain or www hostname is correctly served.
Rank #3
- With Square Terminal, you can ring up sales, accept payments, and print receipts, all with one device. Use it at the counter or ring up customers anywhere in your store.
- Accept all major credit and debit cards and pay one low rate with no hidden fees and no long-term contracts.
- Process chip cards in just two seconds.
- Get your money as soon as the next business day.
- Use it cordlessly with the built-in battery, designed to last all day.
Set up Apple Pay with PayPal Payments
Choose this route when the store already relies on PayPal Payments and you want Apple Pay transactions managed alongside that account.
- Install or update PayPal Payments. Connect the extension to the correct PayPal merchant account and complete its normal onboarding.
- Enable Apple Pay in the extension. Open the PayPal Payments settings and switch on Apple Pay where the account is eligible.
- Register every display domain in PayPal. Add the apex domain, the
wwwhostname if used, and every subdomain where the button may appear. PayPal presents the Apple association file automatically, but registration is still mandatory. - Check the shopper conditions. The button appears only on supported Apple devices and browsers, such as Safari where applicable, when the shopper has an Apple Wallet card available for payment.
- Run a live-style test. Test from each registered hostname and verify that the payment sheet opens, the authorization succeeds, and the order is recorded in WooCommerce and the PayPal account.
If the Apple Pay sheet opens and immediately closes, check the PayPal domain registration first. Also remove conflicting third-party Apple validation files; two plugins serving different association files can cause validation failures.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Use a third-party gateway when its payment features justify the extra work
Authorize.Net, CyberSource, Moneris, and similar gateways can support Apple Pay, but they generally require a developer-style setup rather than a single switch. WooCommerce’s developer guidance identifies these common requirements:
- A complete HTTPS site using TLS 1.2 or later.
- Merchant identity and payment-processing certificates in the formats required by the gateway.
- An Apple association or verification file served from the exact path required by the integration:
/.well-known/payment-processing-cert. - A gateway-specific WordPress filter or setting that turns on Apple Pay after the file and certificates are in place.
Follow the selected gateway’s current certificate instructions exactly; filenames, PEM contents, permissions, and merchant-ID values are not interchangeable between providers. Have a qualified WooCommerce developer handle this route if you do not routinely manage TLS certificates and server files. Most of these alternatives support one-time transactions only, so confirm recurring-payment support before using Apple Pay for a subscription product.
Rank #4
- Pay one transparent rate per swipe for Visa, Mastercard, Discover and American Express.
- Works in conjunction with most downloadable Square point-of-sale apps on your device. Customers can pay, tip and sign directly on your device. Track payments in cash, gift cards and more. Also lets you send receipts via e-mail or text message, makes it easy to apply discounts, keeps a data and sales history log and more.
- Accepts magstripe credit card payments, including those from Visa, Mastercard, Discover and American Express (fees apply).
- App sends deposits to your bank account within 1 to 2 business days, or enjoy instant deposits (fees apply).
How domain verification works
Domain verification is Apple’s way of ensuring that a merchant controls the website requesting Apple Pay. Your payment provider either publishes the required association file for you or tells you where to place it. Apple then checks that file at the hostname where the button will be displayed.
Register the exact hostname
Count each hostname separately. These can all be different registrations:
example.comwww.example.comshop.example.comcheckout.example.com
Register staging or preview hosts only if they will actually be used for Apple Pay testing; do not expose a production payment configuration on an unsecured staging site.
Check the file from the public internet
Use the provider’s documented verification path and test it without being logged in to WordPress. The request must not be redirected to HTTP, blocked by a firewall, challenged by basic authentication, rewritten by a security plugin, or cached as an old file by a CDN. A successful browser response is useful, but the provider’s dashboard status is the final indication that registration completed.
Best Value
- Case Set for Square Card Reader (2nd gen): Protect your card reader while giving it a dedicated spot on your counter, with magnetic docking that allows easy removal when needed.
- Durable, Drop-Resistant Case: TPU construction with silicone grip and a raised lip around the tap surface provides shock absorption and added protection, with precise cutouts for the charging port, card slot, and battery indicator button.
- Non-Slip Dock: Soft-touch stand with built-in magnets and a rubber base keeps the reader stable and secure on any surface.
- Fast, Flexible Mounting: The magnetic case stays on your Square reader and snaps on or off the display stand in seconds — ideal for quickly switching between countertop and handheld use. Compatible with MagSafe for a convenient phone mounting option.
- Compatible Model: Square Card Reader 2nd generation (USB-C)
Keep one owner for the file
WooPayments and Stripe create their files automatically. PayPal presents its file automatically after registration. If you switch gateways, deactivate the old integration’s validation mechanism and follow the new provider’s process; leaving competing Apple validation files or filters active can create hard-to-diagnose errors.
Choose sensible button locations
Express checkout works best where the shopper has already selected a product and shipping or tax can be calculated. Checkout and cart are the least surprising locations. Product-page buttons can shorten the path for simple products, but test variable products, required options, quantity rules, coupons, and shipping calculations before enabling them broadly.
Use the gateway’s placement controls rather than inserting a second Apple Pay button with a page-builder widget. Duplicate buttons can create conflicting payment sessions, and a theme update can remove custom markup without warning.
Test the complete purchase flow
- Open the store on a supported Apple device and browser with an eligible Wallet card.
- Test the apex domain and the
wwwor subdomain version customers actually use. - Open every location where you enabled express checkout: product page, cart, and checkout.
- Select Apple Pay and confirm that the payment sheet shows the correct merchant and total.
- Authorize the payment with the Wallet card.
- Confirm the WooCommerce order status, order total, and payment record in the gateway dashboard.
- Repeat with the site’s normal coupon, shipping, tax, and variable-product combinations that can change the total.
Do not judge the integration from a Windows browser or an Apple device without a Wallet card; those tests are expected to hide the button.
Troubleshoot a missing button or failed payment
The button is absent for one shopper
- Confirm the shopper is using a supported Apple device and browser.
- Confirm an eligible payment card is present in Apple Wallet.
- Check that the provider and account support Apple Pay in the shopper’s and merchant’s applicable region.
- Verify that Apple Pay is enabled in the gateway and that the current page is one of the locations you selected.
The provider reports a domain error
- Copy the hostname from the browser address bar and compare it character-for-character with the provider dashboard entry.
- Register
www, the apex domain, and each checkout subdomain separately when they are used. - Open the required association-file path publicly and make sure HTTPS does not redirect through a blocked or password-protected URL.
- Temporarily bypass CDN, firewall, maintenance-mode, and security-plugin rules that could intercept the verification request.
Stripe does not show Apple Pay
- Confirm the domain is enabled on Stripe’s payment-method domains page.
- Confirm the SSL certificate is valid on the exact hostname and the entire site uses HTTPS.
- Check that port 443 is open and TLS 1.2 or later is available.
- Ensure the official Stripe extension is active and that no second plugin is replacing its association file.
The PayPal payment sheet closes
- Recheck registration for the exact PayPal hostname, including
www. - Remove conflicting third-party Apple validation files or filters.
- Repeat the test with a supported Apple device, browser, and Wallet card.
A manual gateway cannot validate
- Check the merchant identity certificate, payment certificate, merchant ID, PEM or verification file, and file permissions.
- Confirm the file is under the gateway’s required
/.well-known/payment-processing-certpath. - Recheck the gateway-specific filter and settings after the certificates are installed.
- Ask a WooCommerce developer to inspect the server and certificate chain if the provider still reports failure.
Keep the integration working after launch
- Keep WordPress, WooCommerce, PHP, the payment extension, and the theme on supported versions.
- Renew the SSL certificate before expiration and check that renewals continue to cover every checkout hostname.
- Do not change the canonical domain, add a checkout subdomain, or move to a new CDN without registering and testing the new hostname.
- When changing gateways, complete the new provider’s verification before disabling the old payment route, then remove obsolete validation files and settings.
- Retest Apple Pay after major theme, caching, firewall, or checkout-plugin changes.
The practical decision is straightforward: start with WooPayments when you want automatic verification and subscription support; use Stripe when Stripe already runs your card processing; use PayPal Payments when PayPal is already the store’s operational hub. Select a manual gateway only when its broader payment requirements outweigh the additional certificate and domain work.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
