BigCommerce Status · History · Incident #3760
RESOLVEDPayment capture failures
Minor · Started May 14, 2026 · 5:00 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
BigCommerce Status · History · Incident #3760
RESOLVEDMinor · Started May 14, 2026 · 5:00 AM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
A subset of payment capture events were failing for a subset of stores from May 14 @ 10:00 UTC until May 17 @ 14:00 UTC. The root cause has been found and fixed.
Started
May 14, 2026 · 5:00 AM
Resolved
May 14, 2026 · 5:00 AM
Duration
< 1m
Severity
Minor
Event timeline
Resolved
May 17 · 6:27 PM BigCommerceA subset of payment capture events were failing for a subset of stores from May 14 @ 10:00 UTC until May 17 @ 14:00 UTC. The root cause has been found and fixed.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT