Bankloch

  When starting a new product , there is always a difficult question: how much should you build from the start? On one side, there is the MVP philosophy . Build only what you need, get it in front of customers, learn from their feedback and improve from there. Don’t spend months solving scalability problems for a product that might never have a scalability problem. Don’t automate processes before you even know whether those processes are the right ones. And don’t build a perfect architecture around requirements that will probably change anyway. On the other side, there is an equally convincing argument. If you already know something will eventually need to be automated , why build it manually first? If you know you will need APIs, scalability, proper monitoring and high availability, why postpone them? Doing the work twice is rarely cheaper than doing it properly once. Even worse, changing something later can become very difficult once customers are using it and depend on t...

  Over the past decade, application security has changed dramatically. Yet the biggest shift is not that software has suddenly become less secure . The real change is that discovering vulnerabilities has become much easier , while fixing and distributing those fixes has become significantly harder . For software vendors, the bottleneck is no longer finding security issues. It is maintaining secure software throughout the entire lifecycle of a product. Not that long ago, finding vulnerabilities was largely a manual exercise. Internal penetration tests, customer security assessments and occasional code reviews uncovered issues that developers would then address before the next release. Today, vulnerability discovery is continuous and increasingly automated . Static Application Security Testing (SAST) tools such as SonarQube analyze every build for insecure coding patterns. Dynamic Application Security Testing (DAST) has become a standard part of many security programs, both int...

  Open Banking has been around for several years. With PSD2 in the European Union and Open Banking in the UK, banks were forced to open access to payment accounts and payment services to regulated third parties. Since then, we have seen a growing number of use cases emerge: account aggregation in personal financial management applications, transaction data used for credit scoring and risk decisioning, account verification during onboarding, cashback and loyalty services, and account-to-account payments. Yet despite all the attention Open Banking has received, its impact remains relatively limited compared with its original promise. Part of the explanation is technical. API quality and availability still vary significantly between banks. Implementations differ, making connectivity complex and costly for third-party providers. Authentication and consent processes can introduce additional friction, while seemingly basic challenges around historical information, joint accounts, transac...

  Banking is undergoing a quiet but profound transformation. While most people still interact with their bank through mobile or web applications, this model is quickly becoming outdated. The future lies in contextual, intelligent, and embedded financial experiences , powered by AI and shaped by the user’s life. Today’s digital banking is largely pull-based, i.e. customers log into their banking app to perform specific tasks, from checking balances to transferring money. In tomorrow’s world, banking will be increasingly push-based . Financial institutions, powered by AI and integrated ecosystems, will proactively suggest actions at the right moment. Imagine getting a pop-up to pay an invoice as soon as it’s received, or being notified when you’re about to go overdrawn with the option to transfer funds or access a credit line, all without opening an app. Banking is moving beyond the app. In the near future, financial actions will be initiated within other digital environments, such...

  For many years, electronic invoicing has been presented as one of the major milestones in the digital transformation of finance. In Belgium, that transformation accelerated significantly with the mandatory adoption of PEPPOL for B2B invoicing (since 1st January 2026). The promise is compelling: invoices become structured, digital and standardized , allowing companies to exchange them securely and efficiently while improving transparency, reducing administrative overhead and creating a foundation for further automation. On paper, it sounds like the moment finance departments have been waiting for. If invoices can move automatically from one ERP system to another, shouldn’t Accounts Payable and Accounts Receivable departments become dramatically smaller? Interestingly, that is not what we are seeing in practice. While PEPPOL adoption is undoubtedly an important step forward, most organizations have not  experienced the dramatic reduction in headcount that some initially ...