Payment Processing Reliability and Uptime: What Happens When Your Processor Goes Down

On September 22, 2023, Square experienced a major outage that lasted over four hours. Restaurants could not process card payments. Retail stores had to turn customers away or scramble for cash. Food trucks at busy lunch spots watched lines form and then dissolve as people realized they could not pay.

Square's status page showed the issue. Social media lit up with business owners posting screenshots of failed transactions. And for the businesses that depended entirely on Square for payment processing, those four hours meant zero revenue.

This is not a Square-specific problem. Every major payment processor has experienced outages. The question is not whether your processor will go down. The question is what happens to your business when it does.

The Real Cost of Payment Processing Downtime

Let's do the math that most business owners have never done.

Average small business revenue: $500,000 per year, or roughly $1,370 per day, or $171 per hour during an 8-hour business day.

A 4-hour outage costs that business: $684 in lost sales.

But that is the optimistic number. It assumes customers come back later. In reality, many do not. Research from payment industry analysts suggests that 30-40% of customers who cannot complete a purchase due to a payment issue do not return to complete that purchase.

If 35% of those customers are permanently lost, a 4-hour outage actually costs $923 when you factor in the sales that never come back.

For a restaurant doing $1 million per year in revenue, a 4-hour outage during dinner service costs $1,000 to $2,000 in direct lost sales plus the intangible damage of frustrated customers who may not come back.

Multiply that across a year. If your processor has 99.9% uptime (which sounds excellent), that still allows for 8.76 hours of downtime per year. At $171 per hour in lost sales, that is $1,498 per year in potential revenue loss from a processor that markets itself as "highly reliable."

And 99.9% uptime is better than what many processors actually deliver.

Real Outage History: Square, Stripe, and Toast

Understanding how often major processors go down helps you make an informed choice. Here is a factual history of notable outages.

Square Outages

September 2023 - Major Outage (4+ hours): Square's payment processing went down for sellers across the United States. Point-of-sale systems could not process card transactions. Square acknowledged the issue on their status page and social media. The outage affected millions of transactions during peak business hours.

June 2023 - Intermittent Failures (2+ hours): Square experienced intermittent payment processing failures that caused transactions to fail or time out. Some sellers reported being able to process some transactions while others failed unpredictably, which is arguably worse than a complete outage because you do not know whether to tell customers to try again.

March 2022 - Dashboard and Payments (3+ hours): Both the Square Dashboard and payment processing experienced disruptions. Sellers could not view their transaction history or process new payments. Square's status page reported "degraded performance" before eventually acknowledging a full outage.

Square publishes their status history at status.squareup.com. You can review past incidents directly.

Stripe Outages

November 2023 - API Degradation (90 minutes): Stripe's API experienced elevated error rates that caused payment failures for businesses using Stripe for online checkout. Businesses running e-commerce sites saw checkout completion rates drop significantly during the incident.

June 2022 - Partial Outage (3+ hours): Stripe experienced issues with their core API that affected payment processing for a subset of users. The outage primarily impacted businesses processing high volumes of transactions.

July 2019 - Major Outage (2+ hours): Stripe experienced a significant outage that affected all API endpoints. Online businesses could not process any payments during the incident. This was one of Stripe's most widely reported outages.

Stripe publishes their status at status.stripe.com.

Toast Outages

September 2024 - POS Disruption: Toast's point-of-sale system experienced disruptions that prevented restaurants from processing orders and payments. Restaurants reported being unable to send orders to the kitchen or process card payments.

January 2023 - Widespread Issues (5+ hours): Toast experienced a prolonged outage that affected restaurants across the country during dinner service. The timing was particularly damaging as restaurants lost revenue during their highest-volume period.

June 2022 - Intermittent Failures: Toast POS terminals experienced intermittent connectivity issues, causing transaction failures and slow processing times. Restaurants reported long wait times for card authorizations.

Toast's status page is at status.toasttab.com.

The Pattern

Every major payment processor experiences outages. The frequency, duration, and timing vary, but no platform is immune. The processors with the most users tend to have the most reported outages simply because more businesses are affected when something goes wrong.

What to Look for in Uptime SLAs

