Fiserv Is Retiring a Dozen Gateways. Only 68 US Profiles Say ISO 8583
Fiserv cut 3,000 roles since June with no single layoff date. Here's how to find its switch, gateway, and VisionPLUS engineers by platform name and city.
If you hire engineers who understand how a card authorization actually moves, Fiserv is releasing them, but not on any date you can put in a calendar. Its new CEO says 3,000 employee and contractor roles have been cut since June, and more than a dozen legacy gateways and switches are being shut down. The catch is that there was no layoff day, and most of these engineers never put "Fiserv" or "ISO 8583" anywhere you would think to search.
What did Fiserv announce on its Q3 2026 call?
Fiserv said it has cut 3,000 employee and contractor roles since June 2026, including more than 10% of senior management. It also doubled its Elevate savings target from $500M to $1B and said it will retire more than a dozen legacy gateways and switches while exiting non-core products.
Here is what the call and the coverage around it confirmed:
- New CEO, new math. Takis Georgakopoulos was appointed CEO on June 15, 2026, after Mike Lyons left to run Truist. In his words: "since I took over as CEO, we have reduced contractors and employees by 3,000 people, including a more than 10% reduction of senior management."
- Activist pressure. The target went to $1B after Jana Partners pushed Fiserv to aim for $1.25B in savings.
- Gateway consolidation. Fiserv is consolidating onto Commerce Hub, which management said "will allow us to remove the complexity of supporting more than a dozen legacy gateways and switches around the world."
- Divestitures in progress. "We are in conversations with multiple parties with NDAs and processes in place." The products being exited serve very few clients.
- Earlier pruning. Selling the student loan servicing and managed ATM businesses cost Fiserv roughly 100 basis points of Q3 adjusted revenue. Last year it also cut its core technology services platforms from 16 to five.
For scale, Fiserv had more than 38,000 employees at the end of 2025, and Georgakopoulos referred to "our 14,000 engineers" on the call. If all 3,000 cuts had been employees, that would be about 7.9% of headcount. Treat that as an upper bound, because the 3,000 includes contractors.
Why is there no single Fiserv layoff date?
The cuts started when Georgakopoulos took over in June and have continued as a steady stream ever since. Fiserv also says the new savings "will largely come beyond the 2027 time frame." So searching news for "Fiserv layoffs 2026" will give you the headline, but it won't give you the people.
The reason is how a gateway gets retired. A gateway is the entry point merchants send card transactions through. A payment switch routes those authorization messages between acquirers, card networks, and issuers. Neither can simply be turned off. Fiserv's stated approach is to move clients onto Commerce Hub first and shut the old system down afterward. The engineers who know a legacy platform stay until its last merchant has moved, and then they become optional.
For a sourcer, that has three consequences:
- Supply arrives in batches through 2027 and 2028. Each gateway shutdown frees a different group of specialists.
- Profiles update late. People leaving in a slow trickle rarely announce it, and few switch on an open-to-work banner on day one.
- Many leavers never listed Fiserv at all. The 3,000 explicitly includes contractors, and contractors usually list their staffing or services firm as their employer.
Why does an ISO 8583 skill search miss almost everyone?
In Refolk's index of professional profiles, only 68 US profiles list ISO 8583 as a skill. Fiserv alone has 14,000 engineers and has run First Data's switches since 2019. Switch engineers describe their work by platform name, or they don't describe it at all.
ISO 8583 is the message standard for card transactions: the format an authorization request travels in from terminal to acquirer to network to issuer. Everyone who works on a switch uses it every day, and that is exactly why almost nobody lists it. To them it's plumbing. They'll write "Buypass authorization" or "VisionPLUS batch" before they'll write the name of the message spec.
India's numbers are bigger but follow the same pattern. Refolk's index has 206 ISO 8583-tagged profiles there, about three times the US count, concentrated in Bengaluru, Mumbai, Noida and Pune.
| Signal | Count | Source |
|---|---|---|
| US profiles with ISO 8583 as a skill | 68 | Refolk's index |
| India profiles with ISO 8583 as a skill | 206 | Refolk's index |
| India-to-US ratio | 3.0x | Derived |
| Fiserv roles cut since June | 3,000 | Q3 2026 call |
| Fiserv engineers | 14,000 | Q3 2026 call |
| US ISO 8583 profiles vs. Fiserv engineers | ~0.5% | Derived, illustrative |
That last row is only an illustration, since the 68 profiles don't all come from Fiserv. But it shows the problem. If you run ISO 8583 developer recruiting the usual way, with a skill filter and a keyword string, you end up with the same few dozen people, many of them already employed at Capital One, JPMorganChase and Citi. You spend weeks on that list, and then you widen the search to "payments engineer" and drown in API integrators who have never touched an authorization host.
Which platform names should replace the keyword?
Search the legacy platform names, because those are the words switch and issuing engineers actually put on their profiles. The most useful ones are Nashville, Buypass, Cardnet, Omaha, RapidConnect, STAR and VisionPLUS, plus Commerce Hub for the engineers doing the migration.
The platform names have long outlived the companies that built them. Merchant integrations still connect directly to Nashville, Buypass or Cardnet, which are separate from RapidConnect. Authorize.net still lists the FDMS Omaha and Nashville processing platforms as supported processors. VisionPLUS, the card-issuing platform First Data acquired in 2001, is described by one G2 reviewer as "Designed using Legacy Programming Languages (COBOL..)", which means its engineers often look like mainframe developers, not payments engineers.
| Search term | What it is | Pair it with |
|---|---|---|
| Commerce Hub | Fiserv's consolidation gateway | Migration, cutover, current Fiserv |
| Buypass | Legacy platform separate from RapidConnect | "First Data", authorization |
| Cardnet | Legacy platform separate from RapidConnect | "First Data", host, switch |
| Nashville | Legacy merchant platform and FDMS processing platform | "FDMS", processing |
| Omaha | FDMS processing platform | "FDMS", First Data dates |
| VisionPLUS | COBOL-era card-issuing platform | COBOL, mainframe, issuing |
Omaha and Nashville are also city names, so on their own they return every banker in Nebraska and Tennessee. Always pair them with "FDMS," "processing," or a First Data employment date range.
Boolean strings fall apart at this point. You need platform OR platform, crossed with past employer OR services firm, crossed with a metro, and then someone has to read each result to check whether "Omaha" means the platform or the address. That's the gap Refolk closes: you describe the engineer in plain English and get back a ranked shortlist with the platform evidence behind each match.
Where are former First Data engineers now?
In the US, ISO 8583-tagged profiles cluster in Dallas-Fort Worth, Atlanta, Plano, Tampa, Orlando and Mount Laurel, NJ, which is the old First Data footprint. Their current employers include Capital One, JPMorganChase, Bank of America, Citi, TCS and Wipro. In India, the pool centers on Bengaluru, Mumbai, Noida and Pune.
The geography tells you something. The clusters suggest these engineers didn't scatter after 2019. They stayed in the old First Data metros, and the big banks hired them locally. If you hire payment switch engineers for a bank or a fintech, a Dallas-Fort Worth or Atlanta search with platform terms will beat a nationwide skill search.
The "First Data" keyword trap
A US headline search for "First Data" in Refolk's index returns 9,631 matches, and most of the top titles are founders and CTOs. That isn't a list of former First Data engineers. It's generic "first data..." wording polluting the results. Narrow it with at least one of these:
- A platform name from the table above.
- A First Data metro: Omaha, Atlanta, Dallas-Fort Worth or Tampa.
- A past-employment date filter, so "First Data" has to appear as an employer and not as a phrase.
The contractor pool is bigger than it looks
In the India sample of 25 ISO 8583 profiles, Capgemini (4), TCS (3) and Wipro (2) account for 9, more than a third. Since Fiserv's 3,000 cuts include contractors, many 2026 leavers will show a services firm as their employer and mention Fiserv, if at all, only in a project description. Search for the services firm plus the platform name, not the services firm plus "Fiserv."
When will each group come loose, and who leaves with a buyer?
Expect Fiserv's legacy engineers to become available in stages through 2027 and 2028, one group per gateway shutdown, and some of them never to hit the open market at all because they move with a divested product. Management has said most of the savings land "beyond the 2027 time frame," which matches a long migration, not a single wave.
The sequence goes like this:
- Migration phase. Engineers on a legacy gateway get pulled into moving clients to Commerce Hub. They're busy and kept on, but they're also seeing their platform's end date up close.
- Shutdown phase. Once the last merchant moves, the gateway's specialists are surplus. This is your window.
- Divestiture phase. For the non-core products under NDA talks, whole teams could transfer to a buyer. They change employers without ever being "laid off."
A divested team doesn't show up as a layoff. It shows up as a new logo next to an old product name.
Watch for that pattern on profiles: a new employer listed alongside a familiar Fiserv product. Those people are worth a call once the buyer's plans for the product become clear. Re-running the same plain-English search in Refolk every few weeks will surface those profile changes as they happen, which is easier than rebuilding boolean strings each time Fiserv announces a deal.
How should you pitch a payments switch engineer leaving Fiserv?
Lead with the platform they know and the problem it solves at your company, not with the layoff. These engineers have watched 3,000 colleagues leave since June, and a generic "sorry to hear about Fiserv" message reads like every other one in their inbox.
What works for this group:
- Name the platform. "You ran Buypass authorization" shows you read the profile. "Payments experience" doesn't.
- Sell the migration skill. Anyone who moved clients onto Commerce Hub has done a live cutover of a production switch. That is rare experience for any team running an old host.
- Offer contractors a full-time path. Many people in the 3,000 were contractors. A permanent role at a bank is a real upgrade from a services-firm contract.
- Time outreach to shutdowns, not headlines. The news cycle peaked with the Q3 call. The people peak whenever their gateway goes dark.
- Pitch senior leaders on scope. More than 10% of senior management is gone. Directors who ran platform groups want ownership, not a lateral move.
FAQ
How many people has Fiserv cut in 2026?
Fiserv said on its Q3 2026 earnings call that it has cut 3,000 employee and contractor roles since Takis Georgakopoulos became CEO in June, including more than 10% of senior management. There was no single layoff date. The cuts came gradually alongside the Elevate program, whose savings target was doubled to $1B and is expected to land mostly beyond 2027.
Why can't I just search for "Fiserv" or "ISO 8583"?
Many leavers were contractors who list TCS, Wipro or Capgemini as their employer, not Fiserv. Switch engineers also rarely tag the protocol: Refolk's index has only 68 US profiles listing ISO 8583, against Fiserv's 14,000 engineers. Search by platform names like Buypass, Cardnet, Nashville, Omaha and VisionPLUS, paired with a First Data metro or employment dates.
Which Fiserv engineers are most likely to become available?
Engineers on the more than a dozen legacy gateways and switches that Fiserv is moving to Commerce Hub, along with teams on the non-core products being exited. Gateway specialists usually become available after their platform's migration ends, so they arrive in groups through 2027 and 2028. Teams on divested products may move to a buyer instead of entering the market.
Where do former First Data engineers live?
In the US, the densest clusters in Refolk's index are Dallas-Fort Worth, Atlanta, Plano, Tampa, Orlando and Mount Laurel, NJ, which matches the old First Data footprint. Many now work at Capital One, JPMorganChase, Bank of America or Citi. In India, look in Bengaluru, Mumbai, Noida and Pune, often at IT services firms.
The data behind this
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.