Payments modernisation has become the defining boardroom debate in banking, and according to Tieto, the banks that move in months rather than years will be the ones that thrive in the real-time era.
In a new industry insight, Tieto argues that legacy payment infrastructure has been the biggest headache for bank CIOs and CTOs since the turn of the century. The market is now crowded with vendors promising modernisation without genuinely modern platforms, while traditional procurement processes often fail to surface trusted partners.
European banks, Tieto notes, are moving well beyond instant payments. Soon, bulk, high-value, cross-border and even direct debit transactions will all be real-time. For mid-to-large banks, the question is no longer whether change is necessary, but whether they can move quickly enough to avoid turning a straightforward technology transformation into a costly, long-haul operational burden.
Regulatory mandates around instant payments and ISO 20022 forced many banks into workarounds on legacy systems simply to hit compliance deadlines. Tieto likens this to an eighty-year-old with a chronic heart condition surviving on a pacemaker: functional for now, but far from a permanent fix.
The firm warns that some of these systems date back to an era of cheques and multi-day file-based processing, wholly unsuited to real-time demands. As volumes climb, they will either fail or become prohibitively expensive to run, with mainframe ecosystem operating costs recently tripling. A legacy platform, Tieto suggests, resembles a vintage car: familiar and valued, but ever more expensive to keep on the road. Beneath the surface, ageing teams, continuity risk and buried resilience issues compound the problem.
Hesitation is understandable. Modernising payments can feel like overhauling an aircraft engine mid-flight, and the fear is operational and emotional as much as technical. As Tieto puts it, “The risk of doing something on time is easier to manage than the risk of not doing anything.” Yet delay simply means CIOs keeping the lights on while accumulating enormous technical and operational debt.
Tieto’s answer is a step-wise, agile operating model tailored to each bank’s complexity, systems landscape and ecosystem, rather than big-bang migrations that drag on without delivering value. The firm points to a client operating legacy systems across three European countries: selected as vendor in May, contract signed in July, live in September. SEPA Credit Transfer Instant Payments were delivered in roughly three months, with cross-border capability following about six months later.
The bottom line, Tieto concludes, is that change should mean progress fast enough to matter, controlled enough to trust, and tailored enough to fit. The future of payments will not wait for long-haul transformation programmes.
For more, read the full story here.
Copyright © 2026 FinTech Global
Facts Only
* Payments modernization is a defining boardroom debate in banking.
* Tieto argues that banks moving quickly will thrive in the real-time era.
* Legacy payment infrastructure has been a headache for bank CIOs and CTOs since the turn of the century.
* The market contains vendors promising modernization without genuinely modern platforms.
* Regulatory mandates like instant payments and ISO 20022 forced workarounds on legacy systems to meet compliance deadlines.
* Some systems date back to cheque and multi-day file-based processing, which are unsuited to real-time demands.
* Mainframe ecosystem operating costs have recently tripled.
* A legacy platform is described as familiar but increasingly expensive to maintain.
* Hesitation in modernization can lead to accumulating technical and operational debt.
* Tieto proposes a step-wise, agile operating model instead of big-bang migrations.
* A client moved from vendor selection to live implementation for SEPA Credit Transfer Instant Payments across three countries in September.
Executive Summary
Full Take
The narrative frames the transition away from legacy payment systems not just as a technical upgrade but as a necessary act of managing existential risk and cognitive friction. The core tension lies between the immediate operational fears—the fear of disruption during change—and the long-term systemic failure caused by inertia. The concept that delay is equivalent to accumulating debt mirrors psychological principles where inaction compounds negative outcomes. This dynamic suggests that reluctance often stems from uncertainty about control, as articulated by the quote regarding managing risk: the risk of acting swiftly is manageable, whereas the risk of stagnation results in unmanageable burdens.
The pattern observed here involves reframing systemic technical obsolescence as an emotional and operational burden to drive immediate agency. The source employs a classic framing where inertia (delay) is positioned as the primary, quantifiable cost, pushing the reader toward an agile solution rather than letting fear paralysis dictate the decision. This functions by linking complex, abstract technology shifts directly to concrete financial and risk management concerns for executive leadership.
What assumptions are unstated? The narrative assumes that complexity management is a solvable engineering problem, overlooking the often-political and organizational inertia involved in shifting entrenched operational cultures within large banking institutions. Who benefits from emphasizing speed? Those who can successfully push through centralized decision-making without sufficient decentralized operational authority. The implications suggest that true transformation requires not just agile technology but also an institutional commitment to valuing incremental progress over monolithic, high-risk transformations.
Bridge questions: How does the inherent fear of change interact with established organizational hierarchies in large financial institutions? What mechanisms can be developed to ensure that agility is embedded operationally rather than remaining a project constraint? If step-wise models are favored, what governance structures can mitigate the risk of siloed implementation across diverse regional systems?