Last updated: July 2024

Payment declines cost UK ecommerce merchants revenue, customers, and operational time. Here's a clear breakdown of decline rates by industry, why they happen, and how Pay by Bank via Fena removes the most common causes structurally.

A declined payment isn't just a failed transaction — it's a lost customer

When a card payment is declined at checkout, most merchants record it as a failed transaction and move on. The customer, however, often doesn't try again. They abandon the purchase, look for what they wanted elsewhere, or simply lose the intent to buy in the moment. The revenue impact extends well beyond the individual transaction.

Card payment declines are more common than most merchants realise, and the rates vary significantly by business model and industry. For subscription businesses, recurring billing declines can trigger involuntary churn at scale. For ecommerce merchants, authorisation failures at checkout contribute directly to cart abandonment. For high-value retailers, fraud detection systems designed to protect the business can block entirely legitimate purchases.

Understanding where declines come from — and which ones are addressable — is the starting point for reducing their impact. This guide covers decline rates by industry, the most common causes, and how Pay by Bank via Fena removes the structural vulnerabilities that make card declines a recurring problem.

Quick summary

• Payment decline rates vary significantly by industry, from around 15% for subscription and recurring billing to over 17% for ecommerce and higher still for luxury retail

• The most common causes — outdated card information, suspected fraud, data mismatches, and issuer rules — are structural features of card payments rather than isolated errors

• Declines don't just delay revenue; they trigger cart abandonment, involuntary churn, and customer support overhead that compounds the direct financial cost

• Pay by Bank removes the most common causes of card declines by replacing card credential verification with direct bank authentication

• Offering Pay by Bank via Fena alongside cards gives customers an alternative path to completing payment when card authorisation fails — and reduces the proportion of transactions exposed to card decline risk in the first place

Why payment declines are higher than most merchants expect

The instinct is to assume a declined payment means something went genuinely wrong — fraud attempt, insufficient funds, or a misconfigured gateway. In practice, a significant proportion of declines are false positives: legitimate transactions blocked by fraud detection systems, card credentials that haven't been updated after a card replacement, or issuer rules that flag transactions outside normal spending patterns.

These soft declines — transactions declined not because the customer can't pay but because the card system has introduced a barrier — are structurally embedded in card payment processing. Every party in the card chain has their own risk rules: the issuing bank, the card network, and the acquiring bank all have the ability to decline a transaction independently, and the merchant has limited visibility into which one declined it or why.

The result is a persistent background rate of failed payments that costs revenue, damages customer experience, and creates operational overhead — and most of it can't be fixed by improving the checkout page.

Decline rates by industry

Recurring billing and subscription payments: 15–30%

Recurring card billing carries the highest decline rates of any payment model, for a reason that's structural rather than behavioural. Card details change. Customers replace expired cards, cancel and reissue following fraud, or switch banks — and the card-on-file credentials that were valid at sign-up quietly become invalid over time. The subscription continues in the system; the payment fails silently.

Across subscription businesses, average decline rates run around 15%. In categories with longer average customer lifecycles — where card details have more time to become outdated — rates can exceed 30%. Each failed renewal is a potential churn event: customers who might have continued indefinitely become lapsed subscribers not because they chose to cancel but because a payment mechanism failed without visible intervention.

Smart retry logic and account updater services reduce this, but they add cost and complexity without addressing the underlying cause. The card credential model requires active maintenance to stay current.

Ecommerce: up to 17%

Ecommerce merchants face decline rates up to 17% at the point of card authorisation. Online transactions carry higher fraud risk in the card network's view — no physical card present, no PIN, just credentials that could theoretically have been obtained without the cardholder's involvement. Issuers apply stricter authorisation criteria as a result.

The practical consequence is that a meaningful proportion of legitimate purchases are declined. Customers who were genuinely trying to buy something are stopped at the payment step — and many of them don't retry with a different card or try again later. They leave. The merchant doesn't see a lost sale in the analytics; they see an abandoned cart with an ambiguous status.

