Offline card processing when your network goes down

What happens to your card sales when the internet goes down? Offline credit card processing, sometimes called store-and-forward, lets some terminals accept a card while disconnected, save the sale, and send it for approval once the connection returns. It keeps the line moving. The catch is that you're taking a risk, because a stored sale can still decline later.

Every store loses its connection eventually. A plan makes the difference between a calm hour and a lost one.

How does store-and-forward work?

In normal operation, your terminal sends each sale to your processor and waits for an approval before the customer leaves.

In offline mode, a terminal that supports it skips that step. It reads the card, saves the transaction securely, and prints a receipt. When the network is back, it forwards the saved sales for approval.

Most of those sales will go through. Some won't. A card might be over its limit, closed, or reported stolen. Since the customer is already gone, the store absorbs the loss.

Not every terminal or processor supports offline mode, and those that do usually have limits on amounts and the number of stored sales. Ask the NRS Pay team what your setup supports before you count on it.

What's the real risk of offline sales?

It comes down to trust. You're handing over goods on the promise of a payment that hasn't been approved yet.

Here's a hypothetical. Your internet is down for two hours on a Saturday. You take 40 card sales offline, averaging $25 each, for $1,000 in stored sales. When the connection returns, two of them decline. You're out $50 plus the goods, and you have no easy way to reach those customers.

On a small ticket, that's a cost many owners will accept to keep the store open. On a large ticket, like a case of energy drinks or a stack of phone cards, it's a real exposure.

That's why most stores that use offline mode set a limit. Accept offline card sales under a set amount. For anything bigger, ask for cash or another card, or wait for the network.

What should your backup plan look like?

Think about this before the outage, not during it.

1. Know how your terminal behaves offline. Does it store sales, or just stop? Test it once during a slow hour so you're not guessing.
2. Have a backup connection. Some stores keep a mobile hotspot or a cellular-capable terminal for exactly this. Know where it is and how to turn it on.
3. Set an offline limit if you use store-and-forward, and tell every cashier.
4. Keep enough cash in the drawer to make change if more customers pay cash.
5. Put up a simple sign when you're offline. "Cash preferred right now, card limit $X" is enough.

One more thing: don't write card numbers down on paper as a workaround. It feels practical in the moment, but it creates a data security problem. The PCI Security Standards Council sets the rules for protecting card data, and paper records of card numbers go against them.

How do you know the stored sales went through?

When your connection comes back, give it a few minutes, then check. Your terminal or POS should show that stored transactions were sent.

Look at your batch report for the day. Offline sales should appear alongside your normal ones. If any declined, they'll show as declined or missing.

Close your batch as usual. Then compare your deposit with the batch total over the next day or two. Any gaps should match the declined offline sales.

If something doesn't add up, call your processor. NRS Pay has live support seven days a week. You can also look at NRS Pay equipment if you're thinking about a reader with a backup connection option.