The customer is ready to pay, but your terminal will not complete the transaction. Your staff need a clear next step: check what failed, confirm whether a payment went through and use a backup method that is actually supported.
That plan is worth building before an outage. An advertised uptime percentage cannot tell you whether your internet connection, device or checkout software is working. A useful backup plan explains what your team can do with the equipment and services your business already uses.
First, identify what stopped working
Start with a few simple observations. Is one terminal affected or every device? Can other systems reach the internet? Does the payment provider report an incident? Record the time and the error message without capturing customers’ payment details.
Different failures need different responses. A backup internet connection may help when the problem is your local connection. It will not repair a failure inside a payment provider’s service. A spare terminal connected to the same failing network may not solve the problem either.
Keep the relevant support numbers and official status-page links somewhere staff can reach without opening the affected system. Assign one person to coordinate the response so several employees are not independently restarting equipment or retrying the same payment.
Check uncertain payments before taking another one
A timeout is not the same as a confirmed decline. An interrupted connection can leave you uncertain whether a payment request reached the provider.
Stripe’s error-handling documentation describes this uncertainty and the safeguards developers use when retrying requests. For a business owner or cashier, the practical step is to check the transaction through the provider’s supported process before collecting payment again.
If the result is still unclear, contact support and record the transaction reference. Avoid asking the customer to repeat the payment several times or immediately moving the same sale to another system without checking its status. Your backup plan needs a way to identify and resolve possible duplicates.
Confirm what offline payments mean for your setup
Some systems support collecting card payments while disconnected, with processing completed after reconnection. Availability depends on the device, software, payment method and configuration. Ask your provider to confirm your exact setup and demonstrate the procedure.
Offline collection carries risk. Square’s official offline-payment guidance explains that merchants remain responsible for expired, declined or disputed offline payments and that supported devices have reconnection and upload deadlines. A stored offline payment is not a guarantee that the business will receive the money.
Agree on transaction limits, which staff can use the feature and when they should decline an offline sale. Keep the provider’s recovery instructions with the checklist. Square, for example, warns that actions such as signing out or factory-resetting a device with pending offline payments can permanently lose those payments. Follow the instructions for your actual system rather than applying one provider’s procedure to another.
Choose backup options that fit the failure
Discuss practical alternatives with your provider before relying on them. A supported cellular connection, a compatible spare device or a documented offline mode may address different problems. Ask what each option costs, what it requires and which failures it will not cover.
A payment link is only useful if the customer and the required payment services can reach it. A second processing account also introduces separate setup, fees and reconciliation; it is not automatically the right answer for a small business.
Where appropriate for your business, decide whether staff can accept cash, arrange a later invoice or pause the sale. Consider the amount at risk and whether goods or services have already been delivered. Do not improvise by collecting card details in ordinary email, text messages or spreadsheets.
Practise the response and reconcile afterward
Walk staff through a short scenario with your provider’s approved test or training procedure. They should know how to identify the problem, check an uncertain payment, contact support and explain the available options to a customer. Avoid repeated live charges simply to test whether the system works.
After service returns, review pending payments, uploaded offline transactions, retries and refunds. Match them against invoices or sales records, and follow up on exceptions before assuming the day’s payments are complete.
If a proposal includes an uptime commitment, request its written terms: what service is covered, how availability is measured, exclusions and any remedy or claim deadline. Do not assume a service credit reimburses lost sales. Record payments collected later separately from sales permanently lost when assessing the incident’s impact.
Put your plan on one page
Your staff guide should identify the person in charge, support contacts, transaction-status checks, approved fallback methods and recovery steps. Review it whenever your devices, software or payment provider change.
Platinum can help you review your payment-processing setup and identify the support and backup questions to resolve with the providers involved. Request a free merchant analysis and tell us how your business takes payments and where interruptions create problems. Any backup capability or service commitment needs to be confirmed for the proposed arrangement.
