Banks Race to Close Real-Time Payment Gaps

Speaker A: Foreign

Speaker B: this m is what's next in Payments, a payments podcast forward looking insights from industry leaders on the trends and technologies reshaping payments and fintech. In this episode, i2C Chief Client Officer Serena Smith says real time payments require interoperability so banks can connect compliance and stop fraud.

Speaker A: Hello everyone, it's howlavypayment.com and for another conversation, Serena Smith with Cheap Cloud client officer at i2C joining me for what's next in payments? The word of the year. Now, maybe not just a word, maybe a few different concepts are, uh, dominant already as uh, we move into uh, 2026 more firmly. But clearly there are some trends that are taking shape and maybe some um, ideas that are different this time around. Nice to have you. Welcome back.

Speaker C: Oh, thanks, Hal. I am, um, I always love talking to you, so thank you.

Speaker A: Likewise, likewise. Thanks so much. So let's get right started. Um, um, the first thing I think we might discuss is the idea of a single constraint. Is there a single business constraint that is shaping 2026 in your mind more than any other?

Speaker C: Both of us have been in payments for a really long time and we've been able to see the evolution that's happening. And I think that as we look at 2026, the thing that we are faced with is we have all of these different Rails, all of these different regulatory structures that we have. We have more standards than ever before. I think one of the things that we've got to figure out as an industry is how do we really make them all work together? Because today there's a lot of standalone Rails or payment channels that are occurring. So when I think about what needs to happen, and I think about the word of the year really is around interoperability because we all have to figure out a way, especially with AI, to look across and bring together all of those payment channels so that we can fight fraud, we can create better customer experiences and we can also make sure that, you know, just from a, uh, compliance and a regulatory standpoint, we're doing all of the right things that we need to do in order to service our customers.

Speaker A: The industry in the endeavor to do, as you put it, all the right things, what do you suspect your own customers will notice, uh, as a change? First, what do they want you to fix or improve for their own, um, well, being, let's put it in the meantime,

Speaker C: so what do they expect us to change? So when I think about like all the technology that's now available, so we've been talking about AI for a long time We've been talking about stablecoins, we've been talking about crypto, we've been talking about all the different payment rails, um, the regulatory requirements. I think today, um, a lot of the regulators are just trying to figure out in the new ecosystem that we continue to evolve in, how do they actually regulate that? And there's not one piece of anything that's happening that's wrong and it's very few of them are designed to work together. And so as we think about there's more pressure around this real time processing, there's more pressure around ISO 20022 adoption. We've been talking about that for a long time as well. Regulatory expectations. Each of those initiatives makes sense individually, but collectively they create a coordination problem that uh, really all of us needs to start working through better. So what we see are institutions continuing to add capabilities faster than they're simplifying their architecture. And so we have to think about the underlying architecture that's sitting there. How do you build faster, how do you build with these integrations? And each one of these integrations are going to add cost, they're going to add operational friction, they're going to add risk. And even if we solve them for a short term, fragmentation really makes it harder to apply consistent controls across. You got to think about fraudsters and how do you fight them from an identity perspective and authorization perspective, you got to work through settlement. So every growth initiative now depends on how well these systems we connect data across them and how we execute. So what we're looking at, so when we think about the challenge that customers are facing, we think about the industry, we think about interoperability. What works best is when platforms are designed to be extended and configurable rather than stitching them together piece by piece and figuring out how on the back end, how to do that individually

Speaker A: with all these moving parts, um, my guess is uh, you don't really take uh, a breath, you don't have the moment to stop thinking about this stuff. So let's talk a little bit from your own point of view. Uh, let's talk about risk. You've mentioned fraud, you've mentioned uh, the friction that's inherent in a complex ecosystem. Um, and so when you are thinking about where we are now, where we need to go, tell me a little bit about what risk maybe is, is most, um, in your mind, keeps you up at night, let's call it. And then there's also the ability. There are risks that are acceptable, acceptable ones if they're calibrated well. That are okay to embrace. What would those two different things be?

Speaker C: Yeah. So I will tell you what keeps me up at night is really the risk of losing trust in our, in what we're actually providing. Trust in our systems, trust in our technology, trust in what we're building for the future. So I've talked about, you know, fraud a little bit. So fraudsters are getting smarter in everything that they do. So when you think about fraud, scams, account compromises, these things are now happening in real time across the entire ecosystem. And the margin for error keeps getting smaller, uh, as settlement speeds increase. So when controls lag behind execution, it creates gaps that are harder to close after the fact. So, you know, when you think about fraud today, moves across rails and channels, it's not just an isolation. The time to detect and intervene keeps shrinking. Post transaction monitoring wasn't built for instant or irreversible payments. So we have to rethink how we're actually managing, um, those systems. And the risk you're willing to take is modernizing faster than what traditionally feels comfortable. So one of the things we have to, you know, we have to look at is how do you embed identity fraud compliance decisions directly into execution in a practical way that supports the interoperability without increasing exposure. And that's one of the things that we're focused on here.

Speaker A: Um, with some of these acceptable risks and obviously the faster time to modernization, uh, the payoffs and rewards can be significant. So if we look ahead, let's look ahead a few months, Ah, we're already only a few weeks into 2026. So if you had to define success at the end of the year, you're looking back and there's one measurable yardstick benchmark outcome that you think may, ah, point toward, um, a job well done, what would it be?

Speaker C: Well, for me, I think success is being able to move money faster without adding operational risk or complexity. Institutions should feel comfortable scaling your real time payment channels instead of being cautious about them. So how do we make that easier, easier for the market to absorb. So you've got to have fewer custom integrations, which means the platform is doing more of the heavy lifting for you versus having developers doing that for you. New payment capabilities, being able to be launched without destabilizing what's already in place, and teams spending less time chasing expectation and more time improving, uh, customer experiences and controls that they have of their own destinies through the ecosystem. So real time execution becomes predictable and trusted. I think that's, that to me would dictate success. And from my perspective here at i2C, success really means that true interoperability, um, allowing innovation and reliability in everything that we do from start to finish.

Speaker A: Is it your idea, too, that, um, interoperability becomes table stakes?

Speaker C: Eventually, I think it has to. When we think about, um, how do you remain competitive? You remain competitive by making these things table stakes in your overall business. So I think in order to be successful, money does need to behave consistently. Consistently regardless of the rail, region or channel that it's in. And so that has to be the definite table stakes as we look at moving forward.

Speaker A: All right, so not there yet. But we do have a North Star to pursue, and that would be, um, frictionless interoperability. And clearly 2026 promises to be, um, a different year than what we've seen previously. I'm going to hold you to it. Uh, when we get to the end of the year, we'll see where we are. And thank you again as always for your time and your insight.

Speaker C: All right, I'm looking forward to it. Thanks, S. Take m care.

Speaker B: That's it for this episode of the payments podcast. The thinking behind the doing conversations with the leaders transforming payments, commerce and the digital economy. Be sure to follow us on Spotify and Apple podcasts. You can also catch every episode on payments.com podcasts. Thanks for listening.