Is Go Cardless down?

Status: Monitoring We received reports of users being unable to access their GoCardless dashboard via SSO. We can confirm that the issue has now been resolved. We will continue to monitor the situation to ensure stability. We apologise for any inconvenience caused and thank you for your patience.

Status: Resolved Following a period of monitoring, we can confirm that the issue has been fully resolved and SSO access to the GoCardless dashboard is working as expected. Thank you for your patience, and we apologise for any inconvenience caused.

Status: Monitoring Between October 1st and October 8th, some emails from GoCardless to Yahoo and AOL addresses were rejected and may not have reached customers and merchants. We applied a fix on October 8, and emails to Yahoo and AOL addresses have been delivering normally since 17:25 UTC that day. We plan on resending the emails that didn’t get through and will continue to monitor delivery. We’ll post another update once the resend is complete.

Status: Resolved We have completed resending the emails to Yahoo and AOL addresses that were affected by the delivery issue between October 1 and October 8. All affected users were notified on October 13. Thank you for your patience.

Status: Investigating We experienced an issue affecting a number of Bacs collection payments with a charge date of 2 October 2026, as well as some Bacs mandates. As a result, payments due for collection on 2 October will be collected from customers early next week. We are actively working to resolve the issue and are taking steps to ensure affected payments and mandates are processed as soon as possible. Under Bacs rules, merchants are not required to send an additional notification to payers, as a payment can be collected within three working days of the date given in the advance notice. However, merchants may wish to proactively notify customers. Some mandates that were due to be submitted for creation and/or cancellation on 2 October 2026 will also be delayed. We will contact affected merchants directly to confirm which payments and mandates are impacted and provide further information on expected processing dates. We apologise for any inconvenience caused to you or your payers. Affected components Submissions (Degraded performance)

Status: Monitoring We’ve now resubmitted the Bacs collection payments and mandates due to be processed on 2 October 2026. Our engineering team are monitoring to identify any further issues. Payments that were due for collection on 2 October will now be collected on 5 October 2026. The same revised processing date applies to affected mandates that were due to be submitted for creation and/or cancellation on 2 October. We’ll continue to monitor processing, and we will contact all affected merchants tomorrow morning to provide an update. Affected components Submissions (Degraded performance)

Status: Monitoring We can now confirm that the issue has been resolved and all affected payments and mandates have been successfully resubmitted. Payments originally due for collection on 2 October 2026 will now be collected on 5 October 2026. Affected mandates will follow the same revised processing timeline. We will shortly contact all affected merchants directly to provide further details and clarify the impact of this issue. We apologise for the disruption and thank you for your patience and understanding. Affected components Submissions (Operational)

Status: Resolved We've resolved the issue affecting the delivery of a batch of Bacs payment submissions on 30 September. Affected payments and mandates have been resubmitted and confirmed, with collection and processing dates moved to 5 October, which has now completed as planned. We're sorry for the disruption this caused and thank you for your patience while we worked through it. Affected components Submissions (Operational)

Status: Investigating We are investigating delayed BACS failure reports. This means that returned-payment information is not yet available in the dashboard or scheduled reports. We are working with the relevant provider to restore report delivery and will provide an update as soon as we have more information. We apologise for any inconvenience and appreciate your patience. Affected components Reporting (Partial outage)

Status: Identified The issue has been identified and is affecting the Bacs scheme more broadly. The relevant parties are actively implementing technical fixes, and work is progressing to restore normal service as soon as possible. We are closely monitoring the situation and will provide further updates as they become available. Affected components Reporting (Partial outage)

Status: Identified We have seen BACS failure reports begin to flow again and are working with our provider to reconcile report completeness and ensure all delayed reports are processed. Some returned-payment information may remain delayed in the dashboard and scheduled reports while this work continues. We will provide a further update once reconciliation is complete. Affected components Reporting (Partial outage)

Status: Identified On Monday 21st September we received delayed reports for failed payments, mandate cancellations and other BACS reports. We have confirmed internally that all reports received were processed before midnight yesterday and all relevant payment and mandate statuses were updated and accurate when viewed today. Statuses will be visible in the dashboard and scheduled reports as usual, and expected API events have been sent. We have identified a very limited number of customers where we did not receive failure reports yesterday. We are working with our provider to receive these missing reports and will contact each affected merchant directly with more information. BACS report delivery has returned to normal resumed so no further impact is expected. We will provide a further update once this work is complete. Affected components Reporting (Operational)

Status: Resolved We can confirm that the issue affecting reports for failed payments, mandates, cancellations, and other BACS reports has now been resolved. We have contacted the affected merchants directly with further details. We apologise for any inconvenience this may have caused. Affected components Reporting (Operational)

Status: Investigating We are receiving reports that some mandates transferred from one bank to another are being cancelled with an AUDDIS-I error. The issue appears to be affecting multiple banks, with the majority of reported cases currently involving Nationwide Bank, as well as HSBC, NatWest, Barclays, and others. Our team is actively working with our banking partners to investigate the issue and identify the root cause. We are continuing to monitor the situation closely and will provide another update as soon as we have more information.

Status: Monitoring Following our investigation with our banking partner, we identified the root cause of the issue. The payer’s bank has since implemented a fix, and the issue is now resolved. However, further investigation has revealed that the information previously shared via email with the affected merchants is no longer accurate. We will therefore contact all affected merchants again to clarify the situation, provide the correct information, and explain the next steps. We apologise for any inconvenience caused and appreciate your continued patience and understanding.

Status: Resolved We have contacted all affected merchants directly with further details on the failed mandates. We apologise for the disruption caused and thank you for your patience and understanding.