Skip to Content

SIL-IPLA Replacement


Plan your move off IPLA and SIL before support ends

SWIFT is moving to zero-footprint, API-driven integration. 
IPLA support ends on 30 June 2026, and Alliance Access 7.9 runs without it. If your integration depends on IPLA or SIL, you need a path that keeps payments flowing and preserves your custom logic.


Talk to Swift Expert!
What it is.

Modern Integration for Alliance Cloud

The Netlink Integration Platform (NIP) replaces IPLA and SIL with a standalone, SWIFT-certified integration layer that connects your back office to Alliance Cloud using zero-footprint APIs.

Why it matters.

Replace Legacy IPLA and SIL Integrations

IPLA reaches end of support on 30 June 2026. Access 7.9 requires Alliance Cloud and provides no IPLA. Without a replacement, custom integrations built on IPLA or SIL stop being supported.

How it helps.

Simplify Connectivity and Reduce Maintenance

NIP decouples integration from the messaging interface, so maintenance effort drops. It runs on-premises or in the cloud and carries GPI, Pre-validation, and screening modules.

Your three-step migration path

1

Explore

Align your IPLA use cases with your roadmap, decide between a like-for-like replacement or a broader change, and identify third-party and vendor dependencies.

2

Assess

Audit existing custom code and workflows, map requirements to NIP connectors, APIs, and modules, and define your target architecture across on-premises, cloud, or hybrid.

3

Execute

Set governance, milestones, and resource plans, migrate connectors, APIs, and custom logic, run end-to-end testing, then go live and retire IPLA.

Overview


SWIFT Access versions have defined support windows. Reading them against your own upgrade plan shows how much time you have and which version you are moving toward.


Version
Position on IPLA
End of support
Access 7.7Runs with IPLA. IPLA support ends first.IPLA: 30 June 2026. Access 7.7: 30 June 2027.
Access 7.8No IPLA developer seat. All business modules available.31 January 2028.
Access 7.9Runs without IPLA. Zero-footprint APIs. Alliance Cloud required.

Current target for a low-maintenance setup.


NIP is a SWIFT Certified Enabler under partner codes PTSQGBBB and ETPXGB35. It is modular, so you integrate only the parts you need, and it coexists with Alliance Cloud or legacy systems without forced bundling.

The platform maps and translates between MT and MX and ISO 20022, runs GPI, Pre-validation, and Case Management workflows, and integrates with your back office with limited change. Deployment supports on-premises, cloud-native, and hybrid models, so the target architecture can match your operational and compliance constraints.

Benefits


 Continuity through the change

Keep payments flowing as IPLA and SIL retire, with custom logic preserved and migrated.


 Lower maintenance effort

Replacing IPLA and SIL with a standalone platform decouples integration from interface upgrades.


 Alliance Cloud compatible

Zero-footprint APIs connect to Alliance Cloud for a lower-maintenance setup.


 Swift Essentials ready

GPI, Pre-validation, and screening modules integrate into the same platform.

FAQs

IPLA support ends on 30 June 2026. Alliance Access 7.7 support ends on 30 June 2027, and Access 7.8 on 31 January 2028. Access 7.9 runs without IPLA and requires Alliance Cloud.

During the Assess step, existing custom code and workflows are audited and mapped to NIP connectors, APIs, and modules, then migrated during Execute so your logic is preserved.

IPLA support ends on 30 June 2026. Alliance Access 7.7 support ends on 30 June 2027, and Access 7.8 on 31 January 2028. Access 7.9 runs without IPLA and requires Alliance Cloud.

Both. NIP supports on-premises, cloud-native, and hybrid deployment, so the target architecture can match your operational and compliance constraints.

Yes. It is a SWIFT Certified Enabler under partner codes PTSQGBBB and ETPXGB35, aligned to SWIFT integration standards.
No. NIP is modular. You integrate only what you need, and it coexists with Alliance Cloud or legacy systems without forced bundling.

Contact us

Have a question? We're here to help with your SWIFT journey.

Submit