Central 1 Status

Resolved: Central 1 has confirmed that the changes implemented last night have resolved the issue affecting AFT transactions where the due date could change by one day after an AFT record was created or modified.

Central 1 - [email protected] - 1.888.889.7878, press 1

Monitoring: Central 1’s technical teams implemented two changes early this morning to resolve an issue affecting AFT transactions in which the due date could shift back by one day when an AFT record was created or modified with a due date in November or later.

Clients are encouraged to test their AFT transactions and contact Client Support if they continue to experience any further issues with AFT due dates.

Central 1 - [email protected] - 1.888.889.7878, press 1

Identified: Please note that the production deployment has been postponed by one day to allow for additional review, and is now scheduled for Wednesday, October 21, 2026, between 1:00 a.m. and 1:30 a.m. PT (4:00 a.m. and 4:30 a.m. ET). Our apologies for the inconvenience.

Central 1 - [email protected] - 1.888.889.7878, press 1

Identified: Central 1 has successfully tested the fix for the issue affecting AFT transactions where the due date may shift back by one day after an AFT record is created or modified. This issue affects transactions with due dates in November or later. Transactions with October due dates are not impacted.

Our technical teams will implement CHG175932, which updates PaymentStream Direct, concurrently with CHG175631, which updates the AFT warehouse. We will implement the changes on October 20, 2026, between 1:00 and 1:30 a.m. PT (4:00 and 4:30 a.m. ET).

We will provide an update by October 20, 2026, at 1:00 p.m. PT (4:00 p.m. ET), or sooner if we have additional information.

Central 1 - [email protected] - 1.888.889.7878, press 1

Identified: Central 1 is testing a fix for an issue affecting AFT transactions in which the due date may shift back by one day after an AFT record is created or modified if the due date is in November or later.

Transactions with October due dates are not affected.

Our technical teams are currently validating the fix in the QA environment. Once testing is complete, we will implement the fix in production.

We will provide an update by Monday, October 19, 2026, at 1:00 p.m. PT (4:00 p.m. ET), or sooner if we have additional information.

Central 1 - [email protected] - 1.888.889.7878, press 1

Investigating: Central 1 continues to investigate the issue affecting AFT transactions where the due date falls back by one day after an AFT record is created or modified. This issue impacts transactions with due dates in November and onwards. Transactions with October due dates are not affected.

Our technical teams are actively investigating to determine the conditions contributing to the issue and the full scope of impact.

We will provide an update on October 16, 2026, by 1:00 p.m. PT (4:00 p.m. ET), or sooner if additional information becomes available

Central 1 - [email protected] - 1.888.889.7878, press 1

Investigating: Central 1 is investigating an issue affecting a limited subset of AFT transactions where the due date may change by one day after an AFT is created or modified.

At this time, the issue does not appear to affect all AFT transactions. Our technical teams are actively investigating to determine the conditions causing the issue and the scope of impact.

We will provide further updates as more information becomes available.

Central 1 - [email protected] - 1.888.889.7878, press 1

Resolved: Central 1 has identified an issue where some organizations may not have received the CAD Online Return Processed Items (ORPI) and USD Cheque Return (ORUI) reports dated October 19, 2026, in this morning's MERG file.

If your organization did not receive a report, or received a blank report, the missing report details will be included in tomorrow's MERG file. For Ontario credit unions, the reports will also be available in their SFTP folder.

Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

Investigating: Our Development and Support teams continue to actively investigate reports of saved login credentials unexpectedly being cleared within the iOS Forge App. This remains a high-priority investigation, and we continue to devote resources toward identifying the underlying cause.

As part of our ongoing troubleshooting efforts, we may have identified an instance where the issue was reproduced by a staff member using a debug version of the production iOS application. While this is an encouraging development, the investigation is still in progress and additional analysis is required.

We continue to encourage users testing the debug version of the iOS application to report any occurrences of this issue and provide as much detail as possible to assist with our investigation.

We understand the impact this issue has on affected users and appreciate your continued patience and cooperation. Please be assured that the investigation remains active and ongoing, and we will provide further updates as soon as significant new information becomes available.

Thank you for your continued partnership as we work toward a resolution.

[email protected] 1.888.889.7878 (option 2)

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

[email protected] - 1.888.889.7878 (option 2)

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

[email protected] - 1.888.889.7878 (option 2)

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.

[email protected] - 1.888.889.7878 (option 2)

Investigating: Our Development and Support teams continue to actively investigate reports of saved login credentials unexpectedly being cleared within the iOS Forge App. This remains a high-priority investigation, and we continue to devote resources toward identifying the underlying cause.

As part of our ongoing troubleshooting efforts, we may have identified an instance where the issue was reproduced by a staff member using a debug version of the production iOS application. While this is an encouraging development, the investigation is still in progress and additional analysis is required.

We continue to encourage users testing the debug version of the iOS application to report any occurrences of this issue and provide as much detail as possible to assist with our investigation.

We understand the impact this issue has on affected users and appreciate your continued patience and cooperation. Please be assured that the investigation remains active and ongoing, and we will provide further updates as soon as significant new information becomes available.

Thank you for your continued partnership as we work toward a resolution.

[email protected] 1.888.889.7878 (option 2)

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

[email protected] - 1.888.889.7878 (option 2)

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

[email protected] - 1.888.889.7878 (option 2)

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.

[email protected] - 1.888.889.7878 (option 2)