Skip to main content

GOV.UK Pay product strategy and upcoming features

4 icons indicating the services offered by GOV.UK Pay, including Pay Now and Refund buttons.

GOV.UK Pay is the payments platform for the UK public sector. Our vision is to:

  • make it easy for individuals and businesses to pay the public sector
  • make it cheap and easy for the public sector to take and manage payments

September 2023 marks 7 years since we took our first live payment. Reaching such a milestone birthday gave us a great opportunity to reflect on how far we’ve come and decide on what’s next for Pay. 

Here's what we're doing to deliver our vision.

Our overall aim

Our aim is to support more central government and local authority teams to take payments for their services digitally. This allows them to automate their financial processes, reduces burden on their teams, and saves government time and money. This aim closely aligns with GDS’s strategy.

The 6 things we want to do

We’ve defined 6 strategic objectives as part of Pay’s product strategy. These objectives describe what we need to do for Pay over the next few years and why it’s important.

1. Diversify payment types

What: We want to expand from card payments into other inbound payment types

Why: Ten years ago, mobile wallets (like Apple Pay) did not exist, but now our users expect them as standard. This rate of change in the fintech industry is likely to increase and we’ll see our users’ expectations change too. We want to offer paying users with the most convenient ways to pay now and in the future


In June, we released recurring card payments to enable our users to make payments in instalments without having to manually input their card details every time.

We already offer Apple Pay and Google Pay for our central government services. This month, we’ll be releasing the same mobile wallet payment types to our local authority services too.

Later this year, we’ll be investigating how Pay might offer open banking, so that users can pay for public services via their banking app.

2. Enhance paying users' experience

What: We want to make Pay more usable and accessible for all our paying users. 

Why: Paying for public sector services should be hassle free. It's important that the widest range of users are able to complete their payments as quickly as possible.


We’re making updates to the payment journey, so that the content presented to paying users is clearer and easier to understand.

3. Improve public sector users' experience of managing card payments

What: We want to improve the Pay admin tool and documentation for our public sector users

Why: So that public sector users can manage transactions and refunds quickly and focus their energy on delivering great services


In June, we released webhooks so that services can receive automatic updates after payment events have taken place.

We’re reviewing and updating content in our tech docs to make it easier to use and understand.

4. Run a resilient, scalable, secure and cost efficient service

What: We want to continue to provide a robust, reliable and secure payments platform for all our users

Why: We need to keep all sensitive information secure in line with legislation. We want Pay to continue to perform successfully as our number of users and services grows


We’ll continue to provide responsive 24/7 support and improve our support processes.

We’ll continue to maintain our Payment Card Industry compliance.

5. Make it easier for the Pay team to improve the product

What: We want to create the right conditions so that our team can do their jobs with as little friction as possible

Why: Reducing pain points for our software engineers will help our team to work more efficiently. This should shorten product release cycles, enabling our team to add value for our users more quickly.


We’re improving the visibility of logs and metrics for our whole team, so everyone has access to the data they need to make decisions.

We’ve built up some technical debt and we want to address it. Over the next 12 months, we’ll be investing time in improving the quality of our code by breaking down known pieces of work and feeding them into our team’s backlogs.

6. Improve our knowledge of procurement and suppliers

What: We want to build up our team’s knowledge about procurement processes in government, and learn about payments suppliers in the fintech market 

Why: So that we can make sure we work with payment suppliers that offer the best value for money for our services 


We’ll be growing our team’s commercial capability through training and partnering with commercial experts across government.

What we're not doing

As well as describing what’s in our strategy, it’s equally important to describe what’s not in Pay’s scope and why. 

The main areas Pay will not be exploring are outbound payments, Direct Debit and PayPal.

Outbound payments

Pay provides inbound payments, enabling businesses and people to pay for UK public sector services. Outbound payments allow government and local authorities to make payments to businesses and people. Pay will not be offering outbound payment types as the approach required is vastly different from inbound payments and the public sector has other existing mechanisms to manage outbound payments.

Direct Debit

Direct Debit was not originally designed with digital payments in mind. This makes it difficult for Pay to integrate with and offer Direct Debit to users. Instead, we’re prioritising other types of recurring payment (like recurring card payments) so we can still offer ways for our users to make repeat payments while limiting our technical overheads.


We’re prioritising the mobile wallet payment types that have the lowest fees for our services, while still meeting the needs of our paying users (Apple Pay and Google Pay wallets). PayPal is not a mobile wallet payment that we plan to offer in the immediate future.

What now?

We’re using the 6 strategic objectives in our product strategy to drive decisions about our product roadmap and to prioritise our backlogs. We’ll be working towards these objectives over the next few years. 

Watch this space to see how we iterate on GOV.UK Pay, achieve our goals and find out more.

Sharing and comments

Share this page


  1. Comment by Huw Pritchard posted on

    Is GOV.UK Pay available to charities, NGOs and other government-funded third-sector organisations?

    • Replies to Huw Pritchard>

      Comment by Beth Brown, Lead Product Manager for GOV.UK Pay posted on

      Hi Huw,

      GOV.UK Pay can be used by public sector organisations in central government, local government, the NHS and police sectors. We’re not currently able to work with charities, businesses, schools, or housing associations.

      Doing so could open you up to a state aid challenge. We also do not support features you might need like Gift Aid and VAT support, which other payment providers can offer.

      We are hoping to look at what work would be needed to change this in the future, but it’s unlikely to happen in the next year.


      • Replies to Beth Brown, Lead Product Manager for GOV.UK Pay>

        Comment by Huw Pritchard posted on

        Thanks anyway Beth, and thanks for replying

        Great service anyway - all councils should use it (but I bet they don't)

  2. Comment by Genista Dunham posted on

    Sounds all great