Building and strengthening our common components and shared platforms, is at the heart of what we do at GDS. Here’s detail on our progress and product iteration since we last blogged in March.
GOV.UK Pay is the new simple, secure way to pay for government services online. It will make it easier and more efficient for government to process payments, saving time and effort for service teams across government.
In this post Richard Buttrey talks about the market briefing held at TechUK. He explains the opportunities Government as a Platform offers suppliers.
As more and more services begin to adopt our Government as a Platform components, we’ve decided to post regular updates on our progress building them. This is a list of what we’ve done so far in 2017. We’ll iterate the format of these updates to make them as useful as we can.
On Friday 2 September we reached a major milestone - we took our very first live payment on GOV.UK Pay. Product Manager Till Wirth was confident enough to process a payment using his own debit card. Until now, we’ve been using dummy cards.
GOV.UK Pay is now compliant with the Payment Card Industry Data Security Standard. This means GOV.UK Pay can process credit and debit card payments on behalf of government and wider public sector organisations. Till Wirth and Rory Smith talk about the team's approach to security in the context of agile software development and continuous delivery.
Dominic Hey (Ministry of Justice) and David Ware (Government Digital Service) spotted an opportunity to pool resources and partner up on user research. They recently held the first joint usability session, with members of both teams observing.
Paying for things online can be a tough task, especially for people who aren't very confident users of the internet. One of the aims of GOV.UK Pay is to make it easier to pay government. Stephen McCarthy explains how the team have been working to help build trust.
Ian Maddison explains how user research has informed the approach and technical decisions in the GOV.UK Pay beta. He also gives an update on the public API, how they're making integration straightforward, and security.