Store and forward: taking card payments offline

Store and forward is how a card terminal keeps taking payments when it loses its connection. Instead of sending each sale for approval on the spot, the terminal stores it and forwards it to your processor once the internet or cellular signal comes back. Visa's guidance for US terminals calls this a deferred authorization approach, sometimes called store and forward (Visa). It keeps the line moving during an outage. It also means you're handing over goods before the customer's bank has said yes.

That trade is fine for a $6 coffee and reckless for a $1,600 laptop. Below: how store and forward works on a terminal, what you're risking, the limits we'd set, and when to skip it and fix the connection instead. The Visa rules cited are current as of October 2026.

What is store and forward?

It's offline card acceptance with the authorization delayed, not skipped. Visa's minimum terminal configuration guidance says US EMV cards and online-only terminals typically don't support offline approvals. For merchants with temporary connectivity problems, it suggests considering deferred authorization, which it says is common in magnetic stripe environments and equally suited to online-only chip ones. Under that approach, merchant rules and policies may let the customer take the goods or service while the authorization request waits until the connection is restored.

Visa puts a clock on it. Merchants that submit a deferred authorization must include a deferred authorization indicator and obtain the authorization within 24 hours of the transaction date for most merchant category codes, or within four days for transportation-related codes (Visa).

Two things follow from that. Whatever your screen shows on an offline sale, it means "saved," not "approved by the customer's bank." And you can't let stored sales sit for a week; they need to go out as soon as you're back online.

How does store and forward work on a card terminal?

The terminal saves the sale, then sends it for approval later. Here's the usual sequence:

1. The terminal can't reach your processor. The cause might be your internet, a cellular dead zone, or an outage further down the line.
2. The chip can't approve the sale on its own. Visa's minimum configuration for US online-only terminals uses a zero floor limit, which forces the terminal online, and says that when the host connection is unavailable, the card and terminal will typically perform an offline decline, followed by a deferred authorization.
3. If your offline mode is on and the sale is within your limits, staff completes it and the customer leaves with the goods.
4. The terminal holds the stored sale in a queue.
5. When the connection returns, the terminal forwards each stored sale for authorization, flagged as deferred.
6. The issuer approves or declines each one. Approved sales go into your batch. Declined ones land on a report, and that's money you won't collect through the card.

Step 2 is where chip security normally does its work. EMVCo explains that a chip generates a one-time security code, called a cryptogram, for each transaction, which lets the issuer authenticate the card. During an outage, that check doesn't happen until the sale is forwarded, so nobody knows whether the card is good while the customer is still standing there.

Not every terminal or account supports offline mode, and the settings vary by device and processor. Our guide to credit card machines for small business covers what to ask about connections when you choose hardware.

Is store and forward the same as an offline approval?

No, though the two get mixed up. With a true offline approval, the chip card and the terminal approve the sale between themselves, without contacting the issuer, within limits set in advance. Visa's guidance says US EMV cards and online-only terminals typically don't support offline approvals, so in the US the realistic offline option is store and forward: the terminal keeps the sale and the issuer decides later.

The difference matters when a help desk or a sales rep tells you a terminal "works offline." Ask which kind they mean. If it's store and forward, every offline sale is one you might not get paid for, and your limits should reflect that. And if anyone suggests getting past a decline by typing in an approval code by hand, the answer is no. That's the forced sale Visa's dispute rules are written to catch.

What's the risk of store and forward?

You carry the loss on every stored sale that's declined. The customer is gone, the goods are gone, and the issuer owes you nothing for a sale it never approved.

The cards that get declined later are the same cards that would have been declined at the counter: closed accounts, maxed-out cards, cards reported lost or stolen, and sales the issuer's fraud model doesn't like. The outage just hides the answer until it's too late. And anyone who notices your terminal is offline also knows nobody is checking cards in real time.

