Square Offline Payments in a Restaurant Outage: Device Limits, Deadlines and a Handoff Sheet

Yes, if your device and app support it and offline payments are turned on. When the internet drops or Square goes down, a supported Square POS keeps taking chip and contactless cards (plus cash) and stores the card payments on the device as pending. Pending isn't approved. Nothing is charged until that device gets back online and uploads, and some payments will come back declined.

Three rules reduce avoidable losses:

• Know your device's limit. Square Stand and the Square Reader for contactless and chip (2nd generation or 1st generation v3) stop taking offline card payments 24 hours after the offline session starts. Square doesn't list a separate limit for the Square Reader for magstripe (see Step 1). Older 1st generation v1 and v2 contactless and chip readers can't take offline cards at all. Square lists no 24-hour acceptance cutoff for Square Register, Square Terminal or Square Handheld.
• Upload as soon as you can. Square's offline payments article says pending payments expire 72 hours after the offline session starts, and it strongly recommends uploading within 24 hours to cut chargeback and decline risk. Expired payments can't be retrieved or reprocessed. Other Square pages count the 72 hours from the first payment instead, and if nobody saw when the session started, you don't know how much time is left. Step 4 covers both cases.
• Don't wipe the device. While anything is pending, nobody signs out of the Square app, deletes it, switches modes, switches locations or factory resets the device. Square says that permanently loses the pending payments. Restarting or powering off is allowed, as long as the device is turned back on and uploads in time.

We built this from Square's U.S. Support Center articles and two Square PDF guides as they read on October 5, 2026. We didn't simulate an outage or take payments on a Square account. The restaurant, devices, times and dollar amounts in the example are made up, and the arithmetic is ours.

Step 1: Check which devices can take cards offline

Don't assume every device on the floor works the same way. Square's offline article lists them separately:

To tell reader generations apart, look at the serial number on the back. Digits 5 to 8 give the version. On a contactless and chip reader, S070 or S092 is 1st generation v1, and S084, S095, S098, S103 or S127 is 1st generation v2. Neither works offline. S109, S130, S146, S148, S192 or S193 is 1st generation v3. S171, S172, S222 or S223 is 2nd generation. For Register, Terminal and Handheld, Square Dashboard shows the version under Settings > Device management > Devices.

Square stopped software updates on September 1, 2025, for Square Terminal (1st generation, v1) and Square Register (1st generation, v1). The offline article doesn't list either one as unsupported. If you still run one, ask Square Support before you count on it in an outage.

Some things don't work offline on any device:

• Payment types: Tap to Pay on iPhone and Android, manually entered (keyed) cards, Square Gift Cards, Afterpay, Cash App Pay and EBT/SNAP. A phone-in order paid with a keyed card can't be taken offline. Take payment at pickup on a supported device instead, or take cash.
• Apps: the Square Point of Sale app in services mode, the Square Invoices app and the Square Kiosk app. The supported apps are Square Point of Sale (full service, quick service, bar, retail, bookings or standard mode), Square Restaurants, Square Retail and Square Appointments.
• Features: close of day reporting doesn't work offline. Square Loyalty points earned on offline payments have to be linked and added by hand after the upload.

Step 2: Set your offline risk policy before you need it

Offline card payments are a business risk you choose to take. Square says you're responsible for expired, declined and disputed offline payments. You won't get decline notices while offline, and Square can't give you customer contact information or contact the customer for you. Square also says your normal processing fees apply, so there's no fee difference.

Square's article says offline payments would be turned on automatically in April 2026 on devices where the seller took no action on the Dashboard task. Don't assume yours is on, or off. An account owner, or someone with permission to change checkout settings, can check it:

• Square Dashboard: Settings > Device management > Modes, choose the mode, Manage, then under Checkout settings, Offline payments. A setting saved on a mode applies to every device assigned that mode.
• On the device, if you don't use modes: More > Settings > Checkout > Offline payments.

You make three choices there:

1. During an internet outage: cash and offline card payments, or cash only.
2. During a Square service disruption: the same two options, set separately.
3. A maximum per offline transaction, anywhere from $1 to $50,000.

A practical way to set the maximum is to ask what the largest single check is that you could absorb if it declined. A fictional café with $14 average checks might pick $150. Because the Dashboard setting lives on a mode, a counter mode and a private-dining mode can carry different caps.

Step 3: Work out what kind of outage you have

