Stripe Status · History · Incident #3877
RESOLVEDElevated Bancontact errors
Minor · Started May 20, 2026 · 1:50 PM
$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'] . '/'; ?>
Stripe Status · History · Incident #3877
RESOLVEDMinor · Started May 20, 2026 · 1:50 PM
Duration
15m
Severity
Minor
Detection lead
—
User reports
—
Summary
From 13:38–13:53 UTC, we saw a partial service disruption of the Bancontact payment method. This is now resolved.
Started
May 20, 2026 · 1:50 PM
Resolved
May 20, 2026 · 2:06 PM
Duration
15m
Severity
None
Event timeline
Monitoring
May 20 · 1:50 PM StripeWe're currently investigating a Partial Service disruption of the Bancontact payment method that began at 13:38 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the Bancontact payment method. We are actively monitoring the situation and will provide updates as more information becomes available.
Resolved
May 20 · 2:06 PM StripeFrom 13:38–13:53 UTC, we saw a partial service disruption of the Bancontact payment method. This is now resolved.
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