Live / Authorize.net / Incident
Authorize.net: Chase Paymentech Settlement/Batching Disruption
Authorize.net · authorize.netMinor incidentResolved2026-11-10 15:04 UTC
Public — what happened
Summary
Authorize.net said an issue was affecting settlement and batching for transactions going through Chase Paymentech, which could cause customers to see delays in funding and settlement. The company posted its first notice at 12:13 UTC on 7 November 2026, giving a reported start of 01:00 GMT that day, and said at 12:32 UTC that it had identified the issue. At 13:42 UTC it reported the problem as mitigated, with a reported end time of 13:39 GMT, and said it was monitoring. The incident is marked resolved as of 15:04 on 10 November 2026.
Affected
Chase Paymentech Solutions
Timeline
- Started — 2026-11-07 12:13 UTC
- Investigating — 2026-11-07 12:13 UTC
- Identified — 2026-11-07 12:32 UTC (2 updates)
- Monitoring — 2026-11-07 13:42 UTC
- Resolved — 2026-11-10 15:04 UTC · 3 days 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 Authorize.net 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 Authorize.net: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Authorize.net report →
More from Authorize.net
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.