ARTICLE
6 October 2022
Companies building payment products or processing large volumes of payments as part of their operations often cannot rely on usual bank connectivity solutions. Their bank's web app or vendor's cash management system introduce technical, functional, and scalability limitations. The alternative is a direct integration with their banks that enables them to automate their payment operations from their in-house systems.
Although highly scalable and secure, banks’ direct connectivity solutions can be complex to understand and integrate, even for the most skilled product and engineering teams. They can also be a significant de-focus on a roadmap already filled.
At Mambu Payments, we have built more than 10 bank integrations over the last 12 months. This first-hand experience has enabled us to learn the specificities of every bank we have integrated with and refine our integration model over time. We now have a scalable process and a powerful bank integration engine that enables us to connect most banks to the platform in a fraction of the time it took to develop our first integration.
This article shares our learnings on the challenges of building direct bank integrations. We also outline how Mambu Payments can help accelerate bank integration projects, prepare companies for the future, and transform high upfront investment costs into predictable variable costs.
Accessing banks' direct connectivity solutions is more complex than creating a self-serve account and obtaining your API keys. If not already done, the first thing to do before even getting access to the bank's documentation is to open an account, and subscribe to the bank's connectivity solutions. The right stakeholders to do so is the cash manager.
Cash management is one of the many lines of products and services that banks offer to their corporate customers. It is also one of the most technical. As a result, banks have built teams of cash managers that are distinct from teams of account managers.
Because account managers have large customer portfolios and need to liaise with different teams from within the bank, response turnaround can sometimes be longer than what product or engineering teams working on a sprint need to reach their velocity goals.
Banks have strengthened their systems' reliability through years of iterations, keeping their customers’ funds secure and processing billions of payments yearly to power the economy. This iterative process created significant variability and complexity in those systems, reflected in the heterogeneity of their connectivity solutions for different use cases.
In Europe, connectivity channels include the below main channels
Bank integrations present a high upfront investment for companies. The learning curve can be steep, even for the best product and engineering teams. And it is not infrequent for a company to spend 3-6 months designing and developing a bank integration, even for the most payment-savvy teams. At Mambu Payments, it took us three months to build our first bank integration and blueprint.
Bank integrations are also, unfortunately, mostly sunk costs. Since they rely on connectivity protocols and file formats that can be niche, the codebase created for the project usually has limited applicability to other parts of the company.
In addition to the visible complexity and direct costs of building bank integrations, several hidden costs derive from the decision to build a bank integration.
At Mambu Payments, we thought about how to step-change the experience of connecting with banks. And we believe a better path for a company with complex payment workflows is to lean on an API-first payment operations platform abstracting the complexity of the building. By relying on a well-documented API integrated with all banks, teams can: