Card payments during an internet outage: a calm plan for service counters

A payment terminal rarely stops working at a convenient moment—usually when a repair is being collected or a counter is busy. The useful response is not an improvised technical fix; it is a routine agreed in advance. It lets staff and customers see what has been checked, which payment options are genuinely available and what still needs follow-up.

Establish the scope before acting

Before anyone restarts a terminal, router or cable, one person should capture three points: is one terminal affected, does another device still have internet access, and does the screen show a specific message? A photo of the display and the time of the event make a support call much easier.

Whether a terminal can process a payment without a connection is not a universal promise. It depends on the acquirer, contract, risk settings and device. Providers document offline processing as a configured, risk-bound feature—not a default rescue option for every transaction (Adyen documentation). The reliable answer therefore belongs in the documentation for the business’s own payment provider.

A short counter routine

1. Name the interruption: “Card payments are temporarily unavailable; we are checking it.” This is clearer than guessing the cause.
2. Keep job and payment status separate: The repair, collection or sale stays visible; payment is marked “open” or “needs review”.
3. Offer only approved alternatives: Cash, bank transfer, a payment link or later payment only if the business has actually set them up.
4. Protect the record trail: Never collect card numbers, PINs or security codes in notes.
5. Mark the return to normal: After recovery, check open cases one by one against the terminal journal, receipt and, where relevant, the bank record.

One process, local guardrails

The operational core works in Germany, Austria, Czechia, Croatia, Slovenia and Türkiye: make the interruption visible, do not force an alternative payment method, and give every uncertain amount a traceable reference. Receipt, tax and cash-register obligations, however, vary by country and by contract. A contingency card should not pretend that one legal consequence applies everywhere.

For Germany, it is sensible to align the business’s receipt and retention practice with the published GoBD guidance from the Federal Ministry of Finance. Elsewhere, the same practical rule applies: do not bypass the local cash-register process because a terminal is briefly unavailable; confirm local requirements with the relevant adviser or authority.

The follow-up that closes the loop

Reconciliation stays short when nobody guesses during the incident. A list with job number, amount, time, alternative method and owner is enough. At close of business, compare those cases with the terminal journal and receipts; only then set the payment to final. Keeping jobs, contacts and statuses in one operational view can make open payments easier to work through without creating a separate shadow system.

Questions teams often ask

Should we restart the router immediately?

Only if the internal procedure says so and it is clear whether other devices are also affected. Restarting without a note makes later diagnosis harder.

Can we try the payment again later?

Only after checking whether the first attempt was actually not processed. The terminal journal and provider guidance are more reliable than memory at the counter.

Is a handwritten list enough?

It can be a short-term work list if it contains no sensitive card data and each case is promptly transferred into the normal record.

This routine does not replace the payment provider’s instructions or professional tax advice. It does make an interruption calmer, more transparent and easier to audit.