On 30th June 2026, Swift will retire IPLA (Interface for Alliance Access) and SIL (Swift Integration Layer). For many banks, these technologies have quietly underpinned Swift connectivity for years – often out of sight, but deeply embedded in payments operations. With the deadline now just six months away, institutions face a clear choice: apply a short-term workaround or use this moment to modernise their messaging architecture.
When dependable plumbing becomes a constraint
Swift’s decision to retire IPLA and SIL reflects a fundamental shift in financial messaging. IPLA and SIL were designed to abstract Swift connectivity away from internal banking systems, acting as a stable integration layer for routing, validation and message transformation.
This model made sense in an era dominated by on-premise infrastructure, batch processing and tightly coupled legacy systems. For many institutions, IPLA and SIL became dependable plumbing, requiring little to no intervention once in place. But this is changing and that stability is part of the problem.
As the industry moves towards richer structured data, higher levels of automation, and API-driven and cloud-ready models, legacy integration layers are being stretched beyond their original purpose. IPLA and SIL were never built to support the real-time processing, validation and workflow complexity now required across modern payment flows.
The underlying technologies that IPLA and SIL rely on themselves are also reaching end of life. Maintaining them would increase cost, complexity and operational risk at a time when banks need more agility, not less.
The approaches banks are taking
As the deadline approaches, banks are typically considering one of four paths:
- Direct connectivity via Swift APIs and cloud services, reducing on-premise infrastructure but requiring strong internal orchestration capabilities.
- Like-for-like middleware replacement, which can reduce short-term risk but often recreates the same architectural constraints.
- A central messaging and orchestration platform, which consolidates Swift connectivity, internal routing, enrichment and exception handling in one place.
- A phased hybrid approach, combining short-term continuity with a clear roadmap towards modernisation.
In practice, many institutions are blending these approaches depending on geography, payment type and existing architecture. But what matters is not just meeting the deadline, but ensuring the chosen approach supports Swift’s future requirements for richer data and faster settlement cycles.
Why acting now matters
Leaving IPLA and SIL replacement until the last minute often leads to reactive decisions. That’s when banks resort to translation tools simply to keep payments flowing.
These fixes may buy time, but they paper over deeper issues. They fragment data, complicate audit trails and make future regulatory changes more difficult. As Swift continues to mandate richer datasets and structured workflows, those stopgaps quickly become liabilities.
Acting now allows banks to control the pace of change, align IPLA/SIL retirement with wider modernisation programmes, and avoid repeating the same cycle of short-term fixes.
How Aqua Global can help
Aqua Global works with banks to turn the IPLA/SIL deadline into a structured modernisation step, providing a single, modern messaging and orchestration layer that sits alongside existing core systems, rather than replacing them.
- A single interface to Swift: Aquila provides a centralised interface to Swift, supporting both FIN and ISO 20022 messaging and removing the need to manage multiple integration layers as standards evolve.
- Automated processing and orchestration: Messages from any internal or external source are automatically validated, enriched and routed through configurable workflows to improve straight-through processing and reduce manual effort.
- Full visibility and auditability: Every message, decision and exception is tracked end to end, giving operations and compliance teams real-time visibility, structured exception handling and a complete audit trail.
- Seamless integration with existing systems: Aquila integrates with core banking, AML and sanctions screening systems via APIs, enabling banks to modernise Swift connectivity without replacing critical infrastructure.
- Continuously updated, proven technology: Aquila is continuously enhanced to reflect industry and regulatory change, with updates delivered ahead of Swift deadlines and a proven track record supporting live, high-volume payment environments.
With six months to go, the question is no longer whether to act, but how. The right approach now can remove today’s dependency on IPLA and SIL and prevent the next generation of quick fixes from taking their place.
