Central 1 incident
INC220280 - Incoming/outgoing wires not processing
Central 1 experienced a notice incident on April 20, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Apr 20, 2026, 12:14 PM UTC
Central 1 is currently unable to send or receive CAD, USD, or FX wires. Wires can still be created and reviewed in PaymentStream Direct Wires. Central 1’s technical resources are actively working to restore full service. We will provide an update by 5:45 a.m. PT (8:45 a.m. ET). Central 1 – [email protected] - 1.888.889.7878, press 1
- postmortem May 07, 2026, 12:17 PM UTC
**Postmortem: INC220280 - Wire Transfer Service Disruption** On April 20, between 1:42 a.m. and 7:02 a.m. PT \(4:42 a.m. and 10:02 a.m. ET\), Central 1 experienced a service disruption impacting incoming and outgoing wire transfers. During this time, wire creation through PaymentStream Direct remained available; however, processing, transmission and transaction inquiry functions were unavailable due to an issue with a third-party service provider. The disruption was caused by failures within Fiserv’s Enterprise Payments Platform \(EPP\), which supports wire processing. As a result, wires could not be transmitted or processed, leading to delays in time-sensitive payments and increased client escalations. Service was fully restored after the vendor applied corrective actions, and normal processing resumed. To restore the wires service, Fiserv reverted an automated change and restarted the impacted servers. **Point of Failure:** The incident originated within Fiserv’s infrastructure across multiple layers. An automated process within Fiserv’s environment incorrectly modified hostname configurations on IBM MQ gateway servers, preventing MQ services from starting and halting wire message processing. In parallel, required database configuration settings were not consistently applied in the legacy environment, resulting in degraded performance, timeouts, and instability within the Enterprise Payments Platform. Together, these issues caused a complete interruption of wire processing services. **Corrective Actions:** Fiserv will reduce the likelihood of recurrence by enhancing validation and testing procedures for configuration changes to ensure all dependencies, such as server name formatting, are identified and addressed prior to deployment. Additional monitoring will also be implemented to detect and alert on wire processing delays or missing acknowledgments in real time. At Central 1, we are enhancing monitoring to improve early detection of third-party processing failures and reviewing vendor support and escalation processes to enable faster resolution. We are also assessing our internal incident handling procedures to strengthen coordination and response effectiveness during third-party outages. * Implemented an automated 4:00 a.m. PT \(7:00 a.m. ET\) end-to-end outgoing wire smoke test for early incident detection * Assessed Central 1 incident handling procedures across all teams * Completed Dynatrace knowledge transfer and documented key troubleshooting guidance and operational procedures for Computer Operators We sincerely apologize for the disruption and the impact this incident had on your operations, particularly for time-sensitive wire transactions. We appreciate your patience while services were restored. Liz Ackroyd, Manager of Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337