Do Apple Pay and Google Pay increase WooCommerce conversion?

How To Implement

• 1 Choose one primary wallet route first

  If you already take cards through WooPayments, start there. If you already use the official Stripe extension for cards, use its express checkout setup. If PayPal is already central to your checkout mix, use PayPal Payments. That keeps reconciliation, refunds and reporting simpler because Apple Pay and Google Pay are configured inside the gateway you are already using, rather than layered on top through a second card gateway. This is an operational recommendation drawn from the way each plugin handles wallet setup and domain registration, not from a head-to-head platform test.

• 2 Baseline measurement before you switch anything on

  Make sure GA4 is already collecting the standard ecommerce events you need: begin_checkout, add_shipping_info, add_payment_info and purchase. GA4’s Checkout journey report uses those events as the funnel. Also remember that GA4 can take a payment_type parameter on add_payment_info, and any extra parameters you want to analyse in reports need to be registered as custom dimensions. A practical setup here is a custom event such as express_wallet_click with parameters like wallet_name, page_type and gateway, because early wallet taps on product or cart pages happen before the standard checkout funnel begins. Measurement note: do not judge the rollout on purchase totals alone; compare eligible-device segments before and after launch.

• 3 If you use WooPayments, enable Apple Pay and Google Pay in Payments > Settings

  WooPayments lets you toggle Apple Pay and Google Pay together, choose where the button shows, and style text, size, colour scheme and border radius. Customers then skip the regular checkout flow and WooPayments redirects them to the thank-you page after authorisation. On retry, WooPayments recommends toggling Apple Pay / Google Pay off and back on, then checking the WooPayments log for domain verification. Test mode works, but WooPayments notes that Apple Pay test purchases use the real wallet card on the device without making a live charge, and Woo test cards cannot be used for Apple Pay.

• 4 For WooPayments, handle classic templates and Blocks differently

  On classic product and cart templates, WooPayments relies on standard WooCommerce theme hooks to render the buttons, so non-standard themes can stop them appearing. On block themes, cart and checkout placement is controlled by the relevant Woo checkout blocks, and Woo notes that some style choices can be overridden by the Express Checkout block’s “Apply uniform styles” setting introduced in WooCommerce 9.4.0. In the Site Editor and Checkout block architecture, the relevant block surfaces are woocommerce/cart-express-payment-block and woocommerce/checkout-express-payment-block.

• 5 If you use the official Stripe extension, enable Express checkouts in WooCommerce > Settings > Payments > Stripe > Payme

  Stripe requires a valid SSL certificate, full-site HTTPS, and for Apple Pay specifically port 443, TLS 1.2 or later, plus the domain enabled in Stripe’s payment method domains. Google Pay also requires the domain to be enabled there. Apple Pay and Google Pay cannot be enabled separately in the WooCommerce Stripe extension. After saving, use Customize to choose whether the buttons appear on checkout, product pages and cart pages, and to set the CTA, size and theme.

• 6 For Stripe, treat Blocks and custom checkout fields as a real implementation detail, not a footnote

  Stripe’s WooCommerce documentation says extra checkout fields are ignored on shortcode checkout pages, and on Blocks they are only recognised if they were added using the woocommerce_register_additional_checkout_field hook. It also notes that some product types and flows will suppress express buttons, including non-default product types, certain pre-orders, file upload fields, some subscription states, and non-shippable products when tax is calculated from billing address. As of Stripe for WooCommerce 9.5.0, there is a filter — wc_stripe_should_hide_express_checkout_button_based_on_tax_setup — to override the default hiding behaviour for digital products, but Stripe documents the tax-mismatch risk plainly. Use that only when you fully understand the VAT and address implications.

• 7 If you use PayPal Payments, set button locations first, then add Apple Pay and Google Pay inside PayPal’s own wallet set

  PayPal’s plugin lets you choose Smart Button Locations, and by default PayPal smart buttons can be enabled on checkout, single product and cart pages. For Apple Pay and Google Pay specifically, the plugin’s documented route is: sign up for the wallet in PayPal, go to the Connection tab and click Check available features, then go to Advanced Card Processing > Digital Wallet Services and enable the Apple Pay or Google Pay button. Apple Pay also needs domain registration through PayPal’s Manage Domain Registration flow. The plugin serves the domain association file automatically, but the domain still has to be registered inside PayPal.

