58 recorded Magensa incidents since December 2020, with official updates, affected components, duration and resolution information.
Today, between 2:42pm and 2:46pm PT, Magensa services encountered processing errors. Normal transaction handling has resumed.
Update on Intermittent Service Degradation Affecting Multiple Applications - INC022546902 An update has been posted This issue has recurred, Fiserv continues to take remediation activities. Some users may continue to experience intermittent latency and transaction timeouts affecting the following applications: Commerce Control Center (CCC) CommerceHub Spin Catalyst Pay by Bank Rapid Connect Marketplace Money Network Mobile Money Network IVR Money Network CMS uCom / Connected Commerce Technical teams remain actively engaged in implementing and validating mitigation measures, with a focus on restoring service as quickly as possible. Further updates will be provided as additional information becomes available or by 7:00 p.m. ET. Time posted Oct 19, 21:54 UTC
Magensa is closing this notification with the following from FISERV that repairs/work are ongoing: Update on Intermittent Service Degradation Affecting Multiple Applications - INC022546902 An update has been posted Fiserv has engaged additional vendor's and continues to investigate the cause of the latency and timeouts for additional remediation activities. While we work to resolve the overall issue, some users may continue to experience intermittent latency and transaction timeouts affecting the following applications: Commerce Control Center (CCC) CommerceHub Spin Catalyst Pay by Bank Rapid Connect Marketplace Money Network Mobile Money Network IVR Money Network CMS uCom / Connected Commerce Further updates will be provided as additional information becomes available or by 8:00 p.m. ET Time posted Oct 19, 23:01 UTC
The following notification was received from FISERV: Update on Intermittent Service Degradation Affecting Multiple Applications - INC022546902 Incident status: Identified Fiserv has identified an intermittent latency condition impacting the CommerceHub, Pay by Bank, Rapid Connect, and uCom platforms, resulting in elevated transaction timeout rates. Mitigation actions have been implemented, including traffic rerouting, and teams are actively monitoring performance to validate service recovery. Investigation and monitoring efforts remain ongoing, and additional actions will be taken if required to fully restore service stability. Further updates will be provided as they become available. Time posted Oct 19, 16:37 UTC
Update on Intermittent Service Degradation Affecting Multiple Applications - INC022546902 An update has been posted The impact associated with the intermittent latency condition affecting the CommerceHub, Pay by Bank, Rapid Connect, and uCom platforms has been mitigated as of 12:15 p.m. ET. The condition resulted in elevated transaction timeout rates for some users. Fiserv teams continue to actively monitor platform performance and are prepared to take additional actions if necessary to ensure full service restoration. Further updates will be provided as information becomes available or by 3:00 p.m. ET. Time posted Oct 19, 17:14 UTC
Intermittent partial latency and time outs possible from 8:47pm PT to 8:55am PT. Services currently fully operational, monitoring ongoing.
This incident has been resolved.
Magensa is tracking some MPPG/DAF long running or disconnecting transactions when sending to the TSYS production endpont. It appears isolated to the LAX datacenter environment. Log analysis indicates the lag or disconnect events are occurring during or after connecting to the TSYS endpoints. Most of these failures will return 721 or 5000 errors. This is not a magensa processing issue.
The incident was resolved.
The following incident is being report by WorldPay for their Express payments transaction processing - possible declines: Initial Incident #: INC0658940 Incident Start: 2026-09-21 07:12:00 UTC | 2026-09-21 03:12:00 EDT Platform Affected: Integrated Payments - Express - Transaction processing Issue: There is an incident which is intermittently affecting transaction processing on the Integrated Payments - Express platform. Status: Initial Impact: Some transactions may be declined. Actions Taken to Restore Service: Worldpay technical resources are working to identify and resolve the issue. NEXT UPDATE : 2026-09-21 18:00:00 UTC | 2026-09-21 14:00:00 EDT Worldpay Incident Communication Management Global Command Center
FYI: resolved: Final Incident #: INC0658940 Incident Start: 2026-09-21 07:12:00 UTC | 2026-09-21 03:12:00 EDT Platform Affected: Integrated Payments - Express - Transaction processing Issue: There was an incident which intermittently affected transaction processing on the Integrated Payments - Express platform. Status: Final Impact: Some transactions may have been declined. Actions Taken to Restore Service: Worldpay technical resources resolved an internal issue to restore service. Worldpay teams will continue to monitor the environment for stability. Incident Resolved: 2026-09-21 16:49:00 UTC | 2026-09-21 12:49:00 EDT Worldpay Incident Communication Management Global Command Center
This is notification of a Non-Magensa related incident: Worldpay is reporting the following: Issue: There is an increase in failures for transactions authorizations processing on the Integrated Payments - Express, MercuryPay, and triPOS Cloud platforms. Status: Initial Impact: Some transactions may be declined. Actions Taken to Restore Service: Traffic has been redirected to mitigate the impact to clients. Worldpay technical resources are working to resolve an internal network issue and restore service. NEXT UPDATE : 2026-08-19 17:30:30 UTC | 2026-08-19 13:30:30 EDT
Worldpay update: Resolved. Incident Start: 2026-08-19 16:09:00 UTC | 2026-08-19 12:09:00 EDT Platform Affected: Integrated Payments - Transaction Authorizations Issue: There is an increase in failures for transaction authorizations processing on the Integrated Payments - Express, MercuryPay, and triPOS Cloud platforms. Status: Final Impact: Some transactions may have been declined. Actions Taken to Restore Service: Traffic was redirected to mitigate the impact to clients. Worldpay technical resources will continue to monitor the environment for stability. Incident Resolved: 2026-08-19 16:40:00 UTC | 2026-08-19 12:40:00 EDT
We are aware of a service interruption with Magensa and are currently investigating. The outage began at 7:45 am PST. We will continue to provide updates as our investigation continues.
We have identified the interruption as part of a broader Microsoft Azure health status issue. We will continue to investigate and provide updates as we further understand the situation.
We have identified the current outage to be a Microsoft Azure issue that they are currently working on. Microsoft Response: Microsoft has acknowledged the disruption and stated they are actively investigating the issue under incident ID MO1437424. In the meantime, we have an alternative processing path that you can take advantage of. Depending on the Magensa service you are using, replace your current endpoint URL with one of the following below (ie. If you are using MPPGv4, Replace your current endpoint with https://mppg.magensa.net/v4/MPPGv4Service.svc Decrypt V2: https://decrypt.magensa.net/decrypt.svc (Client certificate and IP restricted) Decrypt V3: https://decrypt.magensa.net/V3/decrypt.svc (Client certificate and IP restricted) Decrypt and Forward (DAF) v3: https://daf.magensa.net/V3/Service.svc Decrypt and Forward (DAF) v4: https://daf.magensa.net/V4/Service.svc MPPG v3: https://mppg.magensa.net/v3/MPPGv3service.svc MPPG v4: https://mppg.magensa.net/v4/MPPGv4Service.svc Unigate: https://mppg.magensa.net/unigate We will continue to update you as we get updates from Microsoft.
We are awaiting updates from Microsoft, and we continue to explore additional options for restoring service.
Microsoft Azure services are now fully operational. The issue has been resolved.
Microsoft identified a recent change that was strongly correlated with the onset of impact. They have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Magensa Customers should observe recovery at this time. We are closely monitoring service health and will provide additional updates if necessary.
From WorldPay Incident Communications: Final Incident #: INC0505900 Incident Start: 2026-05-20 07:42:00 UTC | 2026-05-20 03:42:00 EDT Platform Affected: Integrated Payments - Express, MercuryPay, triPOS Cloud Issue: There was an incident affecting transaction processing on the Integrated Payments - Express, MercuryPay and triPOS Cloud platforms. Status: Final Impact: Some transactions may have resulted in an error. Actions Taken to Restore Service: Worldpay technical resources identified an unexpected issue during a scheduled change event. Worldpay will continue to monitor the processing environment for stability. Incident Resolved: 2026-05-20 08:12:00 UTC | 2026-05-20 04:12:00 EDT Worldpay Incident Communication Management Global Command Center
Slow/Intermittent transaction processing. Impacted services: MPPG, Unigate, DAF, Decrypt Network connections may have been delayed or rejected resulting in retries or failures (500 errors).
Magensa Unigate Service is down. We're working to resolve the issue.
As of 11:28am PT, this incident was resolved
We are currently investigating an intermittent Decryption failure issue.
This incident has been resolved.
Beginning at or around 7:17am PT today we started seeing long running transactions (> 20seconds) for MPPG/DAF transactions processing through Heartland – Production endpoints. Magensa systems are processing requests normally but the Processor Response coming back are showing the following messages: “System Error” or “Transaction has timed out. You may need to submit a reversal for the transaction.” The processor endpoint generating this error is: https://api2-c.heartlandportico.com/Hps.Exchange.PosGateway/PosGatewayService.asmx We will continue monitoring this situation.
The processor is aware of the issue and is working to resolve the situation.
It appears the Heartland processing issue has been resolved.
At 1:46pm PT transaction connections started failing. Communications issue has been resolved as of 1:52pm PT and should be processing normally. Investigation is ongoing.
This incident has been resolved.
Magensa services are currently unreachable. This is being investigated.
Connectivity restored.
We are investigating reports of intermittent connectivity/processing errors at this time.
A remedy has been implemented and we are monitoring results.
Issue has been resolved.
This incident has been resolved.
Intermittent processing errors with message similar to "Unable to read data from the transport connection" causing transaction failures has been resolved.
Notification: TSYS is currently experiencing connectivity/processing errors resulting in Magensa rsponses showing the following: "Payload post failed. Message The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."
Appears TSYS processing issue is resolved.
We are aware of a Magensa Service interruption and are currently investigating.
We are continuing to investigate this issue.
The system is running.
Magensa is aware of an intermittent service interruption for the QwickCards and RS2/RS3 services. We are currently investigating the issue and hope to have it resolved quickly. Please visit the status page for updates: https://magensa.statuspage.io
Issue Resolved
We are continuing to investigate this issue.
This incident has been resolved.
