Identified - Central 1 continues to work with Interac to investigate an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R).
Interac has identified a potential fix and is currently conducting testing and validation activities to confirm the root cause and effectiveness of the solution. Subject to successful testing and approval, Interac is currently targeting deployment of the fix as part of its September 20 production release.
The issue remains intermittent and may affect some customers using Scheduled or Recurring e-Transfers. Customers requiring immediate fund transfers should send an immediate e-Transfer instead of a Scheduled or Recurring e-Transfer until this issue has been resolved.
We continue to work closely with Interac and will provide our next update, including any changes to the expected release timeline, on Wednesday, September 9.
Central 1 - Support@central1.com - 1.888.889.7878 Option 1
Sep 03, 2026 - 16:21 PDT
Interac has identified a potential fix and is currently conducting testing and validation activities to confirm the root cause and effectiveness of the solution. Subject to successful testing and approval, Interac is currently targeting deployment of the fix as part of its September 20 production release.
The issue remains intermittent and may affect some customers using Scheduled or Recurring e-Transfers. Customers requiring immediate fund transfers should send an immediate e-Transfer instead of a Scheduled or Recurring e-Transfer until this issue has been resolved.
We continue to work closely with Interac and will provide our next update, including any changes to the expected release timeline, on Wednesday, September 9.
Central 1 - Support@central1.com - 1.888.889.7878 Option 1
Sep 03, 2026 - 16:21 PDT
Update - Central 1 continues to work with Interac to investigate an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R).
Our review of historical processing volumes indicates that the number of impacted Scheduled and Recurring e-Transfers is relatively low, and the majority continue to be processed successfully. The issue may affect any customer using Scheduled or Recurring e-Transfers.
Scheduled and Recurring e-Transfers are managed by Interac within a separate system, and Central 1 is unable to directly view or identify pending S&R transactions.
We continue to engage Interac for updates and will provide our next status update on Thursday, September 3 at 12:00 p.m. PT (3:00 p.m. ET).
Central 1 - Support@central1.com - 1.888.889.7878 Option 1
Sep 01, 2026 - 14:36 PDT
Our review of historical processing volumes indicates that the number of impacted Scheduled and Recurring e-Transfers is relatively low, and the majority continue to be processed successfully. The issue may affect any customer using Scheduled or Recurring e-Transfers.
Scheduled and Recurring e-Transfers are managed by Interac within a separate system, and Central 1 is unable to directly view or identify pending S&R transactions.
We continue to engage Interac for updates and will provide our next status update on Thursday, September 3 at 12:00 p.m. PT (3:00 p.m. ET).
Central 1 - Support@central1.com - 1.888.889.7878 Option 1
Sep 01, 2026 - 14:36 PDT
Investigating - Central 1 is aware of an Interac issue they are having with the Scheduled and Recurring e-Transfers. Currently some e-Transfers are not being processed on the due date. Customers requiring immediate fund transfers may send an immediate e-Transfer instead of a scheduled or recurring e-Transfer at this time.
We have reached out to Interac support to investigate and will provide updates as we receive them.
Central 1 - Support@central1.com - 1.888.889.7878 Option 1
Aug 28, 2026 - 13:29 PDT
We have reached out to Interac support to investigate and will provide updates as we receive them.
Central 1 - Support@central1.com - 1.888.889.7878 Option 1
Aug 28, 2026 - 13:29 PDT
Update - Please be assured that we continue to treat this as a priority investigation and remain actively engaged with our Development team. Over the past several weeks, we've dedicated significant effort to reproducing the behavior internally and identifying a reliable pattern that would help us isolate the root cause.
Unfortunately, despite extensive testing, we have not yet been able to replicate the issue in our own environments. We've also worked with a small number of affected clients by providing debug versions of the iOS application to capture additional diagnostic information during reproduction attempts; however, these efforts have not yet produced any conclusive findings.
While we do not have a meaningful update on the root cause at this time, the investigation remains active and ongoing. We understand the impact this issue has on your users and appreciate your patience as we continue working to gather the information necessary to move the investigation forward.
In the meantime, we encourage affected staff members to continue testing with the debug iOS application where possible. For impacted clients who have not yet received the debug version and would like to assist with troubleshooting, please let us know and we would be happy to provide it.
Should the issue occur again, any details surrounding the event would be extremely helpful to our investigation. In particular, we would appreciate information regarding the actions performed leading up to the login being cleared, the timestamp, the device type and model, the operating system version (iOS), and any screenshots or screen recordings that may help us better understand the circumstances under which the issue occurred.
We remain committed to resolving this issue and will provide further updates as soon as we have any significant developments to share.
Thank you for your continued patience and understanding.
DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)
Aug 21, 2026 - 06:11 PDT
Unfortunately, despite extensive testing, we have not yet been able to replicate the issue in our own environments. We've also worked with a small number of affected clients by providing debug versions of the iOS application to capture additional diagnostic information during reproduction attempts; however, these efforts have not yet produced any conclusive findings.
While we do not have a meaningful update on the root cause at this time, the investigation remains active and ongoing. We understand the impact this issue has on your users and appreciate your patience as we continue working to gather the information necessary to move the investigation forward.
In the meantime, we encourage affected staff members to continue testing with the debug iOS application where possible. For impacted clients who have not yet received the debug version and would like to assist with troubleshooting, please let us know and we would be happy to provide it.
Should the issue occur again, any details surrounding the event would be extremely helpful to our investigation. In particular, we would appreciate information regarding the actions performed leading up to the login being cleared, the timestamp, the device type and model, the operating system version (iOS), and any screenshots or screen recordings that may help us better understand the circumstances under which the issue occurred.
We remain committed to resolving this issue and will provide further updates as soon as we have any significant developments to share.
Thank you for your continued patience and understanding.
DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)
Aug 21, 2026 - 06:11 PDT
Update - We continue to investigate an issue affecting some members using the Forge App on iOS devices, where saved login information may not be retained as expected.
Through our investigation, we have identified a valid workaround that allows saved login functionality to continue working as designed. Members should ensure that Biometric Login (Face ID or Touch ID) is enabled within the Forge App. We have observed that when Biometric Login is disabled, saved login information may be removed, either immediately or after a period of time.
While the workaround has proven effective, our team continues to investigate the underlying cause. We have experienced challenges consistently reproducing the issue within our internal testing environments, which has extended the time required to identify the root cause and implement a permanent fix.
Our team remains actively engaged in the investigation and will provide additional updates as more information becomes available.
DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)
Jul 08, 2026 - 07:34 PDT
Through our investigation, we have identified a valid workaround that allows saved login functionality to continue working as designed. Members should ensure that Biometric Login (Face ID or Touch ID) is enabled within the Forge App. We have observed that when Biometric Login is disabled, saved login information may be removed, either immediately or after a period of time.
While the workaround has proven effective, our team continues to investigate the underlying cause. We have experienced challenges consistently reproducing the issue within our internal testing environments, which has extended the time required to identify the root cause and implement a permanent fix.
Our team remains actively engaged in the investigation and will provide additional updates as more information becomes available.
DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)
Jul 08, 2026 - 07:34 PDT
Investigating - We are currently investigating an issue affecting some users on iOS devices where saved login information is not being retained as expected on the v18.1 Forge App.
Some members reported that the issue was resolved after upgrading their device to iOS 26.5 operating system. While we have not yet confirmed this as a universal solution, members experiencing this issue may wish to ensure their device is running the latest available version of iOS.
Members can continue to access the service by manually entering their card number and password if their saved login is unavailable.
Our team is actively investigating the issue and working to determine the root cause. Additional updates will be provided as more information becomes available.
We apologize for any inconvenience and appreciate your patience while we work toward a resolution.
DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)
Jun 30, 2026 - 13:54 PDT
Some members reported that the issue was resolved after upgrading their device to iOS 26.5 operating system. While we have not yet confirmed this as a universal solution, members experiencing this issue may wish to ensure their device is running the latest available version of iOS.
Members can continue to access the service by manually entering their card number and password if their saved login is unavailable.
Our team is actively investigating the issue and working to determine the root cause. Additional updates will be provided as more information becomes available.
We apologize for any inconvenience and appreciate your patience while we work toward a resolution.
DigitalBanking_Support@Central1.com - 1.888.889.7878 (option 2)
Jun 30, 2026 - 13:54 PDT
Central 1 Services
Operational
Payment Services
Operational
Treasury Services
Operational
Digital Banking Services
Operational
Incident Alerting
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
CHG173875 – Interac Scheduled Database Maintenance Sep 6, 2026 00:00-03:00 PDT
Update -
We will be undergoing scheduled maintenance during this time.
Sep 03, 2026 - 09:27 PDT
Sep 03, 2026 - 09:27 PDT
Scheduled -
Interac has advised Central 1 of planned database maintenance on September 6 between 12:00 a.m. and 4:00 a.m. PT (3:00 a.m. to 7:00 a.m. ET).
Interac e-Transfer services are expected to be unavailable for approximately 120 minutes between 1:00 a.m. and 3:00 a.m. PT (4:00 a.m. and 6:00 a.m. ET).
During this period:
• Interac e-Transfer transactions may not be available.
• Interac e-Transfer payment deposit links will be unavailable.
• Email, SMS, and push notifications related to Interac e-Transfer transactions may be delayed.
• Bulk e-Transfer file processing (Legacy and ISO formats) will be unavailable from 12:30 a.m. to 6:00 a.m. PT (3:30 a.m. to 6:00 a.m. ET). Financial institutions may continue to submit files during this period; however, processing will resume after 3:00 a.m. PT (6:00 a.m. ET).
We appreciate your patience and understanding while Interac completes these maintenance activities.
Central 1 – support@central1.com – 1.888.889.7878 (press 1)
Aug 31, 2026 - 11:24 PDT
Interac e-Transfer services are expected to be unavailable for approximately 120 minutes between 1:00 a.m. and 3:00 a.m. PT (4:00 a.m. and 6:00 a.m. ET).
During this period:
• Interac e-Transfer transactions may not be available.
• Interac e-Transfer payment deposit links will be unavailable.
• Email, SMS, and push notifications related to Interac e-Transfer transactions may be delayed.
• Bulk e-Transfer file processing (Legacy and ISO formats) will be unavailable from 12:30 a.m. to 6:00 a.m. PT (3:30 a.m. to 6:00 a.m. ET). Financial institutions may continue to submit files during this period; however, processing will resume after 3:00 a.m. PT (6:00 a.m. ET).
We appreciate your patience and understanding while Interac completes these maintenance activities.
Central 1 – support@central1.com – 1.888.889.7878 (press 1)
Aug 31, 2026 - 11:24 PDT
CHG174070 - MDB, Forge Commercial, and CAS Online Release 529+530 Sep 9, 2026 01:00-01:30 PDT
Please be advised that MDB, Forge Commercial, and CAS Online Release 529+530 has been scheduled for Wednesday September 9, 2026 at 1 a.m. PT (4 a.m. ET).
DigitalBanking_Support@Central1.com - 1.888.889.7878, option 2
Posted on Aug 26, 2026 - 10:54 PDT
DigitalBanking_Support@Central1.com - 1.888.889.7878, option 2
Posted on Aug 26, 2026 - 10:54 PDT