Live status of the card terminals and checkout APIs businesses run on. When Square or Toast go down the till stops taking money — these cards show what a real HTTP probe of each vendor's public host returns via 4 methods, plus the vendor's own status feed where they publish a readable one.
POS terminals + Square for Restaurants/Retail. A Square outage means card payments stop at the counter.
Restaurant POS — ordering, KDS, payroll. When Toast is down, most of a restaurant's front-of-house is.
Fiserv's small-business POS platform: terminals, kiosks, and the Clover dashboard.
The checkout API behind millions of sites. A Stripe blip fails carts everywhere at once.
Checkout buttons, invoicing, and P2P. One of the most panic-searched payment brands during any outage.
Enterprise payments platform behind large retailers and marketplaces worldwide.
Core processing for thousands of banks and merchants — outages surface as card declines far from the source.
The headline verdict on each card is our own measurement: an HTTP probe of the vendor's public host using 4 independent methods in parallel (HTTP/1.1, HTTP/2, browser User-Agent, curl HEAD), refreshed every 5 minutes. Where a vendor publishes a machine-readable status feed, we poll it too and show their classification as a second line — the two can disagree, and when they do, both facts belong on the page.
What this does not catch: failures inside authenticated dashboards, a single merchant's terminal losing connectivity, or vendor-side problems that never touch the public host. For those, the vendor's own status page — linked where one exists — is the better source.