IPLA/SIL Replacement

SWIFT no longer supports IPLA and SIL. Every instance still running is unsupported software in your SWIFT data flow, a Customer Security Programme control gap that stays open until the component is replaced. Prowide replaces it with a supported, ISO 20022-ready platform in a fixed 90-day program.
!
Compliance risk: SWIFT no longer supports IPLA and SIL. While they run, they are unsupported software in your CSP/CSCF scope, to be remediated or declared at every attestation.

Unsupported middleware is a compliance liability

IPLA (Alliance Access Integration Platform) and SIL (SWIFT Integration Layer) sit between your back-office systems and the SWIFT network. They handle message transformation, routing, and integration with Alliance Access or Alliance Lite. SWIFT ended support for both in June 2026, driven mainly by Red Hat Fuse, the framework under SIL, reaching end-of-life. The gap does not close on its own: it comes back at every Customer Security Programme attestation.
CSCF Control 2.2

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.

CSCF Control 2.4

It sits in the back-office data flow

Control 2.4 (Back Office Data Flow Security) is a mandatory CSCF control. 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.

Annual Attestation

Declared every year

Every annual CSP attestation taken while IPLA/SIL is in production carries the gap. It must be remediated or formally risk-accepted and declared, and your independent assessor and the counterparties that consume your attestation will see it.

Where the Messaging Hub fits

The Messaging Hub runs behind your SWIFT interface. It replaces the end-of-life middleware layer and keeps your existing SWIFT network connectivity.
SWIFT Network
Alliance Access / Alliance Lite / Alliance Cloud
↕
Middleware
Prowide Messaging HubReplaces IPLA/SIL
↕
Back-Office
Core Banking · Treasury · Trade · Payments · Other Systems
CapabilityIPLA / SILProwide Messaging Hub
Vendor support & security patchesEnd-of-life, no security patchesSupported, continuously patched
CSP / CSCF postureControl 2.2 gap; sits in 2.4 flowSupported component, clean attestation
Message transformationCustom code / configGUI-driven rules + MyFormat engine
MT↔MX translationLimited / manualAutomatic, 40+ message pairs, CBPR+
Message routingConfiguration-basedVisual rule builder with content-based routing
Back-office connectivityFile / queue adaptersFile, queue, database, API connectors
SWIFT compliance validationBasic format checksFull semantic rules + CBPR+ usage guidelines
ISO 20022 readinessNot fully supportedNative MX support, coexistence ready
Web-based operations UINoFull message browse, search, monitoring
Message entry & initiationNoIntelligent forms with BIC auto-complete
SWIFT SRG updatesEnd-of-lifeAnnual 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 plan you can put in front of an auditor.

Fixed
Fixed scope & deliverables -- no open-ended transformation program
90 days
From kick-off to cutover, with a parallel run before you switch
Like-for-like
Your flows, replicated -- nothing new to learn, nothing to redesign

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

The Hub supports all of this -- you simply adopt it later, on your own schedule, once the liability is gone.

Weeks 1–2
Discovery & flow inventory

Map every flow currently on IPLA/SIL -- message types, routing rules, transformations and back-office connections. Lock the fixed scope.

Weeks 3–8
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.

Weeks 9–11
Parallel run & reconcile

Run the Hub alongside the existing setup and reconcile outputs message-by-message until they match. No big-bang switch.

Week 12
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

The Messaging Hub replaces both. In either case, remove the unsupported component first. Modernization beyond a like-for-like swap is Phase 2, on your own schedule.
Support ended

No more updates

SWIFT no longer supports IPLA and SIL. No security updates for the components or the Red Hat Fuse framework beneath SIL.

While it runs

An open control gap

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.

Every attestation

Declared, year after year

Each annual CSP attestation has to show the component remediated or declared as a gap for your assessor and counterparties to see.

After replacement

Clean attestation

With the Messaging Hub in place and IPLA/SIL decommissioned, the gap is closed and your next attestation is clean.

SIL Replacement

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.

IPLA Replacement

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.

Phase 2: Modernization

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 own schedule.

Prowide Messaging Hub

One supported platform that covers everything IPLA and SIL did, delivered through the fixed-scope Rapid Replacement package.
On-Premises Platform

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.

Full IPLA/SIL capability replacement
Vendor-supported, continuously patched
CSP/CSCF evidence pack for attestation
Visual rule configuration -- no coding
Docker / VM / bare-metal deployment
Basic, Silver, or Gold support plans
Explore Messaging Hub →

Ready to replace IPLA/SIL?

Talk to our team about your current IPLA/SIL flows, your infrastructure, and the shortest path to a supported messaging platform.