Why did GOV.UK Pay dump Stripe?

GOV.UK Pay switches payment provider to Adyen

GOV.UK Pay has moved to Adyen as its payment services provider, replacing Stripe. The change matters because GOV.UK Pay isn’t a consumer payments app—it’s the UK government’s infrastructure for collecting fees, taxes, and other payments from the public, so reliability, security, and integration details carry high stakes.

In practical terms, the migration implies that the government’s payment stack will now rely on Adyen’s platform capabilities for routing, processing, and merchant tooling. That can affect how payments are authorized and captured, how payment failures are handled, and what reporting or operational controls the platform exposes to government teams.

The broader significance is that governments increasingly treat payments platforms like critical infrastructure rather than interchangeable vendors. Moving off a major provider also suggests there were procurement, cost, performance, or policy-driven reasons to re-platform—though the specific rationale beyond “selected as payment services provider” is not spelled out in the provided story.

For users, the key question is continuity: whether payment pages, checkout flows, and confirmation emails remain consistent while back-end processing changes. For agencies, the focus is on maintaining service levels while adapting to a new payments provider’s tooling and operational requirements.

For industry watchers, the switch is also a signal that even widely adopted payment processors can face replacement as public-sector requirements evolve. Adyen’s win demonstrates its ability to fit complex institutional use cases where compliance, transaction handling, and system integration are central considerations.