Why do fragile payment systems survive in retail and fuel?

• Organizations stick with fragile payment systems because change feels riskier than inefficiency. Status quo bias makes potential disruption seem more dangerous than lost revenue.
• Fragmented systems come at a cost. Siloed gateways, disconnected pump and store systems, and anonymous transactions limit visibility and commercial performance.
• Internal consensus slows transformation. Multiple stakeholders evaluate risk differently, which often strengthens the case for staying still.
• The real risk is inaction. Without orchestration and centralized control, technical debt grows, revenue opportunities remain hidden, and resilience weakens over time.

Don't have time to read more now? Sign up to our newsletter to get the latest insights directly in your inbox. 

...Across brands and across maturity levels, the same issues surface again and again.

Retailers continue to operate with fragmented stacks, fuel operators run disconnected pump and store systems, and loyalty programs struggle to link experiences consistently.

Multiple gateways accumulate across regions, while obvious opportunities to improve authorization performance often remain untouched. The inefficiencies are widely understood. 

And it’s clear, no one is pushing this over the line.

The systems keep running - purely because they’re embedded into day-to-day operations, and changing them feels too risky. So, if the inefficiencies are obvious, and the architectural tools to modernize safely already exist, why does meaningful change still stall?

Over thirty years ago, economists William Samuelson and Richard Zeckhauser described what they called “status quo bias” - the tendency to stick with the existing setup even when better options exist. Daniel Kahneman and Amos Tversky later built on this idea with Prospect Theory: the idea that losses hit roughly twice as hard as equivalent gains.

In enterprise environments that bias tends to run even stronger, and nowhere is it more visible than in retail and fuel payments - where the potential downside of change feels immediate. If a new architecture fails, transactions stop; if a migration introduces instability, forecourts grind to a halt; and mishandled compliance can create regulatory exposure. Every day, teams feel the impact of these risks on their work.

So even when the benefits are clear - a 1-2% authorization uplift, lower routing costs, improved loyalty attachment, reduced technical debt - the internal conversation quickly comes back to one question: what if it breaks?

That question carries more weight than any incremental gain, and so organizations often stay still. But choosing not to change is still a decision - and it carries consequences.

The cost of inaction shows up in three places: fragmented infrastructure, lost commercial visibility, and technical debt that continuously drains resources over time.

Let’s explore them in more detail...

Fragmentation by design

Modern retail and fuel environments are structurally complex. For example, a large multi-country retailer might run three to seven different gateway integrations across regions - each with its own certification cycles, reconciliation overhead, and change friction. Pump controllers often sit in one ecosystem, store POS in another, loyalty platforms in a third, and data lakes somewhere else entirely. These environments function, but they function in silos.

Fragility creeps in gradually - a local acquirer here, a workaround for a new regulation there. Over time, tactical decisions pile up into a layered stack that keeps running, keeps processing payments and settling money, so that from the outside nothing appears broken. But internally, technical debt compounds.

The revenue hidden in anonymity

Industry estimates suggest that between 50-60% of fuel transactions at the pump remain anonymous - no customer identification, no loyalty linkage. And that’s a missed opportunity.

We know from Bain & Company research that using customer data and personalisation effectively can generate revenue uplifts of 5-15% and improve marketing efficiency by 10-30%, yet in many forecourts the underlying architecture makes capturing that uplift nearly impossible.

Technical debt as operating drag

McKinsey research suggests that in large enterprises, technical debt can consume between 20 to 40% of IT budgets. That cost rarely appears as a single line item, instead showing up as slower deployments, longer certification cycles, higher integration costs, and the inability to roll out innovation consistently across markets. Eventually, the inefficiencies stop feeling temporary and become just another part of doing business.

The cost of change is obvious: project budgets, external support, internal resources, certification hurdles, and migration planning. The cost of staying the same is less obvious, but no less real, slowly spreading through processes and routines until it shapes how teams work and make decisions.

The reality is that much of this complexity is the absence of a unifying orchestration layer that could manage it centrally.

Even when leadership is personally convinced that change is the right call, they're rarely making the decision alone. Gartner puts the average enterprise buying group at six to ten stakeholders, but in enterprise retail and fuel transformations, that number can easily exceed fifteen, which comes with another set of challenges, as too many cooks can spoil the broth (or so to speak). 

Every one of those functions has a rational reason to be hesitant - the security argument in particular is hard to counter on its own terms. A data breach carries costs, in reputational and financial terms, that dwarf the efficiency gains on the table. IBM's Cost of a Data Breach Report consistently puts average global breach costs in the millions, higher still in regulated sectors - effectively making securities’ case year after year.

Each function is doing its job - but collectively that becomes the real bottleneck. McKinsey has reported that around 70% of digital transformation initiatives fail to meet their objectives, typically because of integration complexity and organizational misalignment. That’s exactly what plays out in payment modernization.

The misclassification that makes everything worse

Part of why this keeps happening is that in many organizations the payment stack is still treated as background infrastructure: old plumbing, rather than a growth enabler. As long as transactions are clear and funds are reconciled, the system is considered to be a success - job done. But in fuel and convenience retail, the payment interaction carries far more weight. That’s the point where:

1. Identity is established
2. Loyalty is recognized
3. Subscriptions are activated
4. Offers are applied

And perhaps, most importantly:

5. Margin is either protected or lost

When more than half of pump transactions remain anonymous, businesses lose visibility into visit patterns, basket behavior, and long-term customer value. That’s a major blind spot, one that rarely stems from marketing strategy...

The more likely culprit is a structural limitation in the payment architecture.

Until payments are seen as a commercial lever (opposed to just a cost centre), the case for transformation will struggle to reach the right level. That’s why leadership needs to frame change around resilience and operational control.

When acceptance is orchestrated across acquirers and pump and store environments are managed under a single control layer, risk reduces rather than increases, and transformation stops feeling like a gamble.

The invisible incentives protecting legacy systems

There’s also a political dimension that rarely gets acknowledged openly. Legacy vendors have champions, past integration choices have owners, and contracts create dependencies. Replacing architecture can threaten established influence - and people feel that, even when they don't say it. That’s why fragile systems survive.

BCG research on adaptive organizations shows that businesses capable of evolving continuously outperform their peers over the long run. Staying "stable" isn’t safe - it simply transfers risk to the business and its customers.

The leaders who move first won't necessarily be the ones who were most convinced the technology was ready. They'll be the ones who got honest about what inaction was actually costing them - and built a case for change that was as rigorous and specific as the risk analysis sitting on the other side of the table.

Zero risk isn't available. The choice is between managing change deliberately or absorbing its cost gradually, invisibly, and without any of the upside.

Payment architecture in retail and fuel will change - the economics and market pressures guarantee it. The only variable is whether that change happens on your terms or in response to someone else's.

Curious about what inaction is costing your payment operation? Speak to our team about modelling authorization uplift, routing efficiency, and loyalty visibility across your estate.