WooCommerce Payment Gateways for UK Businesses: What to Consider

Choosing a payment gateway is one of the more consequential decisions you’ll make when setting up a WooCommerce store. The gateway you select affects transaction costs, checkout conversion rates, how you handle refunds and recurring billing, what currencies you can accept and whether your checkout meets UK regulatory requirements. It’s not simply a matter of picking the most recognisable name. Priority Pixels provides WooCommerce development for UK businesses where the payment infrastructure is configured to match the way your customers purchase, not just dropped in with default settings.

The UK payments market has shifted considerably over the past few years. Strong Customer Authentication under PSD2 changed how card transactions are processed. Buy Now Pay Later services have moved from consumer retail into B2B. Direct debit solutions have matured to the point where they compete with card payments for subscription and wholesale models. All of this means UK businesses running WooCommerce stores have more options than they did even three years ago, but also more technical and regulatory considerations to work through.

How WooCommerce Handles Payment Gateways

WooCommerce ships with a handful of built-in payment methods. PayPal Standard and direct bank transfer (BACS) are available from a fresh install, alongside cash on delivery and cheque payments. For most UK businesses selling online, these defaults are a starting point rather than a finished setup. The real payment infrastructure comes from gateway plugins that connect your checkout to a specific payment processor.

Each gateway plugin sits between your WooCommerce store and the processor’s API. When a customer enters their card details or selects a payment method, the plugin sends that data to the processor, receives a response and updates the order status accordingly. Some gateways handle the entire transaction on your site through an embedded form, while others redirect the customer to a hosted payment page before returning them to your order confirmation screen. That distinction matters for user experience, conversion rates and PCI compliance obligations, which we’ll come back to later.

The WooCommerce extensions marketplace lists dozens of gateway plugins. Stripe, PayPal, Square, Worldpay, Opayo (formerly SagePay), GoCardless and Klarna all have either official or well-maintained third-party integrations. The question isn’t whether a plugin exists for your preferred processor. It’s whether that processor suits your business model, your customer base and your compliance requirements.

Stripe for WooCommerce

Stripe has become the default recommendation for many WooCommerce stores. There are good reasons for that. The official WooCommerce Stripe plugin is maintained by the WooCommerce team itself, which means it receives regular updates and stays compatible with core releases. Setup is straightforward. You create a Stripe account, enter your API keys in the plugin settings and you’re processing payments.

For UK businesses, Stripe charges a per-transaction fee on European cards with a slightly higher rate for non-European cards. There are no monthly fees, no setup costs and no minimum commitment. You pay per transaction and nothing else. That pricing model works well for businesses with unpredictable sales volumes because you’re not locked into a monthly contract that costs you money during quiet periods.

Where Stripe stands out technically is its approach to checkout. The plugin supports Stripe Elements, which embeds card input fields directly into your WooCommerce checkout page. Customers never leave your site, which keeps the checkout flow smooth and reduces the drop-off that can happen when buyers are redirected to an external payment page. Stripe also handles 3D Secure authentication natively, meeting SCA requirements without any additional configuration on your part.

Stripe’s weakness for some UK businesses is its dispute resolution process. If a customer raises a chargeback, the funds are deducted immediately while the dispute is investigated. For businesses selling high-value items, that cash flow impact can be significant. Stripe also doesn’t suit businesses that need to take payments over the phone without card-not-present infrastructure, though its Stripe Terminal product is closing that gap for in-person sales.

PayPal for WooCommerce

PayPal remains one of the most widely recognised payment methods in the UK. The advantage it offers isn’t technical. It’s trust. A significant proportion of online buyers have a PayPal account and feel comfortable using it, particularly when buying from a brand they haven’t purchased from before. Offering PayPal alongside a card payment option can reduce checkout abandonment simply because some customers prefer not to enter card details on an unfamiliar site.

The current WooCommerce PayPal integration is PayPal Payments, which replaced the older PayPal Standard plugin. It supports PayPal checkout, card payments processed through PayPal, Pay Later options and Venmo (though Venmo is US-only). For UK merchants, the relevant features are PayPal wallet payments and card processing. Transaction fees for UK domestic transactions sit at a percentage plus a fixed fee per transaction, with rates varying by monthly volume.

One practical consideration is that PayPal holds are common for newer accounts or businesses with sudden spikes in volume. PayPal may hold funds for up to 21 days if your account triggers their risk algorithms, which can create cash flow problems for growing businesses. This is a well-documented frustration among UK merchants and worth factoring into your decision. A properly structured web development project should account for payment flow testing under realistic conditions before launch, including how your chosen gateway handles holds, refunds and failed transactions.

