Every merchant on Worldpay IPC is a conversation waiting to happen. Here’s how to have it. 

Worldpay is sunsetting IPC — the Windows/Java payment client that’s been running quietly on the till PC of thousands of UK merchants for over a decade. If any part of your merchant base connects through IPC, a fixed deadline is now on the calendar, and the hardware behind it is already past the point of manufacturer support.  

This guide is for EPOS providers: what’s actually changing, why “just upgrade” is the wrong advice to give your merchants, and how to turn a forced migration into a genuine value-add conversation rather than a support headache. 

Step 1: Know which of your merchants this impacts

Worldpay’s IPC has been retired in stages before, but this round is different in scale, and it’s about to land on your support desk whether you’ve prepared for it or not. The bulk of the IPC 2.3.x install base reaches end of life on 15 October 2026. That’s not an isolated software update. It arrives alongside a hardware problem that can’t be patched away: the terminals IPC typically runs on, Ingenico’s iPP350 and Verifone’s Vx820, are already manufacturer-end-of-life. 

That means any merchant still on this cohort is facing two forced changes tied to one fixed date — a software sunset and a hardware replacement — and most of them won’t see it coming until it’s urgent. 

Before you get into individual merchant conversations, it’s worth mapping your own exposure: 

• Which merchants in your portfolio are integrated via IPC on a till PC? 
• Do you know which IPC version each is running, and which PIN Entry Device it’s paired with? 

Blink Payment can help you map this at a portfolio level, what’s running, what’s connected, and where the exposure sits, so you’re going into merchant conversations with answers, not just a warning. 

Step 2: Don’t lead your merchants toward “upgrade in place”

Worldpay’s own retention path is to move affected merchants onto IPC 2.4.1 or 2.4.2 — same architecture, same terminal category, same on-premises model, just a later sunset clock. It’s the path of least resistance for you as a partner, too: fewer conversations, less reintegration work, nothing to resell. 

But it’s worth being clear-eyed with yourself and with your merchants about what that actually buys them: 

• IPC 2.4.1 sunsets October 2027 
• IPC 2.4.2 sunsets March 2028 

Some of your merchants may already be getting migrated onto 2.4.2 as an interim step off older, already-expired versions. That can be a reasonable short-term fix if a merchant is mid-contract or you’re mid-project with them. But it isn’t a strategic recommendation to be making as their integration partner. Point merchants at “upgrade in place” today, and in 12–24 months you’re both back here: same forced migration, same support burden, no new capability gained in the meantime. 

IPC itself, as an architecture, is being phased out. It’s a Windows/Java client, installed locally, serially or USB-connected to a PED (PIN Entry Device): a design built for a 2010s till estate. Worldpay’s own stated direction is IPS Cloud (Integrated Payment Server Cloud), a cloud-hosted orchestration layer that removes the local middleware entirely. Read between the lines, IPC’s sunset dates are just future maintenance windows, not a real resolution for the merchants relying on you to advise them properly. 

Step 3: Position the migration as an upgrade, not just a compliance fix

This is the real opportunity sitting in your merchant base: you can bring them a genuine architecture upgrade and be the provider who delivered it. 

And it’s worth being upfront that Worldpay’s own answer here — IPS Cloud — is a genuine cloud platform too. The real distinction isn’t on premises vs. cloud. It’s what kind of cloud platform a merchant ends up on once they’re forced to migrate anyway. 

Broadly, there are three directions a merchant coming off IPC can go in: 

1. Staying with legacy IPC means sticking with locally installed software on a till PC, tied to specific ageing terminals, with updates and troubleshooting happening on-site. It’s the model being phased out, and the one causing this whole situation in the first place. 
2. Moving to Worldpay’s own IPS Cloud takes the local middleware out of the picture, which is a real improvement: centralised updates, less on-site maintenance, a more modern foundation. It’s a sensible option for merchants who want to stay put and are happy with a card-present-focused setup on a single acquirer. 
3. Moving to an all-in-one cloud platform like Blink Payment starts with the same cloud foundation but expands what the migration delivers: card-present sitting alongside online, MOTO, pay-by-link, and other payment methods in one account, rather than solving card-present in isolation. 

None of these is wrong; it depends on what a merchant actually needs. But since a migration project is happening either way, it’s worth merchants (and you, as their advisor) weighing up whether they just want out of IPC or would rather use the moment to consolidate payments more broadly. That’s the conversation worth having before anyone defaults to the nearest like-for-like option. 

