Live

Payments Disruption

The issue affecting some debit-card transactions is now resolved. Your business operations are essential to us, and our Engineering team has implemented measures to strengthen our systems against similar incidents. We appreciate your patience throughout this resolution process.

The latest update from Square.

State

Resolved

Started

52 d ago

2026-09-10 21:14 UTC

Lasted

17 min

until 2026-09-10 21:30 UTC

Worst impact

Degraded

Timeline

2 updates
21:1421:1821:2221:2621:30
DegradedUpdate postedTimes in UTC

Investigating

17 min 100%

Updates

Times in UTC

As posted by Square

Resolved2026-09-10 21:30 UTC

The issue affecting some debit-card transactions is now resolved. Your business operations are essential to us, and our Engineering team has implemented measures to strengthen our systems against similar incidents. We appreciate your patience throughout this resolution process.

Investigating2026-09-10 21:14 UTC

We are continuing to work on a fix for payment processing. Sellers will experience a disruption with some debit-card transactions that may fail or be unavailable due to an issue with a third-party payment-processing partner. Sellers can use another available payment method as an alternative for now. We understand how important it is for all of our services to be running for your business, we'll be back with further updates as they come to hand. Thank you for your patience with us as we work to resolve this issue.

Square in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

15

Days with an incident

25

Median duration

1 h 47 min

This incident

84% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 1 h 47 min
90 days agoToday

Other Square incidents

All incidents

Square·Service Disruption

The issue causing delays in orders syncing across devices, including orders reaching kitchen displays, is now resolved. Your business operations are essential to us, and our Engineering team has implemented measures to strengthen our systems against similar incidents. We appreciate your patience throughout this resolution process.

Resolvedresolved 5 d ago

Square·Service Disruption

We recently experienced a disruption that impacted some Square services. We understand how important it is for all of our services to be running for your business, and our Engineering team is actively discussing how to prevent future disruptions like this one. Thank you for your patience with us as we worked to resolve this issue.

Resolvedresolved 15 d ago

Square·Service Disruption

The issue preventing some sellers from adding their Square Credit Card to digital wallets such as Apple Pay is now resolved. Your business operations are essential to us, and our Engineering team has implemented measures to strengthen our systems against similar incidents. We appreciate your patience throughout this resolution process.

Resolvedresolved 25 d ago

Square·Service Disruption

Services have now recovered. Reporting in Dashboard may be delayed. Tip Adjustments that were previously failing can now be entered. We recommend doing so today.

Resolvedresolved 36 d ago

Square·Service Disruption

JCN card processing has been restored to full functionality. Your business operations are essential to us, and our Engineering team has implemented measures to strengthen our systems against similar incidents. We appreciate your patience throughout this resolution process.

Resolvedresolved 38 d ago

Follow Square

Your coding agent knows when Square is down, and tells you when a failure is theirs, not yours. You can also get Square incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "square" and tell me if Square has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=square
Slack
/feed subscribe https://outages.cc/feed.xml?providers=square

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane