Skip to content
Live · self-reported · refreshed every 60s

Payment provider status, on one page.

What Stripe, Adyen, PayPal, Worldpay and 16 other payment and billing providers are telling the world about their own health right now – aggregated from their public status surfaces. Green means self-reported green: status pages lag and under-report, which is why we studied what these pages actually disclose.

Checking 20 providers…

Active incidents

Loading…

Each card shows the live self-reported state plus what that provider's public history looks like – from our transparency study. Where history exists its depth varies 350-fold, and where a provider publishes nothing machine-readable, we say so rather than guess.

Stripe

254-day visible history · API lives on its legacy domain; the current status page exposes none

provider status page →
Adyen

3.5-year visible history · publishes no resolution timestamps

provider status page →
GoCardless

248-day visible history

provider status page →
Wise

463-day visible history

provider status page →
Klarna

291-day visible history

provider status page →
Square

239-day visible history

provider status page →
Worldpay

50-day visible history

provider status page →
Stax

879-day visible history

provider status page →
Airwallex

80-day visible history

provider status page →
Plaid

86-day visible history

provider status page →
Chargebee

475-day visible history

provider status page →
Recurly

139-day visible history

provider status page →
Shopify

6.7-year visible history

provider status page →
Shift4

3.5-year visible history

provider status page →
Authorize.Net

621-day visible history

provider status page →
Nuvei

504-day visible history (ANZ region) · global status page is access-restricted

provider status page →
PayPal

no incident history published · live component status only

provider status page →
Braintree

no incident history published · component status via PayPal's shared platform

provider status page →
Mollie

no incident history published · live status via Instatus

provider status page →
Checkout.com

no machine-readable surface

provider status page →

How this works – and what it can't tell you

We poll each provider's public status surface (the standard status-page API where one exists; Adyen's and PayPal's own APIs otherwise) and cache the result for 60 seconds. Every state on this page is what the provider chose to publish. Three providers publish nothing machine-readable, so they are marked "not verifiable" rather than guessed at; PayPal exposes component states but no incident detail.

This page can't see incidents providers haven't posted, can't compare reliability across providers, and inherits every limitation documented in the study – including its open dataset (CC BY 4.0) if you want the history behind the live view. What it's for: one radar instead of nineteen tabs during an incident, with the self-reporting caveat kept visibly attached.

Status pages tell you what providers admit. PayRes maps what your payment stack actually depends on – and how much revenue each dependency carries – so an incident on this page becomes "these three flows are exposed", not a guessing game.

See how the platform works →