March 29, 2019
Implementing a real-time payments (RTP) solution is an incredible opportunity for any financial institution, but the journey can be a bumpy one for institutions who are not prepared. To help banks build a knowledge base and prepare themselves to ask the right questions (both internally and externally), Levvel has composed a list of key questions and considerations that you can use to prepare.
These questions are based on Levvel’s extensive experience with RTP, including both business considerations (e.g., ideation, use case design, user stories) and technical considerations (e.g., architecture, design, coding & implementation); however, there are always unforeseen considerations. The key is to always ask a lot of questions of your internal teams and any external providers you speak with. And don’t forget—TCH (The Clearing House) is always available as your partner and guide.
Use this RTP checklist to accurately assess your current architectural environment, identify the challenges your institution will need to address, and plan appropriately to deliver a high-quality experience for your customers. Whether you are in the process of implementing RTP or planning your integration, this checklist will help guide your decisions and ensure you are on the right track.
As payment systems domestically and internationally adopt faster money movement, your customers are doing the same. In order to remain competitive, providing your customers with accessible, competitively-priced real-time payments will secure your position both in the market and as their financial institution.
Our team is made up of leaders, thinkers, designers, and builders whose collective experience spans many industries and companies of all sizes. We’re avid fans of technology but even bigger fans of solving business problems. An understanding of the difference between an idea and a solution is just one of the things that set us apart.
Our Payments practice combines enterprise payments experience, technical expertise, and a pulse on emerging technologies to ensure our clients create the right approach the first time. Our team has broad, strong industry relationships and expertise across the payments ecosystem.
Principal Architecture Consultant
Senior Director, Financial Services
Phil Mork is a Principal Architecture Consultant for Levvel. He is responsible for providing architectural insight and guidance on various payment topics which enables clients to deliver on their strategic payments initiatives.
Greg is a Senior Director of Financial Services at Levvel where he is responsible for leading client engagements and building relationships with customers ranging from top-10 banks to payments enablers to start-ups. With over 15 years in financial services, Greg previously spent 7 years at Bank of America, most recently leading product & business teams in the launch of Apple Pay, Android Pay, and Samsung Pay. Prior to Bank of America, Greg held a variety of financial services roles at eSpeed / Cantor Fitzgerald and Reuters. Greg holds an M.B.A. from the Darden School at the University of Virginia and a B.S. from the College of William and Mary. He currently resides in Charlotte, NC with his wife and three children.
Now that 2020 has arrived, the reality of RTP adoption has begun to outpace planning for implementation. The RTP conversation is no longer around should it be implemented, but rather of use cases that have been missed to better serve customers.
Throughout this series we'll provide answers to frequently asked questions surrounding product management for RTP, such as managing the product(s) long term, dealing with cannibalizing current products, and more.
TCH’s RTP adoption is rising. A recent study noted 74 percent of small and large institutions are considering RTP or have begun implementation. Although a large majority are adopting RTP, there are many differences for RTP within small or large FIs.
In 2019, we participated in the RTP Buildathon, sponsored by The Clearing House, Oracle, Yodlee, and The Carolina Fintech Hub. Our task was creating a compelling use case for leveraging the RTP rail and building a working prototype to demo our idea.