Acquired Outage History

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.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

Please be advised that customers may experience intermittent 3DS transaction failures currently via Mastercard.

We are additionally seeing intermittent failures when processing payments which use a Mastercard Network Tokens. We can see the issue originates within the Mastercard system and are awaiting further updates from Mastercard.

We have confirmed that this is an issue on the Mastercard network affecting transaction processing. Visa and other card schemes are unaffected.

We have identified processing errors from Barclays, Lloyds Personal, Halifax, and Bank of Scotland for Pay by Bank. To avoid disruption, we have temporarily disabled affected banks on Hosted Checkout. We will provide updates as they become available.

We are now also seeing processing errors affecting Faster Payments for affected banks. Barclays have acknowledged the outage and are investigating. The affected banks remain temporarily disabled on Hosted Checkout. We will provide further updates as they become available.

Barclays have confirmed their Faster Payments queues have cleared and payments are processing as normal. They are continuing work to restore full resilience this evening. Lloyds, Halifax, and Bank of Scotland are reporting normal service and we have re-enabled these banks on Hosted Checkout. Barclays remains temporarily disabled while their Open Banking service continues to report downtime. Payments to Barclays-banked sort codes, including Revolut, may still be rejected. Where a payment has shown as failed today, please do not retry it, as the beneficiary may already have been credited. We will provide updates as they become available.

Card payments requiring 3DS authentication are experiencing elevated declines since 08:00 BST due to an upstream 3DS authentication provider issue; non-3DS flows unaffected; provider engaged.

We have identified that this is only affecting Mastercard transactions. Mastercard have acknowledged a service disruption. We will provide updates as soon as possible.

Customers may experience intermittent authentication failures when attempting Mastercard 3DS-secured transactions. This may result in some transactions being declined or unable to complete authentication. Based on information provided by Mastercard, the issue originates within the Mastercard Identity Check (3DS) service. Mastercard has confirmed they are actively investigating the incident. We are continuing to monitor the situation closely and will provide further updates as more information becomes available from Mastercard.

We have confirmed that this is an issue on the part of Cashflows. We have enabled load balancing as a mitigation measure, if you have alternative acquirers available.

The issue has been identified and a fix is being implemented.