Here's how that plays out in dollars, with made-up numbers. A food truck in Austin loses signal during a lunch rush and stores 40 sales averaging $14, or $560. Two come back declined, and the truck is out $28 plus the food. Annoying, survivable. Now picture a bike shop in Boise that stores one $1,400 e-bike sale during a storm. One decline wipes out the profit on a lot of tune-ups.

Two Visa rules raise the stakes:

• Don't push it through anyway. Visa's Declined Authorization dispute condition covers a transaction processed after a decline or pickup response, which Visa says is commonly called forced posting (Visa). Our guide to the do not honor decline covers how to handle declines without forcing them.
• Don't sit on stored sales. The same Visa guidelines cover transactions that weren't sent within the required timeframe, and effective April 13, 2024, Visa combined its No Authorization and Late Presentment dispute conditions.

There's a data angle too. A stored sale is card data sitting on your terminal until it's sent. PCI SSC says full track data and PIN block data, both sensitive authentication data, may not be stored after authorization. That's one more reason to use only the offline mode your processor has configured on a supported terminal, and never a workaround like writing card numbers on paper to key in later.

What limits should you set for offline transactions?

Set limits before the first outage, not during it. These are our suggested starting points, not network rules, apart from the Visa timing:

A coffee bar with a $9 average ticket might cap offline sales at $25 each and $400 in total. A home goods store with a $90 average might allow $100 a sale and $1,000 total, and require a manager above that. Pick numbers you'd be comfortable writing off, because occasionally you will.

Train staff on three things: what offline mode looks like on the screen, when the limits are reached, and what to offer instead, such as cash or holding the item until the connection is back. Tell them to be wary of a customer who pushes for a big purchase after hearing the terminal is offline.

When should you use store and forward?

Use it when a few declines cost less than the sales you'd lose by stopping. Skip it when one decline would hurt.

Good fits:

• Small tickets and lots of regulars: cafes, bakeries, food trucks, concession stands.
• Places where connections drop by nature: mobile vendors, markets, events, and rural stops like a farm stand outside Billings.
• Busy rushes where a dead terminal means a line walking away.

Poor fits:

• Large tickets: furniture, electronics, jewelry, repairs.
• Items that are easy to resell, or customers you'll never see again.
• Gift cards and anything else that works like cash.

Often the better answer is a better connection. At a fixed counter, a wired connection is usually the steadiest, and a cellular backup or a second line covers most outages. For mobile sellers, a reader paired with a phone on a different network can keep you online when the terminal isn't. Clearo's mobile payments include tap to pay and mobile card readers, and our POS terminals read chip, tap, and swipe. For a customer you know, such as a regular account or a deposit, sending a payment link from a virtual terminal once you're back online is safer than storing the card. Our restaurant and retail pages cover counter setups in more detail.

How do you set up and manage store and forward?

Treat it like any other cash-handling policy: written down, with someone responsible.

1. Ask your processor whether your terminal supports offline mode, whether it's turned on now, and how it's configured.
2. Confirm in writing that declined stored sales are your loss, so nobody is surprised later.
3. Set the limits above, on every terminal.
4. Ask what happens to queued sales if the terminal loses power or is reset before it reconnects.
5. When the connection returns, make sure the terminal forwards everything, then batch as usual. Our guide on how long a credit card payment takes to process explains why a delayed batch delays your deposit.
6. Pull the declined list the same day. For customers you can reach, ask for another payment method politely and quickly.
7. Count your outages. If you're offline every week, fix the connection instead of leaning on offline mode.

What are the common store-and-forward mistakes?

• Leaving offline mode on with no limits at all.
• Not noticing the terminal has been offline for hours, because sales seem to be going through.
• Re-running declined stored sales, or entering an approval code nobody gave you.
• Writing card numbers down during an outage to key in later.
• Using offline mode for big tickets because the line was long.
• Never checking the declined report after the connection comes back.

Your next step

If outages are a regular part of your day, talk to us about the setup before you rely on offline mode: the right terminal, the right connection, and a backup plan for when both fail. Contact us to go through it with a rep, or send a recent statement for a free statement review and we'll look at your equipment costs and processing fees at the same time.