Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
At StatusCake.com we’re always look at new ways to improve not only our uptime monitoring service, but the customer experience as well.
One of the areas that hasn’t changed much since we launched is the payment gateway – where customers can sign-up or upgrade to a paid StatusCake account. Up until now we’ve been using PayPal for all our payments. Having spoken with our customers, and through the Customer Survey we understand that some of you don’t have PayPal accounts – and don’t want to sign-up for Pay-Pal just to use StatusCake. That’s completely understandable.
So we’ve listened and taken the decision to move away from PayPal as our primary payment gateway. Though for anyone who previously signed up for our downtime monitoring using PayPal your subscriptions will continue as before.
Our new payment gateway, provided by Stripe, is an industry leader – making setting up a StatusCake paid account quick-and-easy.
Safe & Secure
Most importantly all payments are safe-and-secure. Our payment gateway is certified to PCI Service Provider Level 1 – the most stringent level of certification available – with HTTPS forced across all payment transactions.
Encryption
StatusCake does not store any of your credit card details. Payment details are maintained only by our payment gateway, with card numbers encrypted with AES-256. Any decryption keys are stored by them on completely separate machines and from a separate data-centre.
Payment Gateway Now Live
The payment gateway is now live. As we’re a UK business the payment gateway will initially be priced in British pounds. Please don’t worry – you can still use your debit or credit card regardless of where you are from.
If you have any questions at all about the new payment gateway, or indeed anything about StatusCake, then please don’t hesitate to contact us on Live Chat or by email to [email protected].
James Barnes
Share this
More from StatusCake
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026