Is Acquired down?

Between 10:23:00 (UTC) and 10:24:30 (UTC), the entire Acquired platform (including the REST API and the Hub) was unreachable, and Cloudflare 502 errors will have been returned to all requests. This was due to an infrastructure configuration change, and has since been resolved. We are monitoring the issue to ensure it does not occur again.

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.

The third-party provider in the Confirmation of Payee chain has deployed a fix, and CoP requests are now completing as normal. We've been monitoring since the fix went in. Other payment services were not affected at any point. If any CoP requests failed or timed out during the incident and haven't been retried, they can now be retried. Thanks for your patience, and please contact support if you're still seeing problems.

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.

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.

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.

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.

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.

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.

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.

This incident has now been resolved.

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.

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.

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.

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.

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.

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.

We are currently experiencing elevated declined transactions, we are investigating the issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.