• 8 For PayPal, keep the classic-versus-Blocks difference in view

  On classic checkout, PayPal says you need Classic Checkout buttons enabled for the gateway to appear on [woocommerce_checkout] or the Classic Checkout block. On Blocks, PayPal supports Block Cart and Block Express Checkout, but explicitly describes its Cart and Checkout Blocks support as partial, with more features still in development. It also documents that Apple Pay and Google Pay in the checkout context currently sit below the PayPal buttons rather than as entirely separate gateways. That is workable, but it changes how prominent those wallets feel compared with WooPayments or Stripe.

• 9 Choose surfaces deliberately instead of turning every button on everywhere

  Product-page express buttons are strongest when the product is simple, the shopper has already made key variant selections, and there is little reason to force a full review step. Apple and Stripe both recommend earlier wallet surfacing where appropriate. Cart is usually the most balanced starting point for established stores because it still lets shoppers review basket and shipping logic before skipping most form-fill. Checkout should remain enabled as the fallback and for lower-eligibility traffic. Also note WooPayments product-type caveats: bundled, composite and bookable products can be paid with wallets, but the wallet button cannot appear on the product page for those types; it appears on cart and checkout instead.

• 10 Run device, browser, country and order-type QA before launch

  Test as a logged-out shopper first. For WooPayments, browser support differs by device and browser, with Apple Pay broadly appearing on Apple devices and Google Pay on a wider browser set, while Stripe’s Express Checkout Element also only shows supported methods in supported environments and countries. For PayPal, Apple Pay appears only on supported Apple devices and Safari-backed eligible environments, and PayPal provides a device eligibility indicator inside the plugin. Test at minimum: iPhone, Android, a Mac desktop, UK billing and shipping, GBP, a shippable product, a virtual product, a mixed cart, and one refund or void flow. Check WooPayments logs if buttons do not appear, and remember PayPal says account-level feature eligibility sometimes needs a manual refresh through Check available features.

• 11 Check post-purchase operations before calling the rollout finished

  Wallet checkout is not only a front-end change. WooPayments says Apple Pay and Google Pay transactions can be refunded like normal transactions, and PayPal says refunds are returned to the original payment method. That means customer service, returns messaging and finance reconciliation all need a real test, especially for guest orders and mixed PSP setups.

• 12 Put a performance guardrail around the rollout

  Core Web Vitals still matter on product, cart and checkout pages, and third-party embeds can affect LCP, INP and CLS. That matters particularly with PayPal, whose WooCommerce documentation notes that caching or JavaScript minification can interfere with Smart Buttons and that the Mini Cart button can cause PayPal scripts to load on most non-cart, non-checkout pages. Measure the affected templates after launch, not just conversion.

How To Measure

Pitfalls

