Last updated: July 2024

Pay by Bank lets WooCommerce customers pay directly from their bank account without a card. Here's when it genuinely improves margins and conversion for UK merchants, when it doesn't, and how to add it via Fena without disrupting your existing checkout.

The right question isn't whether to offer Pay by Bank — it's when

Pay by Bank is receiving more attention in UK ecommerce, and for good reason. It cuts card network costs, eliminates chargebacks on those transactions, and offers a payment experience that a growing proportion of UK shoppers actively prefer. For WooCommerce merchants, it's a real option worth evaluating.

But it isn't a universal answer. The merchants who get the most value from Pay by Bank are those who understand where it fits in their specific payment stack — not those who adopt it as a wholesale replacement for cards and wallets.

This guide covers what Pay by Bank is, how it works within WooCommerce, the types of stores and transactions where it performs strongest, and where cards and wallets remain the better choice. It also covers what changes when Pay by Bank via Fena is added to a WooCommerce checkout, and what to think through before rolling it out.

Quick summary

• Pay by Bank allows WooCommerce customers to pay directly from their bank account, authorising the payment within their banking app — no card details required

• It is not the same as WooCommerce's built-in manual bank transfer option, which is unautomated and operationally burdensome — Pay by Bank via Fena automates the entire flow and confirms payment within checkout

• Pay by Bank tends to perform best for high-value orders, trust-sensitive purchases, B2B transactions, and merchants where card fees or chargeback rates are a material cost

• Cards and wallets remain essential for impulse purchases, international customers, and checkout flows where speed and familiarity drive conversion

• The strongest WooCommerce payment setups for UK merchants combine all three: cards for breadth, wallets for repeat customers, and Pay by Bank for cost efficiency and high-value transactions

• Fena integrates Pay by Bank directly into WooCommerce, providing automated payment confirmation, real-time settlement, and full transaction reporting

What Pay by Bank actually is

Pay by Bank is a payment method that lets customers pay directly from their bank account at checkout, without a card intermediary. Instead of entering card details, the customer selects their bank, is taken into their banking environment, and authorises the payment using their existing banking credentials — biometrics, PIN, or bank login. The funds transfer directly from their account to the merchant's.

In the UK, Pay by Bank is built on open banking infrastructure — the regulated framework overseen by the FCA that the major UK banks are required to support. This matters because it means the payment is authenticated at the bank level, not at the card network level. There are no card credentials in the flow, no card network intermediaries, and no card dispute mechanism.

From a merchant perspective, adding Pay by Bank via Fena means accepting a new payment rail that operates alongside your existing card and wallet setup — not replacing it. Customers choose at checkout which method they prefer.

Pay by Bank versus WooCommerce's built-in bank transfer: an important distinction

WooCommerce includes a basic bank transfer option — often referred to as BACS or manual bank transfer — and it's worth being clear that Pay by Bank via Fena is a fundamentally different thing, not a more polished version of the same mechanism.

With WooCommerce's built-in bank transfer, the checkout presents the customer with bank account details and asks them to manually make the transfer themselves. The merchant then has to wait for the payment to arrive, manually match it to the order, and update the order status. The customer has to remember to include the right reference. Things go wrong regularly, and the process creates meaningful operational overhead.

Pay by Bank via Fena automates the entire flow. The customer selects Pay by Bank at checkout, chooses their bank, authorises the payment within their banking app, and the confirmation comes back to WooCommerce automatically — the order is marked as paid, the customer sees confirmation, and the merchant sees a completed transaction. No manual reconciliation, no missing references, no waiting to see if the payment arrives.

The customer effort is also dramatically lower. The manual bank transfer flow requires the customer to leave your checkout, open their banking app or log into online banking, navigate to payments, find your account details, enter a reference, and confirm. Pay by Bank guides them through authorisation within a structured, embedded flow that takes a fraction of the time. For merchants currently offering manual bank transfer and wondering why completion rates are low, this difference explains most of it.

Why UK merchants add Pay by Bank to WooCommerce

The reasons merchants evaluate Pay by Bank fall into three consistent categories: cost structure, payment reliability, and the trust dynamic at checkout.

Cost structure.

Card payments carry a layered cost: percentage fees, fixed per-transaction amounts, card network and interchange fees embedded in the gateway rate, plus additional charges for refunds, chargebacks, and cross-border transactions. These all scale with order value. Pay by Bank pricing is typically flatter and less sensitive to basket size. For merchants processing higher-value transactions, subscriptions, or operating in categories with tight margins, the fee difference is meaningful and compounds across volume.