Opayo (SagePay) and Worldpay

Opayo and Worldpay represent the traditional end of the UK payment gateway market. They’ve been processing payments for UK businesses since before WooCommerce existed. Both are now owned by larger financial services groups. Opayo is now part of Elavon (itself a subsidiary of US Bancorp), while Worldpay merged with FIS before being partially separated again.

These gateways typically operate on a monthly fee plus per-transaction pricing model. That’s different from Stripe’s transaction-only approach and can work out cheaper for businesses with consistent, high-volume sales. If you’re processing a large number of transactions monthly, the per-transaction rate from Opayo or Worldpay may be lower than what Stripe charges, enough to justify the monthly fee.

The WooCommerce plugin situation for Opayo and Worldpay is less straightforward than for Stripe. The official Opayo plugin has had periods of inconsistent maintenance. Some merchants use third-party alternatives instead. Worldpay’s WooCommerce integration typically goes through a third-party plugin as well. Before committing to either gateway, check that the available plugin is actively maintained, compatible with your WooCommerce version and supports the checkout experience you want.

GoCardless for Direct Debit Payments

GoCardless fills a gap that card payment gateways don’t address well. Direct Debit through the Bacs system allows you to collect payments directly from a customer’s bank account without card details, card expiry dates or the risk of card-related chargebacks. Transaction fees are typically lower than card processing rates, which makes GoCardless attractive for businesses with recurring billing or high-value B2B transactions where card fees would add up.

The WooCommerce integration for GoCardless works through their payment pages. When a customer chooses Direct Debit at checkout, they’re redirected to GoCardless to set up a Direct Debit mandate. Once the mandate is active, subsequent payments are collected automatically. The timing is different from card payments, though. Direct Debit collections take several working days to clear, so you don’t receive confirmation of successful payment immediately. For physical goods, that delay means deciding whether to ship before the payment has fully cleared.

GoCardless works particularly well for WooCommerce Subscriptions. If you sell products on a recurring basis, whether that’s monthly supply deliveries, ongoing service access or membership fees, the combination of WooCommerce Subscriptions and GoCardless gives you lower transaction costs than card-based recurring billing. The customer sets up one mandate and payments are collected each billing cycle without the risk of a card expiring or being replaced mid-subscription.

Klarna and Buy Now Pay Later

Klarna’s WooCommerce integration lets customers split their purchase into instalments or defer payment entirely. The merchant receives the full payment upfront (minus Klarna’s fee), while Klarna assumes the credit risk and collects from the customer over time. For UK ecommerce businesses selling products in the higher price range, this can increase average order values because customers are less hesitant to commit when the cost is spread across several payments.

From a regulatory perspective, Buy Now Pay Later in the UK is moving towards formal FCA regulation. The government confirmed that BNPL products will be brought within the FCA’s regulatory perimeter, meaning providers will need to carry out affordability checks and customers will have access to the Financial Ombudsman for complaints. If you’re adding Klarna to your WooCommerce store, keep an eye on how the regulatory requirements develop, because they may affect what information you need to present to customers at checkout and how the payment flow works.

The practical consideration with Klarna is fee structure. Klarna charges merchants a higher per-transaction fee than standard card processing. You need to weigh that cost against the uplift in conversion rate and order value that instalment payments can deliver. For low-margin products, the additional fee may not justify itself. For higher-ticket items where purchase hesitation is a genuine barrier, the numbers often work.

PSD2, SCA and What They Mean for Your Checkout

The second Payment Services Directive (PSD2) introduced Strong Customer Authentication (SCA) requirements across the UK and Europe. SCA requires that electronic payments are authenticated using at least two of three factors: something the customer knows (a password or PIN), something they have (a phone or card reader) and something they are (fingerprint or facial recognition). In practice, this means most online card payments now trigger a 3D Secure authentication step where the customer verifies the transaction through their banking app or a one-time code.

The UK retained PSD2 requirements after leaving the EU, so SCA applies to domestic transactions where the card issuer and the merchant’s acquirer are both UK-based. Your payment gateway must support SCA-compliant authentication flows. All the major gateways covered above handle this, but the quality of the experience varies. Stripe and PayPal manage SCA within their checkout components with minimal friction. Some older gateway integrations present a clunkier authentication step that takes customers to a separate page, which can cause confusion and drop-off.

