GoCardless

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-20 14:49 UTC

   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.

2. resolved 2026-10-20 15:44 UTC

   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.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-12 08:39 UTC

   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...

2. resolved 2026-10-15 08:28 UTC

   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.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 12:44 UTC

   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...

2. monitoring 2026-10-01 16:35 UTC

   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...

3. monitoring 2026-10-02 08:05 UTC

   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...

4. resolved 2026-10-05 09:22 UTC

   **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...

Excerpts are shortened. Read the full incident on GoCardless's status page.

1. investigating 2026-09-24 17:21 UTC

   We are aware of an issue affecting a small percentage of Direct Debit payments to Nationwide, which are failing intermittently each day with the code ARUDD-8. We are investigating the issue with our banking partner and will provide an update as soon as we have more information.

2. investigating 2026-09-25 15:00 UTC

   Upon further investigation, we have identified that payments to Nationwide accounts that initially fail with ARUDD-8 are succeeding when retried. **Action for merchants:** We recommend retrying any Nationwide payments that have failed with ARUDD-8. We are continuing to monitor...

3. monitoring 2026-10-07 10:57 UTC

   We are seeing a reduction in the number of payments to Nationwide failing with ARUDD-8, and retries are continuing to successfully go through. We are in contact with our partner bank to monitor the fix that Nationwide is implementing. **Action for merchants:** We continue to...

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-21 15:28 UTC

   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...

2. identified 2026-09-21 16:56 UTC

   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...

3. identified 2026-09-22 07:59 UTC

   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...

4. identified 2026-09-22 12:45 UTC

   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...

5. resolved 2026-09-22 15:56 UTC

   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.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-04 16:22 UTC

   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,...

2. monitoring 2026-09-08 10:58 UTC

   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...

3. resolved 2026-09-21 12:01 UTC

   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.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 19:33 UTC

   We’ve identified an issue affecting some USD payments scheduled to be collected on 31 August 2026. Our team is working with our banking partner to resolve this. We will provide a further update shortly.

2. investigating 2026-09-02 21:13 UTC

   We’ve identified that some USD payments scheduled to be collected on 31 August 2026 were not processed. We’re working with our banking partner to identify the affected payments and reprocess them. We will provide another update as soon as there’s more information.

3. investigating 2026-09-03 11:34 UTC

   Due to the ongoing issue affecting USD payments, merchants will experience a delay in receiving payouts today. We’re working to resolve this as quickly as possible and will share a further update once we have more to report.

4. investigating 2026-09-03 16:49 UTC

   Our team has now managed to identify and send out all USD payouts unaffected by this issue. For merchants affected by this issue, we will reach out directly to clarify the situation and next steps.

5. resolved 2026-09-10 15:22 UTC

   We’ve now confirmed that the issue has been fully resolved. All affected merchants have been contacted directly to explain the situation. We apologise for the issue and thank you for your patience and understanding.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-24 14:21 UTC

   Some customers may be experiencing delays receiving GBP payouts. We are investigating the issue with our banking partner and will provide an update as soon as more information is available. We apologise for any inconvenience caused.

2. investigating 2026-08-24 15:53 UTC

   Some customers are experiencing delays receiving GBP payouts. We are actively working with our bank partner to investigate the issue and confirm when affected payouts will be completed. We apologise for the inconvenience and appreciate your patience.

3. investigating 2026-08-24 16:01 UTC

   Some customers are experiencing delays receiving GBP payouts. We are actively working with our bank partner to investigate the issue and confirm when affected payouts will be completed. We apologise for the inconvenience and appreciate your patience.

4. investigating 2026-08-24 17:19 UTC

   Affected GBP payouts are beginning to be processed. We are continuing to work closely with our banking partner to ensure all delayed payouts are completed as quickly as possible. We will provide further updates once we see all payouts have been confirmed. We appreciate your...

5. resolved 2026-08-24 18:23 UTC

   All affected GBP payouts have now been processed. We apologise for the disruption and thank you for your patience.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-22 12:58 UTC

   We've identified an issue where the homepage of GoCardless for Xero shows an error. The issue is only affecting the display of the homepage. As a workaround, you can access GoCardless for Xero at this url:...

2. resolved 2026-07-22 13:58 UTC

   The issue has been resolved. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-04 17:32 UTC

   We would like to inform you that we are currently experiencing email delivery failures affecting Microsoft mailboxes, including Outlook, Hotmail, Live, and MSN (and their regional extensions). We are in contact with Microsoft regarding this issue, however they have not yet...

