Confirmation of Payee: elevated error rates
Investigating - We are seeing an increased number of Confirmation of Payee (CoP) requests failing or timing out. A third-party provider in the Confirmation of Payee chain has confirmed an issue on their side and is working on a fix. We are monitoring closely.

Other payment services are not affected.

If a Confirmation of Payee request returns an error or times out, please retry it. We will post another update as soon as we hear more.
Oct 22, 2026 - 15:48 BST

About This Site

Here you’ll find real-time information on the availability and performance of our services. We use this page to keep you informed about any incidents, scheduled maintenance, or system updates — so you’re always in the loop.

✅ All systems operational? Great.

🚧 Issues or updates? We’ll post them here right away, along with regular progress updates until they’re resolved.

Uptime over the past 90 days. View historical uptime.
Payments API Operational
Hub Operational
Integration Methods Operational
Components Operational
Hosted Checkout Operational
Product Pillars Operational
Payouts Operational
Pay by Bank Operational
Direct Debit Operational
Cards Operational
Services Degraded Performance
Confirmation of Payee Degraded Performance
Hosted Payment Page Operational
Card API Operational
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.

Oct 23, 2026

No incidents reported today.

Oct 22, 2026

Security maintenance: eMudhra certificate compromise and critical PHP vulnerabilities
Completed - All security fixes are now deployed across the Acquired environment. Both the eMudhra certificate compromise and the critical PHP vulnerabilities (CVE-2026-109618, CVE-2026-109619) are fully resolved on our side, and merchant data and payment processing remain secure.

If you host PHP web applications, such as WordPress, WooCommerce or Magento, please make sure PHP has been upgraded to 8.5.12, 8.4.27, 8.3.36 or 8.2.35. This needs to be done on your side.

If you have any questions, contact Acquired Support.
Oct 22, 15:42 BST
Update - To confirm, there will be no impacts to processing during these updates.
Oct 22, 14:53 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 22, 14:30 BST
Scheduled - We’re carrying out security maintenance in response to two critical vulnerabilities disclosed this week.

eMudhra intermediate certificate compromise:

The private keys for several intermediate certificates issued by eMudhra can be recovered. This lets someone impersonate websites to any software that still trusts those certificates. Major browsers and operating systems have now revoked them. We completed this maintenance across the Acquired environment on the evening of 21 October, and merchant data and payment processing remain secure.

Critical PHP vulnerabilities (CVE-2026-109618, CVE-2026-109619):

These two flaws, each rated CVSS 9.2, can allow unauthenticated remote code execution on servers running PHP. The patch is being tested now and will be deployed by the end of today, 22 October. We’ll update this notice once it’s complete.

Recommended action for merchants

The PHP vulnerabilities are in PHP itself, not in the Acquired WooCommerce plugin. Our plugin is not affected and doesn’t need an update. However, PHP runs on your own servers or hosting, so the upgrade has to be done on your side.

WordPress, WooCommerce, Magento (Adobe Commerce) or anything else that runs on PHP: Ask your developer, agency or hosting provider today to upgrade PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35. This applies to all PHP web applications you host, whether or not they integrate with Acquired.

Servers and devices: Keep operating systems, browsers and CA certificate bundles up to date.

More information:

eMudhra: https://emudhra.we-have-a-problem.com/
PHP: https://www.php.net/releases/

If you have any questions, contact Acquired Support.
Oct 22, 14:21 BST

Oct 21, 2026

No incidents reported.

Oct 20, 2026

Partial Service Degradation
Resolved - This incident has now been resolved.
Oct 20, 17:01 BST
Update - We're now seeing recovery across the failed cloud zone, and Google Cloud have marked their incident as resolved.

We will continue to monitor, but there should be no further impact to service.
Oct 20, 16:20 BST
Monitoring - All affected services have now been moved off the impacted cloud zone, which has greatly reduced the impact on our platform.

The underlying Google Cloud incident is still ongoing, so this incident remains open while we continue to monitor closely. Customers may still see some intermittent processing issues during this time.

We will provide a further update shortly.
Oct 20, 11:16 BST
Update - We have identified additional impact related to this incident:

Payouts: Payouts created since approximately 07:00 BST are currently showing as pending.
Accounts: The transaction list in Accounts is not currently updating to show recently processed transactions.

We are continuing to work on mitigating the impact. The impact described in previous updates remains in place.

We will provide a further update within 30 minutes, or sooner if the situation changes.
Oct 20, 10:20 BST
Update - We have confirmed that this issue is related to an ongoing incident with our cloud provider, Google Cloud. We are monitoring their progress closely and continuing to mitigate the impact on our services.

There is no change to the impact described in our previous update. We will provide a further update within 30 minutes, or sooner if the situation changes.
Oct 20, 09:37 BST
Update - We are continuing to work on a fix for the issue affecting one of our cloud zones.

Webhook delivery has been failing since approximately 07:00 BST. We have now moved webhook services to unaffected infrastructure and are monitoring their recovery.

Open banking payments are still affected, and some customers may see failed or delayed open banking payments.

We will provide a further update within 30 minutes, or sooner if the situation changes.
Oct 20, 09:08 BST
Update - We are continuing to work on a fix for the issue affecting one of our cloud zones.

We will provide a further update within 30 minutes, or sooner if the situation changes.
Oct 20, 08:54 BST
Identified - We are currently experiencing a partial degradation of service caused by an issue with one of our cloud zones.

Our automated failover has activated and our engineering team is actively rerouting traffic to healthy infrastructure. Some customers may experience intermittent errors or increased latency while this takes effect.

We will provide a further update shortly.
Oct 20, 07:40 BST

Oct 19, 2026

No incidents reported.

Oct 18, 2026

No incidents reported.

Oct 17, 2026

No incidents reported.

Oct 16, 2026

No incidents reported.

Oct 15, 2026

No incidents reported.

Oct 14, 2026

No incidents reported.

Oct 13, 2026

Cashflows - Visa Processing Issue
Resolved - This incident has been resolved. Between approximately 19:20 BST on 12 October and 04:05 BST on 13 October, some Visa payments (Card, Apple Pay and Google Pay) processed through CashFlows failed. Mastercard payments were not affected.

Since then, Visa payments have processed normally and we have seen no further failures. CashFlows have confirmed the issue is fully resolved and are carrying out a full review of the incident.
Oct 13, 15:46 BST
Monitoring - CashFlows have confirmed the fix for the issue affecting Visa payments (Card, Apple Pay and Google Pay). Visa payments have been processing normally since approximately 04:05 BST, and we have seen no further failures since then.

We will continue to monitor and will post a final update once the incident is closed. Mastercard payments were not affected.
Oct 13, 08:05 BST
Update - CashFlows are continuing to work through recovery steps to restore Visa processing. Visa payments (Card, Apple Pay and Google Pay) processed through CashFlows remain affected. Mastercard payments are not affected.

Merchants who process solely through CashFlows may still be unable to take Visa payments until service is restored. We are monitoring closely and will post a further update once Visa payments are processing successfully again.
Oct 12, 22:04 BST
Identified - CashFlows have identified the cause of the disruption affecting Visa payments (Card, Apple Pay and Google Pay) and are working to restore service. Visa payments processed through CashFlows have been affected since approximately 19:20 BST. Mastercard payments are not affected.

Where alternative acquirers are available, Visa traffic continues to be routed away from CashFlows. Merchants who process solely through CashFlows may still be unable to take Visa payments until service is restored.

We are monitoring closely and will confirm here once Visa payments are processing successfully again.
Oct 12, 21:26 BST
Update - We are continuing to monitor the disruption affecting Visa payments (Card, Apple Pay and Google Pay) processed through CashFlows. CashFlows are actively investigating and have raised the issue with Visa as a priority.

Where alternative acquirers are available, Visa traffic continues to be routed away from CashFlows. Merchants who process solely through CashFlows may still be unable to take Visa payments until service is restored.

We will share a further update as soon as we have more information.
Oct 12, 20:59 BST
Investigating - Visa payments (Card, Apple Pay and Google Pay) processed through CashFlows are failing. CashFlows have confirmed an issue on their side.

Where possible, we have moved traffic to other acquirers. Merchants who use only CashFlows will see all their Visa payments fail until it’s fixed.
Oct 12, 20:21 BST

Oct 12, 2026

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage