One of the main obstacles to broader API adoption in corporate treasury has been the legacy design of treasury management systems, which were not originally built with APIs in mind. Corporates that have realised tangible business value through APIs have typically supported their implementation with robust IT strategies – upgrading accounting and reconciliation systems to be API-enabled, for example. JPMorgan Payments has been collaborating with ERP and TMS providers to integrate APIs that are essential for treasury and cash management operations. It integrates into SAP’s platform through its multi-bank connector functionality and has also integrated Kinexys Digital Payments within Kyriba Connector, allowing treasurers to facilitate and operate cross-border and real-time payments, and blockchain deposit accounts.The bank’s APIs offer near real-time reporting of cash balances and account transactions, and it has integrations with Trovata, which enable Trovata users to manage multiple bank accounts across institutions in one platform. API adoption also hinges on middleware providers, which act as intermediaries between ERP/TMS systems and end-users. These providers are evolving to support API connectivity alongside traditional file-based and Swift messaging methods. In addition to ERP and TMSs adapting, success also depends on middleware providers stepping up. These providers, which act as the bridge between TMS/ERP systems and end-customers, are gearing up to support API connectivity alongside traditional methods such as file transfers and Swift messaging. Carl Slabicki, co-head of global payments for BNY’s treasury services, points to a notable uptick in API adoption among corporate clients.