When a payment fails for network reasons, the device retries it once. If the retry fails too, it goes offline by itself. You don't press anything.

For an internet outage, Square's network article suggests restarting the modem and router first, then calling your ISP, switching to a backup connection or using offline payments. More > Settings > Hardware > Test connectivity runs a report on internet access, your local network and the connection to Square. Square says it shouldn't be used to decide whether Square itself is down.

None of these checks is conclusive alone. If the device message, your network checks and the status page don't line up, mark the outage "unsure" on the sheet, keep checking the network and the status page, and contact Square Support. You don't need the cause to protect the money: the same rules about pending payments apply either way.

A card that comes back "Declined" while the device is online is a decline, not an outage. Square's failed-payments article describes one exception: if the status page shows a payments problem and every card is declining on a device that's still online, you can turn off Wi-Fi (or unplug Ethernet) under More > Settings > Hardware > Network to force the device offline. Turn it back on when Square says the issue is resolved.

Step 4: Read the 24-hour and 72-hour rules correctly

The headings on Square's offline article are easy to misread. The section headed "24 hours to upload" lists Register, Terminal and Handheld, but the text under it says you must upload within 72 hours and that 24 hours is highly recommended. The section headed "24 hours to take offline payments" covers Square Stand and the contactless and chip readers (2nd generation and 1st generation v3). It doesn't mention the magstripe reader. For those listed devices, the session ends after 24 hours, and you have to reconnect to the internet, with the hardware connected to the phone or tablet, before you can take offline payments again. The 72-hour upload deadline still applies to them.

When does the clock start? Square's offline article says 72 hours from the start of the offline session. Its View offline payments and network articles say 72 hours from the first payment. Square doesn't reconcile the two. A session starts automatically when the device loses its connection, which can be before anyone pays, so the session start is the earlier time. Our planning advice: if you know the session start, count from it. You know it only if someone saw the offline banner appear on that device and wrote down the time. Every deadline you work out this way is planning based on Square's offline article. It isn't a promise of how Square's systems will treat the payments.

If nobody saw the banner appear, the start is unknown. The time someone first noticed a problem (a card going offline, the banner already on screen) can be hours after the session really began, so it can't tell you how much time is left. Our conservative advice for that case:

• Write UNKNOWN for the session start. Write the first-noticed time, and how it was noticed, on a separate line.
• Don't work out a 24-hour or 72-hour deadline from the first-noticed time, and don't tell staff how many hours are left.
• During an internet outage the banner shows Square's countdown. Write down what it shows and when you read it. It's Square's number, not one you've confirmed, and it isn't a reason to wait.
• Get the device back online and uploading as soon as you can: fix the network, or move it to a backup connection such as a cellular hotspot. In a Square service disruption, uploading has to wait for Square, so keep checking the status page.
• Keep the device signed in and leave the pending payments alone (Step 5).
• If the device can't upload soon, or you can't tell how long it has been offline, contact Square Support right away instead of waiting for a deadline.

A few more details:

• Each device has its own session and stores its own pending payments. Record a start time, or UNKNOWN, for each one.
• Count real hours from a known start. If an offline session starts at 6:52 p.m. on Saturday, October 31, 2026, in Central Time, the clocks fall back an hour that night. Seventy-two hours later is 5:52 p.m. CST on Tuesday, November 3, not 6:52. Square doesn't say how its countdown handles the change, so plan on the earlier time. Write all times in the restaurant's local time, even if the owner is checking in from somewhere else.
• Once a device uploads, a new outage starts a new session with a fresh clock.
• Square's failed-payments troubleshooting article still says you must reconnect within 24 hours. We've followed the offline payments article, which is Square's dedicated page and spells out the limits device by device. That doesn't settle the conflict. Uploading within 24 hours of a known session start meets both pages.

Step 5: Take payments, and leave the device alone

Run cards the way you normally would. Square's safety practices for offline payments:

• Have chip cards inserted and contactless cards tapped. Swiping a chip card raises the fraud and decline risk.
• Get a signature where possible and compare it to the back of the card. Square says unsigned cards shouldn't be accepted. You can't require ID, and asking for it doesn't change your chargeback liability. Don't write down anything from a guest's ID.
• Square's offline guide says to print receipts for the guest and for your records.

Offline payments show as pending under Transactions (or More > Transactions), with a circle-and-arrows icon. Pending payments only show in the Square app on the device that took them, not in Square Dashboard.

While anything is pending on a device, nobody does any of these on it:

• sign out of the Square app
• delete the Square app
• switch modes
• switch locations
• factory reset the device or the Square hardware

Square's offline guide also says not to update software during a disruption. Tape this list to the device if you need to.

Restarting or turning a device off is fine. Turn it back on and upload before the deadline. Don't run the same card again on another device "to be safe." Square doesn't describe any check that would catch a duplicate, so treat a second swipe as a second payment. Refunds have to wait too: an offline payment can't be canceled or refunded until it has uploaded.

Step 6: Plan for online orders and the kitchen

Offline mode keeps the register taking payments. It doesn't promise that orders keep flowing. Depending on the type of disruption, Square says new online orders from your Square website or ordering platforms such as Uber Eats won't appear in your POS. They show up on your Square device and in Square Dashboard once the disruption is resolved. That could be an hour of delivery orders arriving at once, or guests turning up for pickups the kitchen never saw.

Decide ahead of time who checks those channels during an outage and whether you pause them. Use each platform's own controls; Square's article doesn't cover pausing. Square's network article also says offline payments may interfere with network printing, so keep paper tickets and a pen at the pass in case kitchen tickets stop printing.

A worked example (fictional)

Juniper Street Kitchen is a made-up 64-seat restaurant in Central Time. The example assumes a local internet outage. On a Saturday at 6:52 p.m. the restaurant's internet drops. The register shows "Check network connection," retries once, then goes offline with a countdown banner. The manager checks More > Settings > Hardware > Network, and the internet provider's outage line confirms a service outage in the neighborhood. On a phone over cellular data, issquareup.com shows no Payment Acceptance incident at that check. The no-X result alone wouldn't rule Square out. The provider's confirmation is what settles it, so the manager circles "internet" on the sheet.

Staff are standing at each device when its banner comes up, so all four start times are known. The manager writes them on the handoff sheet. Every time below is planning from those known starts, using Square's offline article. Square recommends uploading within 24 hours, so the target for every device is Sunday between 6:52 and 6:54 p.m. The limits look like this:

Two devices sit this one out. The patio iPhone uses Tap to Pay only, so it can't take cards offline; patio servers bring Handheld B to the table or take cash. A spare reader in the office drawer has "S095" in serial digits 5 to 8, which makes it 1st generation v2. It isn't supported, so it stays in the drawer.

A guest calls in a pickup order and wants to pay by card over the phone. That's a keyed card, which doesn't work offline, so the host takes payment when the guest arrives.

At 10:30 p.m. the internet is still down. The closer counts the pending payments in Transactions on each device:

The closer leaves all four devices signed in and on their chargers, and leaves the sheet below for the opener. Close of day reporting waits until after the upload.

Sunday at 9:40 a.m. the internet comes back. That's 14 hours 48 minutes after the first session started, inside the recommended 24 hours. Each device shows a notification that it's back online and processing offline payments. Within the hour, every device shows zero pending:

• Completed: 124 payments, $6,571.25.
• Declined: 2 payments, $85.75 (Handheld A, $58.30; bar iPad, $27.45).
• Check: $6,657.00 − $85.75 = $6,571.25.

Square's articles don't describe any retry for a declined offline payment, and Square can't contact the guests or give the restaurant their details. The manager records the $85.75 as an unresolved loss on the sheet, with the owner as the person who decides what happens next. The sheet doesn't hold card numbers or guest contact details.

If the internet hadn't come back: the bar iPad would have stopped taking offline cards at 6:54 p.m. Sunday, so the bar would need a Handheld or cash. The 24-hour recommendation for every device passes Sunday evening, and the 72-hour deadlines from those known starts fall between 6:52 and 6:54 p.m. Tuesday. Waiting until Monday at 11:00 a.m. would be 40 hours 8 minutes, still inside 72 but carrying more decline and chargeback risk. A better move is to connect the devices to a backup connection such as a cellular hotspot on Sunday afternoon and upload. Square's reliability checklist suggests keeping a backup connection.

If nobody had seen the bar iPad's banner: say the bartender only notices at 7:20 p.m., when the iPad already shows the offline banner. The sheet says start UNKNOWN, first noticed 7:20 p.m. (banner already up), and the countdown reading next to the time it was read. The register's 6:52 p.m. start doesn't settle the iPad's, because the iPad may have lost its connection earlier. So the manager doesn't write a Sunday cutoff or a Tuesday deadline for that device. Its Stand could stop taking offline cards at any point, so Handheld B or cash stays ready for the bar. The iPad goes onto a hotspot to upload as soon as one is available, and because its start is unknown, the manager calls Square Support that night instead of waiting.

