Last updated: July 2024 

UK ecommerce merchants face rising chargebacks during economic downturns. Learn how Pay-by-Bank via Fena removes card disputes, reduces fraud exposure, and cuts payment costs for Shopify and WooCommerce businesses.

The payments problem most merchants don't see coming

Economic pressure doesn't just change what consumers buy — it changes how they behave when something goes wrong. For UK ecommerce merchants, that shift shows up in payment disputes, friendly fraud, and the slow creep of chargeback costs eating into already-tight margins.

Card payments have always carried this structural risk. Customers can reverse a transaction after the fact, long after goods have shipped or digital products have been delivered. During stable economic periods, many merchants absorb this as background noise. During a downturn, it becomes a real operational and financial problem.

Pay-by-Bank, available through Fena for Shopify and WooCommerce merchants, changes this at the structural level — not by patching fraud detection, but by removing the card-based dispute mechanism entirely.

This guide explains how chargebacks work, why they scale with economic stress, what they actually cost, and where Pay-by-Bank via Fena genuinely changes the equation.

Quick summary

• Chargebacks rise during economic downturns because consumer financial pressure leads to more disputes, including legitimate claims and deliberate friendly fraud

• Card payments create this vulnerability by design — the dispute mechanism is built into card network rules

• The true cost of a chargeback isn't just the transaction value; it includes fees, lost goods, staff time, and long-term processing penalties

• Pay-by-Bank via Fena eliminates card chargebacks entirely by bypassing card networks and using bank-authenticated payments

• For UK merchants, Pay-by-Bank is typically one of the cheapest payment methods available, removing interchange, scheme fees, and dispute-related costs in one move

• Not all risk disappears — refunds, customer support, and certain fraud types still require handling — but the structural chargeback problem is removed

What is Pay-by-Bank?

Pay-by-Bank is a payment method that lets customers pay directly from their bank account using UK payment rails, without cards or card network intermediaries. Payments are authenticated within the customer's own banking environment and settled as direct account-to-account transfers.

For merchants on Shopify and WooCommerce, Fena makes Pay-by-Bank available as a checkout option. Customers authorise the payment through their bank — using biometrics, PIN, or their banking app — and the funds move directly, without card credentials entering the flow.

This removes the entire card infrastructure layer: no PAN storage, no interchange, no scheme processing, and critically, no card dispute mechanism.

Why chargebacks increase during economic downturns

When consumers are under financial pressure, their behaviour around payments changes. Disputes that might previously have been resolved through a quick call to customer support instead get escalated to the bank. "Item not received" claims increase. "Unrecognised transaction" disputes spike, even on legitimate purchases. Some consumers use chargebacks deliberately as a refund route, a pattern known as friendly fraud.

This isn't speculation — it's a documented pattern in UK ecommerce. For merchants processing between £250k and £10M annually, the operational and financial impact is direct: more disputes, more fees, more staff time, and less predictable cash flow.

For Shopify and WooCommerce merchants specifically, higher dispute volumes also carry a secondary risk: if chargeback ratios cross card network thresholds, merchants face monitoring programmes, higher processing costs, or in serious cases, account restrictions.

Why card payments create chargeback exposure

The chargeback mechanism isn't a flaw in card payments — it's a feature, designed to protect consumers. But for merchants, it creates a specific structural vulnerability. The chargeback mechanism isn't a flaw in card payments — it's a feature, designed to protect consumers. But for merchants, it creates a specific structural vulnerability.

Post-payment reversibility.

Customers can dispute a completed transaction through their issuing bank — meaning revenue can be clawed back weeks or months after a sale has settled.

Dispute initiation.

The issuing bank opens a case via card network rules, and merchants must respond within strict deadlines or lose automatically.

Burden of proof.

Merchants are required to demonstrate the transaction was legitimate. This means high operational effort with no guaranteed outcome — even for sales that were entirely genuine.

Friendly fraud.

Standard dispute categories like "item not received" or "unrecognised transaction" are straightforward to invoke, making dishonest claims structurally difficult to counter.

Settlement finality.

Card payments are not truly final even after settlement, which creates ongoing cash flow uncertainty on every transaction.

Scheme thresholds.

Card networks monitor dispute ratios and impose penalties, rolling reserves, or account restrictions if merchants exceed their thresholds.

The process typically runs like this: a customer disputes a transaction with their issuing bank; the bank initiates a chargeback; funds are provisionally removed from the merchant's account; the merchant submits evidence; the issuer decides. The merchant loses automatically if they miss deadlines or lack sufficient documentation.

For high-volume UK ecommerce merchants, this creates ongoing operational overhead even when win rates are reasonable.

The true cost of a chargeback

Most merchants underestimate what a chargeback actually costs. The transaction value is just the starting point.

Lost transaction revenue.

The full sale amount is reversed — complete revenue loss on that order, regardless of whether goods were delivered.

Lost goods or services.

Products already shipped or digital items already delivered cannot be recovered. The merchant absorbs both the reversal and the fulfilment cost.

Chargeback fee.

Acquirers apply a fee per dispute — typically £10–£25 per case in the UK — regardless of whether the merchant wins or loses.

Operational handling.

Gathering evidence, drafting responses, and managing the dispute workflow takes staff time — often 30 to 60 minutes minimum per case, at scale.

Higher processing costs over time.

Rising dispute ratios affect pricing terms. Merchants with elevated chargeback rates face higher fees, rolling reserves, or restricted accounts from acquirers.

Scheme monitoring penalties.

Entering a card network monitoring programme triggers additional fees and can ultimately threaten account viability if ratios aren't brought down.

A worked example:

a UK Shopify merchant processing £2M annually at approximately 2.5% in card fees pays around £50,000 in processing costs. If chargebacks and fraud account for an additional 1% of GMV, that's a further £20,000 in losses. Shifting 30% of volume to Pay-by-Bank via Fena meaningfully reduces both the fee base and the dispute exposure — often saving several thousand pounds annually without any change to the checkout experience.

How merchants typically try to reduce chargebacks — and where those approaches fall short

Most guidance on chargeback reduction focuses on tactics: better delivery tracking, clearer product descriptions, faster customer support response times, fraud scoring tools. These all help at the margin.

But none of them change the underlying structure. Card payments remain reversible. Customers retain the right to dispute. The dispute workflow still runs through card networks with all its associated costs and timelines.

For UK ecommerce merchants who want to reduce chargebacks structurally — rather than just manage them better — the most effective approach is to shift volume to a payment method that doesn't support chargebacks in the first place.

Does Pay-by-Bank eliminate chargebacks?

Yes, for transactions processed through Pay-by-Bank.

Because payments are authorised directly through the customer's bank and do not pass through card networks, card scheme dispute mechanisms simply don't apply. There are no chargebacks to defend, no dispute fees to pay, and no scheme thresholds to worry about on Pay-by-Bank volume.

For UK merchants using Fena, this means:

• No chargeback fees on Pay-by-Bank transactions

• No dispute response workflows

• No card network monitoring exposure for that payment volume

• Near-final settlement — funds move and the payment is complete

This is a structural removal, not a reduction. The dispute mechanism doesn't exist in the Pay-by-Bank flow to begin with.

Is Pay-by-Bank cheaper than card payments?

For most UK ecommerce merchants, yes — significantly.

Card payments carry interchange fees (typically 0.2–0.3% for consumer debit, higher for credit and commercial cards), scheme fees from Visa or Mastercard, and acquirer margins on top. These stack up across every transaction.

Pay-by-Bank via Fena bypasses all of these layers. Payments settle directly between bank accounts using UK payment infrastructure, removing the card network cost entirely. This is often described as payment mix optimisation — actively shifting volume to lower-cost rails to improve margin without reducing conversion.

For merchants with high card processing costs or elevated chargeback rates, the combined saving on fees and dispute costs can be substantial.

