Should your WooCommerce store offer Klarna or Clearpay selectively?

How To Implement

• 1 Start with the economics, not the logo

  Start with the economics, not the logo. Pull a baseline for UK mobile checkout behaviour, current payment-method mix, average order value, refunds and cancellation rate before adding anything. UK BNPL demand is real, but UK payments are still led by cards and wallets, so the question is whether BNPL fixes a specific leakage point for your store, not whether it sounds modern.

• 2 Pick one primary BNPL route in WooCommerce and avoid overlap

  Pick one primary BNPL route in WooCommerce and avoid overlap. For WooPayments, go to Payments → Settings → Buy now, pay later and enable Klarna and/or Afterpay/Clearpay if your account country is eligible; UK accounts support both Klarna and Afterpay/Clearpay. For the Stripe extension, go to WooCommerce → Settings → Payments → Stripe → Payment Methods and enable the BNPL methods you want. For PayPal Payments, go to WooCommerce → Settings → Payments → Manage PayPal → Pay Later and enable the Pay Later button or messaging. If you use the official Klarna plugin, Klarna says the current plugin bundles Payments and Order Management from version 4.3.0, and Klarna explicitly recommends not enabling Klarna as a payment method through multiple plugins at once because that creates customer confusion.

• 3 Set payment-method prominence deliberately

  Set payment-method prominence deliberately. Because UK cards and digital wallets cover a much larger share of checkout value than BNPL, keep cards and relevant express wallets easy to reach, then add BNPL as an alternative. Baymard’s research supports offering alternative methods, but keeping the choice simple and explicit rather than auto-funnelling users into a third-party flow.

• 4 If you use the Stripe extension, decide whether you want a fixed order or Stripe’s dynamic order

  If you use the Stripe extension, decide whether you want a fixed order or Stripe’s dynamic order. In standard Stripe checkout, you can go to WooCommerce → Settings → Payments → Stripe → Payment Methods → Change display order and drag methods into place. If that control is missing, Stripe’s Optimized Checkout Suite is likely active; WooCommerce documents that OCS uses machine learning to decide method order and recent Stripe extension versions enable it by default for new merchants. If you need a strict “cards and wallets before BNPL” order, go to WooCommerce → Settings → Payments → Stripe → Settings → Advanced Settings and turn off Optimized Checkout Suite, then set the display order manually.

• 5 If you use WooPayments, be aware that method order is less merchant-friendly

  If you use WooPayments, be aware that method order is less merchant-friendly. WooCommerce’s own documentation shows reordering via the option_woocommerce_gateway_order filter rather than a drag-and-drop UI. For stores without a developer, that makes WooPayments a weaker choice if strict payment-method hierarchy is central to the test.

• 6 Make BNPL selective rather than universal

  Make BNPL selective rather than universal. The cleanest no-code route is Woo’s Restrict Payment Methods extension: go to WooCommerce → Settings → Payments → Restrictions, manage the relevant gateway, and set Minimum Order Amount, Maximum Order Amount, Billing Countries, or exclusions. This is the simplest official way to show BNPL only for baskets where fees and returns are more likely to be tolerable. If you do have development support, WooCommerce exposes the woocommerce_available_payment_gateways filter, which is the right place to remove Klarna/Clearpay for low-value baskets, low-margin products, subscription carts, sale-heavy orders or other cases where the economics fail.

• 7 Use provider-specific eligibility where available

  Use provider-specific eligibility where available. The Clearpay Gateway for WooCommerce updates its minimum and maximum payment amounts after credentials are saved, and its docs expose the clearpay_is_product_supported filter for product-level exclusions. That makes Clearpay especially suited to a “show only where basket and catalogue fit” approach.

• 8 Keep classic vs Blocks straight

  Keep classic vs Blocks straight. On Cart & Checkout Blocks, the Payment Options block only shows methods that are available and block-compatible. WooCommerce warns that incompatible gateways can disappear entirely from the block checkout, and offers a one-click route back to classic checkout. If your gateway or restriction logic does not behave in Blocks, transform the page back to Classic Shortcode via Appearance → Editor → Pages → Checkout → Transform → Classic Shortcode or Pages → All Pages on non-block themes. For classic shortcodes, hooks remain the normal way to place messaging around product or cart pages.

• 9 Add messaging where it reduces uncertainty, not where it hijacks choice

  Add messaging where it reduces uncertainty, not where it hijacks choice. PayPal Pay Later messaging can be enabled per location from the Pay Later tab for Single Product, Cart and Checkout. Klarna On-site Messaging lives at the bottom of the Klarna plugin settings and needs a Client identifier from the Klarna Merchant Portal plus placement data keys. Clearpay can show instalment details on product, category/search and cart pages, and its documentation names the default hooks used by classic themes. Keep these placements informational on eligible products and carts; do not let them outrank the actual payment options at checkout.

