Here’s a list of the new and improved functionality we’re planning to offer through GOV.UK Pay.
This roadmap is only a guide and may change. We work in 3-monthly cycles.
New cheaper centralised contracts are now in place. GOV.UK Pay and Government Banking have completed re-procurements for our respective contracts with payment providers. The new contracts have lowered fees for most transactions.
Improvements for Stripe users
As part of the move to new contracts, all transactions using the GOV.UK Pay contract with Stripe benefit from improved fraud protection which means we now include fees on failed payments. We have adjusted our reporting functionality to accommodate this.
We updated the onboarding process in response to new Know Your Customer regulations.
Finally, Stripe users can now request a Stripe test account, allowing them to see how transaction fees and payments to your bank account will work before they go live.
Switch payment provider more easily
Payment provider switching functionality within Pay’s admin tool enables services to easily switch their underlying payment providers between the central contracts without any changes to code or API keys.
Use an external telephone payment system to send card details to the API
Services can now use external telephone payment systems to collect card details and send them to GOV.UK Pay via a new API. This allows these payments to be processed and reported in the same way as online payments through GOV.UK Pay.
We’ve released a new API reference, making it easier for developers to understand how to integrate with GOV.UK Pay.
We’ve migrated our infrastructure to AWS Fargate, making sure we can scale and maintain the platform in an efficient and resilient way.
Improved payment pages
We’ve revised the journey for creating payment pages, and making a payment using them. Users are now asked for one thing per page, and services can provide links with the amount and reference pre-filled.
What we're working on
Users will be able to make recurring payments
Users will be able to agree to allow a service to take payments in the future without their intervention, for example to pay for a licence that renews on a monthly or annual basis.
Some services are testing the functionality in a private beta sandbox.
Before the end of 2022, private beta services will be able to take live recurring payments.
We’ll iterate based on what we learn and plan to release the functionality to all services.
Email email@example.com if you’d like to be part of our research and testing.
Better support for reconciling payments and processing invoices
We want to better support financial processes for inbound payments. Enterprise resource planning (ERP) software is used as part of these processes in central government.
As part of the Government Shared Services strategy, departments are adopting cloud-based ERP software, creating new opportunities for GOV.UK Pay to make finance processes easier and cheaper.
We’re working with the Government Finance Function to ensure that GOV.UK Pay will be integrated with all ERP systems that are adopted.
Continue to pilot ways of integrating ERP systems with GOV.UK Pay to support efficient and automated Order to Cash processes.
We’ll make any changes needed to support integrations to all central government ERP systems, and to meet the Government Finance Function data standard.
- We’ll make infrastructure improvements to make GOV.UK Pay more reliable, cheaper to run, and easier to support and iterate.
- We’ll make improvements to our documentation to make it easier to understand how to use GOV.UK Pay.
- We’ll allow users to use authentication apps for their second step verification when signing in to GOV.UK Pay for the first time. At the moment, this can only be changed after the first login, which causes issues for some overseas users.
Get in touch
Email firstname.lastname@example.org if you’d like to be involved in research, if you have any questions, or if there are other features you’d like us to develop.
Sign up to GOV.UK Pay updates to find out more about what we’re working on and our plans for the future.