Podcast: Interoperability vs. Integration in Payment Data

Posted by Modo on May 7, 2018 1:05:45 PM

Our CEO, Bruce Parker, sat down with Chris from Currency Cloud to talk through the differences between interoperability and integrations in payments, and how Modo is changing the way things are done in payments. Listen to the full podcast, or read the run down of the interview below.


[audio mp3="https://modopayments.com/wp-content/uploads/2018/05/8_Bruce_Parker-1.mp3"][/audio]

Excerpt from interview with Currency Cloud


After two decades in the software side of the payments business, Bruce has seen a lot of technology and infrastructure challenges when it comes to managing data in payments… and navigating exchange between systems and networks among all the various participants in the payments ecosystem.

At Modo, he’s focused on how payment data gets exchanged—and, in particular, how to achieve interoperability. “What Modo does is connect the dots,” Bruce said. “We connect between the new and the old.


The key to interoperability is being able to connect those dots without changing either side. Modo doesn’t change the existing systems.

It’s a software solution to this question: How do you turn the data that’s being exchanged into the same format on both sides of the connection?

Hint: It doesn’t mean changing everything.

“And in our case, we don’t actually think that that’s necessary,” Bruce added. In some cases, it isn’t even possible. “It’s very, very difficult to change payments infrastructure,” he said.

Even when someone wants to change the software, they sometimes can’t. (The systems are being used for huge amounts of volume daily.)

Instead of integration, in comes interoperability.

“So instead we say, hey look, we’ll build a connection to the system, whether that’s new or old or something in between,” he said.

They code to the existing interfaces. So they take data from Bank of America and transform it into a version that can be “read” by PayPal’s API for payouts, for example.

A bank system has a system for communication, and so does a merchant—but they’re very different. “Our job is to bridge the gap,” Bruce said. “How do we take the information out of the bank system and recharacterize it, reformat it, and reassemble it on the other side for PayPal?”

That’s what interoperability is. It leaves both sides the same but helps them to share information anyway.

Interoperability vs. Integration in Payment Data

The process of bridging the gap

It depends on the client for Bruce to determine whether a potential client needs an essential workflow or a more customized system.

“So we have a number of different types of systems that we’ve already got connections on,” Bruce said.

Leading providers of online payment methods, mobile payment methods, the traditional card acquiring, card issuing, a gift card, loyalty, etc.

“That’s generally where the conversation starts. What are we already connected to? And oftentimes people are trying to do the same things,” he observed.

Here are the three different categories people tend to be focused on:

  1. Checkouts. Purchase transactions made online, in store, or by mobile.
  2. Payouts. How money generally moves—from large businesses to small businesses or consumers.
  3. Pay Ins. The reverse of payouts—small businesses or consumers are paying large entities.

The first question that Bruce asks is what system they’re using.

Banks, merchants, corporations—all use something to generate payment requests or a system to manage payments flow.

“So in the checkout environment, that’s pretty straightforward. There are store-oriented systems, either online or physically, that accept payments and process them through the various network connections,” Bruce said.

It’s important for the data to be able to travel to and from many different systems.

Could this be the precursor to an open source environment—which is more than likely where Europe and the US are headed?

In the checkouts environment, Bruce has seen a lot of businesses as providing a democratization of access to different forms of payments. And in payouts, many have made the endpoints for delivery of transactions much more accessible to a whole new audience.

Access to payment information will drive the question, Bruce predicted. “It doesn’t actually solve the problem, though. Just because the market demands it or wants it doesn’t make it any easier for existing players to provide it.”

Which is hard. Because you need to give secure access to payment data and make sure that it’s usable by somebody on the other side, but they’re probably going about it in a very different way than you are.

Which rolls back around to interoperability. “That’s the place where this interoperability demand comes from. Okay, everybody wants to open things up,” Bruce said.

But at the same time, they’re all committed to existing systems or existing choices that they’ve made that constrain their ability to do anything they want.

“So, we’re here to say we’ll help you connect to pretty well anything that you like, because we’ve redefined what we think payment data is,” Bruce said.


To read the full run down, follow this link to the Currency Cloud podcast.


Topics: bruce parker, interoperability