2. monitoring 2026-06-15 10:51 UTC

   Email deliverability to Microsoft mailboxes (Outlook, Hotmail, Live, MSN, etc.) has been restored. We are actively monitoring the service to ensure continued stability

3. monitoring 2026-06-24 15:42 UTC

   We have begun resending the emails that failed to deliver during the recent service disruption. To help you easily identify these messages, **(Delayed Delivery)** has been added to the beginning of the subject line.

4. resolved 2026-06-26 10:28 UTC

   The resending of emails affected by the recent service disruption has now completed. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-19 11:55 UTC

   Due to an issue with a 3rd party provider we have temporarily paused SEPA Instant Payouts at 9:14 BST today. Other payout types are not affected. We will resume SEPA Instant payouts as soon as we've received a confirmation that the issue has been resolved. If the issue persists...

2. identified 2026-05-19 16:45 UTC

   SEPA Instant Payouts remain paused due to a third party issue. Emergency maintenance has been scheduled by our banking partners over night, and we expect to resume payouts tomorrow. All affected parties have been contacted directly. We will provide further updates when the third...

3. monitoring 2026-05-20 10:58 UTC

   The issue has been confirmed as resolved. We have resumed SEPA Instant payouts and all pending payouts should soon reach the recipient bank accounts. We will continue to monitor for errors until the end of day.

4. resolved 2026-05-20 12:59 UTC

   All SEPA Instant payouts have been processing correctly. The issue is confirmed to be resolved.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-30 13:58 UTC

   We identified an issue affecting a small number of merchants, where queries to the Events API returned no events for payments, payment_actions, or customers created after 29 April. This also impacted the dashboard view for these resources. The issue has now been resolved, and we...

2. resolved 2026-04-30 15:13 UTC

   We’ve continued monitoring following the earlier Events API issue, and all systems are operating as expected.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-16 12:52 UTC

   We have identified an intermittent issue with processing Instant Bank Payments and Variable Recurring Payments. Our Engineers have identified the issue and are working on resolving it. We will get back to you shortly with an update.

2. monitoring 2026-04-16 13:39 UTC

   Our team have now resolved the issue, and Instant Bank Payments and Variable Recurring Payments are working as expected. We will continue to monitor closely to ensure stability.

3. resolved 2026-04-16 15:22 UTC

   We have confirmed that Instant Bank Payments and Variable Recurring Payments are now functioning as expected. We apologise for any inconvenience this may have caused.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-04-14 11:25 UTC

   We recently experienced an issue with SEPA Instant Payouts due to a problem with our banking partner. The issue has been resolved, and we’re working closely with them to restore normal service. Payouts scheduled for this afternoon may be slightly delayed and are expected to...

2. resolved 2026-04-14 13:20 UTC

   We can now confirm that all SEPA Instant payouts for April 14th have been processed and received. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-13 08:40 UTC

   ``` We'd like to inform you that some webhooks that should have been sent today between 9:40 and 9:55 BST, were sent out at 11:30 BST. We apologise for any inconvenience caused. ```

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-30 07:53 UTC

   We are currently experiencing an issue affecting the export functionality on the Payments page. Our team is actively investigating the root cause of this issue and working on a resolution. We will provide an update as soon as more information becomes available or the issue is...

2. resolved 2026-03-30 10:15 UTC

   The issue affecting the export functionality on the Payments page has now been resolved. Our team has identified and fixed the root cause of the problem. Exports are working as expected, both with and without filters applied. We appreciate your patience while we worked on...

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-27 13:08 UTC

   We'd like to inform you that GoCardless API for Payout items is not returning the expected result. Other API functionality is not affected. Our engineers are reverting the change that caused the issue and will update you as soon as it's completed.

2. resolved 2026-03-27 14:01 UTC

   The revert was successful, Payout items are now correctly reflected in our API. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-03-17 12:01 UTC

   We would like to inform you that from 12:01-12:03 UTC our API and Payment pages were unavailable. We apologise for any inconvenience caused, our engineers are actively investigating the root cause of this disruption.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-13 10:31 UTC

   We’re currently experiencing an intermittent issue affecting access to the GoCardless dashboard for a few merchants. The root cause has been identified, and we are in the process of implementing a fix. We will provide a further update once the issue has been resolved.

2. resolved 2026-03-13 15:06 UTC

   The issue affecting access to the GoCardless dashboard for a small number of merchants has now been resolved. Our team has implemented a fix, and we can confirm that access to the dashboard has been restored. Thank you for your patience while we worked to resolve this issue.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-04 11:44 UTC

   We are currently investigating reports of discrepancies in the amounts displayed on the GoCardless dashboard homepage. Our engineering team is actively working to identify the root cause and implement a fix. We understand the importance of accurate reporting and appreciate your...

