Picture of Frederrick Hamann
Frederrick Hamann

How long does the integration take and what’s involved?

Now let’s look into how long the integration takes and what’s involved. Let’s start with the first part of that question: how long does it take? 

And the short answer is actually 3 hours! So it takes us three hours to be up and running within your banking environment, showing you exactly what the functionality of the subscription management system is going to be.

But it takes us 180 hours from your development employees to get all the way to market, and both of these numbers are really quick and they’re getting quicker and quicker every time we work with different types of banks. And I’ll just show you how we’re actually able to do it this quickly. So the first thing that we do is that we actually divide the integration into three different paths.

So the first path is the data path. This is where we get the data from you as a bank. We can get it from your data warehouse, we can get it from you, we can get it from a PSD2 aggregator, and that type of data needs to have a certain type of granularity to it, which means that we are we’re working on transactional data that is showing the merchant name, that is showing the amounts, that are showing the frequency, that type of data that’s the first part of the integration.

The second part of the integration is the back-end side and the third part is the front-end side of the engineering process, and those three pass paths are running simultaneously. 

But let’s start with the first one, the data path. So we take all this data, especially when we go into a new market, and then we put the data into our algorithm and then we actually just lean back and it does all the work. It’s the one that’s really crunching the data looking for the patterns, and then it’s spitting these different boxes out with names on it and one of the boxes is ‘recurring payments’, the second one is around subscriptions and the third one is one-offs.

And the one-offs, we don’t need them, aside with that. So we’re only looking at the recurring payments and the subscriptions. And to do this exercise, we of course need a lot of data and that’s why we take our data security very seriously and we are already regulated in several different countries in the European Union by the local FSAs. We have our own ISAE 3402 license which is really showing that we have documentation and processes for securing the data, and the last part is we also have our own AISP license just to make sure. So all this is really what we are doing on the data side and that’s the first path. 

And the second path is then the back-end side which is also one of the important integration points here. We have an API which we are able to integrate into your banking environment and that API has been built by some of the best engineers in Denmark.

The last part of these different paths, is the the front-end side of things. And here we’re working with a so-called SDK. So, the SDK is going to show the user what it is that they’re going to see. It’s going to show them the overview of the different recurring payments, and it’s also the SDK that’s handling the full cancellation process. So as a bank, you are able to build this type of front end yourselves. We can just give you the APIs and you can then build the front end yourselves.

But we have this possibility of showing you the SDK, and then using that to enhance the experience for the end users. And with this SDK of course we’re also able to take all the learnings that we have from the other banks and putting the same learnings into what we’re giving to your bank as well.

The SDK can show the full customer journey within three hours. This means that it’s not going to show exactly the colours and the wording, and the tone of voice, but it’s going to show you the functionalities. 

So within three hours we’re able to deploy this within your banking environment, and show you what it’s going to look like when it comes to the functionality. And then from there on we are working together on building the best type of customer journey, which means that then we’re going to look at the design, the UX, we look at tone of voice, language. All those different parts is something that we are able to develop together when it comes to the SDK, to make it look like your product. This is not Subaio’s product, it’s your bank’s product.

Once we’ve done the data, the back-end, the front-end, we test it with your users or with your employees, and then we’re ready to go to market. And this full process with the data, with the back-end and the front-end, it takes about 180 hours on your end which means that you are going to have to have 180 hours from your developers to work on this on this system to get it up and running. This is an average. We’ve done it quicker with some of these banks, we’ve done it on a weekend with some of our clients. But of course, if you’re a bank with millions of customers, we’ve also seen that this could take up to a thousand hours of development on your side.

So again, it depends on the maturity of your bank on how quickly we can do this, but we have a huge amount of experience in doing this. When it comes to this we can also help you deploy this as quickly as possible, because we’re doing it faster and faster every time. We’re talking to these different banks and integrating with the banks, so we really believe that speed is of the essence here.

So if you want an innovative solution that is going to give your users exactly what it is that they want, then you have to choose a solution that is going to have it quickly into the hands of your end users.

Get a personal demo of how the Subaio solution will work for your bank​