What Happens to Your Card Payments When the Internet Goes Down

Does your card terminal just stop working when the internet goes down?

Usually not. Most modern POS systems, including Clover and Square, switch into an offline or “store-and-forward” mode: they approve the sale on the spot, hold onto the transaction data, and submit it for real authorization once the connection comes back. The catch is who carries the risk in between. If that delayed authorization comes back declined, the loss is yours, not your processor’s.

How does store-and-forward processing actually work?

The terminal can’t reach your processor in real time, so instead of declining every sale outright, it approves the transaction locally based on stored rules (card type, amount, recent history on that device) and queues it up. Once the connection returns, usually within seconds or minutes but sometimes longer, the terminal submits the backlog of stored transactions for the authorization they should have gotten at the time of sale. Most of them clear fine. Some don’t.

Credit cards tend to hold up better offline than debit cards, since debit authorization typically depends on a real-time balance and PIN check that simply can’t happen without a connection. Credit cards are built to support that kind of delayed authorization, which is part of why offline mode leans more heavily on them.

Why does the merchant carry the risk, not the processor?

Processor documentation is consistent on this point. If an offline-approved transaction comes back declined once it’s finally submitted, you don’t get funded for it, and if the cardholder disputes it later (including a straightforward “I never authorized this” dispute), you’re the one dealing with the chargeback. There’s a partial exception: a transaction processed offline through an EMV chip read generally still qualifies for standard EMV chargeback protections. A transaction that was manually keyed in while offline does not get that same protection, which makes keyed entry the riskiest way to take a card when your connection is down.

How does Clover handle offline payments?

Clover’s own documentation confirms that Clover Mini and Flex devices can take offline payments for up to 7 days by default. You can set limits on the dollar amount of any single offline transaction and on the total amount the terminal will process offline before it locks up and refuses further offline sales, or you can turn offline mode off entirely. Clover doesn’t publish a specific default dollar limit on its own support site, so if you want to know your device’s actual current cap, check your terminal’s settings directly or ask Clover support, rather than relying on a number from a third-party forum.

Square just made offline mode the default. What changed?

In April 2026, Square flipped the default: offline payments became automatically enabled on supported hardware, including Square Register, Square Terminal, Square Handheld, the second-generation Square Stand, and the second-generation Reader for contactless and chip, for any seller who hadn’t already set a preference. Square had notified sellers back in March to review their settings ahead of the change. You can still turn offline mode off, or set a transaction limit to cap your exposure, in the Square Dashboard. Square is upfront that it can’t contact a customer on your behalf if an offline payment later comes back declined. That part is on you.

Should you leave offline mode on or turn it off?

For most merchants, leaving it on with a sensible transaction limit beats turning it off entirely. A dropped connection during a dinner rush or a Saturday retail crowd that simply refuses every card is its own kind of loss, in walked-out customers and bad reviews, not just declined fraud. The tradeoff only tips the other way if you’re already seeing a pattern of offline declines or disputes, in which case tightening the limit, or turning it off until your connectivity issue gets fixed, is the safer call.

A few things worth doing regardless of which way you land: know your device’s current offline limit and time window, not a number you half-remember; favor chip reads over manually keyed entries when you’re offline, since keyed transactions lose EMV chargeback protection; and if outages are a recurring problem at your location, the real fix is usually a backup connection (a second internet line or a cellular failover), not leaning harder on offline mode.

If you’re not sure what your current terminal supports or whether it’s time for an upgrade, our hardware page breaks down what’s actually built for high-volume, connectivity-sensitive setups.

None of this is unique to one brand of hardware. Any terminal that takes a card without a live connection is making the same bet on your behalf, approving now and hoping the authorization clears later. The specifics (time windows, dollar limits, which devices support it) differ by platform, but the underlying risk and who carries it doesn’t.

Sources:

• Clover, “Handling Offline Payments” - https://docs.clover.com/docs/handling-offline-payments
• Square, “Process card payments with offline mode” - https://squareup.com/help/us/en/article/7777-process-card-payments-with-offline-mode
• Braintree Developer Docs, “Offline Transactions” - https://developer.paypal.com/braintree/in-person/guides/offline-transactions/
• Payroc, “Offline Processing” - https://docs.payroc.com/knowledge/card-payments/offline-processing