How to Take Clover POS Payments During Internet Outages
Yes — Clover works when the internet goes down, but only if you set it up before the outage. With Clover POS offline mode enabled, your device keeps accepting card payments within limits you set, stores them encrypted on the device, and submits them automatically for authorization the moment you're back online. This guide covers the exact setup steps, the limits and the 7-day rule, what does and doesn't work while offline, the honest risk you're accepting, and the recovery checklist for when the connection returns.
Short on time? The essentials
- Enable it now, not during the outage: Setup app → Payments → Offline payments → "Allow offline payments on demand." The setting is per-device — repeat on every Clover you use.
- Set conservative limits: a per-transaction cap, a total offline cap, and an approval threshold. Offline payments aren't authorized by the bank — a card that declines later is your loss.
- The 7-day rule: Clover accepts offline payments for up to 7 consecutive days offline, and queued payments must reach the processor — reconnect as soon as possible.
- Never uninstall or log out while offline — uninstalling the app deletes every stored payment.
How Clover Offline Mode Actually Works
Normally, every card payment travels from your Clover to the processor and the customer's bank for authorization in about two seconds. When the internet drops and offline payments are enabled, Clover changes the order of operations: the device accepts the card, encrypts and stores the transaction locally, and shows an offline indicator — then, when connectivity returns and you're logged in, it automatically submits every queued payment for authorization. Once authorized, funds deposit normally and customers receive receipts.
The key concept: an offline payment is a promise, not a completed payment. The bank hasn't approved anything yet. That's why Clover puts you in control of limits — and why the setup below matters more than any other step.
Offline payments are supported across the main Clover device family — Flex, Mini, and Station models — per Clover's documentation, and the setting is device-specific: enabling it on the front-counter Mini does nothing for the Flex on the patio. Configure each device.
How to Set Up Clover Offline Payments (Step by Step)
Open the Setup App on Your Clover Device
From the home screen, tap Setup. (You'll need an account with permissions to change payment settings — owner or admin role.)
Tap Payments, Then Offline Payments
Inside Setup, tap Payments and scroll to Offline payments. You'll see the master choice: Do not allow offline payments (the device declines everything when offline) or Allow offline payments on demand — select the latter.
Set Your Three Limits
Tap Edit next to each limitation and set: (1) Limit each offline payment amount — the maximum single offline transaction (defaults are high; lower it to what you can afford to lose on one bad card); (2) Limit total offline payments — the not-to-exceed total for the device while offline; (3) Require merchant approval for each offline payment over $X — below this amount staff can accept without a manager, above it the device prompts for approval. Guidance on choosing the numbers is in the next section.
Save, Then Repeat on Every Device
Tap Save. Then walk to your next Clover and do it again — the setting does not sync between devices. Front counter, bar, patio Flex: each one needs its own configuration.
Brief Your Staff (Two Sentences)
"If the screen shows we're offline, cards still work under $X — over that, get a manager. Never log out, never uninstall anything, and tell whoever's in charge right away." That's the whole training. The manager's addition: start a written or photographed record of offline sales as a backstop, and begin restoring the connection.
How to Choose Your Offline Limits
The right limits balance two costs: sales you'd lose by refusing cards, versus declines you'd eat by accepting them blind. A sensible starting framework by business type:
| Business type | Per-transaction limit | Total offline limit | Approval threshold |
|---|---|---|---|
| Coffee shop / QSR (small tickets) | $25–50 | $500–1,000 | $25 |
| Restaurant / bar | $100–150 | $1,000–2,000 | $75 |
| Retail store | $100–200 | $1,000–2,500 | $100 |
| Services (salon, repair, trades) | $150–250 | $1,500–3,000 | $100 |
Starting points, not rules — the honest question is "what total amount am I willing to lose if every offline card declined?" Set the total limit at that number. Regulars you know personally are lower risk than walk-ins; managers can approve above-threshold payments case by case.
During the Outage: What Works and What Doesn't
What keeps working
- Card payments within your limits — swipe, dip, and tap are accepted and queued (the device may prompt to confirm the offline payment).
- Cash, obviously — and the register, receipts, and order-taking continue on the device.
- Printing receipts — customers get their copy as usual; keep your merchant copies with signatures where applicable, they're your evidence if a payment is disputed later.
What doesn't work offline
- Refunds — they require a live connection to the processor; queue them for when you're back online.
- Gift cards and certain payment types — anything that must check a balance or verify online (gift cards, PIN-verified debit) can't process offline.
- Online ordering, dashboard changes, and syncing — your commission-free ordering page and any cloud-side features pause until connectivity returns (a reason to consider the LTE backup below).
Two things that destroy offline payments: uninstalling the Clover app while offline (this permanently deletes every stored payment) and staying offline past the 7-day window (Clover stops accepting offline payments after 7 consecutive days offline, and queued transactions must reach the processor to become money). Neither is recoverable. Don't test either one.
The Risk, Stated Honestly
Offline payments are accepted at your risk. Because the bank never authorized the card at the moment of sale, any card that turns out to be over its limit, canceled, or fraudulent will decline when the queue processes — after the customer left with the goods. Clover can't verify funds it couldn't reach, and the loss is the merchant's. That's not a flaw; it's the deal you're choosing over turning customers away, and it's exactly why the limits exist.
Three habits keep the risk small: keep the per-transaction limit low enough that one bad card doesn't hurt; be generous with regulars, conservative with strangers during an outage; and check the queue the moment you're back online so a declined card can be followed up while the sale is fresh (your receipt copies and order records are what let you contact the customer or, failing that, document the loss).
When You're Back Online: The 4-Step Recovery Checklist
- Reconnect and stay logged in. Clover submits the offline queue automatically once the device has internet and an active login — no button to press.
- Open the Transactions app and verify. Confirm every queued payment shows as processed. This is the step most merchants skip and the one that matters most.
- Follow up any declines immediately. A declined offline payment means contacting the customer while they still remember the purchase — your receipt copy, order details, and (for regulars) card-on-file records make this recoverable.
- Do a quick post-mortem. If the outage exceeded an hour or cost you sales, that's the signal to add backup connectivity (below) rather than lean harder on offline mode.
Not sure your offline limits, closeout, and failover are configured right? We set up all of it — free — when your Clover comes from Limelight.
Better Than Offline Mode: The Connectivity Backup Ladder
Offline mode is the safety net. The stronger play is not needing it — because with a live connection, every payment authorizes in real time (no decline risk), refunds work, and your online ordering keeps running. Three tiers, cheapest first:
| Backup | Cost | What it covers |
|---|---|---|
| Phone hotspot | Free (uses your phone plan) | Manual failover for one or two devices — fine for short outages; requires someone to set it up in the moment |
| Clover Flex with LTE | Built into the device + data service | Automatic cellular failover on the handheld — payments keep authorizing in real time with zero staff action; the strongest single upgrade for outage resilience |
| Failover router (dual-WAN with cellular SIM) | ~$100–300 + data plan | The whole network — every Clover, the kitchen printer, and online ordering — switches to cellular automatically |
For most businesses, the practical combo is a Clover Flex with LTE as the always-works device plus offline mode enabled everywhere as the last resort. If your area's internet is genuinely unreliable — rural locations, shared building Wi-Fi, storm-prone regions — the failover router pays for itself in one busy afternoon. When Limelight sets up a Clover system, offline limits, closeout timing, and the right connectivity plan are configured before you go live; it's part of why restaurants and retailers buy the same hardware from a partner instead of a box.
Clover Offline Mode Questions, Answered
Does Clover POS work offline if the internet goes down?
Yes — if offline payments are enabled beforehand. With the setting on (Setup app → Payments → Offline payments), a Clover device keeps accepting card payments within your configured limits, stores them encrypted on the device, and submits them automatically for authorization when the connection returns. Without the setting enabled, the device declines card payments while offline.
How do I turn on offline payments on Clover?
On each device: open the Setup app, tap Payments, tap Offline payments, and select "Allow offline payments on demand." Then set three limits: the maximum single offline payment, the total offline amount the device may accept, and the threshold above which a manager must approve. The setting is device-specific and takes about five minutes per device.
How long can Clover hold offline payments?
Clover devices can take offline payments for up to 7 consecutive days offline — a limit that cannot be changed — and queued payments are submitted for authorization once the device reconnects with an active login. Practically: restore your connection as fast as possible; the 7-day window is a ceiling, not a plan.
Are offline payments guaranteed money?
No — this is the critical caveat. Offline payments receive no bank authorization at the time of sale, so a card that is over limit, canceled, or fraudulent will decline when the queue processes later, and the merchant bears that loss. Conservative per-transaction and total limits exist precisely to cap this exposure.
Which Clover devices support offline payments?
Per Clover's documentation, the main device family — Clover Flex, Mini, and Station models — supports offline payments for up to 7 days. The setting must be enabled on each device individually, and integrated point-of-sale setups can behave differently, so verify on your own hardware before you need it.
Can I issue refunds while Clover is offline?
No — refunds require a live connection to the payment processor. Note the refund details (or the customer's contact information) and process it as soon as connectivity returns.
Do gift cards and PIN debit work offline?
No — payment types that must verify something online in real time, like gift card balances and PIN-verified debit, can't process offline. Standard card-present credit and signature debit payments within your limits are what offline mode covers.
What happens if an offline payment is declined later?
The transaction fails when the queue submits, and no funds deposit — so check the Transactions app immediately after reconnecting. With a declined payment, your receipt copies and order records let you contact the customer to collect another way; for regulars with tokenized cards on file, recovery is usually straightforward.
Does my Clover online ordering keep working during an internet outage?
Not through the store's connection — cloud-side features like online ordering pause until connectivity returns. This is the strongest argument for backup connectivity over offline mode alone: a Clover Flex with LTE or a cellular failover router keeps payments authorizing in real time and keeps the online ordering channel alive through most outages.
