WooCommerce CRO Technique

Which payment methods should a UK WooCommerce store offer, and how should they be ordered?

This technique means offering the right payment methods for each country and device instead of showing every method to every shopper. It helps most when checkout drop-off is concentrated in specific countries or on mobile, and when payment failures or weak authorisation rates are suppressing purchase conversion even after shoppers reach the payment step.

Summary

Bottom Line: Offer the few payment methods your buyers are most likely to use, not every method your gateway supports.

  • In the UK, cards still matter, but wallets are no longer optional: Worldpay says direct cards accounted for 46% of UK online value in 2025, digital wallets 40%, and BNPL 8% of UK e-commerce value in 2025, which makes a cards-plus-wallets baseline the sensible starting point for a UK store. Those figures are directional and vendor-sourced.
  • More than half of UK adults used mobile wallets in 2024, according to UK Finance, so mobile wallet coverage is now a mainstream checkout requirement rather than a niche add-on.
  • Do not offer every local method everywhere. WooPayments, Stripe and PayPal all tie local-method availability to country, currency, device or buyer eligibility, and irrelevant choice can add friction instead of reducing it.
  • Measure payment-step completion and authorisation rate together. GA4 tells you whether shoppers move from begin_checkout to add_payment_info to purchase, while gateway reporting and logs tell you whether payments are failing because of issuer declines, blocked payments or gateway issues.
  • Roll out market by market, starting with countries that already generate revenue but show weak late-step checkout completion on a specific device. That gives you the cleanest test of whether method mismatch is part of the leak. This is an evidence-led inference from the reporting and eligibility patterns above, not a platform guarantee.

How To Implement

  • Find the markets and devices worth fixing first

    In GA4, compare begin_checkout, add_payment_info and purchase by Country and Device category so you can spot where shoppers are reaching the payment step but not finishing. Then compare that with gateway-side decline and acceptance data so you do not mistake an issuer-decline problem for a payment-choice problem. A good first rollout is a high-revenue country-device segment with obvious late-step drop-off.

  • Confirm whether the store uses classic checkout or Blocks

    Stores started after WooCommerce 8.3 use Cart and Checkout Blocks by default. If you use the Checkout block and a gateway is incompatible, payment methods can disappear completely. Check the Checkout page in Appearance → Editor → Pages → Checkout for block themes, or Pages → Checkout for non-block themes. If needed, WooCommerce lets you transform the Checkout block back to Classic Shortcode. This matters before you touch payment setup.

  • Set country logic properly before adding methods

    In WooCommerce → Settings → General, set Selling location(s) and Shipping location(s) appropriately, then set Default customer location to Geolocate or Geolocate (with page caching support). If you use geolocation, add your MaxMind licence in WooCommerce → Settings → Integration → MaxMind Geolocation. This does not “solve payments” by itself, but it gives WooCommerce more reliable country context for taxes, shipping and local-currency behaviour.

  • Build the UK baseline before you localise further

    For most UK stores, the baseline should be major cards plus mobile wallets and PayPal, because UK shoppers still use direct cards heavily, but wallets already account for a large share of online value and are mainstream among UK adults. In practice, that means making sure card acceptance is on, enabling Apple Pay and Google Pay where your gateway supports them, and keeping PayPal available as a mainstream alternative. Treat BNPL as an option to test, not as the default lead method. This recommendation is an inference from UK payment-mix evidence, not a universal rule.

  • If you use WooPayments, turn on multi-currency before local methods

    In Payments → Settings, open Advanced settings and tick Enable Multi-Currency, then save. After that, use the Multi-currency settings to add the currencies you actually need and, if appropriate, enable automatic switching to local currency. Then go back to Payments → Settings and enable only the relevant methods in Payments accepted on checkout. WooPayments explicitly requires multi-currency for local methods, and those methods only appear when the customer billing country and customer currency match the relevant rules. For example: Bancontact requires Belgium + EUR, EPS Austria + EUR, iDEAL | Wero Netherlands + EUR, Przelewy24 Poland + EUR or PLN, and Multibanco Portugal + EUR.

  • If you use the WooCommerce Stripe extension, enable only the methods you need and order them in the extension settings

    Go to WooCommerce → Settings → Payments → Stripe → Payment Methods, tick the additional methods you want, then save. Stripe’s WooCommerce extension also provides a Change display order link so you can drag methods into your preferred order. One caveat: if the Change display order control is missing, Stripe says you may be using the Optimized Checkout Suite, which uses its own ordering logic. Stripe’s broader Payment Element guidance is also clear that dynamic payment methods can display the most relevant method based on location, currency and amount, and Stripe’s payment-method rules can hide or show non-card methods by country, currency or amount from the Dashboard.

  • If you use PayPal Payments, curate by disabling noise rather than trying to force every market manually

    PayPal Payments shows Alternative Payment Methods automatically for eligible buyers and says they appear primarily on the Checkout page. In practice, that means you should disable irrelevant APMs in the plugin’s Payment Methods settings rather than leaving everything available “just in case”. For Blocks, PayPal Payments supports Block Cart and Block Express Checkout, Advanced Card Processing on block checkout, and most local APMs, but not OXXO or Pay upon Invoice in the block flow.

  • Order methods by device fit first, then by local preference

    On compatible devices and browsers, show express wallets prominently on product, cart and checkout because they reduce typing and can shortcut the form. For the main payment step, keep the locally dominant method easy to continue with. In the UK that usually means cards remain the visible default, with wallets as explicit alternatives and BNPL below those unless your own data shows otherwise. Baymard’s guidance is useful here: offer multiple methods, but keep the choice simple, preselect the most popular method for the majority path, and never auto-funnel shoppers into an off-site third-party method without deliberate opt-in.

  • Use market-specific local methods only where real demand exists

    A practical starting map for many UK stores selling into Europe is: Netherlands → iDEAL, Belgium → Bancontact, Austria → EPS, Poland → Przelewy24, Portugal → Multibanco. With WooPayments, these methods are hidden automatically unless billing country and currency match. With PayPal Payments, eligible local methods are shown automatically to relevant buyers. With Stripe, dynamic payment methods can do similar relevance filtering. That is why the safest operating model is not “everything everywhere”, but “the right method in the right market”.

  • Test safely before and after launch

    Use gateway test mode where available. WooPayments provides test mode in Payments → Settings, and Stripe’s extension documents test mode and log review; PayPal Payments provides a logging setting for troubleshooting. Put a measurement note into the rollout itself: annotate the launch date in GA4, and keep the first rollout to one country or method family so that the post-launch read is attributable. Also review order notes and gateway logs for declines, authentication failures and timeouts rather than relying on conversion alone.

