All Systems Operational

Gateway




Operational

Transaction Processing




Operational

Reporting




Operational

Payment Engine (Point of Sale Middleware)




Operational

Sandbox




Operational

Support




Operational

Developer Portal




Operational

History (Last 7 days)

Merchants Unable to Process Transactions via Vterm Partial Service Disruption

Incident Status

Partial Service Disruption


Components

Transaction Processing


Locations

primary



December 12, 2025 7:31AM PST
INVESTIGATING

We are investigating an issue regarding merchants being unable to process transactions through the virtual terminal. Merchants may see an error message such as, “An internal error occurred (140)”.

December 12, 2025 7:45AM PST
IDENTIFIED

Our engineers have identified the issue and are working on a fix. We thank you for your patience.

December 12, 2025 8:00AM PST
MONITORING

Service has been restored and we are actively monitoring for any further issues.

December 12, 2025 10:00AM PST
RESOLVED

We have observed no further errors.
Tsys Transaction Processing Operational

Incident Status

Operational


Components

Gateway, Transaction Processing, Reporting, Payment Engine (Point of Sale Middleware), Sandbox, Support, Developer Portal


Locations

01-uswest, 02-useast, 03-uswest, 04-uswest, primary, Phone Support, Tickets



December 7, 2025 6:10PM PST
INVESTIGATING

We are aware of an issue affecting transaction processing on Tsys. Our team is actively working with the appropriate partners to resolve it and will provide updates as recovery progresses.

December 7, 2025 7:29PM PST
RESOLVED

The issue affecting transaction processing on Tsys has been fully resolved. All services are operating normally. Thank you for your patience.
FDMS Transaction ProcessingDegraded Performance

Incident Status

Degraded Performance


Components

Transaction Processing


Locations

primary



December 7, 2025 2:42AM PST
INVESTIGATING

We are aware of an issue affecting transaction processing on FDMS. Our team is actively working with the appropriate partners to resolve it and will provide updates as recovery progresses.

December 7, 2025 5:01AM PST
IDENTIFIED

This issue is currently affecting only merchants processing on FDMS. We are monitoring for additional errors while FDMS investigates. Impacted merchants may encounter the error ‘Could not connect to processor.’ Please retry any affected transactions. We appreciate your patience while this is being resolved

December 7, 2025 6:44AM PST
MONITORING

Fiserve is aware of the disconnect and have confirmed it has recovered. We have not seen any additional errors since our last update. We will continue to monitor the situation.

December 7, 2025 7:36AM PST
RESOLVED

This is now resolved.