How to Accept Apple Pay and Google Pay on Your WooCommerce Restaurant Site (Stripe Setup for 2026)

Something interesting happened at a pizzeria I consult for last quarter. They flipped on Apple Pay and Google Pay on their woocommerce.com/products/tipping-for-woocommerce/” title=”Tipping – Add Order Tip for WooCommerce” rel=”nofollow”>WooCommerce checkout, changed nothing else, and mobile conversions jumped by roughly 18% in three weeks. No magic. No new theme. Just fewer taps between “I’m hungry” and “order confirmed.”

That’s the whole story with digital wallets in 2026. Customers already have their card details saved in Apple Wallet or Google Pay. When your checkout asks them to type 16 digits, a CVV, and a billing address on a greasy phone screen at 7:45pm — they bail. And if you’re running a restaurant site on WooCommerce without one-tap payments, you’re leaving orders on the table every single night.

Here’s how to fix that, properly, using Stripe as the primary route and a few solid alternatives depending on where you’re based.

Why Apple Pay and Google Pay Matter for Restaurant Ordering in 2026

Mobile checkout on food ordering sites is brutal. Industry data from Baymard Institute has consistently put mobile cart abandonment above 75%, and the top reason people quit — after unexpected shipping costs — is a checkout process that feels too long or too complicated. On a restaurant site, where the customer wants dinner in 30 minutes and not a data entry job, that friction hurts even more.

Digital wallets solve most of it. Apple Pay and Google Pay pull the customer’s saved card, billing address, and sometimes even their delivery address into a single confirmation sheet. One tap. Face ID or fingerprint. Done.

For restaurants specifically, the impact compounds because your customers are repeat buyers. Someone who orders from your pizzeria every other Friday shouldn’t have to re-enter their card each time. When they don’t, they order more often. That’s the real ROI — not just fewer abandoned carts, but higher order frequency during lunch rushes, late-night cravings, and those “I’m too tired to cook” Tuesdays.

There’s also a trust angle. Seeing a familiar Apple Pay or Google Pay button on a small local restaurant’s site tells the customer “this place is legit.” It’s a subtle credibility signal, and it matters especially for first-time visitors who found you through a Google search or an Instagram ad.

What You Need Before You Start: Requirements Checklist

Before you touch a single setting, make sure you’ve got the basics sorted. Missing any of these will send you down a rabbit hole of “why isn’t the button showing?” errors that take hours to diagnose.

• SSL certificate installed and active. Apple Pay flat-out refuses to work on non-HTTPS pages. If your padlock icon isn’t showing in the browser, fix that first.
• A supported payment processor account. Stripe is the most flexible and works globally. Square is excellent if you already run a physical POS. Mollie is a strong choice in Europe.
• Business verification completed. Whichever processor you pick, finish their KYC process. Unverified accounts can’t enable wallet payments.
• WooCommerce 8.0 or newer installed. The newer blocks-based checkout plays much better with Express Checkout buttons than the classic shortcode checkout.
• A theme compatible with WooCommerce blocks. Most modern themes are fine, but some older restaurant themes still hardcode the classic checkout. Test before you commit.
• Access to your domain root for Apple Pay verification. You’ll need to upload a small file to /.well-known/apple-developer-merchantid-domain-association. If your host restricts this folder, you’ll need FTP or a plugin workaround.

One more thing worth flagging: if you’re running an aggressive caching plugin or a CDN like Cloudflare with rocket loader enabled, add your checkout and cart pages to the bypass list now. Cached checkout JavaScript is the number one reason Apple Pay buttons “randomly disappear” for some visitors.

Step-by-Step: Setting Up Stripe with Apple Pay and Google Pay in WooCommerce

Stripe is where I start with 90% of restaurant clients. It’s globally supported, the fees are predictable (2.9% + 30¢ in the US, similar elsewhere), and the official plugin handles both Apple Pay and Google Pay through a single toggle. Here’s the full walkthrough.

1. Install the Official Stripe Plugin

From your WordPress dashboard, go to Plugins → Add New and search for “WooCommerce Stripe Payment Gateway” by Automattic. Install and activate it. Don’t use forks or third-party Stripe integrations unless you have a specific reason — the official one is maintained directly by the WooCommerce team and gets updates the fastest.

2. Connect Your Stripe Account

Go to WooCommerce → Settings → Payments → Stripe and click “Connect.” You’ll be bounced over to Stripe’s OAuth flow. Log in (or sign up), pick the account you want to link, and authorize the connection. When you’re returned to WordPress, your API keys will populate automatically.

If you prefer manual key entry — some agencies do for security reasons — you can grab your publishable and secret keys from the Stripe dashboard under Developers → API keys and paste them in.

3. Enable Express Checkout (Payment Request Buttons)

Scroll down in the Stripe settings until you find Express Checkouts or Payment Request Buttons (the wording has changed a couple of times across plugin versions). Turn it on. You’ll get options for:

• Button type: Buy, Donate, or Default. For restaurants, “Buy” reads more naturally.
• Button theme: light, dark, or outline. Match it to your theme.
• Display locations: cart page, checkout page, and product page. I recommend enabling all three for restaurant sites — especially the cart and menu item pages.

Save changes. Stripe will handle both Apple Pay and Google Pay through this single Express Checkout system — you don’t configure them separately.

4. Verify Your Domain for Apple Pay

This is the step that trips people up. Apple requires you to prove you own the domain before it’ll show the Apple Pay button on your site.

In your Stripe dashboard, go to Settings → Payment methods → Apple Pay and click “Add new domain.” Stripe gives you a file to download. You need to upload that file to yourdomain.com/.well-known/apple-developer-merchantid-domain-association. Note: no file extension.

