How we fixed connection reset errors on GOV.UK Pay
When the GOV.UK Pay team noticed some test payments were failing, they set about working out what was happening and how to fix it. Here’s what they did.
When the GOV.UK Pay team noticed some test payments were failing, they set about working out what was happening and how to fix it. Here’s what they did.
When a pull request failed because of an incorrect creation date, the GOV.UK Pay team investigated the cause. Here’s how they found and fixed the bug.
GDS has made it easier for small public sector organisations to set up and use GOV.UK Pay. Previously, it could take some organisations up to 6 months before they could take payments through GOV.UK Pay. Now users can get set up and take payments from citizens on the same day.
Find out how we used the Payment Request API standard and how we managed encryption. We explain why we chose to use Apple’s JavaScript API and not use the Google Pay API.
GOV.UK Pay now offers the ability to show users pages in Welsh. We take a look at the technical details and how this will help us add more language support in the future.
The GOV.UK Pay team has made significant performance improvements by using the GOV.UK Design System. Find out what our migration process was like and how your service can benefit too.
Service team developers no longer need to test on Internet Explorer 8, 9 and 10 (old versions of IE) when following our ‘designing for different browsers and devices’ guidance.
07 August 2020 update: We’ve updated this post to remove references to ‘whitelisting’ and ‘whitelists’. GDS has updated its style guide to ban references to the racist terms ‘whitelist’ and ‘blacklist’. We now use ‘allow list’ and ‘block list’ instead. …
We’ve recently begun using container tools on GOV.UK Pay to help us run the platform locally and make development less resource heavy. GOV.UK Pay consists of several interacting microservices: a citizen front end, a government service admin interface, a public …
As you may know we’ve recently been trying to improve how we write and display our developer documentation. We’ve done lots of user research with technical architects, developers and service managers so we have an idea of what good documentation …