Why digital platforms are re-balancing decisions to build or buy IT in the banking industry
17 December 2021
7 min read
In boardrooms around the UK, one topic raising its head – how to join the race for a digital banking platform.
The digital platform based business model
Digital platforms are one of the hottest business topics today. Examples include Airbnb, Uber, JustEat— these platforms bring access to services the provider doesn’t own. Customers value an interface that makes for painless access to the unique experiences they’re hunting for. As Deloitte puts it in a recent report,
“In the digital economy, you can become a driver without owning a taxi, a hotelier without owning a hotel, or a bookseller without owning a bookstore.”
Market watchers suggest that digital banking platforms signal the death of the vertically integrated business model—where the banking value chain stretches from production to sales, distribution and servicing.
Digital payment platform choices in the financial services industry
Companies must decide how to embrace the platform-based business model— either as an active participant on someone else’s platform or by building their own.
Adopting a platform-based model can be difficult for mature organisations, particularly with so much technical capability internally. Over the past decade, financial service providers have become app innovation factories in their own right. In 2016, the Chief Exec of Barclays, Jes Staley, famously described Barclays as a technology company with a balance sheet and regulators, arguing that, ‘having the right technology in place is a critical obligation’ for the company.
IT teams will instinctively look upon new tech trends with wide eyes, anticipating another opportunity to show their steel and bring value to their internal stakeholders. Tech leaders want to go build—it’s in their DNA. However, sometimes this decision happens without the organization fully considering its commercial implications. Today, some IT choices aren’t just tech decisions—they form part of the customer value an organisation serves up.
As Finbarr Joy, a Technology Advisor to the Financial Services industry and Non-Executive Director of Answer Pay puts it,
“I’m one of those techy people who hears about an innovation like Request to Pay and, having understood its value, starts looking into how to build it. On the face of it, technology solutions RtP become ‘just another API,’ but these sorts of developments can quickly become a distraction. The pressure is on for IT leaders to ace their core business outcomes, and APIs can burn time and resource beyond their commercial value.”
The need for speed
While in-house resources for digital transformation have grown considerably over the last few years, demand for digitisation and re-platforming has grown significantly faster in the financial services industry. One reason for this has been the long tail of legacy systems refreshes and upgrades to core banking systems that have plagued finance houses. This constant resource drain has led many organisations to install dedicated fast-track digital teams.
In the digital age, speed of innovation is everything. Organisations accustomed to adapting their business model once every five or ten years now face regular whiteboard sessions to revisit their underlining business strategy and how it levers technology to deliver more customer value and profitability.
Andrew Lawrie is CTO for NDMC Consulting, is a recognised pioneer of the low-code software development revolution, having authored the Encanvas low-code platform for enterprises. He explains,
“Our clients are transitioning away from agile teams to low-code software platforms to increase their pace of development. Even so, there are always more demands from businesses for apps and platform enhancements than DevOps teams can reasonably cope with. Businesses want to see step-change compound changes in their digital ecosystem that have a profound impact on customer experience.”
Why it makes commercial sense to adopt a ready-made Request to Pay platform
Request to Pay is a set of protocols for establishing a payments messaging platform for integration with the mobile apps of banks and service providers. It’s build around a set of approved operating, messaging and interoperability protocols that are being adopted by the UK’s financial services industry. A European equivalent (SEPA Request to Pay) has been launched this year.
People increasingly run their lives via their smartphones. Traditional ‘Pay by Link’ solutions expose bill payers to serious data security threats.
Adopting Request to Pay for bill payments is a no brainer to UK companies, financial service providers and banks. It offers ease of use for bill payers and adds a way to directly engage with customers through the app. Empowering payers to choose which bills to prioritise adds tremenduos value—key to supporting the financially vulnerable.
For the financial services industry, the conversation is not if but when to adopt RtP.
RTP is a off-the-shelf financial service platform solution
Given Pay.UK has worked to produce such a well documented set of guidelines to implement the RtP protocol, why shouldn’t companies opt for the ‘build’ option?
Peter Cornforth, Operations Director for Answer Pay thinks it’s a journey that presents developers with a series of potentially derailing bear-trap challenges.
“Answer Pay was the first company in the UK to develop a working Request to Pay platform certified by Pay.UK, so we know a thing or two about the complexities. As RtP operates within a highly regulated industry, with complex back-office handshaking protocols for any communications approach, the development is unlike any I’ve personally encountered.”
Answer Pay assists banks and service providers to implement their own RtP solutions by installing SPX ™, its white-label SaaS solution. SPX™ acts as the keystone of the Request to Pay ecosystem, managing the identities of participants and securely routing bill payment messages to the correct destinations, seamlessly connecting invoice management systems with bill payment applications.
Joy believes IT teams will always consider the build option for new interoperability solutions, but his advice is to investigate off-the-shelf RtP options first before doing so.
“With a traditional API, you’re chiefly only focused on the technical challenges, but with RtP it’s more of a market-place and ecosystem; a cog in the financial services plumbing that drives payments. Fail to get the regulators onboard, certify the connections, and satisfy the various stakeholders and it won’t matter how good your tech is, you won’t be able to use it,” he says.