Payment reliability.

Cards fail for reasons merchants can't control — expired cards, issuer declines, fraud rule triggers, insufficient credit headroom. Each failure is a potential lost sale that requires the customer to retry with different details or a different method. Pay by Bank operates differently: the customer sees their actual bank balance before authorising, which eliminates a significant category of soft declines. The payment either goes through or it doesn't — there's no ambiguity, no retry loop, and no invisible issuer decision in the middle.

Trust at checkout.

For some customers — particularly those making high-value purchases from an unfamiliar merchant — entering card details online involves a risk calculation that not everyone resolves in favour of completing the purchase. Authorising a payment within their own banking app, using their existing bank security, can feel more transparent and more controlled. For UK shoppers accustomed to online banking, the flow is familiar in a way that adds rather than removes confidence.

When Pay by Bank performs best

Pay by Bank isn't equally valuable across every WooCommerce store. The scenarios where it consistently makes the biggest positive difference share a few common characteristics.

High average order values.

The fee saving from avoiding card network costs is more significant at higher transaction values. For orders above £100 — and particularly above £250 — the difference in effective processing cost between cards and Pay by Bank becomes a material margin consideration.

Trust-sensitive and considered purchases.

When a customer is making a purchase that involves research, evaluation, or meaningful financial commitment — high-end goods, specialist equipment, professional services, bespoke products — the checkout is part of the trust journey, not just a payment mechanism. Pay by Bank's bank-authenticated flow fits this context better than a fast card entry form.

B2B and trade purchases.

Business buyers tend to be more comfortable with bank-based payment flows and often prefer them. Invoice-style purchasing via bank transfer is familiar in a business context; Pay by Bank offers the same familiarity without the friction of manual transfer.

Categories with elevated chargeback rates.

Merchants in categories where chargebacks are a recurring operational cost — whether from genuine disputes or friendly fraud — benefit from shifting volume to Pay by Bank, which removes the card dispute mechanism entirely for those transactions.

UK-majority customer base.

Pay by Bank via Fena works with the major UK banks. For stores serving primarily UK customers, coverage is comprehensive. For stores with a significant international customer base, the coverage picture is narrower and cards remain the more reliable default.

When Pay by Bank is less effective

Honest evaluation means being clear about the scenarios where Pay by Bank is not the right fit — or where over-emphasising it can harm conversion.

Impulse and low-consideration purchases.

When a customer has made a snap decision to buy, friction is the enemy. Saved cards and digital wallets offer near-zero-friction checkout for returning customers. Pay by Bank introduces an extra step — bank selection, banking app redirect, authorisation — that is worth it for considered purchases but works against conversion for fast, impulsive ones.

Wallet-first customer behaviour.

Customers who habitually pay with Apple Pay, Google Pay, or a stored card are optimised for speed. For this segment, any additional steps reduce conversion. Offering Pay by Bank as an option is fine; surfacing it as the primary or most prominent method is likely to cost sales.

International customers.

Pay by Bank in the UK works within UK open banking infrastructure, which means bank coverage for international customers is limited. Merchants with a material proportion of non-UK buyers need to ensure cards remain fully available and prominent for that segment.

Subscription and recurring billing.

Pay by Bank is suited to one-off payments. For fully automated recurring billing, cards or direct debit provide a better infrastructure. Merchants with subscription models should evaluate Pay by Bank for one-off transactions — initial purchases, top-ups, or upgrades — rather than attempting to retrofit it into automated recurring billing.

The checkout experience: what customers actually see

From a customer perspective, Pay by Bank via Fena sits somewhere between a wallet payment and a manual bank transfer — faster and more structured than the latter, with one additional step compared to a saved card.

The practical flow: the customer selects Pay by Bank at checkout, selects their bank from a list of UK banks, and is taken into their banking app or online banking environment. They review and authorise the payment using their normal banking credentials. The confirmation returns to WooCommerce, the order is confirmed, and the customer sees the same order success page they'd see with any other payment method.

The critical factors for good customer experience in this flow are clear labelling and honest explanation. Customers should understand before they click that they're approving a bank payment — not entering card details, not setting up a recurring transfer, and not sharing their banking credentials with the merchant. That clarity removes hesitation and prevents the confusion that leads to abandonment mid-flow.