If it had been a Square disruption instead: the devices would show "Square payment error," and the banner would have no countdown. The status page might show an X on Payment Acceptance, but the manager shouldn't wait for one. If the network checks out and the devices report a Square error, the sheet says "Square," or "unsure" if the signals are mixed. The manager would have to write down each device's start time, since nothing on the screen would track it, and would write UNKNOWN for any device nobody saw go offline.

After you reconnect: the recovery checklist

1. Turn on any device that was powered off, and connect it to the internet. Square says reconnecting is all it takes to upload.
2. Wait for the notification that the device is back online and processing offline payments.
3. Open Transactions on each device and confirm the pending count drops to zero. If a device still shows pending payments, keep it signed in and connected and contact Square Support right away. Don't wait for a deadline, especially for a device whose start time is UNKNOWN.
4. Find the declines. In Square Dashboard, go to Orders & payments > Orders > All orders > Completed and look for the red notice on offline payments. Or go to Reports > Payments > Discounts, where declines show as "Offline Declined Payment." On the device, Orders > All orders shows a red notice on declined payments.
5. Add handwritten tips from the printed receipts once the offline payments have processed, as Square's offline guide says.
6. Issue any refunds, and link Loyalty points by hand.
7. Run close of day.
8. Write the completed and declined totals on the sheet and name who owns each unresolved item.

Expired offline payments can't be recovered, and no checklist changes that. The only real protection is uploading early.

Printable outage handoff sheet

Print a few and keep them by the register. Fill in one line per device.

SQUARE OFFLINE HANDOFF       Date:
Location:                    Manager:

Outage: internet / Square / unsure
issquareup.com checked at:
Policy: cash+card / cash only
Max per transaction: $

PER DEVICE
Device name/type:
Supported offline? Y / N
Session start (saw banner appear):
  time ______  or  UNKNOWN
First noticed at ______
  how: ________________
Countdown shown? ______ read at ______
IF START KNOWN (Square offline article):
 24h: stop cards (Stand, or contactless
  & chip Reader 2nd gen/1st gen v3):
  magstripe: no Square limit listed;
  our advice: use paired device's time
 24h: recommended upload by:
 72h: upload deadline:
IF UNKNOWN: no deadline. Reconnect and
 upload now, keep signed in, call
 Square Support if it won't upload.
Pending at handoff: count ____ $______
Handed to:                    Time:

DO NOT, while anything is pending:
sign out / delete app / switch mode /
switch location / factory reset / update

AFTER RECONNECT
Back online at:
Pending now 0? Y / N
Completed: count ____  $______
Declined:  count ____  $______
Tips added   Refunds done   Loyalty done
Close of day run at:
Unresolved total $______  Owner:

Never write card numbers, ID details or
guest names, phones or emails here.

What this guide doesn't cover

This is a documentation-based walkthrough of Square's U.S. help articles as they read on October 5, 2026. We didn't run an outage test or process real payments. Square can change device support, limits and menu paths, so check the current offline payments article before you write your staff procedure. Outside the U.S., Square's limits may differ. Nothing here is legal advice about chargebacks or card-network rules.

If you're still choosing a POS, test what happens when the internet or a terminal fails before you sign. The POS, insurance and services cost guide covers that comparison. For another Square setup check, see Square kitchen printer printing duplicate tickets, and find more in RestaurantLaunch Technology.

Sources

• Process offline payments, Square Support Center (U.S.), page metadata shows last modified April 23, 2026; accessed October 5, 2026
• View offline payments, Square Support Center (U.S.), modified April 23, 2026; accessed October 5, 2026
• Identify your Square hardware, Square Support Center (U.S.), modified April 23, 2026; accessed October 5, 2026
• Troubleshoot your network connection, Square Support Center (U.S.), modified September 2, 2026; accessed October 5, 2026
• Troubleshoot failed payments on Square Point of Sale, Square Support Center (U.S.), modified April 23, 2026; accessed October 5, 2026
• Offline payments guide (PDF), Square, last updated August 1, 2025; accessed October 5, 2026
• Reliability checklist (PDF), Square, accessed October 5, 2026
• Square Status, Square, accessed October 5, 2026