Delivering future-proof payments modernisation successfully

The ability to adapt to changes in how payments are cleared and settled, quickly bring new revenue-generating service offerings to market, reduce unsustainable cost-bases, and, for older banks, continue to understand and maintain legacy systems, is entirely dependent on modernising their payments infrastructure.

When embarking on a modernisation programme, banks have historically faced a choice: build the new capabilities in-house, or buy an off-the-shelf solution?

In the past, most banks opted to outsource payments modernisation initiatives to third-party vendors who provided complete solutions. However, many were burned as they found themselves locked in to overly complex, costly and inflexible black-box packages with glacial time-to-market.

Consequently, more and more banks are taking payments modernisation in-house to better stay in control of costs and risk. Yet this comes with its own challenges meaning the more important question is: how can banks successfully approach their in-house builds? In response, a third option has emerged that enables banks to take a sustainable approach to payments modernisation by developing payment processing solutions with the aid of a framework.

Short-term projects and long-term programmes

Before exploring approaches to in-house builds and the unique benefits of a payments framework, it is important to recognise the differences between ‘projects’ and ‘programmes’.

Sometimes, there is a need to build tactical solutions to address a looming short-term requirement. While these ‘projects’ are a necessity and come with clear funding models and motivated teams, they should not be mistaken for a strategic payments modernisation ‘programme’. While focusing on solving immediate headaches through tactical delivery can certainly feel like starting a modernisation journey, it rarely translates to building a truly future-proof foundation for innovation that delivers long-term value.

Escalating transaction volumes are a perfect case in point. A 12-month project to deliver the capability to support ten transactions per second can be successful, but what happens when the requirements escalate to many thousands of transactions per second? More often than not, there is neither the time nor money to prove the project can meet these strategic volume demands, so the bank is progressing in hope more than certainty – with the potential to fall behind the competition and expose themselves to unacceptable risk in the process.

Of course, defining, building and proving a future-proof foundation for modernisation takes time and money. Sometimes the business or industry need allows for neither, and the bank will have to focus on solving today’s problem. But in doing so, it must recognise this is a choice with trade-offs and unlikely to mark the start of a transformation journey. In reality, it will likely add to the ‘drag’ of legacy solutions and create more technical debt to be paid off at the expense of genuine innovation.