Last updated: July 2024 

WooCommerce doesn't charge transaction fees — but your payment methods do. Here's a clear breakdown of what UK merchants pay through PayPal, Stripe, and card-based gateways, and why those costs compound as your store grows.

Payment fees are a margin problem, not just a cost line

For most UK WooCommerce merchants, payment fees feel fixed — a percentage deducted per sale, displayed clearly on a pricing page, easy to account for. In practice, the picture is more complicated and more expensive than that single figure suggests.

Payment costs are rarely one number. They're a stack of charges — some visible, some embedded, some that only appear when something goes wrong. And because most of them scale with revenue, they quietly shape pricing decisions, product viability, and profitability long before most merchants stop to question them.

This guide breaks down where WooCommerce payment fees actually come from, how PayPal and Stripe costs behave in practice, and why the structural differences between payment methods matter more as your order volume grows.

Quick summary

• WooCommerce itself charges no transaction fees — all payment costs come from the gateway or payment method you connect to your store

• Payment fees are almost never a single percentage — they typically include processing fees, card network costs, operational fees, and indirect overhead

• PayPal and Stripe both rely on card infrastructure, which introduces multiple intermediaries and makes costs harder to control at scale

• Indirect costs — refunds, chargebacks, failed payments, reconciliation — are rarely modelled upfront but consistently add up over time

• Small differences in per-transaction fees compound significantly as volume grows, affecting margins, pricing strategy, and product viability

• Payment methods built on fewer intermediaries — such as Pay by Bank via Fena — tend to be structurally cheaper and more predictable as stores scale

First: WooCommerce doesn't charge transaction fees

This is worth stating clearly because it's widely misunderstood.

WooCommerce is an order management and checkout platform, not a payment processor. It doesn't take a cut of your sales and doesn't add platform-level transaction fees on top of your payment costs.

Every fee you pay comes from the payment gateway or payment method you've connected to your store — whether that's PayPal, Stripe, a card processor, or something else. This means your payment cost structure is a merchant decision, not a platform constraint. You can change it by changing payment methods or configurations, without touching WooCommerce itself.

What WooCommerce payment fees actually consist of

When merchants talk about payment fees, they usually mean the headline processing percentage. That's a starting point, not the full picture.

In practice, WooCommerce payment costs tend to fall into several distinct layers:

Gateway processing fees.

These are the fees charged by the payment gateway for authorising, capturing, and settling each transaction. They're applied to every successful payment and scale directly with your sales volume. This is the number most commonly quoted on pricing pages.

Card network and scheme fees.

When payments are processed through card networks — Visa, Mastercard, or similar — there are fees imposed by those networks and by issuing banks. These are usually invisible to merchants, embedded into the rates charged by gateways rather than itemised separately. They exist whether you're using PayPal, Stripe, or any other card-based gateway.

Operational fees.

These cover the costs triggered when transactions change or fail — refund processing, chargeback fees, currency conversion, and payout-related charges. Unlike processing fees, these don't appear on every order; they appear on the problematic ones, making them harder to predict and easier to underestimate.

International payment fees.

Most gateways charge a premium for non-UK cards or cross-border transactions. For stores with a meaningful proportion of international customers, this can add materially to the effective cost per transaction.

Indirect costs.

This is the category most merchants don't fully account for: failed payments that drive abandoned checkouts, chargeback administration that costs staff time as well as fees, reconciliation complexity across multiple gateways and payout schedules, and customer support overhead driven by payment issues. These rarely appear on a payment provider's pricing page, but they compound consistently over time.

PayPal fees in WooCommerce

PayPal bundles a lot into a single checkout experience — wallet payments, card processing, buyer protection, and dispute handling. For customers, this familiarity can be a reason to trust your checkout. For merchants, it comes with a fee structure that reflects everything being packaged together.

PayPal's costs for WooCommerce merchants typically include a percentage-based processing fee on each transaction, a fixed per-transaction component that applies regardless of order size, additional charges for currency conversion and international customers, and fees that may be retained even when a transaction is subsequently refunded.

The bundled model also means limited visibility into how costs are distributed. Merchants see a headline rate but have little insight into how much of that is gateway margin, how much is card network cost, and how much relates to the additional services PayPal provides.

For stores where PayPal drives meaningful conversion — particularly among customers who prefer paying from a stored wallet — this may be a trade-off worth making. But it's worth being clear that it is a trade-off. PayPal is one of the more expensive ways to accept payments at scale, particularly for lower-margin products where each fraction of a percent matters.

Stripe fees in WooCommerce

Stripe is often the default choice for WooCommerce merchants who want straightforward card processing with clean reporting and reliable technical integration. It's generally more predictable than PayPal and more transparent about where fees come from.

Stripe's WooCommerce costs typically involve a percentage plus a fixed amount per successful card payment, higher rates for international or non-UK issued cards, chargeback handling costs when disputes arise, and optional add-ons — advanced fraud tooling, additional payment methods — that layer costs on top of the baseline.

The predictability is a genuine advantage. But the underlying constraint is the same as with PayPal: Stripe is fundamentally a card-based payment processor. Its baseline fees are set by card network economics, which means they're non-negotiable and scale directly with transaction volume regardless of how efficiently you run your operation.

For many merchants, Stripe is the right choice. It's worth understanding, though, that choosing Stripe is also choosing the cost structure of card infrastructure — including the chargeback exposure and network fee layer that comes with it.

The costs that don't appear on pricing pages

The fees quoted by payment providers — the percentage rates, the fixed per-transaction amounts — are real costs but not the complete picture. Over time, many merchants absorb a significant additional layer of costs that are operational rather than transactional.

