Apple Pay, Google Pay, Shop Pay: which express buttons to add

Short answer: Turn on the wallets your platform already supports (Apple Pay and Google Pay almost always, plus Shop Pay if you're on Shopify), then let the platform decide which buttons each shopper sees. Put express buttons at the top of checkout and in the cart; add them to product pages only when people usually buy a single item. If you run a custom Stripe integration or WooCommerce, Apple Pay won't appear until every domain that shows the button is registered.

Express buttons are the "pay with what's already on your phone" row: one tap, a saved card, a saved address, done. The work isn't deciding whether to have them. It's deciding which ones, where they go, and how to keep them from turning your checkout into a wall of logos.

What each platform can show (as of November 2026)

The table below sums up what each provider's own documentation lists. Your account country, currency and plan can narrow it, so check the settings page in your own admin before promising anything to customers.

	Shopify	Stripe (custom site, Express Checkout Element)	WooCommerce + Stripe extension
Wallets listed in the docs	Shop Pay, Apple Pay, Google Pay, PayPal, Amazon Pay, Venmo	Link, Apple Pay, Google Pay, PayPal, Klarna, Amazon Pay	Apple Pay, Google Pay, Link, Amazon Pay
Who picks the order	Shopify orders them dynamically for each shopper	Stripe sorts by relevance; you can set `paymentMethodOrder`	Set per location in the extension's settings
Product page buttons	Yes, shown next to Add to cart	Yes, wherever you mount the element	Yes, chosen per location
Domain registration for Apple Pay	Handled by Shopify	Required for Elements and embedded Checkout	Required (the extension creates the association file)
Can you hide a wallet?	Yes in settings; conditional hiding needs Shopify Plus and a custom app	Yes, set a wallet to `never`	Yes, untick it (Apple Pay and Google Pay toggle together)

A few details from those pages are worth knowing before you start:

Shopify's product-page buttons buy one variant only. A shopper can buy two large T-shirts with an accelerated button, but not a large and a small together. If your customers typically mix variants, the cart is the better home for the button.
Shopify decides branded vs unbranded. If no third-party wallet is active, shoppers see a plain "Buy it now" button that skips the cart. You can restyle that one, not the branded versions.
On WooCommerce's Stripe extension, some products never show express buttons. The documentation lists composite products, pre-orders charged on release, products with file upload fields, free products and non-default product types, among others.
Stripe hides wallets a shopper hasn't set up. Someone without Google Pay configured will never see the Google Pay button, so an empty row on your own laptop isn't necessarily a bug.

Apple Pay domain setup, in plain terms

On a hosted page (Stripe Payment Links, Stripe-hosted Checkout, Shopify's checkout), Apple Pay works with no extra configuration. On your own pages it doesn't, and this is where most "the Apple Pay button isn't showing" tickets come from.

Serve the whole site over HTTPS. WooCommerce's guide also asks for port 443 open and TLS 1.2 or later.
Register every domain that shows the button. Stripe's docs are explicit that this means the top-level domain and each subdomain (example.com, www.example.com, shop.example.com), in test and live mode. Do it on the Payment method domains page in the Stripe Dashboard, once per domain.
Watch iframes. If the payment form sits in an iframe from another domain, Stripe says both domains must be registered.
Test on real devices. A Mac with Safari and an iPhone with a card in Wallet. Stripe notes that Apple Pay in non-Safari desktop browsers only appears if you explicitly set it to always show.

Shopify's help center has a separate testing page for accelerated buttons; run through it after any theme change, because a theme that doesn't support the buttons can quietly drop them.

Placement rules

Wallet buttons convert best when they appear early and don't fight each other for attention. These rules come from the platforms' documentation and Apple's Human Interface Guidelines, plus some common sense about clutter.

1. Checkout first. Every platform puts an express row at the top of checkout. That's the one place where almost every shopper benefits, so start there.

2. Cart second. For stores where people add several items, the cart is where the decision to pay happens. Apple's guidelines describe express checkout as buying everything in the cart with a single shipping method and destination.

3. Product pages only for single-item buyers. Apple suggests product-page buttons for quickly buying one item and says that purchase should cover only that item, not what's already in the cart. Good fits: a single bestseller, a gift card, a refill, an event ticket. Poor fits: anything people build into a bundle.

4. Keep the Apple Pay button full size. Apple asks for it to be no smaller than other payment buttons and visible without scrolling. Shrinking it to make room for six logos defeats the point.

5. Cap the row. Two or three wallets beat five. Stripe's element pushes low-relevance options into an overflow menu when space runs out; on other setups, decide yourself. A sensible US default is Apple Pay, Google Pay and one of Shop Pay or PayPal, depending on platform.

6. Don't duplicate. If wallets show in the express row, they shouldn't appear again further down as payment options. Stripe's Payment Element does this de-duplication for you when both components are used.

7. Make shipping and discounts work inside the wallet. Collect the shipping address in the wallet sheet and pass back real shipping options. Apple's guidelines also recommend letting people enter a coupon code. A wallet sheet that shows the wrong shipping price is worse than no button.

Which ones to switch on

On Shopify: Shop Pay, Apple Pay and Google Pay, then let the dynamic ordering do its job. Add PayPal or Venmo if your customers ask for them.
On a custom Stripe build: Apple Pay, Google Pay and Link through one Express Checkout Element; it handles detection and ordering.
On WooCommerce: Apple Pay and Google Pay (they switch on together), Link if your Stripe account country qualifies, and set locations per page type in the extension's customise screen.

After launch, look at your payment reports by method. Shopify's payments finance report can be filtered by payment method; Stripe's Dashboard shows the same. If a wallet is barely used after a few months, removing it makes the row calmer.

FAQ

Why does Apple Pay show for some customers but not others?

Wallet buttons appear only when the shopper's device, browser and wallet support them. Someone on Chrome for Windows without a saved Google Pay card may see no wallet at all, and that's expected behavior.

Do I need an Apple developer account to add Apple Pay to my store?

Not when you use Stripe, Shopify or the WooCommerce Stripe extension. Stripe says it handles Apple merchant validation; you register your domains in the Stripe Dashboard instead.

Will express buttons skip my upsells and order notes?

Often, yes. Product-page buttons go straight to payment, and WooCommerce notes that some custom checkout fields arrive empty when an express payment starts from the product or cart page. Test any required field before going live.

Can I show Shop Pay on a non-Shopify site?

This article only covers Shop Pay inside Shopify's checkout. If you're on another platform, check Shopify's current documentation for what is offered outside its own stores.

If your wallet buttons work on your phone but not your customer's, send us the store link and we'll trace which setting is hiding them.