Live / BigCommerce / Incident
BigCommerce: Authorize.net orders coming in with an incomplete transaction ID for payments made using a stored instrument affecting a subset of stores
BigCommerce · bigcommerce.comMinor incidentResolved2026-10-23 03:46 UTC
Public — what happened
Summary
BigCommerce said some stores using Authorize.net were receiving orders with an incomplete transaction ID when customers paid with a stored payment method. It reported that this caused the Capture Payment button to be missing from the Orders interface, and it rated the issue as minor. The company began investigating at 20:14 UTC on 2026-10-22, said it had identified the problem at 23:22 UTC, and reported a fix in place at 00:51 UTC on 2026-10-23. BigCommerce marked the incident resolved at 03:46 UTC that day.
Affected
Checkout & Payment Processing
Timeline
- Started — 2026-10-22 20:14 UTC
- Investigating — 2026-10-22 20:14 UTC (2 updates)
- Identified — 2026-10-22 23:22 UTC
- Monitoring — 2026-10-23 00:51 UTC
- Resolved — 2026-10-23 03:46 UTC · 7h 33m 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 BigCommerce 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 BigCommerce: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the BigCommerce report →
More from BigCommerce
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.