Skip to main content
NewChargeback Protection + Fee Intelligence for high-volume merchants. Get a savings analysis and a review of your dispute handling.See how it works
Details

Chargeback Protection + Fee Optimization

See how it works: high-volume merchants get automated dispute evidence, interchange optimization, and real-time savings visibility.

See how it works

POS Offline Mode: What Actually Happens When the Internet Fails

POS offline mode lets the till keep ringing sales when the internet drops, but card behaviour varies: credit cards can often queue through store-and-forward with the merchant absorbing decline risk, while Interac debit normally requires a live connection for PIN authorization. Terminals with automatic LTE failover close most of the gap.

5 min read · RapidCents Editorial Team

Published 2026-08-22 · Last reviewed 2026-08-22

A customer at the counter of a small shop while the owner serves them

Scope: For Canadian merchants who need to understand exactly what their POS and payment terminal can and cannot do during an internet outage.

Why offline resilience belongs on your POS checklist

Internet outages are not edge cases. Fibre gets cut by construction crews, ISPs suffer regional failures, storms take down last-mile infrastructure, and plenty of Canadian businesses — from cottage-country restaurants to rural grocery stores — operate in places where connectivity is fragile on a good day. When the connection drops during a lunch rush or a Saturday peak, every minute is measured in walked-out customers.

Yet offline mode is one of the most loosely used phrases in POS marketing. Two vendors can both claim it while delivering completely different behaviour. This guide breaks down what actually keeps working when the internet fails, what silently stops, and what to demand from a vendor before you find out the hard way.

Two systems, two failure modes: POS software versus payments

A modern checkout is really two systems. The POS software manages the catalog, the cart, open tickets, and reporting. The payment side authorizes cards against the card networks. They fail differently, and a useful offline conversation treats them separately.

Cloud-first POS software with no local cache can leave you unable to even open a sale when the connection drops. Local-first designs keep a copy of the catalog on the device and queue transactions locally, then sync when connectivity returns — sales continue, though some functions such as loyalty lookups, gift card balances, and e-commerce sync pause until the connection is back.

Ask the specific question: with no internet at all, can I start a sale, modify an open ticket, print a receipt, and close the till? If the answer involves the word usually, keep probing.

How store-and-forward card payments actually work

Payment authorization ultimately requires reaching the card networks, so true offline card acceptance is a calculated risk, not magic. The mechanism is called store-and-forward: the terminal captures and encrypts the card data, approves the transaction locally, stores it in a queue, and forwards everything for real authorization once the connection returns.

The catch is in who carries the risk. If a stored transaction is declined when it is finally forwarded — insufficient funds, a cancelled card — the merchant absorbs the loss. That is why store-and-forward is typically disabled by default and, when enabled, governed by limits: a maximum amount per transaction and a cap on the total value that can sit in the queue.

Set those limits deliberately based on your average ticket size and your appetite for risk, and keep them conservative for high-value categories. A queue full of large unauthorized transactions is a liability sitting in a terminal.

The Interac problem: why debit usually stops in an outage

Here is the distinctly Canadian wrinkle: Interac debit transactions are PIN-verified and authorized online, in real time, against the cardholder's account. There is no meaningful store-and-forward path for a typical Interac debit purchase — if the terminal cannot reach the network, the debit transaction cannot complete.

That matters because debit is a large share of Canadian in-person payments, and in categories like grocery and convenience it is often the dominant tender. An outage plan that only covers credit cards leaves a big hole in the till.

Practically, a hard outage without any failover means credit store-and-forward (if enabled), cash, and goodwill. Which is exactly why the next section is the most important one in this guide.

LTE failover: the difference between a blip and a bad day

The cleanest answer to offline payments is not to be offline. Terminals with built-in cellular connectivity, or a network router with an LTE backup SIM, switch over automatically when the primary connection drops — usually within seconds. Debit keeps working, credit authorizes normally, and staff may not even notice the ISP is down.

When you evaluate failover, check the scope: a terminal with its own SIM keeps payments alive but does nothing for a cloud POS register stranded on dead Wi-Fi, while a site-level failover router protects everything on the network at once.

Ask who supplies the SIM, how the data is billed — flat monthly, usage-based, or bundled into the terminal fee — and whether the switchover is genuinely automatic or requires someone to change a setting in the middle of a rush.

Questions to ask your POS and payments vendor

• With no internet at all, can I open the till, ring items, apply discounts, and print receipts?

• Is store-and-forward supported on my terminals, is it enabled by default, and what are the per-transaction and total queue limits?

• Who is liable when a forwarded transaction declines?

• Can I keep accepting Interac debit during an outage through cellular failover, and does the failover cover the POS register too?

• How do queued transactions appear in reporting and settlement once they sync — will my deposits be delayed?

• What happens to a queued transaction if the terminal is damaged or powered off before it syncs?

Get the answers in writing. Offline behaviour is precisely the kind of detail that demo environments gloss over and real outages expose.

An outage playbook your staff can actually follow

Technology aside, the difference between a calm outage and a chaotic one is usually a laminated card by the register. Write down: how to confirm whether failover has kicked in, how to switch the POS to offline mode if it needs a manual step, which tender types to accept and what limits apply, how to log cash sales if the till itself is down, and who to call — with the account number already printed on the card.

Then rehearse it once. Unplug the router on a quiet Tuesday and watch what actually happens. A ten-minute drill teaches you more about your POS offline mode than any datasheet, and it turns your outage plan from a document into a habit.

Frequently asked questions

Can a POS system work without internet?

It depends on the architecture. Local-first POS software keeps the catalog on the device and queues sales locally, so you can keep ringing items, printing receipts, and closing the till, then sync when the connection returns. Cloud-only software with no local cache may not even open a sale. Card authorization is a separate question with its own limits.

Can I accept debit cards when the internet is down?

Generally not over a dead connection. Interac debit is PIN-verified and authorized online in real time, so there is no store-and-forward path for typical debit purchases. The practical solution is a terminal or router with automatic LTE failover, which keeps debit working through most ISP outages by switching to cellular within seconds.

What is store-and-forward payment processing?

Store-and-forward is offline card acceptance: the terminal encrypts and queues the transaction locally, then forwards it for real authorization when connectivity returns. It usually applies to credit cards only, is often disabled by default, and is governed by per-transaction and total queue limits because the merchant absorbs the loss on any transaction that later declines.

Who is liable if an offline card payment is declined?

The merchant. A store-and-forward transaction is approved locally without contacting the card issuer, so if it declines when forwarded — for insufficient funds or a cancelled card — the merchant absorbs the loss. That risk is why offline limits exist and why they should be set conservatively relative to your average ticket.

Do payment terminals have cellular backup?

Many modern smart terminals include a built-in SIM for LTE connectivity, either as the primary connection or as automatic failover. Alternatively, a site-level failover router with a backup SIM protects the whole network, including the POS register. Ask who supplies the SIM, how data is billed, and whether switchover is automatic.

How long can a POS stay in offline mode?

POS software can usually run locally for an extended period and sync later, but payments are bounded by the store-and-forward queue limits — a cap on total queued value — and by risk: the longer transactions sit unauthorized, the more exposure accumulates. Treat offline mode as a bridge measured in hours, not a way to operate for days.