GOV.UK Pay

All Systems Operational

About This Site

Overview of the current status of GOV.UK Pay, including updates on any active incidents.

To subscribe for alerts about disruption to service, select the 'Subscribe to updates' option above, or email us at govuk-pay-support@digital.cabinet-office.gov.uk and we'll add you.

Uptime over the past 90 days. View historical uptime.
Public API Operational
Self Service Operational
Payment pages Operational
90 days ago
100.0 % uptime
Today
Stripe API Operational
Stripe Webhooks Operational
Technical Documentation Operational
Worldpay Operational
Google Pay Operational
90 days ago
100.0 % uptime
Today
Apple Pay Operational
90 days ago
100.0 % uptime
Today
Stripe Payouts Operational
90 days ago
100.0 % uptime
Today
Payment emails Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Dec 7, 2025

No incidents reported today.

Dec 6, 2025

No incidents reported.

Dec 5, 2025

No incidents reported.

Dec 4, 2025
Updated card numbers used for testing
Resolved - We have updated the card numbers used for testing (https://docs.payments.service.gov.uk/testing_govuk_pay/#mock-card-numbers-and-email-addresses). These card numbers are used for testing accounts that are not live.

This is because a card issuer changed the Bank Identification Number (BIN) ranges they use to potentially include numbers we use for testing. This caused an incident.

Do not use the card numbers in the range 4000 62** **** 0007 for testing. Use the card number 4111111111111111 instead, which will work the same. If you use the old numbers now, your tests will fail.
Dec 4, 14:38 GMT
Dec 3, 2025

No incidents reported.

Dec 2, 2025

No incidents reported.

Dec 1, 2025
Permanent removal of weak ciphers
Completed - This scheduled change is now complete and we have no reported impact. Please refer to earlier information which outlined the weak ciphers we have removed support for, and a list of the ciphers we continue to support. Thank you for your understanding.
Dec 1, 10:26 GMT
In progress - Our scheduled change to permanently remove support for weak ciphers is now in progress. This should be completed by 11am and we will provide updates as necessary. We do not expect this change to have any impact on our services and their paying users. If you have any questions please contact govuk-pay-support@digital.cabinet-office.gov.uk.
Dec 1, 10:17 GMT
Update - We will be undergoing scheduled maintenance during this time.
Oct 1, 14:22 BST
Update - We have made a change to the schedule of the removal of these ciphers. The work will now happen at 10AM on 1 December 2025.
Sep 23, 15:17 BST
Scheduled - To maintain a highly secure and stable platform we will be removing support for 2 outdated ciphers at 10am on 1 December 2025. This is an extension from when the work was previously scheduled to happen on 30 September 2025.

We will be removing support for these TLS 1.2 ciphers on 1 December 2025:

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (ECDHE-RSA-AES128-SHA256)

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (ECDHE-RSA-AES256-SHA384)

To help services affected by this we have already added an ECDSA certificate which will also enable support for these TLS 1.2 ciphers:

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (ECDHE-ECDSA-AES128-GCM-SHA256)

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (ECDHE-ECDSA-AES256-GCM-SHA384)

This change introduced two further new weak TLS 1.2 ciphers that we will also remove on 1 December 2025:

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (ECDHE-ECDSA-AES128-SHA256)

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (ECDHE-ECDSA-AES256-SHA384)

A list of the changes:

TLS 1.2 ciphers that we support before 1 December 2025:

* TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (ECDHE-RSA-AES128-SHA256)
* TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ECDHE-RSA-AES128-GCM-SHA256)
* TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (ECDHE-RSA-AES256-SHA384)
* TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (ECDHE-RSA-AES256-GCM-SHA384)
* TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (ECDHE-ECDSA-AES128-GCM-SHA256)
* TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (ECDHE-ECDSA-AES256-GCM-SHA384)
* TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (ECDHE-ECDSA-AES128-SHA256)
* TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (ECDHE-ECDSA-AES256-SHA384)

TLS 1.2 ciphers that we support after 1 December 2025:

* TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ECDHE-RSA-AES128-GCM-SHA256)
* TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (ECDHE-RSA-AES256-GCM-SHA384)
* TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (ECDHE-ECDSA-AES128-GCM-SHA256)
* TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (ECDHE-ECDSA-AES256-GCM-SHA384)

We have directly contacted services affected by this change, and are encouraging the use of TLS 1.3 where possible.

This will be a permanent change and we will not be able to provide extensions to use these ciphers after November 2025.

If you have any questions about this change please email us at govuk-pay-support@digital.cabinet-office.gov.uk
Jul 1, 15:10 BST
Nov 30, 2025

No incidents reported.

Nov 29, 2025

No incidents reported.

Nov 28, 2025

No incidents reported.

Nov 27, 2025

No incidents reported.

Nov 26, 2025

No incidents reported.

Nov 25, 2025

No incidents reported.

Nov 24, 2025

No incidents reported.

Nov 23, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage