Today, it’s all about faster payments! Customers are demanding near real-time payments and banks - especially in the United States - are struggling to keep up. Non-bank third-party processors find themselves in a situation where they do not have the onus of regulation or the risk that a bank needs to manage. Add a brand new payments infrastructure to this and banks are struggling to compete, and the odds are stacked against them. In the bid to compete in this faster payments world, banks are implementing new technologies at a rapid pace to uplift an ageing payments infrastructure while ensuring regulatory compliance and reduced risk to customers.
Another perspective to look at this from a bank executives mind is this:
“How do I deliver a great user experience to my customers through a near real-time payments product while meeting new regulatory requirements and ensuring that we increase fee income while doing all this?”
Sounds like a tall order, doesn’t it? Make no mistake it is - and we don’t have all the answers! We know,however,that every new payments implementation or payments system upgrade/ release is fraught with risk (just like most of these projects are) and there are landmines waiting to blow up in your next implementation/ release. Some of these that we have experience are:
Wire payments pose the highest risk in a payments implementation, followed by other payment functions
Evolving requirements and customized capabilities (that move away from the core functionality of a vendor product) introduce avoidable new risks
Dependency and coordination of activities with third party providers of interfaces always results in delays
Compressed QA and UAT cycles result in poor quality
Single points of failure (one person responsible for key activities) result in schedule slippage
Data and client migration components need special attention
Performance of payment systems is critical and test data generation for the same is fraught with issues
Similarly generating test data for end-to-end validations can impact schedule
Outage or data refresh in the host/back-end integrating systems results in rework
Triaging and fixing environment issues specific to QA, PreProd, or Prod can be challenging
Lack of environments/multiple activities being simultaneously carried out on the same environment (e.g., functional, data migration and performance testing being carried out on the same environment) can result in an activity stack up
Interface contracting risks always exist with a payments system, given the number of systems it interacts with
Some of the ways in which we have experienced banks avoiding these landmines are:
Ensure that they have enterprise-wide buy-in before embarking on a project of such nature. This includes being on the same page on scope, objectives, deliverable, responsibilities, funding and resources
Create a fully integrated project map
Identify key risks upfront and devise mitigation strategies
Create realistic timelines and plan integrations early
Establish Go-Live criteria up-front and share it with everyone involved in the project
Would love to hear some of the other experiences all of you have had. On another note, we talked about this in detail in a round-table we recently hosted at the ACI User Group conference. Please feel free to visit our Resources page to download the slides from that talk.
If you are looking for someone who can help you accelerate your time to market on product releases look no further. Get in touch with us today to explore our scientific and analytical reports derived from our proprietary technology!