An uptime SLA (Service Level Agreement) is a contractual commitment from your payment processor about how available their service will be. Here is what to evaluate.

Uptime Percentage

99.99% uptime = 52.6 minutes of downtime per year (excellent)
99.95% uptime = 4.38 hours of downtime per year (good)
99.9% uptime = 8.76 hours of downtime per year (acceptable)
99.5% uptime = 43.8 hours of downtime per year (concerning)
99% uptime = 87.6 hours of downtime per year (unacceptable for payment processing)

Most flat-rate processors like Square and Stripe do not offer formal uptime SLAs to small and mid-size merchants. Their terms of service typically disclaim liability for downtime and do not guarantee any specific uptime level.

Traditional merchant account providers and direct processors are more likely to offer contractual uptime guarantees because they have more control over the processing infrastructure.

What the SLA Actually Covers

Read the fine print. Some SLAs only cover "core payment processing" and exclude:

Dashboard and reporting access
Settlement and funding
Peripheral features (invoicing, loyalty programs, gift cards)
Maintenance windows (scheduled downtime is often excluded from SLA calculations)

A processor can claim 99.99% uptime on "core processing" while their dashboard is down for hours, leaving you unable to see your transaction history or issue refunds.

Remedies and Credits

What happens when the processor violates their SLA? Common remedies include:

Service credits (a percentage off your next bill)
Extended contract terms
Fee waivers for affected transactions

In most cases, the service credit is a fraction of what the downtime actually cost your business. A $50 credit does not make up for $2,000 in lost sales.

The real question to ask your processor: "What is your uptime commitment, and what specific compensation do I receive if you fail to meet it?"

If the answer is vague or nonexistent, that tells you something about how much they prioritize reliability.

Your payment processor's reliability directly affects your revenue. Talk to Sleft Payments about processors with real uptime commitments and local support that answers the phone when something goes wrong.

Redundancy and Failover: Protecting Your Business

Smart businesses do not rely on a single point of failure for something as critical as payment processing. Here is how to build redundancy into your payment setup.

Have a Backup Processor

The simplest protection against downtime is having a second payment processor ready to go. This does not mean actively using two processors for every transaction. It means having a second terminal or payment method configured and tested so you can switch over quickly when your primary processor goes down.

Options for backup processing:

A standalone terminal on a different processor. If your primary POS runs on Toast, have a countertop terminal from a traditional processor as backup.
Mobile processing via phone. Services like Sleft's mobile payment solution let you process transactions using your smartphone if your primary terminal goes down.
Manual card imprinters. Yes, they still exist. For extreme situations, a manual imprinter can capture card information for later processing. This carries risk and should be a last resort.

Offline Processing Capability

Some modern POS systems and terminals can store transactions locally and process them when connectivity returns. This is called "store and forward" processing.

Not all processors support this. Ask your provider:

Does your terminal support offline transactions?
What is the maximum dollar amount for offline transactions?
How long can transactions be stored before they must be processed?
What happens if an offline transaction is later declined?

Offline processing is not perfect. You assume risk on every offline transaction because the card is not authorized in real time. But for small transactions during a brief outage, it can keep your business running.

Internet Redundancy

Many payment outages are not actually processor outages. They are internet outages at the business location. Your processor is working fine, but your connection to them is down.

Protecting against this:

Cellular backup. Many modern terminals and POS systems can fail over to a cellular connection if Wi-Fi or wired internet goes down. Confirm this feature is enabled on your equipment.
Dual ISP. For businesses where payment processing is mission-critical (restaurants, retail), having a backup internet connection from a second provider is worth the $50-100/month it typically costs.
Mobile hotspot. At minimum, keep a charged smartphone available as a mobile hotspot if your primary internet goes down.

Regular Testing

A backup plan you have never tested is not a backup plan. Once a quarter:

1. Process a small test transaction on your backup processor
2. Verify your terminal can operate in offline mode
3. Test your cellular backup connection
4. Confirm your backup equipment is charged and functional

Why Local Support Matters During an Outage

When Square goes down, you call Square's support line. You wait on hold. You eventually reach someone reading from a script who tells you what you already know: "We are aware of the issue and working on a resolution."

