Infrastructure

API-First Connectivity

The Messaging Hub plugs into SWIFT's Zero Footprint stack via Alliance Cloud and the Microgateway, runs a local SWIFTRef API proxy, and exposes REST endpoints to your back-office systems. One platform, three API channels, no legacy Alliance integration boxes in your data centre.
!
30 June 2026: SWIFT support for IPLA and SIL ended; since 1 July they are end-of-life software in CSP/CSCF scope. End of November 2026 -- legacy SWIFTRef files retired in favour of SWIFTRef Evolution and API. Both are forcing the move to API-first messaging.
The Shift

SWIFT is going API-first

SWIFT's Zero Footprint strategy moves the messaging gateway off the bank's premises and into Alliance Cloud. Back-office systems no longer drop files to a local Alliance Access server. They call RESTful APIs through the Swift Messaging API, optionally fronted by the Swift Microgateway, a single on-prem proxy that aggregates every SWIFT API service.

SWIFT is also retiring the legacy SWIFTRef files at end of November 2026. SWIFTRef Evolution exposes BICs, identifiers, LEIs, participants, SEPA, SSI, calendars and codes through APIs. On the network side, Alliance Connect Virtual on Premises VPN replaces the SRX hardware VPNs.

The Hub keeps the bank's messaging logic (validation, translation, routing, archive, audit) in one platform and talks to every party over APIs: back-office, SWIFT and reference data.

Channel 1

PMH → SWIFT via Microgateway & Alliance Cloud

The Hub connects to SWIFT through the Swift Microgateway in front of Alliance Cloud, over the Swift Messaging API. The SWIFT-managed gateway carries every MT and MX message. No Alliance Access partner, SIL or IPLA is needed.

  • Outbound MT and MX over the Swift Messaging API
  • Inbound messages consumed from the API queue, routed and archived
  • End-to-end non-repudiation when the Microgateway runs over the SIPN
  • No CSCF surface area for legacy IPLA/SIL components on your side
Channel 2

PMH ↔ SWIFTRef local API proxy

Prowide ships a companion Spring Boot application that loads SWIFTRef Evolution data into a local database and serves a REST API matching SWIFT's own /swiftrefdata/v5/ endpoints. PMH points to localhost instead of api.swift.com, with no application changes.

  • Drop-in API compatibility with swiftref_api.yaml
  • Cuts external API spend and removes the network hop on every BIC lookup
  • Works air-gapped or on slow links. Lookups never leave the perimeter
  • Same data model SWIFT publishes; daily/weekly refresh from SWIFTRef files
Channel 3

PMH REST API for back-office & tooling

The Hub exposes its own RESTful API. Payment systems, treasury, core banking and operations tooling submit, query, configure and reconcile over HTTP.

  • Submit MT and MX payments with JWT-authenticated POST
  • Search, status, archive retrieval and operator actions over HTTP
  • Configure routing rules, validation packs and translations programmatically
  • Legacy systems keep their queue and file connectors
End-to-End

Inside the bank, only the Hub

The Alliance stack moves out. The Hub stays in as the only messaging software the bank still operates. Deployment platforms and high availability are covered on the Messaging Hub page.
Payments back-office
Treasury / FX
Core banking
Ops tooling
↓
PMH REST API
Prowide Messaging Hub
Capture Validate Translate (MT ↔ MX) Route Archive & Audit REST API
↓
Swift Messaging API
Swift Microgateway
↓
Alliance Cloud
↓
SWIFTNet
↔
/swiftrefdata/v5/
SWIFTRef local API proxy
↑
SWIFTRef Evolution files
Zero Footprint

What leaves the data centre and what stays

"Zero footprint" means no SWIFT-branded boxes on premises. The bank still owns validation, translation, routing, archive and audit. That is the Hub's job.

What leaves

Alliance Access / Entry message partners
SIL (Swift Integration Layer) and IPLA
SRX hardware VPN appliances (over the SD-WAN transition)
Local SWIFTRef file processing scripts and ad-hoc loaders
Custom MQ bridges and file drops between back-office and Alliance
CSCF scope and patch burden for legacy SWIFT software
→

What stays (and the Hub owns it)

All MT and MX validation: SRG, CBPR+, HVPS+, regional clearings
MT ↔ MX translation with audit-grade traceability
Routing logic, 4-eyes authorization, business workflows
Centralised archive, full-text search, operator UI
BIC / IBAN / SSI lookups via the local SWIFTRef proxy
REST API surface for every back-office integration point
Related Solutions

Often deployed alongside

Infrastructure

IPLA/SIL Replacement

After 30 June 2026, IPLA and SIL are end-of-life and a CSP/CSCF liability. Going API-first removes them from your premises, and the same Hub deployment covers both.

Learn more →
Modernization

SWIFT Infrastructure Modernization

Consolidating fragmented on-prem SWIFT components is the prerequisite for moving cleanly to Alliance Cloud and API-first integration.

Learn more →
Infrastructure

Multi-Network Switch

Once SWIFT is just one of several API channels, the Hub can route the same ISO 20022 payload to SWIFT, domestic RTGS rails or instant schemes from one rules engine.

Learn more →

Going API-first with SWIFT?

Talk to our team about plugging the Messaging Hub into your Zero Footprint, Alliance Cloud or Microgateway setup.
Contact Us Explore Messaging Hub