• Myth: “Apple Pay and Google Pay will definitely lift conversion for every WooCommerce store.” They can help, and the evidence is good enough to justify testing, but the strongest published figures are vendor data and often apply only to eligible users or eligible checkouts. Treat Stripe’s 22.3% Apple Pay figure and its “2x when shown earlier” figure as directional vendor evidence, not a benchmark you can promise in a proposal.
• Mistake: only showing wallets at the end of checkout. If a wallet appears only after the shopper has already filled in most of the form, you leave a lot of the speed benefit unused. Independent UX guidance says mobile checkout should minimise steps and typing, and Stripe’s own studies say earlier Apple Pay placement can materially outperform end-of-checkout-only placement.
• Mistake: assuming the button preview means customers can actually use it. Live eligibility still depends on browser, device, country, account setup and wallet availability. WooPayments publishes browser/device scenarios, Stripe says supported methods only show in supported countries and browsers, and PayPal says preview styling can appear even when the current device is not eligible.
• Mistake: forgetting domain registration and HTTPS requirements. WooPayments uses domain verification and logs it, Stripe needs payment method domains plus HTTPS and Apple Pay technical requirements, and PayPal requires manual domain registration for Apple Pay even though the plugin serves the verification file automatically. Miss this and the button may not show, or the Apple Pay sheet may open then close.
• Mistake: ignoring tax, field and product-type edge cases. WooPayments and Stripe can suppress wallet buttons for non-shippable products when tax depends on billing address; WooPayments limits product-page buttons on some product types; Stripe documents unsupported product types and warns that extra checkout fields may be skipped unless registered correctly; WooPayments also says Checkout Field Editor-style extra fields are not compatible.
• Myth: “Wallets mean I can remove card payments.” Usually no. WooPayments says there is no way to completely disable card payments while still accepting Apple Pay or Google Pay through WooPayments, and Stripe says card payments generally need to stay enabled for express checkout methods to work.
• Mistake: shipping the front-end and forgetting refunds, returns and support language. Wallet orders are still normal orders operationally, but the refund path matters. WooPayments supports refunds for Apple Pay and Google Pay transactions, and PayPal says refunds go back to the original payment method, sometimes on card or bank timelines outside your control. If support does not explain that clearly, you can create avoidable post-purchase friction.
• Mistake: ignoring performance impact, especially with PayPal. Third-party embeds can affect Core Web Vitals, and PayPal’s WooCommerce docs specifically warn that caching or JS minification can break Smart Buttons and that some PayPal features can load scripts more broadly than expected. This is why wallet rollout needs a performance guardrail, not just a revenue dashboard.

Examples

FAQs

Sources & Further Reading

• Testing the conversion impact of 50+ global payment methods – Stripe’s 2025 experiment write-up; useful for vendor-directional figures on Apple Pay, relevant payment methods, conversion and revenue impact among eligible checkouts. Date: 10 April 2025.
• What 63,000 shoppers just told us about paying – Worldpay summary with UK-specific wallet share and 2030 outlook; useful for demand context, but still platform-industry data rather than a WooCommerce study. Date: date not stated on page; accessed 3 June 2026.
• The Checkout UX Guide – Independent checkout UX research and abandonment context; useful for the business case, not a wallet-specific experiment. Date: date not stated on page; accessed 3 June 2026.
• Checkout UX 2025: 10 Pitfalls and Best Practices – Updated Baymard benchmark with checkout quality and abandonment context. Date: published 13 November 2024, updated 25 November 2025.
• Accepting Apple Pay with WooPayments – Official WooPayments setup, styling, test-mode and troubleshooting guidance. Date: date not stated on page; accessed 3 June 2026.
• Apple Pay and Google Pay compatibility – Official WooPayments product, browser, tax, field and refund compatibility notes. Date: date not stated on page; accessed 3 June 2026.
• Enabling express checkouts – Official WooCommerce Stripe extension guide covering payment method domains, placement controls, unsupported scenarios and the tax override filter. Date: date not stated on page; accessed 3 June 2026.
• Express Checkout Element – Stripe’s underlying wallet-element documentation; useful for support matrices, eligibility and relevance-based button sorting. Date: date not stated on page; accessed 3 June 2026.
• WooCommerce PayPal Payments documentation – Official PayPal Payments guide for Smart Button locations, Apple Pay domain registration, Google Pay setup and Blocks caveats. Date: date not stated on page; accessed 3 June 2026.
• Blocks reference – Official WooCommerce block names for cart and checkout express payment blocks. Date: date not stated on page; accessed 3 June 2026.
• Checkout block – Official block editor guidance and checkout block behaviour. Date: date not stated on page; accessed 3 June 2026.
• Recommended events – Official GA4 event definitions, including add_payment_info and payment_type. Date: 7 May 2026.

About This Page

• Written By: Eliot Webb – Founder & WooCommerce CRO Consultant
• Last Reviewed: 5 Jun 2026
• Last Updated: 5 Jun 2026