WooCommerce CRO Technique

Stripe Link and PayPal Fastlane on WooCommerce: should you enable recognised returning-guest checkout?

Stripe Link and PayPal Fastlane are recognised guest-checkout layers that try to identify a shopper early, authenticate them without a traditional account login, and then autofill saved payment and shipping details to reduce checkout effort.

Summary

Bottom Line: Enable one recognised returning-guest checkout option on WooCommerce when it is genuinely eligible for your stack and you have repeat buyers, but do not clutter the payment step with multiple competing recognised-checkout prompts.

  • Link and Fastlane are not the same as a normal site account login. Link recognises shoppers by email, phone number, or browser cookie and authenticates with a one-time code; Fastlane uses passwordless recognition for guest shoppers and keeps its profile separate from a standard PayPal account.
  • The upside is real but concentrated. Stripe says businesses with a large repeat-customer base have seen an average 14% returning-user conversion increase and Link users check out 3x faster; PayPal’s own US internal data says Fastlane-accelerated shoppers converted about 50% higher and checked out around 28% faster on one merchant page, while a 2025 press release 51% and over 36% faster. All of those figures are directional vendor data, not a sitewide promise.
  • Eligibility is the first filter, not the last. WooPayments’ Link documentation still limits Link to U.S.-based WooPayments accounts taking USD, whereas the standalone WooCommerce Stripe gateway says Link can be used when the Stripe account is based in listed countries including any European country.
  • Fastlane is checkout-page sensitive on WooCommerce. Current WooCommerce PayPal Payments docs say Fastlane only works on the default WooCommerce checkout surfaces: the Checkout block, Classic Checkout block, or the [woocommerce_checkout] shortcode, and it is for guest users only.
  • Do not stack every acceleration method you can find. Baymard’s research supports offering multiple payment options but warns against overwhelming users with too many choices or unclear flows, which is why payment-step hierarchy matters if you already show PayPal, Apple Pay, Google Pay, saved cards, or Pay Later.

How To Implement

  • Audit the current payment stack before enabling anything

    In WooCommerce, confirm which express and payment methods already show at checkout and whether your checkout page is block-based or shortcode-based. For Fastlane, verify the page set at WooCommerce → Settings → Advanced → Checkout page contains the Checkout block, Classic Checkout block, or the [woocommerce_checkout] shortcode; if you use unsupported third-party checkout widgets or funnels, Fastlane will not appear. Put a measurement note here: record today’s begin_checkout → add_payment_info → purchase funnel and take screen captures of current payment-step layouts before you change anything.

  • Choose your primary recognised guest-checkout option before you switch it on

    If you are a UK store using the standalone WooCommerce Stripe gateway, Link is usually the more straightforward recognised-checkout candidate because the plugin’s Link docs include European Stripe accounts. If you are relying on WooPayments, do not assume the same eligibility: WooPayments’ Link docs still say U.S.-based account and USD only. If you are using WooCommerce PayPal Payments, Fastlane is the PayPal-side recognised guest-checkout option, but public PayPal availability messaging is still inconsistent outside the UK, so verify your business dashboard status before rollout.

  • Enable Link in the correct WooCommerce surface for your Stripe setup

    • WooPayments path: go to Payments → Settings, then in Express Checkouts tick Link by Stripe and save. WooPayments’ own Link doc says it will only show when the WooPayments account is U.S.-based and the shopper is paying in USD.
    • Standalone Stripe gateway path: go to WooCommerce → Settings → Payments → Stripe → Payment Methods, scroll to Express checkouts, tick Link by Stripe, and save. Link also requires HTTPS and an eligible Stripe account country. If you are still on the old Stripe checkout, update away from legacy checkout because WooCommerce says it stopped receiving important performance and feature enhancements after July 2025; for newer installs, Optimized Checkout Suite is the modern path and is enabled by default for new merchants from version 10.7.0, with Woo saying 10.8.0 enables OCS by default for all eligible merchants.

  • Enable Fastlane in WooCommerce PayPal Payments, but only after Advanced Card Processing is live

    Go to WooCommerce → Settings → Payments → PayPal Payments → Payment Methods, make sure Enable Advanced Card Processing is on, then enable Fastlane by PayPal and save. Current WooCommerce docs say Fastlane is only shown to guest users; logged-in store users continue to see the regular Advanced Card Processing fields.

  • Clean up competing buttons instead of simply adding more of them

    Stripe’s extension can show express checkout buttons on product, cart, and checkout pages, while Link also integrates directly in the card form. Baymard’s research supports choice but warns against complexity and unexpected flows, so if you already show Apple Pay, Google Pay, PayPal buttons, Pay Later, and saved cards, decide which option deserves first visual priority rather than presenting every accelerated method at equal prominence. This is an evidence-based inference from Baymard’s payment-choice research and the way Woo/Stripe expose Link across multiple surfaces.

  • Check custom fields and product-type compatibility before going live

    With the Stripe extension, express checkout methods can ignore checkout custom fields if those fields are added on the shortcode checkout page, or on Checkout Blocks without the woocommerce_register_additional_checkout_field API. On single-product pages, express checkout buttons are also known not to support some custom product fields such as Product Add-Ons, so disable those buttons there if needed. For Fastlane, unsupported third-party checkout builders are currently a blocker rather than a minor caveat.

  • Test both recognised and non-recognised journeys in sandbox or staging

    • Stripe Link: Woo’s test guide says to enable test mode, log out of the site and Link, go through checkout with a fake email and the documented test phone number, complete a purchase, then repeat as a returning Link user.
    • Fastlane: test in a logged-out or incognito session, verify that Fastlane shows for guest checkout, and confirm that logged-in store users see regular card fields instead. If you sell into the UK or EEA, also test normal SCA/3DS card challenges, because recognised checkout reduces form effort but does not remove card-authentication rules where they apply.

  • Wire the measurement before rollout, not after

    GA4’s recommended ecommerce model uses begin_checkout, add_shipping_info, add_payment_info, and purchase, and Google explicitly recommends passing payment_type with add_payment_info when relevant. To compare recognised vs non-recognised users, add an event-scoped custom dimension such as recognised_checkout or checkout_acceleration_variant if your current GA4 setup does not already capture it. In practice, that usually means adding a small data-layer or tag-manager update alongside the payment-method rollout.

