WooPayments offers five express checkout methods: Amazon Pay, Apple Pay, Google Pay, Link by Stripe, and WooPay. Offering these methods can speed up checkout and help reduce cart abandonment.
Each one behaves a little differently depending on what you sell, where the customer is located, and what browser they’re using. This page explains how the five methods work across various product types, browsers, settings, and features. To configure, customize, test, or troubleshoot each individual method, see its own page linked above.
Apple Pay, Google Pay, and Amazon Pay appear together as buttons. WooPay uses its own separate button. Link by Stripe isn’t a button at all: it appears inside the checkout form, where it auto-fills details for returning customers. These differences explain much of the variation you’ll see below.
Product-type compatibility
↑ Back to topAmazon Pay, Apple Pay, and Google Pay work with every product type WooPayments supports: simple and variable products, subscriptions, as well as bookable, bundled, composite, and Mix and Match products. WooPay works with all of these too, except that it is not compatible with bookable products.
A few other conditions apply:
- Subscriptions: These require the customer to have or create an account (see Guest checkout requirements). A subscription with a free trial will only show express checkout buttons if there’s a sign-up fee. A free trial with no sign-up fee “costs” $0, which express checkout buttons cannot process, so they will be hidden instead, even for physical products.
- Composite, Bookings, and Mix and Match: The Apple Pay, Google Pay, and Amazon Pay buttons will not appear on the product page. Bookings products that require confirmation don’t show express checkout buttons at all.
- Bundled products: Express checkout buttons appear on the product page only for fixed-price bundles that do not require configuration. For bundles that are priced per item, allow configurable quantities, or require input, the buttons are hidden on the product page.
- WooPay: Cannot be used for bookable products.
Browser compatibility
↑ Back to topThis table shows which methods appear in common browser and device combinations.
| Browser and device | Amazon Pay | Apple Pay | Google Pay | Link by Stripe | WooPay |
|---|---|---|---|---|---|
| Chrome (desktop) | ✅ | macOS only | ✅ | ✅ | ✅ |
| Edge (desktop) | ✅ | macOS only | ✅ | ✅ | ✅ |
| Firefox (desktop) | ✅ | ❌ | ✅ | ✅ | ✅ |
| Opera (desktop) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Safari (desktop) | ✅ | macOS only | ✅ | ✅ | ✅ |
| Chrome (iOS) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Firefox (iOS) | ❌ | ✅ | ✅ | ✅ | ✅ |
| Edge (iOS) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Chrome (Android) | ✅ | ❌ | ✅ | ✅ | ✅ |
| Firefox (Android) | ✅ | ❌ | ✅ | ✅ | ✅ |
| Edge (Android) | ✅ | ❌ | ✅ | ✅ | ✅ |
Settings and regional constraints
↑ Back to topSome express checkout methods have their own regional and currency requirements, documented on their own pages:
- Amazon Pay: Limited to merchants in certain countries and with certain tax setups. The currencies you can accept also depend on your account country. See Amazon Pay requirements for more information on these.
- Link by Stripe: requires either a U.S. or UK account, and the customer must be paying in either USD or GBP as well. See Link by Stripe requirements.
- WooPay: Available to U.S.-based merchants and U.S. customers only. Please see the WooPay merchant documentation for more info.
- Apple Pay and Google Pay: These are hidden for products that don’t require shipping (i.e. virtual products) when your store enters prices exclusive of tax and calculates tax based on the customer’s billing address. This occurs because the billing address isn’t known before checkout in that scenario.
Feature compatibility
↑ Back to topAll five express checkout methods support manual capture, refunds, and test mode, the same as standard card payments.
Note: there is no supported method for disabling card payments while still offering the express checkout methods. See the Can I offer express payment methods without accepting card payments? page for more information.
Guest checkout requirements
↑ Back to topApple Pay, Google Pay, and Amazon Pay
↑ Back to topIf your store allows account creation during checkout, customers who aren’t logged in can still pay, and WooCommerce creates their account when the order is placed. (The Send password setup link and Generate account login settings under WooCommerce > Settings > Accounts & Privacy don’t affect this process.)
Customers who aren’t logged in must log in or create an account before the payment sheet opens in the following cases:
- If the Enable guest checkout setting and Allow customers to create an account > During checkout are both disabled.
- The purchase includes a subscription item, and neither Allow customers to create an account > During checkout nor Allow subscription customers to create an account during checkout is enabled. This is because subscriptions always require an account, even when guest checkout is enabled.
WooPay
↑ Back to topThe button is hidden for logged-out customers buying a subscription item, and hidden in all cases when guest checkout is disabled.
Link
↑ Back to topLink follows your store’s standard guest checkout rules, the same as paying by card. It has no separate guest checkout requirements of its own.
Using more than one method together
↑ Back to topYou can offer several of these methods at the same time, but a few specific scenarios have limitations to keep in mind:
- Apple Pay and Google Pay: These are enabled (or disabled) together by a single setting. You cannot enable or disable one without the other.
- Link and WooPay: These cannot both be enabled at the same time.
Checkout Field Editor
↑ Back to topCheckout Field Editor is a separate extension that adds custom fields to the checkout form. Please keep the following compatibility notes in mind:
- Because Apple Pay, Google Pay, and Amazon Pay bypass the usual checkout form, custom fields added by Checkout Field Editor aren’t collected during purchase.
- WooPay is also incompatible with Checkout Field Editor.
- Link autofills data in the checkout form rather than bypassing it, so Checkout Field Editor will still work with Link purchases.
Note that Checkout Field Editor itself works only on the classic shortcode checkout, not the newer Checkout block.
Diagnosing buttons not showing
↑ Back to topIf an express checkout button isn’t appearing where you expect, the WooPayments logs can usually tell you why. To check the logs:
- Enable WooPayments debug mode and logging.
- Load or refresh a page where you expect the button to show.
- Check the most recent WooPayments log.
For Apple Pay, Google Pay, and Amazon Pay, look for the text Express Checkout Element button disabled.
For WooPay, look for the text WooPay Express button disabled.
Usually the log will contain a straightforward reason why the button does not show, e.g. Items in the cart have unsupported product type (Express Checkout Element button disabled). Other reasons may include an unsupported product type on the product page, a zero order total, or an out-of-stock product.
Keep in mind that Link by Stripe is not a button, so it isn’t covered by these diagnostics. If Link isn’t showing, confirm that the account is U.S. or UK-based, that the customer is paying in USD or GBP, and that WooPay isn’t also enabled.