SCA exemptions exist for low-value transactions and for transactions flagged as low risk by the payment processor’s fraud analysis. If your gateway supports these exemptions (Stripe does through its Radar fraud detection), low-risk transactions can proceed without the additional authentication step. That’s worth considering for stores where the majority of orders fall below the exemption threshold, as it keeps checkout friction to a minimum.

Choosing the Right Gateway for Your Business

The decision comes down to a few practical considerations that vary from one business to the next. Before comparing gateways, work through these questions first:

• What volume of transactions do you expect monthly, and is that volume consistent or seasonal?
• Do your customers pay primarily by card, or do you need direct debit, BNPL or wallet options?
• Are you selling one-off products, subscriptions or a mix of payment models?
• How much developer resource do you have for integration, testing and ongoing maintenance?
• What level of PCI compliance are you prepared to manage internally?

A business processing a modest number of monthly transactions doesn’t benefit from a gateway with monthly fees. Stripe’s pay-per-transaction model makes more sense there. A high-volume operation running thousands of transactions monthly might save meaningfully on processing costs with Opayo or Worldpay, even after accounting for the monthly fee.

Your customers also matter. If you’re selling to consumers who expect to pay by card or PayPal, offering those options is obvious. If you’re selling to other businesses on recurring terms, GoCardless direct debit removes card-related failure points and reduces your per-transaction costs. If your products carry a higher price point, adding Klarna might reduce the hesitation that causes abandoned carts.

Running multiple gateways is common and often practical. A typical UK WooCommerce store might offer Stripe for card payments, PayPal as an alternative for buyers who prefer it and GoCardless for subscription billing. The key is testing each gateway’s checkout flow under real conditions, not just confirming that it processes a test payment.

PCI compliance is another consideration. If your gateway uses a hosted payment page or embedded elements that keep card data off your server (Stripe Elements, PayPal’s hosted buttons), your PCI obligations are limited to the simplest self-assessment questionnaire. If you choose a gateway integration that processes card data through your own server, your compliance requirements increase significantly. For most WooCommerce stores, staying with an integration that keeps card data off your infrastructure is the sensible default. WordPress development that follows security best practices should treat PCI scope reduction as a priority from the outset rather than an afterthought.

Checkout Experience and Conversion

The technical capabilities of a payment gateway don’t exist in isolation. How the checkout feels to the customer has a direct effect on whether they complete the purchase. A checkout that redirects to an unfamiliar payment page, asks for information the customer has already provided or presents a confusing authentication step will lose sales. The best gateway in the world is worthless if the checkout experience it creates drives customers away.

Embedded checkout forms, where the card input fields sit within your own checkout page, tend to convert better than hosted payment pages. Stripe Elements and PayPal’s Advanced Card Fields both support this approach. The customer stays on your site throughout the process, which maintains visual continuity and trust. If your WooCommerce theme uses a custom checkout layout or a one-page checkout design, make sure the gateway plugin you choose supports that layout without breaking the design.

Payment method visibility at checkout also matters. Displaying logos for accepted payment methods early in the checkout process (not just at the payment step) reassures customers that their preferred method is available. Research from the Baymard Institute consistently identifies lack of trust and limited payment options among the leading causes of cart abandonment. Conversion rate optimisation for ecommerce sites should always include a review of the checkout flow and payment presentation, not just landing pages and product pages.

Testing and Going Live

Every gateway offers a sandbox or test mode. You should use it thoroughly before accepting real payments. Test the full purchase journey, not just a successful card transaction. Test what happens when a card is declined, when the SCA step times out, when a customer closes the browser mid-payment and when a refund is processed. Each of these scenarios produces different order statuses in WooCommerce. Your order management workflow needs to handle all of them.

Webhook configuration is one area that catches people out. Most gateways send event notifications (payment succeeded, payment failed, dispute opened, refund processed) back to your WooCommerce store via webhooks. If the webhook URL is misconfigured or your server doesn’t respond correctly, order statuses in WooCommerce won’t update to reflect what’s happened at the gateway. A customer might pay successfully but see their order stuck on “pending payment” because the webhook notification never arrived.

Before going live, confirm that your SSL certificate is valid and covers the checkout pages, that your WooCommerce cron jobs are running (they trigger scheduled payment retries for subscriptions) and that email notifications are firing correctly for each order status change. A well-designed ecommerce site will have all of these details covered during the build process, not discovered the first time a real customer places an order.