How To Measure

The primary KPI here is returning-user checkout completion, specifically the rate from begin_checkout to purchase and, more narrowly, from add_payment_info to purchase for returning users and recognised-checkout users. In GA4, use the Checkout journey report if you send begin_checkout, add_shipping_info, add_payment_info, and purchase, or build a Funnel exploration if you want stricter step logic. Segment first by returning users, then by payment_type and, ideally, by a custom event-scoped dimension such as recognised_checkout = true/false. Success looks like a higher payment-step completion rate and shorter checkout time for the recognised cohort, with some positive movement in RPV from returning users. Guardrail metrics are overall conversion rate, RPV, AOV, and the same checkout-completion funnel for non-recognised users, because a cluttered payment step can shift share without creating net gain. If you use a WooCommerce GA4 plugin, WooCommerce Google Analytics Pro documents support for GA4 recommended checkout events and Blocks compatibility, including Add Payment Info on payment-method selection.

Pitfalls

  • Myth: “Link and Fastlane are just Apple Pay or Google Pay with a different logo.” Not quite. Link is technically Stripe’s wallet, but on WooCommerce it often behaves as an email-recognised, one-time-code autofill flow inside your payment form as well as an express option; Fastlane is a passwordless recognised guest-checkout layer and its profile is separate from a normal PayPal account.
  • Mistake: judging the result on sitewide conversion alone. Vendor evidence for both products is strongest among accelerated or recognised shoppers, so judging only total-site conversion can hide the real effect or overstate it if overall traffic mix changed at the same time.
  • Mistake: assuming WooPayments Link eligibility and standalone Stripe-gateway eligibility are the same thing. They are not the same in the current docs: WooPayments still says U.S. account + USD, while the standalone Stripe gateway says eligible Stripe accounts include any European country.
  • Mistake: expecting Fastlane to work for logged-in customers or in heavily customised checkout builders. Current WooCommerce docs say Fastlane is for guest users only and requires a default WooCommerce checkout surface, not unsupported widgets like Elementor Checkout Widget or funnel builders such as Cartflows or FunnelKit.
  • Mistake: placing every accelerated method above the fold and calling it “more choice”. Baymard’s evidence says users need flexibility without complexity; too many competing payment prompts can turn a cleaner checkout into a noisier one. That is especially relevant when Link can appear on product, cart, and checkout pages while Fastlane adds another recognised path at checkout.

Examples

FAQs

Sources & Further Reading

Want us to implement this for you?

We run measured CRO consultancy for WooCommerce. If you want help prioritising, testing & implementing these improvements, tell us about your store.

Book Pilot

About This Page

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