The good news is the modern Stripe WooCommerce plugin usually handles this automatically once you enable Express Checkout — it creates the .well-known directory and serves the file. But if you’re on managed WordPress hosting like WP Engine or Kinsta that blocks dotfile directories by default, you may need to add the file manually via FTP or ask support to whitelist it.

Once uploaded, hit “Verify” in Stripe. If it comes back green, you’re clear.

[IMAGE: Screenshot-style illustration of the WooCommerce Stripe settings page with Express Checkout toggled on and Apple Pay domain verification highlighted]

5. Test in Safari and Chrome

Open your site in Safari on an iPhone (Apple Pay only shows in Safari, not Chrome on iOS). Add an item to your cart. You should see the black Apple Pay button appear on the cart and checkout pages. Tap it — the payment sheet slides up with your saved card, address, and Face ID prompt.

For Google Pay, open Chrome on Android or desktop Chrome (with a Google account signed in and a card saved). The Google Pay button should appear in the same slots. Run at least one real test transaction with Stripe in live mode, then refund it. Testing in test mode alone isn’t enough — some wallet issues only surface in production.

Common Gotchas

A few things I’ve hit repeatedly:

• Apple Pay doesn’t show in incognito/private browsing. Don’t waste an hour debugging this.
• If you’re using the classic shortcode checkout, the button placement can look off. Switch to the blocks checkout when possible.
• Some page builders (Elementor, Bricks) override the cart page template. If Apple Pay works on /checkout but not /cart, that’s your culprit.

Alternative Setup: Using Square, Mollie, or PayPal for Digital Wallets

Stripe isn’t the only game in town, and depending on your setup, another processor might make more sense.

Square

If your restaurant already uses Square terminals for in-store payments, the WooCommerce Square plugin is a no-brainer. Your online and offline transactions land in the same account, inventory syncs between your POS and website, and Apple Pay/Google Pay come baked in through Square’s Web Payments SDK. Fees are 2.9% + 30¢ for online transactions in the US.

Setup is similar to Stripe: install the plugin, connect via OAuth, enable digital wallets in the settings. Domain verification for Apple Pay happens automatically through Square’s servers, which is one less headache.

Mollie

For European restaurants — especially in the Netherlands, Belgium, Germany, and France — Mollie is worth a serious look. Their fees are often lower than Stripe for local payment methods (iDEAL, Bancontact, SEPA), and they support Apple Pay and Google Pay out of the box. The official Mollie plugin for WooCommerce is well-maintained.

The tradeoff: Mollie’s subscription/recurring payment support isn’t as strong as Stripe’s, so if you’re planning to add a meal subscription service later, factor that in.

PayPal

PayPal’s Smart Payment Buttons technically include Apple Pay and Google Pay support now, but the implementation feels bolted-on compared to Stripe or Square. The buttons work, but the UX inside the payment sheet isn’t as clean, and PayPal’s fees (3.49% + 49¢ in the US as of late 2025) are noticeably higher for card transactions.

I’d only recommend PayPal-only setups for restaurants whose customer base specifically demands PayPal — otherwise, use it as a secondary option alongside Stripe.

Optimizing the Express Checkout Experience for Food Orders

Getting the button to show up is step one. Getting it to actually convert is where the real work happens — and food ordering has some quirks that generic e-commerce advice misses.

Put the Button Where Hungry People Can See It

Above the fold. Always. On mobile especially, if your customer has to scroll past a delivery zone selector, an upsell popup, and three “recommended sides” before seeing the Apple Pay button, you’ve lost half of them. The cart page and the checkout page should both show the Express Checkout button in the first 400 pixels of screen space.

If you’re using FoodMaster’s restaurant ordering system, the checkout is designed with this in mind — the Express Checkout slots plug into the existing flow without you having to hack template files. That’s one of the reasons I lean on it for client builds; the plugin plays nicely with Stripe’s Payment Request API right out of the gate.

Handle Delivery Address and Time Slots Correctly

Here’s where restaurants trip up. Apple Pay and Google Pay pull the customer’s billing address from their wallet, but they don’t automatically know your customer wants delivery vs pickup, or which time slot they’ve selected.

The fix: collect the order type (delivery/pickup/dine-in) and time slot before the customer taps Apple Pay. That way, when the payment sheet opens, those details are already saved in the WooCommerce session, and the total (including any delivery fee) is accurate.

FoodMaster handles this by locking the customer into an order type on the menu page itself, before they reach the cart. It’s a small UX decision that prevents huge headaches at checkout.

Tips and Delivery Fees Must Be Included in the Total

The Apple Pay and Google Pay sheets show the customer a total. If your tip prompt or delivery fee is added after they tap the wallet button, you’ll either see confused customers or failed transactions.

Add tipping as part of the cart, not as a post-payment option. A dedicated plugin like Tipping for WooCommerce integrates the tip amount into the WooCommerce cart total before checkout, so when the Apple Pay sheet loads, the customer sees the complete amount they’re actually paying — tip included. That transparency matters, and it prevents the “wait, I thought I was paying $24, not $28” chargebacks.

[IMAGE: Mobile phone showing a restaurant checkout page with the Apple Pay button prominently placed above the fold, tip and delivery fee visible in the order summary]

Keep the Menu Page Fast

Digital wallets remove checkout friction, but if your menu page takes 6 seconds to load on 4G, none of it matters. Compress your food photos (WebP format, under 100KB each), lazy-load anything below the fold, and be ruthless about which plugins you actually need. Core Web Vitals directly impact conversion — Google’s own data shows a 1-second delay in mobile load time can drop conversions by up to 20%.

Troubleshooting Common Issues and