The Green Sheet Online Edition
August 10, 2026 • 26:08:01
Why a generic checkout is becoming a commercial risk
The internet can remember the shoes you viewed three weeks ago, the city you usually fly from, and the exact point where you abandoned a purchase. Yet the moment the payment process begins, many checkouts develop a sudden case of amnesia.
A returning customer who usually pays by mobile wallet, a new customer making a high-value purchase and a shopper in a market where bank payments are common may all reach the same payment page. They see the same card fields, payment methods and prompts, regardless of which checkout flow would work best for them.
A fixed, complex or glitchy checkout makes customers work harder. They have to hunt for the payment method they want, take extra steps, or give up and go elsewhere. It’s a challenge that all merchants have to tackle. But even a small checkout change can become a bigger development job, especially when a new payment method or provider has to be connected.
The average customer does not exist
Many checkout decisions still revolve around a broad picture of the average customer: a person using a familiar card, in a core market, on a standard device, making a transaction within a typical value range. Real customers are far less predictable.
Payment preferences can change with the purchase, the device and the market. Someone booking a costly trip may want reassurance and clear confirmation, while a customer adding money to a gaming or trading account is likely to prioritize speed. On mobile, Apple Pay or Google Pay may be the obvious choice; elsewhere, a local bank payment may come first.
Getting those choices wrong can cost the sale. Among shoppers who abandoned an order, checkout research puts too few payment options behind 10 percent of exits, while 8 percent cited a declined card (see baymard.com/lists/cart-abandonment-rate).
The usual response is to add another payment option. Then another. Before long, the checkout has become a menu, and the customer is left to sort through it.
That misses the point. Someone shopping on an iPhone expects Apple Pay to be easy to find. In markets where bank payments are widely used, leading with a card form makes little sense. If a payment provider starts timing out or approving fewer transactions in a market, payments should be sent through another route before customers see failures.
Use the information already there
Merchants already have useful signals to work with, including device, location, currency, transaction value and customer history. That data can help decide which methods appear first and how the payment is handled once it leaves the page. It could mean bringing Google Pay higher up on Android, showing a bank payment option where it suits the customer and market, or choosing a provider with a better record in that region.
Merchant risk controls need the same care. A regular customer making their usual purchase presents a different profile from a new account attempting a much larger payment. Applying the same process to both can slow down a trusted customer or expose the merchant to more risk than intended.
Payment personalization lives in these choices: what the customer sees, how risk rules shape the journey and where the transaction goes once they press pay.
After the customer clicks
The payment page is only one part of what happens. Once they hit the PAY button, the transaction still has to get through authentication, fraud checks and at least one payment provider. If a provider times out or approves fewer payments in that market, good checkout design cannot save the sale.
Routing has a direct effect on whether the payment completes. Geography, currency, cost and potential approval rates can all help decide which provider receives it. If one route slows down or fails, another should take over automatically and invisibly. Sending the customer back to try again leaves them dealing with a problem the merchant should handle behind the scenes.
Using one payment provider can make the admin easier: one contract, one set of reports and fewer systems to manage. The weakness shows up during an outage, a rise in fees or a run of poor approval rates. The checkout itself can create lock-in too. If it comes from the same company handling the payments, adding another provider or method may depend on that company’s technology and roadmap.
With an independent payment orchestration layer, the checkout sits separately from any single processor, allowing methods, providers and routing rules to change behind the customer journey.
Make the data useful
Payment teams can already see approval rates, decline reasons, provider performance and the methods customers choose. However, seeing the pattern is only useful if they can act on the information it has to offer.
If wallets perform better on mobile, move them up the page. If one provider is rejecting more payments in a market, send less traffic there. A new method can start with a small group of customers and reach more people if it improves completion rates.
Too often, the insight ends up on a dashboard. The team spots the problem, raises a ticket and waits for a development slot. By the time the change goes live, months may have passed.
Checkouts should be easier to adjust. Small tests can show which changes improve conversion and approval rates, or reduce costs, without a redesign. Payment, product, fraud and commercial teams can see the result and decide what to do next.
This brings payment leaders closer to decisions about new markets and customer strategy. Transaction data can show how people prefer to pay, where provider coverage falls short and whether a new method is worth the investment. It should shape commercial plans, rather than sit in a monthly report.
Keep checkout moving
Payment habits constantly change. Customers may start using a different wallet, approval rates can fall in defined spots, or a new product launch might attract higher transaction values and more first-time customers than normal. However, the checkout often still looks exactly the same, even as its performance slips.
The checkout has to keep up. Payment teams need to be able to reorder methods, change the fraud checks applied and flexibly route transactions without opening a development project. Customers simply want their preferred way to pay to be available and the transaction to work.
Leave the checkout untouched for too long and it starts costing sales. 
Jacob Spencer is the chief revenue officer at BR-DGE, an innovation enabler for the payments ecosystem. The company provides a technology anchor-point that empowers merchants, financial institutions, payment providers and platforms to increase revenue, optimize costs and manage payments performance. For more information on BR-DGE, see https://br-dge.to. Contact Jacob via LinkedIn at linkedin.com/in/jacobkspencer.
Notice to readers: These are archived articles. Contact information, links and other details may be out of date. We regret any inconvenience.
