IPLA/SIL Replacement
IPLA (Alliance Access Integration Platform) and SIL (SWIFT Integration Layer) are middleware components provided by SWIFT that sit between your back-office systems and the SWIFT network. They handle message transformation, routing, and integration with Alliance Access or Alliance Lite.
SWIFT has announced that both products will be discontinued on June 30, 2026, driven primarily by Red Hat Fuse reaching end-of-life -- the integration framework that underpins SIL -- and the broader industry shift toward ISO 20022 and API-driven, cloud-native connectivity.
Institutions currently relying on IPLA or SIL must replace the middleware capabilities these products provide -- while maintaining uninterrupted SWIFT connectivity and, ideally, using the transition as an opportunity to modernize their messaging infrastructure.
IPLA
Integration platform for Alliance Access. Enables communication between back-office systems and SWIFT, supporting custom message transformation, routing, and data enrichment. Requires significant in-house development and maintenance.
SIL
Higher-level integration layer built on Red Hat Fuse, with message routing, transformation, and back-office connectivity out of the box. Configuration-driven approach to message workflows. Being retired as Red Hat Fuse reaches end-of-life.
Message Transformation
Converting messages between formats -- MT to back-office proprietary formats, MX to internal systems, field mapping, enrichment, and data extraction.
Message Routing
Directing messages to the right back-office system or SWIFT destination based on message type, content, BIC, currency, or custom business rules.
Back-Office Connectivity
Interfacing with core banking systems, treasury platforms, trade systems, and other internal applications via file drops, queues, databases, or APIs.
Workflow Orchestration
Sequencing operations such as validation, enrichment, authorization, and delivery -- with error handling, retry logic, and exception management.
Validation & Compliance
Ensuring messages comply with SWIFT network rules, usage guidelines, and internal policies before transmission to the network.
Monitoring & Audit
Tracking message status, generating audit trails, producing operational reports, and alerting on failures or exceptions.
For IPLA users: The Hub replaces all custom transformation and routing logic. You keep your Alliance interface for SWIFT network connectivity.
| Capability | IPLA / SIL | Prowide Messaging Hub |
|---|---|---|
| Message transformation | Custom code / config | GUI-driven rules + MyFormat engine |
| MT↔MX translation | Limited / manual | Automatic, 40+ message pairs, CBPR+ |
| Message routing | Configuration-based | Visual rule builder with content-based routing |
| Back-office connectivity | File / queue adapters | File, queue, database, API connectors |
| SWIFT compliance validation | Basic format checks | Full semantic rules + CBPR+ usage guidelines |
| ISO 20022 readiness | Not fully supported | Native MX support, coexistence ready |
| Web-based operations UI | No | Full message browse, search, monitoring |
| Message entry & initiation | No | Intelligent forms with BIC auto-complete |
| Business matching | No | Rule-based MT matching for Treasury & Securities |
| Deployment | On-premises | On-premises (Docker / VM / bare metal) |
| SWIFT SRG updates | End-of-life | Annual updates, Early Release by May |
Your migration path depends on which product you currently run. Institutions typically use either IPLA or SIL -- and the Messaging Hub replaces both, with a tailored approach for each.
For SIL users, the Messaging Hub provides a full like-for-like replacement and more -- covering transformation, routing, workflow, and back-office connectivity in a single platform.
For IPLA users, the Hub replaces all the custom integration logic you've built on top of IPLA, eliminating the need to maintain in-house middleware code. Your Alliance Access interface continues to handle SWIFT network connectivity.
Either way, the transition is an opportunity to modernize beyond a like-for-like swap. The Hub adds capabilities that neither IPLA nor SIL ever offered -- MT↔MX translation, web-based message operations, intelligent message entry, and built-in ISO 20022 readiness.
Full platform replacement
The Hub replaces SIL entirely -- message transformation, routing, back-office connectors, and workflow orchestration. Everything SIL did, plus ISO 20022 translation, message entry, and a web operations dashboard.
Custom code elimination
Replace custom-built IPLA integration logic with GUI-driven configuration. No more maintaining transformation code, routing scripts, or adapter patches. Your Alliance Access stays in place for network connectivity.
Consolidate and modernize
Use the IPLA/SIL retirement as the catalyst to consolidate multiple middleware systems and fragmented infrastructure into a single centralized platform. Reduce operational complexity and prepare for a fully ISO 20022-native future.
ISO 20022 Translation
Automatic bidirectional MT↔MX translation with CBPR+ compliance and regional clearing support -- ready for migration today, not after years of development.
Web-Based Operations
Browse, search, and monitor messages through a modern web interface. No command-line tools, no terminal sessions -- full operational visibility from the browser.
Message Entry & Initiation
Create payment instructions with intelligent forms, BIC auto-complete, and field validation. Enforce 4-eyes authorization workflows for outgoing messages.
GUI Configuration
Configure transformation rules, routing logic, and message workflows through visual tools -- no custom code to write or maintain. Configuration over code.
Business Matching
Real-time matching of trade confirmations for Treasury and Securities. User-defined matching rules independent of counterparty systems.
Future-Ready Architecture
On-premises deployment with Docker support, REST APIs, and a platform designed for the ISO 20022 era -- not a legacy product approaching end-of-life.
SWIFT announces retirement
SWIFT confirms IPLA and SIL will be discontinued, driven by Red Hat Fuse reaching end-of-life and the shift to ISO 20022.
Migration planning window
Institutions assess their current IPLA/SIL usage, evaluate replacement options, and begin planning their migration.
IPLA & SIL support ends
SWIFT ceases all support for IPLA and SIL. Institutions must have their replacement fully deployed and operational by this date.
Next SWIFT SRG go-live
The annual Standards Release Guide goes live. Your replacement must be capable of absorbing SRG changes -- Prowide delivers Early Release updates by May.
Messaging Hub
A single platform that replaces IPLA/SIL middleware with modern, GUI-driven message management. Deploy on-premises or in your private cloud with full control over your infrastructure.