{"id":6102,"date":"2021-10-21T08:23:00","date_gmt":"2021-10-21T08:23:00","guid":{"rendered":"https:\/\/codeandpepper.com\/?post_type=case_study&p=6102"},"modified":"2025-05-08T11:51:23","modified_gmt":"2025-05-08T11:51:23","slug":"the-id-co","status":"publish","type":"case_study","link":"https:\/\/codeandpepper.com\/case-studies\/the-id-co\/","title":{"rendered":"The ID Co."},"content":{"rendered":"\n
\"\"<\/figure><\/div>\n\n\n\n
\n
FinTech Development<\/div>\n
.Net<\/div>\n
Microsoft Azure<\/div>\n <\/div>\n<\/section>\n\n\n\n

In the last couple of years, the business world has been shaken by scandals connected with customer data management in different sectors. The changes in legislation became inevitable, with the European Union taking the lead by introducing PSD2 directive. Our long-term client, The ID Co., requested us to help them adapt to complex legal requirements by integrating with Salt Edge, a third-party open banking<\/a> solution.<\/p>\n\n\n\n

About DirectID by The ID Co.<\/h2>\n\n\n\n

The ID Co. is a FinTech solutions company with two individual products under their belt: DirectID<\/a> and NoMo<\/a> (developed together with Code & Pepper). This project concerned DirectID, a banking data aggregator which enables customers to use their online banking profiles to log in to other applications and platforms. The product offers two key integration points: DirectID Connect and DirectID Data API. The security model is layered and protected by OAuth authentication and strong encryption.<\/p>\n\n\n\n

Challenge<\/h3>\n\n\n\n

After the implementation of PSD2, The ID Co. faced an urgent issue that could affect the product\u2019s ongoing operation. They needed to find a means to ensure continuous flow of customer data from European banks. After choosing Salt Edge<\/a> as a data aggregator, it was our job to build an API compatible with an existing solution \u2013 Yodlee<\/a>, which communicates with the remaining DirectID API.<\/p>\n\n\n\n

\"Transition<\/figure>\n\n\n\n

Solutions for Salt Edge<\/h2>\n\n\n\n

API compatibility<\/h3>\n\n\n\n

Some fragments of Salt Edge API turned out to vary significantly from Yodlee API. This forced us to adapt the Salt Edge solution to some extent to ensure our custom API<\/a> communicates with each service. Documentation<\/a> provided by Salt Edge proved to be of vital support.<\/p>\n\n\n\n

Based on Yodlee source code, our team performed reverse engineering to create an analogical API layer. This included:<\/p>\n\n\n\n