IPLA/SIL Replacement
Since 30 June, IPLA/SIL is a compliance liability
Unsupported software, no patches
Control 2.2 (Security Updates) requires in-scope components to run vendor-supported, security-patched software. With SWIFT support ended and Red Hat Fuse end-of-life, IPLA/SIL receive no security updates. The control cannot be satisfied while they remain in production.
It sits in the back-office data flow
Control 2.4 (Back Office Data Flow Security) is mandatory in CSCF v2026. IPLA and SIL sit on exactly this path, between your back-office systems and the SWIFT interface. An unsupported component there is squarely in scope.
The forcing function
The annual CSP attestation against CSCF v2026 runs from July to December 2026, while your middleware is unsupported. Any gap must be remediated or formally risk-accepted and declared. Your independent assessor and the counterparties that consume your attestation will see it.
Where the Messaging Hub fits
| Capability | IPLA / SIL | Prowide Messaging Hub |
|---|---|---|
| Vendor support & security patches | End-of-life since 30 Jun 2026 | Supported, continuously patched |
| CSP / CSCF posture | Control 2.2 gap; sits in 2.4 flow | Supported component, clean attestation |
| 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 |
| SWIFT SRG updates | End-of-life | Annual updates, Early Release by May |
Rapid Replacement — like-for-like, in 90 days
A fixed-scope program that lifts your existing IPLA/SIL flows onto the Messaging Hub exactly as they run today -- same message types, same routing, same back-office connections. No redesign, no scope creep. You decommission the unsupported components and attest clean, on a timeline you can put in front of an auditor.
What's in scope
- Full inventory of your current IPLA/SIL flows, message types, routing rules and back-office connections
- Like-for-like rebuild on the Messaging Hub through GUI configuration -- transformation, routing, connectors
- Parallel run alongside the existing setup, with output reconciliation
- Cutover and decommissioning of the end-of-life components
- A documentation pack mapping the new platform to your CSP/CSCF controls for attestation evidence
Deliberately deferred to Phase 2
- New ISO 20022 / MX message flows beyond what you run today
- New channels, clearings or counterparties
- Business-process redesign or re-engineering of existing flows
- Net-new functionality such as message entry or business matching
The Hub supports all of this -- you simply adopt it later, on your own schedule, once the liability is gone.
Discovery & flow inventory
Map every flow currently on IPLA/SIL -- message types, routing rules, transformations and back-office connections. Lock the fixed scope.
Like-for-like build
Configure the equivalent flows on the Messaging Hub through visual rules -- no custom code. Each flow validated against its current behaviour.
Parallel run & reconcile
Run the Hub alongside the existing setup and reconcile outputs message-by-message until they match. No big-bang switch.
Cutover & evidence
Switch production to the Hub, decommission IPLA/SIL, and hand over the CSP/CSCF evidence pack for your attestation.
Whether you run IPLA or SIL
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.
Support ended
SWIFT ceased support for IPLA and SIL. No further security updates for the components or the Red Hat Fuse framework beneath SIL.
The liability is live
Every running instance is unsupported software in your CSCF scope: a Control 2.2 gap on a component in the Control 2.4 back-office data flow.
CSP attestation deadline
You attest against CSCF v2026 with the unsupported component either remediated or declared as a gap for your assessor and counterparties to see.
Full platform replacement
The Hub replaces SIL entirely: message transformation, routing, back-office connectors, and workflow orchestration, on a supported platform that stays current with SWIFT standards.
Custom code elimination
Replace custom-built IPLA integration logic with GUI-driven configuration. No more maintaining transformation code, routing scripts, or adapter patches on an end-of-life base. Your Alliance Access stays in place for network connectivity.
Once the liability is gone
Use the same platform to add MT↔MX translation and web-based operations, move toward ISO 20022, and consolidate fragmented middleware. On your schedule, free of deadline pressure.
Prowide Messaging Hub
Messaging Hub
Deploy on-premises or in your own private cloud (e.g., Amazon Web Services), managed entirely by you, with full control over your infrastructure.