How To Measure

The primary KPI is payment-step completion in the target country-device segment: compare shoppers who fire add_payment_info with shoppers who reach purchase, and also compare begin_checkout to add_payment_info so you can tell whether the leak sits before or after method selection. GA4 explicitly recommends begin_checkout, add_payment_info and purchase for online sales, and add_payment_info includes a payment_type parameter for the chosen payment method. Build an Exploration with Country and Device category, both of which GA4 populates automatically.

The secondary KPI is authorisation rate, read in your gateway reporting rather than GA4. Stripe’s Acceptance analytics distinguishes payment success rate from network authorisation rate and lets you break results down by payment method, buyer country, card country and currency. That matters because a conversion dip after payment selection can be caused by issuer declines, 3DS or fraud controls, not just by weak method coverage. For WooCommerce stores using WooPayments or PayPal Payments, review failed-payment behaviour in order notes and logs at the same time.

The additional KPI set should include purchase conversion rate by country and device, payment-method share in the target segment, and RPV as a commercial sense-check. Success looks like better payment-step completion in the target segment alongside stable or better authorisation rate and overall purchase conversion, without simply shifting shoppers into a lower-performing method or creating more failed orders.

The guardrails are failed-payment volume, checkout error rate, order-note decline reasons, unexpected drops in AOV or RPV, and any rise in refunds, disputes or support contacts after rollout. If you add new scripts or wallet buttons on product, cart or checkout pages, watch page performance as a secondary guardrail too. The goal is more completed payments, not just more method impressions.

Pitfalls

  • Myth: more payment methods always means more conversion. It does not. Baymard explicitly recommends multiple methods without sacrificing speed and warns against overwhelming users or forcing unexpected flows. The better rule is “relevant choice, minimal clutter”.
  • Mistake: enabling a local method without enabling its matching currency. WooPayments requires multi-currency for local methods and hides methods unless billing country and customer currency match the documented rules. Stripe’s WooCommerce docs make the same point with examples such as Bancontact requiring EUR and Przelewy24 requiring a Polish billing address.
  • Mistake: reading conversion alone and ignoring authorisation rate. A store can add a new method, see more payment-method clicks, and still lose orders because issuer declines, fraud blocks or authentication failures are the real constraint. Stripe’s own analytics separates payment success rate from network authorisation rate for this reason.
  • Mistake: assuming a wallet is “broken” because it is not visible on every device. Apple Pay and Google Pay are device- and browser-dependent in both WooPayments and Stripe’s WooCommerce extension, so absence on an incompatible device is often expected behaviour, not a setup failure.
  • Mistake: forgetting Blocks compatibility. If your gateway does not support the Checkout block, methods may fail to appear at all. For some stores the fastest safe fix is to revert the checkout to Classic Shortcode until the payment stack is block-compatible.
  • Myth: BNPL should be promoted first because it always lifts sales. BNPL is meaningful in the UK, but Worldpay’s UK mix still shows cards and wallets as the bigger foundations, and BNPL regulation comes under the FCA from 15 July 2026. Treat BNPL as a tested option with compliance and merchant-economics implications, not as an automatic default.

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: