About a-team Marketing Services
The knowledge platform for the financial technology industry
The knowledge platform for the financial technology industry

A-Team Insight Blogs

Swift Eases Payments Data Consumption With SwiftRef APIs

Subscribe to our newsletter

Swift has added 12 application programming interfaces (APIs) to its SwiftRef reference data utility with a view to helping financial institutions and corporates automate payment processes by identifying and validating payments reference data in real time using information in SwiftRef.

The APIs have been piloted for 18 months and are now market ready. They cover industry identifiers including BICs, IBANs and LEIs, as well as settlement instructions and national bank codes, and allow users to check queries against the SwiftRef repository via proprietary applications. The APIs add to SwiftRef’s existing data delivery channels that include online manual look-up, manual and automated file download and secure file delivery over Swift.

Herve Valentin, head of reference data at Swift, says: “The APIs ease consumption of data, which is one of Swift’s strategic aims, and ensure payments reference data is correct. Through this approach, banks and corporates can increase operational efficiency, reduce costs and risk, and reduce time spent on errors resulting from manual repairs and investigations.”

One early user, Kimmo Veistola, manager of cash management at Finnish paper and forest products company UPM-Kymmene, says: “We implemented SwiftRef APIs for BIC and IBAN validation, which has led to a very clear workload reduction resulting from automation and higher data quality. The data quality has also reduced the turn-around time for payments.”

Swift expects corporates to be the biggest users of the APIs and, to date, a few tens of the 500 or so corporates Swift works with have implemented some of them. Large banks are not expected to use the APIs as they rely on direct access to local SwiftRef sites, but bank subsidiaries with limited payments requirements may favour the API approach above implementing a local SwiftRef data centre.

Looking forward, Valentin says Swift will continue to extend SwiftRef with the addition of new directories. Entity Plus, a directory designed to support regulatory reporting by providing a consistent view of entities by cross-referencing identifiers including BICs, LEIs and GIINs, will be available in the next couple of months. In a second phase of development, the directory will be enriched with entity hierarchy and ownership data to support regulatory compliance and risk management.

Subscribe to our newsletter

Related content

WEBINAR

Recorded Webinar: GenAI and LLM case studies for Surveillance, Screening and Scanning

As Generative AI (GenAI) and Large Language Models (LLMs) move from pilot to production, compliance, surveillance, and screening functions are seeing tangible results – and new risks. From trade surveillance to adverse media screening to policy and regulatory scanning, GenAI and LLMs promise to tackle complexity and volume at a scale never seen before. But...

BLOG

FpML to DRR: TradeHeader’s Journey to the Heart of Regulatory Data Standards

Digital Regulatory Reporting (DRR) has gained momentum as the industry looks to replace fragmented, firm-specific interpretations of reporting rules with a shared, machine-executable model that consistently links regulatory requirements to the data used to fulfil them. Rather than relying on templates, local mappings and bespoke logic embedded deep within legacy systems, DRR provides a common...

EVENT

RegTech Summit New York

Now in its 9th year, the RegTech Summit in New York will bring together the RegTech ecosystem to explore how the North American capital markets financial industry can leverage technology to drive innovation, cut costs and support regulatory change.

GUIDE

Data Lineage Handbook

Data lineage has become a critical concern for data managers in capital markets as it is key to both regulatory compliance and business opportunity. The regulatory requirement for data lineage kicked in with BCBS 239 in 2016 and has since been extended to many other regulations that oblige firms to provide transparency and a data...