Live / Gateway / Incident
Gateway: Batch Settlement Delays on Fiserv (First Data)
Gateway · transactiongateway.comMinor incidentResolved2026-10-18 05:13 UTC
Public — what happened
Summary
Gateway reported a minor incident in which settlement batches for merchants on Fiserv's First Data platforms were delayed, which could also hold up funding. Gateway said Fiserv had told it that maintenance on Fiserv's own systems was behind the delay, and it planned to send the waiting batches once those systems came back. By 04:30 UTC on 2026-10-18, Gateway said Fiserv had finished the maintenance and connectivity was back, so pending batches were being submitted while it checked that they settled properly. The incident began at 03:51 UTC and was marked resolved at 05:13.
Affected
First Data Nashville North, Credit Card Processing, First Data Caribbean, First Data Canada
Timeline
- Started — 2026-10-18 03:51 UTC
- Identified — 2026-10-18 03:51 UTC
- Monitoring — 2026-10-18 04:30 UTC
- Resolved — 2026-10-18 05:13 UTC · 1h 22m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Gateway against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Gateway: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Gateway report →
More from Gateway
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.