GOV.UK dumps Stripe for Adyen in a £25.3 million payments switch

The UK Government Digital Service has officially swapped Stripe for Adyen on many GOV.UK Pay payments, and the price tag is up to £25.3 million over three years. The new setup covers card payments for local authorities, police forces and armed forces units, plus pay by bank services, which means the plumbing behind a huge slice of public-sector payments is changing even if the front end is supposed to look the same to users.

That matters because this is not a niche back-office tweak. According to the tender notice published in February 2025, the contract represents around 17 percent of payments made through GOV.UK Pay, but more than 70 percent of its organizations. In other words, most of the service’s customer count is moving, even if most of the money volume is not. The contract also includes the only option that lets users start taking payments within one working day, which is a very specific capability that can matter a lot to local bodies that need to launch quickly and do not want a months-long integration project just to collect fees, fines, or other charges.

The January-ish? No, the sequence here is clearer than that. The tender estimated the maximum value at £49 million when it was published in February 2025, although there were no guarantees over volume. The award, announced by GDS in a blogpost on 2 June, comes in below that ceiling at up to £25.3 million, which tells you two things that procurement teams always care about: first, ceilings are not spend, and second, the final shape of a contract can land very differently once reality, volume, and supplier selection enter the picture. GDS said it will migrate around 1,000 services to the new supplier.

Alan Maddrell, senior content designer for the service, said, “We will make migration as straightforward as possible while complying with Know Your Customer legislation that protects everyone from fraud.” He also said, “Most importantly, there will be no discernible difference for paying users and no loss in functionality.” That is the core promise for anyone watching enterprise payment migrations: switch the processor, keep the user journey intact, and do not create a queue of support tickets because someone changed a button, a redirect, or a payment method at the wrong time. The fact that GDS is making compliance with Know Your Customer legislation explicit also shows how much trust and fraud prevention sit inside what looks, from the outside, like a simple checkout flow.

The real strategic wrinkle is the new functionality. Maddrell said the supplier change will help introduce pay by bank, which transfers money directly between bank accounts using open banking services and avoids the need to type in card details. For users, that can mean less friction. For public services, it can mean fewer card-processing dependencies and a different relationship with payment cost and authentication. For decision-makers, it is a reminder that payments are no longer just about accepting money. They are about choosing which rails you want customers to use, how much identity and risk work you push into the flow, and how quickly a new service can go live without rebuilding the whole stack.

GDS is not abandoning its existing setup wholesale. It will continue to use WorldPay to process payments for central government, linked organizations and NHS bodies. That split matters because it shows GOV.UK Pay is being run as a layered platform rather than a single supplier monolith. Different parts of government have different requirements, different volumes, and different service constraints, so the platform is matching providers to use cases instead of treating every payment the same. For operators outside government, that is a familiar lesson: the best payment architecture is often less about one perfect vendor and more about which vendor fits which workflow.

The scale underneath all this is why the switch deserves attention beyond Whitehall. GOV.UK Pay was set up to save public services the effort and cost of building online payments themselves, and it does not charge organizations for the service beyond passing on transaction fees. Since 2016 it has processed 137.5 million transactions worth around £9.2 billion. It currently provides 1,718 services across 608 organizations, including 662 for local government and 256 for police forces, ranging from 1079 (Tiverton) Squadron RAF Air Cadets to Yeovil Town Council. That breadth is the whole point: if one payments provider changes, a lot of frontline public services feel it, even if the change is meant to be invisible.

For executives, the takeaway is simple. Payment infrastructure decisions are now product decisions, compliance decisions, and operating-model decisions all at once. GDS’s move from Stripe to Adyen shows how platform owners can redesign cost, speed, and user options without changing the promise to the end user. For anyone responsible for transactions, whether in government, fintech, marketplaces, or services, the question is no longer just who can process the payment. It is who can do it fast, flexibly, and with enough trust baked in that the user never notices the machinery behind the curtain.