Refund leakage

is a common one. Most payment processors don't return the processing fee when an order is refunded. A £50 order that gets refunded still cost you the processing fee to accept it. At low refund rates this is noise; at higher rates, in categories where returns are frequent, it accumulates.

Chargeback costs

go beyond the fee per dispute. Each chargeback requires staff time to investigate, compile evidence, and respond within the card network's deadlines. The fee — typically £10 to £25 per case in the UK — is visible. The hour or more of internal handling time per dispute often isn't budgeted for.

Failed payment fallout

affects both revenue and operations. Customers whose payments fail don't always try again — some abandon the purchase entirely. The cost isn't just the lost sale; it's the customer support queries and the cart abandonment rate that result.

Reconciliation friction

is the unglamorous one. Multiple payment gateways with different payout schedules, different reporting formats, and different fee structures create reconciliation complexity that consumes finance team time and introduces the risk of errors. The bigger the payment stack, the more this costs.

None of these are unique to any one provider — they're structural features of card-based payment processing. But they're worth modelling explicitly, because they tend to be invisible until they're large enough to be painful.

How payment fees compound as you scale

A 0.3% difference in effective per-transaction cost seems negligible on a single order. Across £500,000 of annual revenue, it's £1,500. Across £2M, it's £6,000. And that's before accounting for the indirect costs above.

This compounding effect shows up in a few specific ways that merchants often only notice in retrospect.

Products with tight margins gradually become less viable as payment costs erode the contribution per sale. The product hasn't changed; the economics have shifted under it.

Pricing decisions get made defensively — products priced slightly higher to absorb payment costs, which affects conversion, which requires more marketing spend to maintain volume. The payment fee is two steps removed from the pricing decision, so the connection isn't always made.

Growth creates the illusion of health while margins compress. Revenue is up; profitability per order is quietly declining. This is particularly common at the transition from small to medium scale, where payment costs start to matter seriously but the business isn't yet large enough to negotiate bespoke rates.

Why some payment methods cost less structurally

Card-based payments — whether through PayPal, Stripe, or any other card gateway — involve multiple parties in every transaction: the issuing bank, the card network, the acquiring bank, and the gateway itself. Each layer takes a margin. Each layer adds potential for fees, delays, and points of failure.

Pay by Bank works differently. Payments move directly between the customer's bank account and the merchant's, using UK payment rails rather than card network infrastructure. There's no card network layer, no interchange, no scheme fees embedded in the rate.

For WooCommerce merchants, Pay by Bank via Fena offers this direct-settlement model alongside the rest of your payment stack — not as a replacement for cards, but as an option that removes the intermediary costs for customers who use it.

The practical effect is lower per-transaction fees, no chargeback exposure on Pay by Bank volume, and a more predictable cost structure as transaction volume grows. These savings come from the payment architecture itself, not from introductory pricing or short-term incentives — which is why they tend to hold up over time.

Thinking about payment fees as a design choice

The most useful framing for WooCommerce payment fees isn't "what does it cost?" but "what does this payment architecture cost at the volume I'm heading towards?"

A payment method that's acceptably priced at £200k GMV may look materially different at £1M. The difference between payment methods compounds over time in ways that don't show up in initial evaluation.

Understanding the full cost structure — processing fees, card network costs, operational costs, indirect overhead, and the structural differences between payment architectures — gives merchants the information needed to make that evaluation properly.

Fena works with UK WooCommerce merchants to map out their current payment costs, model how fees compound at different volumes, and identify where Pay by Bank can reduce structural cost without disrupting checkout performance. If you'd like to look at how your payment stack performs over time, get in touch.

Frequently asked questions

Does WooCommerce charge transaction fees?

No. WooCommerce does not charge transaction fees or take a percentage of sales. All payment costs come from the gateway or payment method connected to your store — PayPal, Stripe, or any other provider you use.

What payment fees do WooCommerce merchants typically pay?

Most merchants pay a combination of gateway processing fees, embedded card network costs, operational fees triggered by refunds or chargebacks, and indirect costs like failed payments and reconciliation overhead. The total effective cost is usually higher than the headline processing rate.

Are PayPal fees higher than Stripe fees on WooCommerce?

In most cases, yes. PayPal bundles additional services including wallets and buyer protection, which results in higher overall fees. Stripe is generally more predictable, but both are built on card infrastructure and carry the associated cost structure.

Do I pay fees on refunded orders?

Often yes. Many payment providers retain processing fees when an order is refunded, meaning a returned transaction still carries a cost. At scale, refund fee leakage can represent a meaningful drag on net revenue.

Why do international or non-UK cards cost more?

International and non-UK cards involve additional card network processing steps, which increases transaction costs compared to domestic card payments. Most gateways apply a premium for these transactions.

What are indirect payment costs in WooCommerce?

Indirect costs include failed payments, chargeback handling, customer support driven by payment issues, and reconciliation time across multiple gateways and payout formats. These aren't itemised on pricing pages but consistently add up as volume grows.

Do payment fees increase as my WooCommerce store scales?

Yes. Most payment fees scale directly with revenue, and even small differences in effective per-transaction cost compound materially over time. This is why payment method choice becomes more consequential as transaction volume increases.

Is Pay by Bank cheaper than card payments for WooCommerce?

Generally yes, and structurally so. Pay by Bank removes the card network layer entirely, which eliminates interchange fees, scheme fees, and chargeback exposure on those transactions. The cost difference comes from the payment architecture, not promotional pricing — which means it holds up as volume grows.