Merchant Insights · Practical guidance

POS System Down? A Merchant's Payment Outage and Recovery Checklist

When the POS stops accepting payments during lunch rush, the first priority is protecting customers and the business—not repeatedly attempting charges and hoping for the best. A reliable plan separates connectivity, device, processor, and bank problems.

Published October 29, 2026 · Educational guidance with official primary sources

1. Diagnose the failure in minutes

Is one terminal affected or the entire location? Does ordinary internet access work on another device? Can the POS log in, but transactions fail? Are card-present and online channels both affected? Check the provider's official status page and your ISP without assuming the processor is down. Capture the error code and time before restarting equipment. Avoid repeatedly resubmitting transactions whose status is unknown.

2. Keep a documented fallback plan

Before an outage, inventory supported payment methods, a cellular backup connection if available, approved backup equipment, cash-handling procedures and the staff member authorized to activate contingency operations. Test network failover and transaction reconciliation periodically. Do not presume mobile hotspot access will fix failures caused by the processor itself.

3. Offline mode is not a universal safety net

Some POS products support offline payments on certain hardware, software versions and account configurations, but offline acceptance can increase the risk of declines, unpaid sales and disputes when transactions upload later. Square's official guide documents device-specific restrictions and upload deadlines. Clover's Go SDK documentation, by contrast, explicitly says its SDK does not support offline store-and-forward payments. Neither statement proves that all Clover products or all Square configurations have identical capabilities. Confirm the exact device and software workflow before relying on it.

4. What to do while payments are unavailable

Record affected times, terminal serial numbers and error codes. Inform staff which approved fallback methods are available, stop attempts on uncertain transaction status and communicate clearly with customers. Do not write down full card numbers, CVV codes or other sensitive card data as a makeshift offline method. If using an approved offline feature, follow that provider's device-specific instructions and risk limits.

5. Recovery checklist: avoid duplicate charges

Restore network and POS services using the vendor's documented sequence; confirm unsettled or pending payments in the processor dashboard before retrying them; review approved, declined and offline-stored transactions; upload transactions within the applicable limits; reconcile receipts, tips, batch settlement and bank deposits. Document and resolve any customer double-charge claims promptly.

6. Make the outage plan measurable

After each incident, record downtime length, affected registers, lost or delayed sales, number of uncertain transactions and whether backup communications worked. Assign an owner to fix the recurring root cause. For high-volume operations, consider separate network equipment, backup internet and staff drills rather than relying entirely on the payment terminal.

7. Where SalvaTap fits

SalvaTap can help merchants assess Clover setup, equipment and support options, including staff onboarding. Actual offline capabilities, processor downtime and account-level support depend on the installed products and provider. The goal is not to claim that any one processor never goes down; it is to design a business workflow that fails more gracefully.

Sources and further reading

• Square: offline payment restrictions and limits
• Clover developers: Go SDK offline payments

Related SalvaTap resources

• Clover setup and support
• Clover equipment comparison

Source review: October 29, 2026. This content is general merchant education, not legal or financial advice. Provider terms, device capabilities and card-network requirements can change and are account-specific.