What actually changes when you add Pay-by-Bank?

Payment initiation.

With cards, the customer enters their card number, expiry date, and CVV. With Pay-by-Bank via Fena, they're redirected to their own banking app or environment — no card credentials involved.

Authentication.

Cards use credentials plus optional 3D Secure. Pay-by-Bank uses bank login, biometrics, or Strong Customer Authentication (SCA) natively within the banking app.

Authorisation.

Cards require card network and issuer approval. Pay-by-Bank is approved directly by the customer's own bank, without any card network involvement.

Settlement.

Card payments clear through card network cycles. Pay-by-Bank settles as a direct account-to-account transfer.

Finality.

Card payments remain reversible via chargebacks. Pay-by-Bank transactions are near-final — there is no card scheme reversal mechanism to invoke.

Dispute mechanism.

Card disputes run through card network rules and are handled by issuers. Pay-by-Bank has no equivalent — disputes are handled directly between merchant and customer, as refunds.

Fee structure.

Cards carry interchange fees, scheme fees, and acquirer margin. Pay-by-Bank via Fena removes all of these layers, resulting in meaningfully lower processing costs.

Fraud exposure.

Card payments are vulnerable to stolen card details and card testing attacks. Pay-by-Bank reduces this risk significantly because bank authentication is required — stolen card numbers are irrelevant.

Operational workload.

Card payments create ongoing overhead through dispute management and evidence handling. Pay-by-Bank shifts the focus to direct customer support and refunds, which are simpler and cheaper to manage.

The shift is structural. Merchants aren't just getting a cheaper version of a card payment — they're using a fundamentally different payment architecture.

What disappears — and what remains

Pay-by-Bank removes specific risks and costs. It doesn't remove all merchant responsibility.

What Pay-by-Bank via Fena removes:

• Card chargebacks and the associated dispute workflows

• Interchange fees, scheme fees, and related card processing costs

• Card network monitoring thresholds on Pay-by-Bank volume

• Exposure to stolen card credentials and card testing attacks

What remains the merchant's responsibility:

• Processing legitimate refunds when customers return goods or are unsatisfied

• Providing customer support and resolving disputes directly

• Managing social engineering and authorised push payment fraud (where customers are deceived into making a payment themselves)

• Any subscription or billing models that currently depend on card-on-file infrastructure

The risk profile changes — it doesn't disappear. But for many UK ecommerce merchants, removing the chargeback layer is the most material improvement available.

How Pay-by-Bank affects fraud exposure

Bank-authenticated payments reduce one specific and common fraud vector: unauthorised transactions using stolen card details. Because Pay-by-Bank requires the customer to authenticate directly within their banking app — using biometrics or their banking credentials — stolen card numbers are simply not relevant to the transaction. There are no card credentials to steal.

This also removes exposure to card testing attacks, where fraudsters use small transactions to validate stolen card numbers in bulk.

What Pay-by-Bank does not eliminate is authorised fraud — cases where a genuine account holder is socially engineered into making a payment. This type of fraud, sometimes called APP fraud (Authorised Push Payment), operates at the bank account level and requires different controls.

For UK merchants, the net effect is a meaningful reduction in fraud-related losses on Pay-by-Bank volume, with a different and generally more manageable residual risk profile.

When Pay-by-Bank is particularly effective for UK merchants

Pay-by-Bank via Fena is most impactful for merchants where the structural weaknesses of card payments are most exposed:

• High chargeback rates

  — if disputes are already a recurring cost and operational burden, removing the mechanism is more valuable than optimising around it

• Digital goods and instant-delivery products

  — where "item not received" claims are difficult to defend and goods cannot be recovered

• High-value transactions

  — where the absolute cost of a chargeback (fee plus lost goods) is most significant

• Categories with elevated friendly fraud risk

  — where customers have learned that chargebacks are an accessible refund route

• Merchants with tight margins

  — where card processing fees represent a meaningful percentage of GMV and every basis point matters