• 10 Make the next action explicit

  Make the next action explicit. Baymard found that shoppers hesitate when a third-party payment flow is selected but the main button still implies the order is already complete. In practice, that means the shopper should explicitly choose Klarna, Clearpay or PayPal, and the copy should make the redirect obvious rather than feeling like a disguised default. Where your gateway supports editable checkout titles or descriptions, use them to name the provider clearly. PayPal’s Blocks integration already uses “Proceed to PayPal”, which is the right pattern. Measurement note: before going live, complete test orders and confirm that your GA4 implementation captures add_payment_info with a usable payment_type, otherwise you will not be able to tell whether BNPL improved payment-step completion or simply changed attribution.

• 11 Test refunds, order management and ops before rollout

  Test refunds, order management and ops before rollout. Klarna’s WooCommerce documentation says Order Management can capture, cancel and refund orders from WooCommerce. Clearpay’s docs cover automatic refunds and settlement. This matters because a payment method that looks good in conversion but adds refund friction or finance-cost drag is not a CRO win.

• 12 Roll out narrowly first

  Roll out narrowly first. Start with one BNPL option, one clear threshold, and one audience or basket band. Turning on Klarna, Clearpay and PayPal Pay Later together often creates more choice complexity than useful coverage, especially when cards and wallets already satisfy most intent. Baymard’s guidance is to offer choice without complexity, not to maximise logos.

How To Measure

Pitfalls

• Myth: BNPL should sit at the top because it lifts conversion. In UK payments data, BNPL is meaningful but still trails both cards and wallets by share, so leading with BNPL is usually a choice-architecture decision, not an evidence-led default. (Worldpay share data is vendor/industry data.)
• Mistake: enabling the same provider through multiple plugins. Klarna expressly warns that if Klarna is already enabled through another plugin, you should not enable it again as a payment method because that creates confusion at checkout.
• Mistake: turning on Stripe’s Optimized Checkout Suite while assuming you still control exact method order. WooCommerce documents that OCS uses machine learning to order methods and can remove the manual display-order control; if hierarchy matters, switch OCS off.
• Mistake: assuming every gateway and payment restriction works in Cart & Checkout Blocks. WooCommerce’s block checkout only shows available, compatible methods, and incompatible gateways may disappear completely until you revert that checkout to classic.
• Mistake: calling any post-change conversion increase a win. BNPL can simply change method mix; if refund rates, cancellation rates, provider fees or margin per order worsen, the store may be less profitable even if purchases rise. WooPayments itself states that fees vary by the payment method used, and Klarna “Pay Now” can still incur the full Klarna fee.
• Myth: explanatory text is enough even if the next step is vague. Baymard’s research found that generic primary-button copy still causes hesitation in third-party payment flows; the user needs a clear, intentional next action, not just a finance badge nearby.

Examples

FAQs

Sources & Further Reading

• What 63,000 shoppers just told us about paying – Worldpay’s 2026 market view for UK payment-method share, including cards, wallets and BNPL; useful market context, but still vendor/industry data. Date not stated on page; accessed June 2026.
• The Financial Services and Markets Act 2000 (Regulated Activities etc.) (Amendment) Order 2025: impact assessments - RPC opinion (green-rated) – UK government summary of the BNPL regulatory change, including affordability checks, clearer information and consumer protections. Published 20 May 2025.
• Update: domestic premises suppliers and Buy-Now, Pay-Later (BNPL) – HM Treasury update on BNPL merchant oversight, Consumer Duty expectations and timing around regulation. Published 16 June 2025.
• Payment Method UX: Designing Payment Selection – Independent checkout UX research on payment choice, third-party methods and button microcopy for redirected flows. Published 5 September 2023.
• Ecommerce Checkout UX Guide - Optimize Your Order Flow – Baymard guidance on offering choice without complexity and avoiding auto-funnelling users into third-party payment flows. Published 2025 page update; exact page date not stated in the open article view.
• Stripe WooCommerce Extension – Official WooCommerce documentation for Stripe payment methods, BNPL support and checkout behaviour. Date not stated on page; accessed June 2026.
• Additional payment methods Documentation – Official setup, requirements and manual display-order controls for Stripe BNPL methods in WooCommerce. Date not stated on page; accessed June 2026.
• Optimized Checkout Suite Documentation – Official Stripe-for-Woo docs on dynamic payment ordering and the conditions under which method order is controlled by machine learning. Date not stated on page; accessed June 2026.
• WooPayments: Payment Methods – Official WooPayments documentation for Klarna and Afterpay/Clearpay support and reordering limitations. Date not stated on page; accessed June 2026.
• Buy now, pay later with WooPayments – Official WooPayments BNPL documentation, including UK availability and Klarna fee caveat for “Pay Now”. Date not stated on page; accessed June 2026.
• Pay Later – Official WooCommerce PayPal Payments documentation for Pay Later eligibility, buttons and messaging. Date not stated on page; accessed June 2026.
• Customize the Pay Later messaging layout on WooCommerce – PayPal developer instructions for enabling Pay Later buttons and messaging on WooCommerce product, cart and checkout pages. Date not stated on page; accessed June 2026.

About This Page

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