That person cannot fix the problem. They cannot give you a timeline. They cannot offer you a workaround. They are a call center employee managing thousands of inbound calls from panicking merchants.

This is the fundamental limitation of large, centralized payment processors. Their support infrastructure is designed for scale, not for urgency. When everything is working, their support is fine. When everything is down, their support is overwhelmed.

Local payment processors and merchant service providers operate differently. When you work with a local provider like Sleft Payments, you have a direct relationship with people who know your business. When something goes wrong, you call a number that reaches a real person who can:

Diagnose whether the issue is on the processing side or your equipment
Walk you through switching to a backup solution
Send a technician to your location if needed
Give you honest timelines based on direct communication with the processing network

The difference between calling an 800 number and getting a recording versus calling your local rep and getting a person who knows your restaurant name is significant when you are losing $200 per hour in sales.

Building a Payment Continuity Plan

Every business should have a written payment continuity plan. It does not need to be complicated. A single page covering these items is enough:

1. Primary Processor Contact Info

Support phone number
Account number
Status page URL

2. Backup Processor Info

Where the backup terminal is stored
How to activate it
Login credentials (stored securely)

3. Staff Instructions

Who is authorized to switch to backup processing
What to tell customers during an outage
Maximum transaction amount to accept offline
When to start refusing cards and requesting cash

4. Communication Plan

Who to notify when the primary processor goes down
Whether to post on social media about payment issues
How to handle pending transactions when service resumes

Print this plan and keep it near the register. When an outage hits, you will not have time to figure it out on the fly.

Do not wait for your next outage to think about reliability. Contact Sleft Payments for a free review of your payment setup, including redundancy recommendations and processors with real uptime commitments.

FAQ: Payment Processing Reliability

How often do payment processors go down?

Major payment processors like Square, Stripe, and Toast typically experience several notable outages per year, ranging from brief partial disruptions to multi-hour full outages. The exact frequency varies by provider, but no processor has a perfect track record. Check your processor's public status page to review their incident history.

What should I do when my payment processor goes down?

First, check the processor's status page to confirm it is a platform-wide issue, not a local problem. If confirmed, switch to your backup processing method. If you do not have one, announce to customers that you are temporarily cash-only. Document the duration and estimated lost sales for potential SLA claims and tax records.

Do payment processors compensate businesses for outages?

Most flat-rate processors (Square, Stripe) do not offer financial compensation for outages. Their terms of service typically limit liability to the fees paid during the affected period. Some traditional merchant account providers offer SLA-backed service credits, but these rarely cover the full cost of lost sales. Review your processor's terms of service for specific downtime policies.

What uptime should I expect from a payment processor?

Industry standard for reliable payment processing is 99.95% uptime or better, which translates to about 4.4 hours of downtime per year. Enterprise-grade processors often guarantee 99.99% uptime (under 53 minutes per year). If your processor does not publish or guarantee an uptime figure, consider that a red flag.

Can I use two payment processors at the same time?

Yes, and many businesses do. Having a primary and backup processor is a common strategy for protecting against downtime. The backup processor does not need to be actively used day-to-day. Just keep a terminal or mobile processing app configured, tested, and ready to activate if your primary system goes down. The small monthly cost of maintaining a backup is worth it compared to the revenue you lose during an outage.

How do I check my payment processor's uptime history?

Most major processors maintain a public status page: Square at status.squareup.com, Stripe at status.stripe.com, and Toast at status.toasttab.com. These pages show current status and historical incidents. Third-party monitoring services like Downdetector also track user-reported outages across payment platforms.

The Bottom Line on Payment Reliability

Payment processing is the one system in your business that cannot go down without immediately costing you money. Every hour of downtime is revenue lost, customers frustrated, and potentially permanent damage to your reputation.

The best protection is a combination of choosing a reliable primary processor, having a tested backup ready, and working with a provider that offers real support when things go wrong - not a chatbot and a status page.

If your current processor has gone down on you before, it will happen again. The question is whether you will be prepared next time.

Get a free payment setup review from Sleft Payments and make sure your business is protected.