When Pay-by-Bank may not be the primary solution

Pay-by-Bank works best as part of a payment mix, not necessarily as a wholesale card replacement — particularly where:

• Subscription models rely on card-on-file billing

  — recurring payments currently depend on stored card credentials, which require a different setup with bank payment methods

• Customer familiarity is a concern

  — some customers prefer cards and may not yet be comfortable with bank redirection flows, though this is changing rapidly as Open Banking adoption grows in the UK

• Refund UX differs

  — refunds on bank payments work differently from card refunds and require some operational adjustment

These are manageable trade-offs rather than hard blockers for most merchants, and the infrastructure around Pay-by-Bank continues to mature.

How to add Pay-by-Bank via Fena

For Shopify and WooCommerce merchants, Fena provides a straightforward integration that adds Pay-by-Bank as a checkout payment option. The process typically involves:

1. Installing the Fena payment integration on your store

2. Configuring Pay-by-Bank alongside existing payment methods

3. Customers see Pay-by-Bank at checkout, select it, and are directed to their banking environment

4. The bank authenticates the payment and confirms it directly to your store

5. Settlement completes as an account-to-account transfer

No card credentials are collected, no card network is involved, and the chargeback mechanism does not apply.

Frequently asked questions

How can UK ecommerce merchants reduce chargebacks?

UK merchants can reduce chargebacks through better delivery tracking, clearer communication, and robust fraud screening. For a structural reduction, switching volume to Pay-by-Bank via Fena removes the card-based dispute mechanism entirely, which is the most effective single change available.

Why do card payments lead to chargebacks?

Card network rules give consumers the right to dispute a transaction through their issuing bank after payment has been made. This post-transaction reversal mechanism is built into how card schemes operate. It protects consumers but exposes merchants to disputes, fees, and revenue loss.

Does Pay-by-Bank completely eliminate chargebacks?

Pay-by-Bank eliminates card chargebacks on transactions processed through bank payment rails. Since card networks are not involved, their dispute mechanism does not apply. Merchants still manage refunds and direct customer disputes, but these operate differently from formal card chargebacks.

Is Pay-by-Bank cheaper than card payments in the UK?

Yes, in most cases. Pay-by-Bank avoids interchange fees, card scheme fees, and the processing costs associated with card network infrastructure. For UK merchants, this typically makes it one of the lowest-cost payment methods available.

Is Pay-by-Bank secure?

Pay-by-Bank relies on bank-level authentication — the same security infrastructure customers use for their own online banking. Strong Customer Authentication (SCA) is inherent to the flow. This makes unauthorised payments significantly harder to execute than card fraud using stolen credentials.

What is the difference between card fraud and a chargeback?

Card fraud refers to unauthorised or deceptive transactions — payments made without the genuine account holder's knowledge. A chargeback is the formal dispute process within card network rules, which can be initiated for fraud but also for legitimate disputes or, in some cases, deliberately as a refund mechanism. Not all chargebacks involve fraud, and not all fraud results in a chargeback.

Is Pay-by-Bank worth it for Shopify or WooCommerce merchants?

For merchants with meaningful card processing costs, recurring chargebacks, or high fraud exposure, Pay-by-Bank via Fena typically delivers measurable savings and operational simplification. It is most effective as part of a payment mix strategy, allowing merchants to direct appropriate transaction types to the most efficient payment rail.

The bottom line

Chargebacks are a structural feature of card payments, not a fixable edge case. During economic downturns, that structure becomes more expensive as dispute volumes rise and margins compress.

Pay-by-Bank via Fena doesn't offer a better way to manage chargebacks — it removes them. By routing payments through bank authentication and UK payment rails rather than card networks, the dispute mechanism that creates chargebacks simply doesn't exist for those transactions.

For UK Shopify and WooCommerce merchants, adding Pay-by-Bank is one of the clearest levers available for reducing payment costs, removing dispute exposure, and making revenue more predictable — without requiring customers to change how they think about paying.