What Is Store-and-Forward? Taking Cards When the Internet Drops
Store-and-forward credit card sales keep you selling when the internet drops. See who pays for offline declines and how to set limits that cap losses.

Photo: Pixabay
On this page 5 sections
Key takeaways
- An offline sale gets approved after the customer has left. If the card declines or the sale expires, you lose the money, and it never counts as a chargeback.
- Visa has rules for late (deferred) approvals, but your provider sets how long you can wait and how much you can hold: 24 hours at Square in the U.S., and 7 days by default on Clover.
- Before fees, offline selling pays as long as your decline rate stays below your gross margin. The real risk comes from large tickets and from the running total of unapproved sales.
- Before a busy event, cap per-sale and total offline amounts, allow only chip and tap, and test an upload.
A store-and-forward credit card sale is one your terminal accepts while it can't reach your processor. The device saves the encrypted card data and sends it for authorization once the connection comes back, so you keep selling through the outage. Nobody has approved the payment yet, though. If the card declines when it finally goes through, you take the loss. Square's U.S. terms say this directly: a seller who turns on offline payments is responsible for any "expired, declined, or disputed payments accepted while offline."
That trade-off matters most where connections fail at the worst moment, like a festival crowd jamming the cell network during the lunch rush or a restaurant's internet dropping on a Friday night. Offline mode keeps the line moving. It also turns every sale into a small bet on the customer's card, and you decide how big that bet gets.
How a Store-and-Forward Credit Card Sale Works
In a normal card sale, approval takes seconds. Your terminal sends an authorization request through your processor and the card network to the bank that issued the card. That bank checks for available funds or credit, screens for fraud and answers approve or decline. For the full chain, see how processors, acquirers and gateways fit together.
Store-and-forward puts that check off until later. When the terminal loses its connection, it switches to offline mode, either on its own or after you confirm. Each sale is stored on that device. Once the signal returns, the queue uploads and each stored sale gets its own authorization request, exactly as if it had been run live. Approvals join your open batch and declines get flagged. Closing the batch sends the approved sales to settlement on your normal schedule. Our guide to closing out card sales each day covers the batch side.
Visa Has Rules for Late Approvals, but Your Provider Sets the Limits
Many people believe offline selling sits entirely outside the card networks. It doesn't. Visa calls it a deferred authorization: one the merchant can't complete at the time of the sale because of connectivity, system problems or other limits, and completes later. Visa sent acquirers and merchants a reminder in March 2021: starting April 16, 2021, deferred authorizations on card-present and card-absent sales had to carry a specific indicator (value 5206), so the issuing bank knows the request is late. The same notice tells issuers they must not decline a deferred authorization only because the chip's transaction counter is out of sequence. That can happen when stored sales upload out of order.
None of that guarantees you get paid. The issuer can still decline for funds, fraud or a closed account. And your processor or POS provider sets the practical terms, not the network. The provider decides whether offline mode is available, which cards qualify, how much you can hold and for how long. Your POS software adds the indicator, so you don't have to enter anything.
Here is how three widely used platforms describe their offline settings in their own documentation. The table shows how much the terms vary. Get your own provider's terms before you rely on them.
| Platform | How long stored sales can wait | Built-in limits |
|---|---|---|
| Square (U.S.) | 24 hours from the first offline payment; sales not uploaded by then expire | Mobile Payments SDK allows up to 1,000 offline payments per device; per-payment and total limits apply |
| Clover (Mini, Flex, Station) | Up to 7 days by default | Merchant can turn offline mode off or cap each sale and the total held offline |
| Stripe Terminal | Reconnect as soon as possible | Stripe enforces a $10,000 maximum per offline payment |
Card types vary too. Chip and tap are the usual candidates. According to a vendor comparison by JetPOS, Stripe doesn't allow swiped cards offline because magnetic stripe data is easy to copy. The same source lists U.S. PIN debit among Stripe's exclusions. The reason applies to any provider: an online PIN has to be checked by the issuer in real time, and that can't happen without a connection. Ask your provider whether PIN debit works offline on your terminal.
The Queue Lives on One Device
Stored sales exist only on the terminal or phone that took them. Square's developer documentation, for example, says offline payments are queued locally on the mobile device. If you factory-reset that device or log out of the POS app before the upload finishes, you risk losing those sales for good. Ask your provider exactly which actions clear the offline queue, and tell staff to leave the device alone until the queue is empty.
Upload timing affects cost as well as collection. Interchange categories, the rate tiers Visa and Mastercard set for different kinds of sales, assume prompt authorization and settlement. A batch that settles late can land in a more expensive category. Our explainer on how interchange fees are set covers those categories. Upload as soon as you reconnect, and close the batch only after the queue clears.
Declines After the Sale Come Out of Your Pocket
An offline card declines on upload for the same reasons it would at the counter: insufficient funds, a closed account, a card reported lost or stolen, or a purchase the issuer flags as fraud. Online, you'd see the decline and ask for another card. Offline, the customer is gone with your product. If the upload report shows a generic decline, our guide to what "Do Not Honor" means explains the most common one.
A declined offline sale is not a chargeback. A chargeback pulls back money you already received. A declined offline sale is money that never arrives, and your processor won't chase it. Square, for one, states that it can't contact customers for the seller when an offline payment declines or expires. A contactless tap at a festival leaves you no name or phone number anyway.
Fraud adds to the risk. Offline mode gets its heaviest use when the venue is packed and staff are rushing. That is exactly when someone with a dead or stolen card will try their luck. Your exposure is the dollar total you let sit unapproved, multiplied by the share of it that declines. You control the first number. You don't control the second, which is why limits matter.
Worked Example: Is Offline Mode Worth It for a Food Truck?
Every number here is illustrative, chosen to show the method. Swap in your own.
Assumptions: a truck works a six-hour festival with no usable signal. It takes 300 card sales averaging $14, or $4,200 in card revenue. Food and packaging cost 30% of the menu price, so $4.20 on the average order. We assume 2% of offline sales decline on upload. That's a planning figure, not an industry statistic, because no published decline rate fits every business. We also assume customers who couldn't pay by card would walk away rather than pay cash.
At a 2% decline rate, 6 sales fail. The truck never collects $84, but its real out-of-pocket cost is the $25.20 in food and packaging it handed over. Against that, it keeps $4,116 in approved card sales it would otherwise have lost.
The break-even point is the figure worth remembering. Before processing fees, an approved $14 order earns $9.80 over food cost and a declined one loses $4.20. Losses only equal profits when 70% of sales decline. The general rule: before fees, offline selling pays as long as your decline rate stays below your gross margin percentage. Fees pull that line slightly lower, but not enough to change the answer for a low-ticket food vendor.
Two things turn the math against you. Bigger tickets raise the loss on each decline: one bad $2,000 sale wipes out the profit on a long run of good ones. And declines stop being random once someone figures out the network is down. A $14 taco is a poor fraud target. A large order is a better one when the buyer knows nothing is being checked. The real risk sits in large single sales and in the running total you let pile up, and you can cap both.
Set Store-and-Forward Limits Before the Outage
Offline-capable systems give you some combination of the controls below. The names differ by provider, so match them to your settings menu. Stripe's own advice to merchants lines up with the first three: reconnect quickly, refuse offline sales above a set amount, and stop taking offline payments once the stored total passes a threshold.
- Per-transaction limit. The largest single sale the terminal accepts offline. Set it just above your normal biggest ticket, such as a family meal on a food truck menu. Anything larger is paid in cash or waits for a connection.
- Total offline limit. The cap on unapproved sales held on the device, by dollars or count. Pick a figure you could lose outright without missing payroll or your next supply order.
- Time window. Know exactly when stored sales expire on your system, and plan to reconnect well before then.
- Entry method. Where your provider allows it, accept only chip and tap offline and turn keyed entry off. A typed card number is far easier to misuse than a physical card. Our comparison of tap, chip and swipe security explains why.
Limits only help if staff know what to do when the terminal refuses a sale. Settle that before the event, whether it means switching the customer to cash or holding the order until the signal returns.
Then cut how often you need offline mode at all. A terminal with its own cellular connection, or a backup hotspot on a different carrier from your phone, keeps you online through many outages. If you're choosing hardware, compare countertop, wireless and mobile card readers by how each one connects, and look at mobile terminals built for selling on the move. For setup steps on specific systems, see our guide to keeping your POS running in offline mode.
Sales That Should Wait for a Live Approval
Offline mode suits fast, low-ticket sales to customers standing in front of you. These sales need a real-time answer:
- High-ticket sales. One declined jewelry purchase or catering order can erase a day's margin.
- Bar tabs and pre-authorizations. A tab relies on an authorization hold to prove the card works. Open one on an unverified card and a walkout costs you the whole tab.
- Gift cards. Selling stored value against an unapproved payment hands out spendable money before you know you'll be paid, which is what fraudsters look for.
- Unattended kiosks. With nobody watching, offline acceptance has no human check at all.
Long outages call for a different response. Once the queue grows past what you'd comfortably lose, switch to cash or backup connectivity rather than raising your limits. And if you land in offline mode every weekend because your own Wi-Fi or router keeps failing, fix the equipment. Changing settings won't solve it.
Before your next event or busy weekend, get four answers in writing from your provider: whether offline mode is on, your per-sale and total limits, how long stored sales last, and which card types are excluded. Then test it. Put the terminal in airplane mode, run a small sale on your own card, reconnect, and confirm the sale reaches your batch and settles. If you're not sure what your current setup can do, a MannyPay specialist can review your hardware and food truck payment setup. Request a free quote and you'll hear back within one business day.
Sources
- Square: Offline Credit Card Processing (U.S.)
- Square: Payments (offline payment terms footnote)
- Square Developer: Mobile Payments SDK Offline Payments
- Clover Developer Docs: Handle Offline Payments
- Clover Developer Docs: Per-Transaction Settings
- Stripe Docs: Collect Card Payments While Offline
- Visa: Deferred Authorization Indicator Reminder (March 25, 2021)
- Visa Merchant Business News Digest: Revised Implementation Dates for New Deferred Authorization Indicator
- JetPOS: What Happens to Your POS When the Internet Goes Down (Stripe offline card-type exclusions)
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

