Customers abandon payments for several reasons: the final price is higher than expected, checkout feels difficult or untrustworthy, their preferred payment method is unavailable, or a card decline, security check, or technical error prevents completion. These causes need different solutions.
A customer who changes their mind is not the same as one who tries to pay but cannot.
For retailers and finance teams, the priority is to identify where an intended purchase breaks down, how often it happens, and which problems the business can reasonably address.
What is payment abandonment, and is it the same as cart abandonment?
Payment abandonment occurs when a customer reaches the payment stage but does not complete a purchase. Cart abandonment is broader: someone puts items in a basket but leaves at any point before buying. A failed payment is an attempted transaction that is not approved or completed; it may lead to abandonment, but the customer could also try again successfully.
The distinction matters when interpreting industry figures.
Baymard Institute’s October 2026 analysis reports a 70.22% average cart-abandonment rate across 50 published studies from 2006–2025. That is not a payment-stage abandonment rate, nor a prediction for an individual UK business. Baymard also notes that some shoppers were only browsing and never intended to purchase immediately.
Why do customers stop before completing payment?
1. The total changes at the last moment
Delivery charges, taxes or other fees revealed near the payment button can make customers reconsider an order. In Baymard’s US shopper research, among abandonment reasons reported after excluding those who were browsing, 40% cited extra costs being too high. This finding concerns cart and checkout abandonment, not payment attempts alone.
A retailer cannot always remove delivery charges. It can, however, show an accurate total early, explain any variable costs and make the final amount easy to check before authorisation. For finance directors, this is as much a pricing-transparency issue as a checkout-design issue.
2. Customers are unsure whether the payment page is safe
People may hesitate when a familiar retail website suddenly sends them to an unfamiliar payment page, the amount is unclear or the page looks inconsistent with the brand. Baymard’s research found that 19% of its relevant US respondents cited a lack of trust in the site with card information.
A consistent checkout experience, recognisable business details, clear order information and an explanation of how payment is handled can help customers make an informed decision. Security claims must also be accurate: displaying a badge does not establish compliance or replace proper payment security.
3. Paying requires unnecessary effort
Forced account creation, repeated address fields, confusing error messages and awkward mobile forms create work at the exact point a customer wants to finish. Even a motivated buyer may leave if correcting one detail means starting again.
Review whether each field is essential, offer guest checkout where practical and preserve information when customers need to correct mistakes. Test the whole journey on actual phones, including what happens after an interrupted payment. A shorter page alone is not enough if the steps remain unclear.
4. The available payment methods do not suit the customer
A shopper may have their phone but not their card details, or may prefer a digital wallet rather than entering card information manually. Offering more methods is not automatically better: the useful choice depends on customers, devices, markets and commercial costs.
For a UK retailer, a sensible review might compare card payments with supported options such as Apple Pay and Google Pay, then look at actual usage and completion by method. NetCollex supports
online card payments and
digital wallets, subject to the relevant payment setup and compatible devices.
5. The bank declines the payment or authentication is not completed
Not every unfinished payment is a usability problem. A card issuer may decline a transaction because of insufficient funds, restrictions or suspected fraud.
A payment can also require additional identity verification. In the UK,
Strong Customer Authentication (SCA) is designed to protect electronic payments, with exemptions applying in certain circumstances. A common card-authentication technology is 3D Secure.
Businesses should not try to bypass legitimate security checks. Instead, they should check where customers fail to complete authentication, make instructions understandable and provide appropriate alternatives after a genuine decline.
6. An error leaves the customer uncertain about the result
A slow response, expired session or broken return from a bank’s authentication screen can stop an otherwise valid purchase. The worst outcome is an unclear status: a customer sees an error but cannot tell whether they have been charged. They may abandon, or retry and risk a duplicate attempt.
Test payment journeys and failure messages, particularly after redirects and on weaker mobile connections. If a result is uncertain, the business should verify the transaction status before asking the customer to pay again-clear confirmation and a route to support matter as much as the payment form itself.
How can businesses identify where payments are being lost?
Begin with a shared view across ecommerce, payments and finance.
Google Analytics 4 recommends events including begin_checkout, add_payment_info and purchase. If implemented correctly, these can help locate friction. They do not, by themselves, explain why a bank declined a transaction.
Compare website events with payment-provider records showing attempts, authorisations, declines and authentication outcomes.
Reconcile confirmed purchases with order and settlement records so a delayed confirmation, repeat attempt, or tracking error isn’t automatically counted as lost business.
Useful questions include: Does the problem affect one device more than another? Does it occur with a particular payment method or at a certain point in authentication? Did it begin after a website change? Where decline reasons are available, are they increasing? Review patterns before changing the checkout.
Which payment metrics should a CFO monitor?
Payment-stage completion rate can be defined as confirmed paid orders divided by eligible checkout sessions that reached the payment stage, multiplied by 100. Define the session and success criteria consistently.
Card authorisation rate measures approved authorisation attempts against total authorisation attempts; it answers a different question. Authentication completion, payment errors and repeat attempts can add useful context.
For example, hypothetically, if 1,000 eligible sessions reach payment and 820 produce confirmed paid orders, the completion rate is 82%. The remaining 180 sessions are not necessarily 180 recoverable sales. Some customers may change their minds, return later or successfully pay through another session.
What should businesses fix first?
Prioritise evidence of preventable problems over headline abandonment averages. If customers disappear before submitting payment details, examine unexpected charges, trust signals, checkout steps and payment choice. If attempts reach the provider but fail, investigate issuer declines, authentication journeys and technical errors with the relevant provider.
Test one meaningful change at a time where possible. Finance teams should assess confirmed incremental sales alongside gross margin, processing costs, fraud exposure, refunds and operational effort. An apparent improvement in checkout completion is valuable only when the underlying orders and payments are genuine.
For businesses that also take orders through sales conversations or invoices,
payment links can offer a separate way for a customer to complete an agreed payment without returning to the original website checkout. This is not a fix for every abandoned basket, and its suitability depends on the sales process.
Make the final payment step easier to understand
Reducing payment abandonment starts with knowing whether customers are hesitating, being declined or encountering a broken journey.
NetCollex brings online payments, supported digital wallets and payment links together, with transaction reporting that can help teams review authorisations and declines.
