The short answer
When a payment terminal goes offline, first establish whether a payment is pending and whether the fault affects one device, the local network or the provider. Preserve transaction records, follow the device’s current troubleshooting instructions, and use only a previously approved backup payment process.
Pause long enough to understand the last payment
A checkout queue creates pressure to press the payment button again. Before doing that, identify the last order and read the terminal’s result. A timeout, a decline and a payment stored for later processing are different outcomes. If you cannot establish the status, use the provider’s support process before treating the payment as a definite failure.
Assign one staff member to the payment problem and another, where available, to explain the delay. Record the start time, terminal identifier, location and exact error. Avoid writing down card numbers or photographing a customer’s payment details.
Your immediate objective is to prevent uncertainty from spreading across several orders. Mark affected orders for follow-up and keep the payment record linked to the order record.
Separate a device problem from a wider outage
Use this sequence as a diagnostic worksheet, then follow the instructions for your actual equipment:
- Power and connection: inspect normal power indicators and whether the expected network connection appears.
- Scope: determine whether one terminal or several are affected.
- Network: check whether another authorized device can use the same connection.
- Provider: check the official service-status page or contact verified support.
- Recent change: note a moved terminal, new router, software update or other relevant event.
Square’s Terminal troubleshooting documentation illustrates checks for Wi-Fi, Ethernet, a second device and provider-directed restart steps. Its instructions are specific to Square hardware. Do not assume another terminal has identical buttons, network requirements or reset behavior.
Record what you tried and its result. “Other terminal works; this terminal cannot connect” gives support more useful information than “cards are down.” Keep network credentials out of the incident notes.
Protect any payments stored offline
Offline acceptance is a supported product feature only where the provider, hardware and configuration allow it. It is not the same as a confirmed online authorization. Square’s offline-payment documentation, for example, identifies eligible equipment, upload deadlines and the merchant’s responsibility for payments that later expire, decline or are disputed. Check your own provider’s current conditions before using the feature.
Square also warns that signing out, deleting the app, changing certain operating settings or factory-resetting while offline payments are pending can permanently lose those payments. This is a concrete reason to check the queue before trying a dramatic reset. For other systems, ask support which actions could erase pending records.
Write the actual reconnect deadline and responsible person into your incident record. Do not borrow another provider’s deadline or assume that a stored payment will necessarily be collected.
Use a fictional outage to rehearse the handoff
Imagine a fictional repair shop taking a $126 payment when its terminal displays a connection error. The employee records order R-42 and asks the manager to check its status. The manager sees a pending offline entry under that order. A second employee tells the customer that confirmation is still being checked; nobody creates another $126 payment.
The team follows its existing provider-approved recovery procedure. Once connectivity returns, the manager checks the original entry’s final result and matches it to the order. Only then does the team decide whether any further payment action is needed under the provider’s guidance.
For new customers during the outage, the shop uses its documented backup options, if available. Those might include cash or an existing approved payment channel. Staff do not improvise by collecting card details in a notebook or personal messaging app.
This scenario does not promise that offline processing will succeed. It shows how clear ownership and order references reduce the chance of accidentally collecting the same payment twice.
Verify recovery and improve the next response
“The internet is back” is the beginning of recovery, not the entire checklist. Confirm that affected devices reconnect and review each pending payment’s outcome. Match successful payments to their orders, investigate failures and reconcile any later payout differences.
Keep a short closing record: outage start and end, affected devices, order references, unresolved amounts, support case number and next action. Have the responsible person sign off on exceptions rather than assuming every stored item uploaded.
After the immediate issue is resolved, prepare a one-page runbook. Include verified support contact routes, the location of current device instructions, the person authorized to change settings and any approved backup process. Rehearse it during a quiet period. Staff should know where the guide is before a busy checkout makes it necessary.
Review repeated incidents with the provider or network professional. The record can help distinguish a recurring local connectivity issue from a device fault without guessing that replacing the whole system will fix it.
Include reliability questions in your provider review
When evaluating payment equipment, ask about connectivity options, outage support, offline eligibility and staff training. Start a merchant-services conversation with basic business and contact information.
Opulent Lending receives your inquiry and coordinates an introduction to Green Payment Solutions. GPS and the applicable provider handle payment-processing proposals, approval, onboarding and service. Supported features and approval depend on the proposed setup; uninterrupted service and savings are not guaranteed.
Frequently asked questions
Should I factory-reset a terminal as the first step?
No. First check for pending transactions and follow the current device instructions. Some reset or sign-out actions can erase stored offline payments.
Does an offline payment mean the money is guaranteed?
No. The payment may still fail after connectivity returns. Eligibility, upload deadlines and merchant responsibility depend on the provider and equipment.
Can I keep taking payments during an outage?
Only through an available, approved process your business understands. Check supported backup options and limitations before an outage; do not assume every reader or payment method works offline.
Sources and further reading
Original sources used to prepare this guide. Provider terms and network requirements can change; check the linked source and your applicable agreement.
About this guide. Prepared by Opulent Lending for general merchant education. Opulent receives inquiries and coordinates introductions to Green Payment Solutions. It does not promise a particular rate, approval or savings.
Read our editorial policy. For a correction, email support@opulentlending.com with the page link and the issue.