For mobile-first merchants, the problem is more acute. Mobile transactions are statistically more likely to be declined than desktop transactions, which combines with the existing mobile checkout friction problem to create compounding abandonment pressure at the payment step.

Luxury and high-value retail

Higher transaction values trigger more aggressive fraud detection across the card system. Issuing banks flag large or unusual purchases for review, and the threshold for what qualifies as "unusual" varies by customer profile and institution — meaning a perfectly legitimate high-value purchase by a genuine customer can be declined because it sits outside their normal spending pattern.

The irony for luxury merchants is that the transactions with the highest revenue impact are the ones most likely to be blocked. A declined £800 transaction costs significantly more than a declined £40 one, and the reputational cost of a high-value customer being turned away at the payment step is disproportionate to the fraud risk the decline was designed to prevent.

Online services and digital products

Online service businesses — software subscriptions, digital content, professional services sold online — face a combination of the recurring billing challenge and the card-not-present risk profile of ecommerce. Where billing is usage-based or variable, the unpredictable transaction amounts add another layer of issuer scrutiny.

For businesses that deliver digital products immediately on payment, a decline that happens after the customer believes the transaction has completed creates a particularly poor experience: the customer thinks they've bought something, the merchant has nothing confirmed, and the resolution requires customer service intervention.

What causes payment authorisation declines

Understanding the cause is necessary for understanding which fixes actually work.

Outdated card information.

The single most common cause of recurring billing declines. Card expiry, card replacement following loss or fraud, and bank account changes all create a gap between the stored credentials and the current valid details. Without an automated update mechanism, these failures accumulate silently.

Insufficient funds or credit.

Genuine inability to complete the transaction at the point of charge. More common in subscription models where billing happens on a fixed schedule regardless of the customer's current account position, and in variable billing where the amount charged differs from what the customer expected.

Fraud detection flags.

Transactions flagged by issuer fraud rules as suspicious. This includes legitimate transactions that match fraud patterns — unusual transaction size, new merchant, unusual geography, rapid sequence of purchases — as well as genuine fraud attempts. The false positive rate in card fraud detection is meaningful and represents a real cost to merchants.

Data mismatches.

Address verification failures, postcode mismatches, and billing detail inconsistencies cause declines independently of whether the customer has sufficient funds or the card is valid. Customers who have recently moved or who enter their billing address differently from how it appears on their card statement are frequently affected.

Issuer rules and velocity limits.

Some issuers impose transaction frequency limits, spending caps, or category restrictions that block otherwise valid transactions. These rules are opaque to merchants — there's no way to predict them or explain them clearly to affected customers.

How Pay by Bank addresses card decline risk structurally

Most approaches to reducing card declines work around the problem: retry logic, account updater services, 3DS optimisation, and intelligent routing are all legitimate tactics. What they share is a dependency on the card credential model that creates declines in the first place.

Pay by Bank via Fena approaches the problem differently. Rather than improving the odds of a card transaction succeeding, it replaces the card transaction entirely for customers who use it — removing the card decline risk for that portion of volume.

No card credentials to become outdated.

Pay by Bank authenticates directly against the customer's live bank account at the moment of payment. There are no stored card details to expire, no replacement cards to update, and no credential drift over time. For subscription merchants, this removes the primary cause of recurring billing declines.

Bank authentication replaces issuer fraud scoring.

Instead of a card issuer applying fraud detection rules to a card-not-present transaction, the customer authenticates within their own banking environment using their existing credentials. The bank approves the payment through the same mechanism it uses for online banking access — it's not a card transaction being assessed for fraud risk, it's a customer confirming a payment they've already chosen to make.

No address verification dependency.

Pay by Bank doesn't involve billing address matching or postcode verification. The payment is authorised by the customer through their bank. Data mismatch declines — which affect a significant proportion of legitimate card transactions — don't exist in the Pay by Bank flow.

Direct bank account confirmation.

The customer sees their actual account balance before authorising the payment, which reduces the soft decline category of "technically sufficient funds but not enough credit headroom" that affects credit card payments in particular.

For UK merchants on Shopify and WooCommerce, Fena's Pay by Bank integration adds this payment option alongside cards at checkout. Customers who choose Pay by Bank complete payment through a direct bank authorisation with no exposure to the card decline mechanisms above. Customers who prefer cards continue to use them. Over time, as more customers adopt Pay by Bank, the proportion of transaction volume exposed to card decline risk decreases.

Practical steps for reducing payment decline impact

Addressing payment declines requires action at both the structural and tactical level.

Offer Pay by Bank alongside cards.

This is the structural change. Customers who encounter a card decline — or who want to avoid the risk of one — have a direct alternative that doesn't carry the same failure modes. For subscription businesses in particular, Pay by Bank removes the outdated card credential problem entirely for recurring billing on bank-authorised payments.

Implement smart retry logic for card payments.

For declined card transactions that might succeed on a second attempt — soft declines from temporary authorisation issues — intelligent retry logic improves recovery rates without requiring customer intervention. The timing and frequency of retries matters; aggressive retry patterns can trigger additional fraud flags.

Use account updater services.

Card network account updater services push updated card credentials to merchants when a customer's card details change. This reduces the outdated card decline rate for recurring billing without requiring customers to actively update their details. Not all card networks or issuers participate, which limits coverage, but it's a meaningful improvement where it works.

Communicate proactively around payment failures.

Customers who receive a clear, prompt explanation of why a payment failed and an easy path to resolution — updating details, choosing a different payment method — recover at higher rates than those who receive a generic failure notification. The customer's experience of a payment failure affects whether they stay or churn.

Review decline reason codes.

Payment gateways provide decline reason codes that, while not always precise, give directional insight into the cause. A pattern of address verification failures suggests a form design issue. A pattern of issuer fraud flags might indicate transaction pattern anomalies worth investigating. Monitoring these codes systematically identifies fixable issues faster than reviewing individual transactions.

Frequently asked questions

What is a normal payment decline rate for UK ecommerce?

Authorisation decline rates for UK ecommerce card payments typically run between 10% and 17%, depending on the merchant's category, average order value, and fraud profile. Higher-value transactions and card-not-present contexts carry higher decline rates than lower-value or in-person payments.

Why do subscription payments have high decline rates?

Subscription billing relies on stored card credentials that were valid at the point of sign-up but become invalid over time as cards expire, are replaced, or are cancelled. Without an automated update mechanism, these outdated credentials generate recurring declines that compound over a subscription base's lifetime. This is the primary driver of what's known as involuntary churn in subscription businesses.

Can Pay by Bank reduce payment decline rates?

Yes, for the transactions processed through it. Pay by Bank authenticates directly against the customer's live bank account, removing the card credential expiry, fraud detection, and data mismatch causes that drive most card declines. For subscription merchants in particular, Pay by Bank removes the outdated card credential problem entirely.

What is the difference between a hard and soft card decline?

A hard decline means the issuing bank has permanently rejected the transaction — the card is reported stolen, the account is closed, or a fraud block has been placed. Retrying won't succeed. A soft decline is a temporary rejection — the issuer's fraud detection flagged the transaction, a temporary limit was hit, or an authorisation timeout occurred. Soft declines can often be resolved through retry logic or customer action.

How does Pay by Bank prevent false positive fraud declines?

Card fraud detection applies issuer-side rules to card-not-present transactions, generating false positives when legitimate purchases match fraud patterns. Pay by Bank replaces this mechanism with direct customer authentication within their banking app — the customer confirms the payment actively, which is treated as a bank-authenticated instruction rather than a card transaction to be scored for fraud risk.

Does offering Pay by Bank alongside cards improve overall approval rates?

Yes, in the sense that it provides a direct alternative for customers whose card payment fails or who prefer not to use a card. Customers who encounter a card decline at checkout and find Pay by Bank available as an option can complete the purchase without leaving the checkout — recovering a sale that would otherwise be lost. Over time, higher Pay by Bank adoption reduces the proportion of volume exposed to card decline risk.