TL;DR: Square Payments Not Working — most cases trace to a config mismatch, a hidden assumption, or a step skipped during setup. The fix path below covers the high-percentage causes first. If you're still stuck after 10 minutes, text PJ — most issues answered in one reply. 858-461-8054.
Operator Problem Guide
Square Payments Not Working
Square payments stop working in 2026 for five main reasons: a Reader connection issue (Bluetooth unpaired, dead battery), an outdated Square app on the POS device, a card type your account does not accept, a transaction amount above your per-transaction ceiling, or an account hold triggered by unusual activity. The cause determines the fix — blindly retrying wastes time.
Why This Happens
Configuration gaps between tools or services
Missing integrations or manual workarounds that weren't designed to scale
Changes in vendor behavior, pricing, or API that weren't communicated clearly
What To Check First
Verify your current setup matches the vendor's latest documentation
Look for recent changes — platform updates, new team members, configuration drift
Check if the problem is consistent or intermittent (different root causes, different fixes)
When To Escalate
The problem is costing you money or customers per week
You've spent more than 2 hours on it without progress
A vendor quoted you more than $500 and you're not sure if it's necessary
Dealing with this right now?
Start with the simplest check: is the Square app updated to the latest version? Outdated apps are responsible for 30% of in-person payment failures. Next, check your Square Dashboard for any account notifications — Square emails the registered address when holds are placed, but those emails land in spam more often than not. For API failures, the Square Developer Console shows error codes: `CARD_DECLINED` with sub-type `INSUFFICIENT_FUNDS` vs `DO_NOT_HONOR` requires different customer messaging.
