Atfinity: Software for KYC/KYB/AML and client onboardings的动态

Transcript

So how do we integrate with core banking systems? That's a question that I'm asked quite a lot. So, when I'm involved with sales, I'm usually involved in the sales process a bit later, when it comes to he slightly harder technical questions. As a CTO, it makes sense that I do technical questions about how do we integrate with these systems. Integrating with the core system or integrating with a core system, of course that's very important. So many clients wonder how do we do this, can we do this and have you done it before. And that's actually - have you done it before - that's pretty easy to answer. So since the beginning, so since our first client like four or five years ago went live with Atfinity, we had integrations with their with their core banking systems. We have quite a few clever ways to actually do that, so over and over the years we got cleverer and cleverer. So four or five years ago that the main thing we did is, at first we built like we hardcoded, to say a technical way to integrate with the core banking systems. However, we hardcoded that part. We're usually not very large on hardcoding. We want a lot of flexibility. We were always very flexible about the way what kind of data you push to. So when you integrate with any systems there's two things you kind of have to figure out. What's the technical way to integrate with that; do we have REST API, do I send something as SFTP and when I have REST API do make five requests to kind of just first get some kind of token and send that token over, or do we encrypt this in a special way, or something like this? It was a technical way to integrate it. And then - what kind of data are we sending? And we always treated these two things a bit separately. So when I say we hard code the core bank integration, I mean the technical way was hardcoded. So, how we integrate it; we sent it to an SFTP server or we go to an HTTP server in special way that was kind of built by our development team in-house. However, the second way, how we push the data that was always flexible, will always be flexible, and that's kind of like the whole intelligence behind Atfinity. So we have this rule engine, we have this way to kind of transform data from one thing to the other and then do calculations and all of that. So you could basically yourself configure a way what kind of data you want to push. Like an easy transformation could for example be an Atfinity, because for other systems you integrated with, you have three digits for country codes and then you use two digits in your core banking system. In Atfinity, that's no problem. You just transform the three-digit system, you have a map and transform this from the three digits to two digits, and you send the data with two-digit country codes to your core bank system. Then obviously, usually Atfinity can do more things, so you can have risk calculators in between, lots of stuff, so there could be more data stored than the core system actually needs. So you also decide that I always sent these 50 data points from the 150 data points we collected for the client onboarding and send them to the to the core bank system. So these two things, technical integration and the flexibility of kind of what we say, like how do we integrate and what do we send as data. And then recently in the how part, we also got much smarter. So we've done it so many times we thought: OK, yeah, of course even the programming got easer and easier by doing it, like, the fifth or sixth time, or tenth time in that case. But even that was not good enough for us. The problem being with the what you sent that's completely independent from a release cycle, it's configuration. So a client can at any point in time decide: I send this differently. However, when whenever the core banking system maybe change the technical way how to integrate it, we need to wait for another release until our developers could do something, and that was not quite good enough for us. So, now we have a way that we do this integrations also kind of configurable. So we have like a huge YAML file basically that kind of has a list of actions you go through per system. So, for example, just first make a request, get a special token and then use that special token to make another request that you send the customer data to the core banking system. It's kind of a series of steps in a YAML file. So we built this huge framework where, basically, you encapsulate the way, the technical way you integrate the system, you encapsulate this in a step of actions you have in that YAML file. And that also means that these YAML files are still developed by us, they're done here in-house, and then they're specially packed in a way that they also kind of like just verify that it comes from Atfinity. But if you drop such a YAML file in on the server - you have a new integration. Meaning that is also now completely independent of our release cycle. So, whenever I come into that question about such a process and they asked me: Can we integrate with their core banking system, I pretty confidently also say - say, yes, we can do that. We have done it many times. We have now lots of clever ways, we were always super-flexible and these days even the technical way how we integrate is super flexible, cleverly done. So yes, we can in all likelihood I'm being a bit of an engineer here - in all likelihood 99.99% we will find a pretty easy, pretty fast way to actually integrate with your core banking system. No problem.