What to do when your card terminals go offline: quick actions and recovery plan
Card terminals can fail at the worst times. This guide gives a concise, action-first playbook for staff, script-ready customer communication, quick technical checks, and follow-up reconciliation to recover payments and customer trust.
- Quick, prioritized actions to keep sales moving and customers calm.
- Short troubleshooting checklist to restore terminals or enable alternatives.
- Post-incident steps: refunds, reconciliation, preventive controls to avoid repeat outages.
Quick answer — immediate outcome and top actions
Immediate outcome: keep revenue flowing using manual or digital backups, preserve accurate records for reconciliation, and maintain customer trust with clear communication.
Top actions (first 10 minutes): 1) Tell staff the outage protocol, 2) Switch to backup payment workflows (contactless app, manual imprint or keyed entry), 3) Display a calm customer message and use scripts, 4) Log transaction details for later reconciliation, 5) Escalate to payments/IT provider.
How terminal outages typically occur
Outages usually stem from one of three domains: network and connectivity issues, hardware or power faults, or provider-side service interruptions. Human errors and software updates can also break terminals unexpectedly.
- Connectivity: Wi‑Fi drop, ISP outage, or blocked ports on the network firewall.
- Hardware: battery failure, damaged card reader, or faulty power adapter.
- Payment processor: scheduled maintenance, certificate expiration, or gateway downtime.
- Software/config: recent configuration changes, incorrect PCI settings, or incompatible firmware updates.
Immediate staff actions when terminals fail
RAPID, consistent responses keep customers calm and limit revenue loss. Use a single, known protocol so every staff member acts the same way.
- Announce the outage protocol and assign roles: front-desk host, backup payment operator, IT contact, manager.
- Activate pre-approved alternative-payment workflows (see section below).
- Start a transaction log: customer name, items, amount, time, method used, staff handling.
- Inform customers proactively — short, helpful message at point-of-sale and receipts if needed.
- Escalate to your payments provider and internal IT with timestamps and terminal IDs.
Communicating clearly with customers (scripts)
Scripts reduce staff stress and ensure consistent tone. Keep language empathetic, concise, and action-oriented.
- When a customer approaches the till:
- “We’re experiencing a card terminal issue right now. We can take payment by mobile tap, keyed card entry, or we can email you a secure payment link — which do you prefer?”
- If you need their patience:
- “Thanks for bearing with us — this should take just a minute. If you’d rather, we can hold your order and call you when we’ve restored the terminal.”
- When offering refunds or later charges:
- “We’ll process your payment now using [method]. If you prefer to be charged later, we can take your details securely and confirm by email once the terminal is back online.”
Fast alternative-payment workflows to enable
Pre-approve and train staff on 2–3 backup workflows so switching is seamless.
- Contactless mobile payments: Accept Apple Pay, Google Pay via staff devices or QR code links.
- Secure payment link: Email/SMS a one-time secure link (merchant gateway) — great for remote capture.
- Keyed entry (card‑not‑present): Take card number, expiry, CVV only if PCI-trained and with manager sign-off; prefer tokenization post-restore.
- Manual imprint (if available): Use for high-trust returns with customer signature; take photo of customer ID for large transactions only if policy allows.
- Invoice / deferred payment: For B2B or high-ticket items, issue invoice with clear due date and terms.
| Method | Speed | PCI risk | Best use |
|---|---|---|---|
| Mobile tap / QR | Fast | Low | Retail, quick service |
| Secure link (email/SMS) | Moderate | Low | Remote payments, order pickup |
| Keyed entry | Moderate | Higher | Small amounts, trained staff |
| Manual imprint | Slow | Medium | Legacy scenarios, offline fallback |
On-the-spot technical troubleshooting checklist
Work top-down: quick checks first, then escalate. These steps are actionable for non-technical staff.
- Power & connections
- Confirm the terminal has power and the display is on; swap power cable if spare available.
- If battery-powered, try a charged spare or plug into power directly.
- Network
- Check Wi‑Fi indicator and reconnect to the correct SSID; try switching to a guest network or tethering from a manager’s phone.
- Restart the router and terminal in sequence: router first, then terminal after 60s.
- Processor and app
- Verify the payments app is up-to-date; restart the app or device.
- Check for provider outage via their status page (search “
status”).
- Security and ports
- Confirm no recent firewall or VLAN changes blocked payment ports; IT should verify port allowlist for the processor.
- Logs and error codes
- Record any error code verbatim and take a photo of the terminal screen for support.
Post-incident reconciliation and refunds
Accurate, timely reconciliation prevents chargebacks and accounting headaches. Prepare to map offline transactions to later captures.
- Collect transaction logs created during the outage: receipts, customer contact, staff notes, timestamps, authorization codes if obtained.
- For keyed or link payments, verify settlement reports against bank deposits and processor records.
- Issue refunds promptly for duplicate or incorrect charges; document refund reason in the system and notify the customer.
- If you authorize later capture (tokenized pre‑auth), follow stored card policies and obtain written customer consent where required.
| During outage | Post-restore step | Owner |
|---|---|---|
| Secure payment link used | Match link ID to settlement and reconcile | Payments lead |
| Keyed card entry | Verify CNP fees and receipts; attach signed record | Manager / Finance |
| Manual imprint | Confirm merchant batch upload; file scanned impressions | Operations |
Preventive measures and monitoring setups
Invest a small amount of prep to avoid high-cost outages. Focus on redundancy, monitoring, and staff readiness.
- Redundancy: maintain two independent connectivity paths (wired + cellular or Wi‑Fi + phone tethering) and spare terminals for peak hours.
- Regular maintenance: schedule firmware updates in low-traffic windows and test backups monthly.
- Monitoring: subscribe to your payments provider status feed and configure SMS/Slack alerts for outages.
- Run tabletop drills quarterly so staff can switch to backup workflows without hesitation.
- Document PCI-safe procedures for keyed entry, secure links, and tokenization to reduce compliance risk.
Common pitfalls and how to avoid them
- Pitfall: No backup workflow. Remedy: Pre-authorize 2 alternative payment options and train staff monthly.
- Pitfall: Poor communication causing upset customers. Remedy: Use short, empathetic scripts and visible signage at POS.
- Pitfall: Incomplete logs that block reconciliation. Remedy: Keep a simple paper/electronic outage log template and require completion.
- Pitfall: Trying complex tech fixes during rush. Remedy: Limit frontline troubleshooting to 2–3 safe steps; escalate the rest to IT.
- Pitfall: Ignoring provider status updates. Remedy: Subscribe to provider status and share incident links with customers when appropriate.
Implementation checklist
- Create and post a one-page outage protocol at each POS.
- Enable and test at least two alternative-payment methods monthly.
- Set up payments-provider status alerts and an escalation contact list.
- Train staff with short scripts and tabletop exercises each quarter.
- Keep spare power/network gear and one backup terminal available.
FAQ
- Q: Can we legally take card numbers over the phone or email during an outage?
- A: Only if staff are PCI-trained and your merchant agreement permits keyed entries; use tokenization and minimize stored data.
- Q: How long should we wait for a terminal to reconnect before switching to backups?
- A: Decide a clear threshold (commonly 60–120 seconds). If no quick fix, switch immediately to a backup workflow to avoid delays.
- Q: What if a customer refuses alternative methods?
- A: Offer to hold the order and call when systems return, or issue an invoice/secure payment link. Keep the tone helpful and offer compensation if appropriate.
- Q: How do we handle chargebacks from keyed transactions during outages?
- A: Retain all supporting docs (signed receipts, logs, communications). Submit them to the processor promptly; expect higher CNP fees.