2. investigating 2026-03-04 13:46 UTC

   The issue affecting the amounts displayed on the GoCardless dashboard homepage has now been resolved. Our engineering team identified the root cause of the discrepancy and implemented a fix. All displayed amounts are now accurate, and the dashboard is functioning as expected. We...

3. resolved 2026-03-04 15:03 UTC

   We’ve monitored for a while and can confirm that the issue with amounts displayed on the GoCardless dashboard homepage has been fully resolved and is now working as expected.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-25 10:19 UTC

   We are currently investigating an incident that has resulted in an increased number of Direct Debit collection failures for some New Zealand customers on 24th February. We are working with our banking partner and will provide further updates as soon as more information becomes...

2. investigating 2026-02-25 15:16 UTC

   We are continuing to investigate the incident that has resulted in an increased number of Direct Debit collection failures for some New Zealand customers. In addition to payments scheduled for 24th February, we have identified that some payments scheduled for 25th February are...

3. resolved 2026-03-02 10:53 UTC

   The previously reported issue affecting some Direct Debit collections for New Zealand customers has now been fully resolved. We have contacted all impacted merchants and continued monitoring confirms that payment processing is operating as expected. Thank you for your patience.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-24 13:50 UTC

   We are currently investigating an issue affecting the GoCardless Dashboard, where some users are encountering a blank screen. We have also received reports of API disruption. Our team is actively working to identify the root cause and will provide a further update as soon as...

2. monitoring 2026-02-24 14:55 UTC

   We’ve identified the root cause and implemented a fix. Access to the GoCardless dashboard and APIs are recovering at the moment. We’ll continue to monitor the system to ensure everything remains stable.

3. resolved 2026-02-24 16:28 UTC

   We have confirmed that our fix has resolved the issue and that users can access the GoCardless Dashboard as normal. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-23 15:09 UTC

   We have identified an issue affecting direct debit mandates for customers holding accounts with **Société Générale** and **Boursorama/BoursoBank** whereby collections for impacted payers have failed and the mandates cancelled. We are working closely with our partner bank to...

2. investigating 2026-02-24 11:20 UTC

   We have identified the root cause, and the issue has now been resolved. We are currently conducting a detailed impact analysis to determine the full scope of affected mandates and collections. We will be back with another update shortly.

3. monitoring 2026-02-24 16:30 UTC

   Following our detailed impact analysis, we have identified the affected mandates and are currently working on the feasibility of reinstating all impacted direct debit mandates. We expect this process to be completed by tomorrow. We will provide a further update tomorrow.

4. monitoring 2026-02-25 13:15 UTC

   Following our detailed impact analysis, we identified the affected mandates and assessed the feasibility of reinstating all impacted direct debit mandates. We have now successfully reinstated all impacted mandates, and these existing mandates are active again (except the ones...

5. resolved 2026-02-26 15:18 UTC

   We have now contacted all affected parties, and have resolved this incident.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-16 11:42 UTC

   We are investigating an issue related to our dashboard, in particular, reports of seeing a blank screen. In most cases, clearing the cache is able to resolve the issue. We will provide another update shortly once we have identified the cause.

2. investigating 2026-02-16 13:31 UTC

   We are continuing to investigate the issue affecting the dashboard, including reports of users seeing a blank screen. Our team is actively working to identify the root cause. In the meantime, clearing your browser cache may help resolve the issue for some users. We appreciate...

3. monitoring 2026-02-16 14:44 UTC

   We’ve identified the root cause and implemented a fix. Access to the GoCardless dashboard should now be fully restored. We’ll continue to monitor the system to ensure everything remains stable.

4. resolved 2026-02-17 09:59 UTC

   We have confirmed that our fix has resolved the issue and that users can access the GoCardless Dashboard as normal. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on GoCardless's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-02-05 13:46 UTC

   We experienced an issue with payouts that has now been resolved. Payouts for SEPA, BECS New Zealand, PAD Canada, and Betalingsservice Denmark were delayed by approximately 40-50 minutes compared to the usual processing time. Apologies for any inconvenience caused.

2. resolved 2026-02-05 14:28 UTC

   We can now confirm that the issue has been fully resolved. All affected payouts have processed successfully and should be delivered to merchants with only a minor delay. We apologise for any inconvenience this may have caused.

Excerpts are shortened. Read the full incident on GoCardless's status page.