Security messaging is particularly important for first-time users of Pay by Bank. Reassurance that the authorisation happens within their own bank's environment — and that the merchant sees only a payment confirmation, not their account details — addresses the most common concern directly.

Fees, settlement, and cash flow

Beyond the per-transaction cost comparison with cards, Pay by Bank has a distinct impact on cash flow that matters for WooCommerce merchants managing working capital.

Pay by Bank via Fena settles faster than the rolling delays typical of card payment cycles. For small and medium businesses where the timing of incoming funds affects purchasing, payroll, or supplier payment decisions, this is a material operational benefit. The money from a Pay by Bank sale is available sooner and with greater predictability than the equivalent card payment.

Refunds on Pay by Bank transactions are handled differently from card refunds — they are sent directly back to the customer's bank account rather than through a card network. This process varies by provider, so merchants should understand how Fena handles refunds before relying on Pay by Bank for categories with high return rates. There are no chargeback fees to contend with, and no card network timeline to wait on, but the refund mechanism does require understanding upfront.

Building Pay by Bank into a WooCommerce payment stack

The framing that works best for most UK WooCommerce merchants is additive rather than substitutive. Pay by Bank via Fena is an addition to your payment stack, not a replacement for what's already working.

In practice, a well-configured WooCommerce payment setup for a UK merchant typically includes cards for speed, familiarity, and broad international coverage; digital wallets for repeat customers and mobile-first checkout flows; and Pay by Bank for cost efficiency, high-value orders, and customers who prefer bank-authenticated payment.

This mix allows customers to choose the method that fits their expectations and comfort level. It also allows the merchant to benefit from Pay by Bank's cost and chargeback advantages on the proportion of volume where customers self-select it — without sacrificing conversion from customers who prefer a different method.

The right balance depends on the specific store: average order value, customer demographics, category, and the current distribution of payment failures and chargebacks. Fena works with UK WooCommerce merchants to assess whether Pay by Bank makes sense for their specific setup and what proportion of volume it's likely to capture.

Frequently asked questions

Is Pay by Bank the same as WooCommerce's built-in bank transfer?

No — they're fundamentally different. WooCommerce's built-in bank transfer is a manual process where the customer sends a payment themselves and the merchant reconciles it manually. Pay by Bank via Fena automates the entire flow within checkout: the customer authorises payment through their banking app, confirmation comes back to WooCommerce automatically, and the order is marked as paid immediately. There's no manual step and no reconciliation required.

Is Pay by Bank safe for WooCommerce customers?

Yes. Customers authorise payments within their own bank's secure environment using their existing banking credentials. The merchant never sees or stores those credentials — only a payment confirmation is passed back to WooCommerce. Authentication meets the Strong Customer Authentication (SCA) standard required under UK regulation.

Does Pay by Bank work with all UK banks?

Pay by Bank via Fena supports the major UK banks. Coverage is comprehensive for most UK-based customer bases, though merchants should confirm supported banks before rollout if their customers include smaller or specialist banks.

Is Pay by Bank cheaper than card processing for WooCommerce?

In most cases, yes — particularly for higher-value transactions. Card payments carry layered costs including interchange, scheme fees, and acquirer margin, all of which scale with order value. Pay by Bank fees are typically flatter, making the cost saving more significant at higher basket sizes.

Can WooCommerce customers get refunds on Pay by Bank orders?

Yes. Refunds are sent directly back to the customer's bank account. The process differs from card refunds, and the timeline varies by provider. Merchants should understand how Fena handles refunds for their specific product category before relying on Pay by Bank for high-return-rate goods.

Do chargebacks apply to Pay by Bank transactions?

Card chargebacks don't apply to Pay by Bank transactions because there is no card network involved. Disputes can still arise and should be resolved directly between merchant and customer, but the card network dispute process — with its fees, deadlines, and evidence requirements — does not apply.

Should Pay by Bank replace cards in WooCommerce?

No. For most UK merchants, Pay by Bank works best as a complement to cards and wallets, not a replacement. Cards and wallets remain the right choice for fast, low-consideration purchases and international customers. Pay by Bank is strongest for high-value, trust-sensitive, or B2B transactions where its cost and authentication advantages are most relevant.

Is Pay by Bank suitable for WooCommerce subscription products?

Pay by Bank is best suited to one-off payments. For fully automated recurring billing, direct debit or card-on-file infrastructure is more appropriate. Pay by Bank can work well for initial subscription purchases or one-off top-ups, but shouldn't be relied on as the mechanism for automated recurring charges.