IPLA/SIL Replacement
Unsupported software, no patches
Control 2.2 (Security Updates) requires in-scope components to run vendor-supported, security-patched software. Once SWIFT support ends and the underlying Red Hat Fuse framework is end-of-life, IPLA/SIL can no longer receive security updates -- so 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) becomes mandatory in CSCF v2026. IPLA and SIL sit on exactly this path -- between your back-office systems and the SWIFT interface -- so an unsupported component there is squarely in scope, not an edge case you can argue away.
The forcing function
The annual CSP attestation against CSCF v2026 runs from July to December 2026 -- you attest during the very window your middleware is unsupported. Any gap must be remediated or formally risk-accepted and declared, visible to your independent assessor and to counterparties that consume your attestation.
IPLA (Alliance Access Integration Platform) and SIL (SWIFT Integration Layer) are middleware components from 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 ends support for both on 30 June 2026, driven primarily by Red Hat Fuse reaching end-of-life -- the integration framework that underpins SIL -- and the broader shift toward ISO 20022 and API-driven connectivity.
They remain in CSCF scope right up to the cut-off. After it, the capabilities they provide still have to run -- but on a supported platform. The task is to lift those flows off the end-of-life components without breaking SWIFT connectivity and without a finding at attestation time.
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. 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 |
|---|---|---|
| Vendor support & security patches | End-of-life after 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.
Your remediation 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 -- covering transformation, routing, workflow, and back-office connectivity in a single supported platform.
For IPLA users, the Hub replaces all the custom integration logic you've built on top of IPLA, eliminating the in-house middleware code you can no longer keep patched. Your Alliance Access interface continues to handle SWIFT network connectivity.
In both cases, the priority is the same: remove the unsupported component first. Modernization beyond a like-for-like swap -- MT↔MX translation, web-based operations, intelligent message entry, ISO 20022 -- is real upside, but it's Phase 2, on your timeline, not a precondition for getting compliant.
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
With the unsupported components decommissioned, use the same platform to consolidate fragmented middleware, add MT↔MX translation, and move toward an ISO 20022-native future -- on your schedule, free of deadline pressure.
ISO 20022 Translation
Automatic bidirectional MT↔MX translation with CBPR+ compliance and regional clearing support -- ready when you choose to adopt it, 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. Institutions begin planning.
Support ends
SWIFT ceases 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 now unsupported software in your CSCF scope -- a Control 2.2 gap on a component sitting in the Control 2.4 back-office data flow.
CSP attestation deadline
The year-end forcing function. You attest against CSCF v2026 with the unsupported component either remediated -- or written up as a declared gap for your assessor and counterparties to see.
Messaging Hub
A single supported platform that replaces IPLA/SIL middleware with modern, GUI-driven message management. Deploy on-premises or in your own private cloud (e.g., Amazon Web Services), managed entirely by you, with full control over your infrastructure.