Step 4: Migrate merchants without creating a repeat support cycle

A well-planned migration off IPC should leave your merchants and your support desk further ahead than before, not just compliant for another cycle. As their integration partner, that typically means: 

• Confirming which terminals and connections are being replaced across your portfolio, not just re-licensed 
• Making sure each EPOS or booking integration is tested end-to-end before go-live, not patched live on a busy trading day 
• Aligning transaction data and reporting with each merchant’s existing finance processes and accounting software 
• Having hands-on support through testing and cutover, so neither you nor your merchants are carrying the migration risk alone 

Done properly, this is a one-time project for each merchant. 

Why Blink Payment is a genuine IPC replacement for your merchant base

Blink Payment’s card-present integration runs on Verifone terminals with a cloud-based payment infrastructure from the outset; it was never built around local middleware. That’s already the architecture Blink Payment runs on. Every estate should be assessed individually, but the direction is the same one Worldpay itself is pointing towards with IPS Cloud — cloud-native, not on-premises. That makes this an easier conversation to have with merchants: you’re not asking them to bet on an unproven alternative, you’re moving them where the market is already heading. 

Blink Payment is the whole payment operation, something you can put your name behind with every merchant you migrate. 

Online, in person, and over the phone payments are in one account and a single dashboard, with the UK-based support team behind you and your merchants. 

• One platform, every channel — Online, in-store, and over the phone payments are consolidated in a single account. Paylinks, hosted payment pages, online API, card machines, and virtual terminal are stitched together in one platform. 
• More ways to get paid — Cards, open banking, Direct Debit, and digital wallets sit alongside each other, so customers pay the way and time that suits them, not just card-at-terminal. 
• No install, live in about a week — Cloud API and hosted pages mean nothing to install on every till. No IPC-style middleware to configure per terminal. 
• Choice of acquirer, better rates — Route across AIB, Elavon, Cashflows, and OBN instead of being locked to one acquirer’s roadmap. 
• Reconciliation built in — Payments, invoices, and refunds are matched automatically, plus automated re-run of failed payments are not just captured but reconciled. 
• People-powered UK support — A named team on live chat, WhatsApp, email, and phone.  

Frequently asked questions about the Worldpay IPC sunset for partners

What is Worldpay IPC? 

IPC (Integrated Payments Client) is the payment software that runs locally on a till PC or server, routing transactions between an EPOS system and a connected card terminal. It’s part of the older, on-premises Worldpay Total architecture, and it’s embedded in a big chunk of merchant integrations in the hospitality sector. 

When is Worldpay IPC being retired? 

The main IPC 2.3.x cohort reaches end of life on 15 October 2026. Worldpay is offering upgrade paths to IPC 2.4.1 (sunsetting October 2027) and IPC 2.4.2 (sunsetting March 2028) as interim steps, but the underlying architecture is being phased out in favour of IPS Cloud.  

Should I recommend my merchants upgrade to Worldpay IPC 2.4.1 or 2.4.2? 

It’s a reasonable stopgap for merchants who are mid-contract or can’t move immediately, but it shouldn’t be your default advice. Both versions are on published sunset clocks of their own — 12 to 24 months out — so merchants who upgrade in place are likely to be back in the same conversation with you again, with nothing gained for the delay. 

Why are my merchants’ terminals affected as well as the software? 

IPC on the older cohort typically runs on Ingenico iPP350 and Verifone Vx820 terminals, both of which are already manufacturer-end-of-life. That means the sunset isn’t purely a software update for the merchants you support; a hardware refresh is bundled into the same deadline. 

What should I be recommending instead? 

Moving affected merchants to a cloud-based payment platform removes the on-premises middleware layer entirely, rather than replacing it with a newer version of the same model. Blink Payment platform, with its card-present API for in-person payments, is built this way from the ground up, and is designed to integrate cleanly with EPOS systems. 

How long does migrating a merchant off IPC take? 

This depends on how deeply IPC is embedded in each merchant’s setup, but most merchants moving to Blink Payment are live within about a week, and manageable across a portfolio migration without a long project tail. 

Do I need to get ahead of the 15 October 2026 deadline? 

Yes. Waiting until the deadline increases the risk of a rushed, reactive integration process and migration across your merchant base, with less time to test integrations properly, and less room to plan around each merchant’s busy trading periods.