Live  /  GoCardless  /  Incident

GoCardless: Bacs Processing Issue Affecting Payments Scheduled for Collection on 2 October

GoCardless · gocardless.comMinor incidentResolved2026-10-05 09:22 UTC
Public — what happened

Summary

GoCardless reported a problem on 1 October 2026 at 12:44 UTC that affected some Bacs direct debit payments scheduled to be collected on 2 October, along with some mandate setups and cancellations planned for that day. The company did not say what caused the problem. By 16:35 UTC it said the affected payments and mandates had been resubmitted, with collection moved to 5 October 2026. On the morning of 2 October it said the problem was resolved and that it would contact affected merchants directly, though the incident remained in monitoring status.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach GoCardless against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for GoCardless: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the GoCardless report →

More from GoCardless

Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.

The full archive is on the GoCardless status & history page.

Related: GoCardless status & history. SquidGrid is not affiliated with GoCardless.