Also called: Offline Sale, Offline Payment, Store-and-Forward, Deferred Authorization, Fallback Transaction
What an offline transaction is
An offline transaction is a card payment your POS accepts while it cannot connect to the processor for real-time authorization. The device or POS stores the payment information and sends it for authorization after the connection returns. This is also called store-and-forward, or SAF.
A customer seeing an acceptance message does not mean the issuer approved the payment. The later authorization can be declined, and your business can lose the sale after handing over the goods or completing the service. Offline processing applies to card payments; the research does not establish that offline bank payments are supported.
Offline acceptance is not issuer approval, and a later decline can leave your business without the sale proceeds.
How it works
When connectivity drops, an enabled POS switches from real-time processing to its offline mode. It applies its configured limits, captures the payment, and queues it on the device or reader. Once online, the system uploads the queued transactions for authorization and processing.
Limits depend on the particular POS integration. One documented reader setup stores transactions for up to 5 days and about 1,000 transactions in a session, but those are product limits, not industrywide rules. Other systems set their own per-sale, total-volume, or time limits. A floor limit controls the maximum sale the system accepts without real-time approval.
A declined offline sale
| Sale accepted offline | $200 (illustrative) |
|---|---|
| Issuer declines after upload | $0 funded |
| Goods already handed over | $200 exposure |
The $200 amount is illustrative. Actual outcomes depend on the transaction and your POS setup.
What it means for your costs and risk
The research notes do not establish a standard extra processing fee for offline transactions. The direct financial exposure is the sale itself: if the issuer declines after upload, you may not receive funds for goods or services already provided. A disputed payment adds another possible loss.
Offline processing does not make a transaction risk-free or guarantee funding. It also delays the answer on whether the card payment was approved. Reconnecting promptly and reconciling every queued transaction helps you spot declines and missing payments before they disappear into a later batch.
Where offline processing can go wrong
A POS can accept more offline sales than its limits allow if the software does not enforce a per-transaction cap, a session total, or a maximum transaction count. A device can also lose queued payments if it is reset or its app data is cleared before upload. Some implementations erase stored transactions after a set period; one reader setup sets that period at 5 days.
Offline acceptance also differs from a card-present transaction authorized in real time: the issuer has not yet returned an approval. Treat the result as pending until the transaction is uploaded and reconciled against its authorization status. Do not assume every terminal supports offline mode or that a transaction accepted offline will be funded.
What you can actually change
- Set firm limits. Configure a per-sale cap, a maximum queued total, and a transaction-count limit. Keep the cap close to the amount your business can afford to lose on a later decline.
- Reconnect promptly. Restore internet access as soon as possible and upload queued transactions. Some POS systems enforce a short time limit, so use the limit shown in your device or integration settings.
- Reconcile every sale. Track each offline transaction ID and status, then compare uploaded transactions with authorization and funding records at least daily. Follow up on any transaction that remains pending or is declined.
- Protect queued data. Do not uninstall the POS app, clear its data, or reset the device while transactions remain unprocessed. Those actions can permanently delete payments that have not uploaded.
Frequently asked questions
Does an offline transaction mean the card was approved?
No. The POS stores the payment and sends it for authorization when connectivity returns. The issuer can decline it later, even if the POS showed an acceptance result at the time of sale.
Who pays if an offline card transaction is declined?
Your business bears the risk of a later decline. If you have already provided the goods or service, you may not receive the sale proceeds. Reconcile queued payments promptly so you can identify declines and missing funds.
Is there an extra fee for offline transactions?
The research does not establish a standard offline-transaction fee or a universal statement line. Offline support and limits are product-specific. Review your processing charges for any separate fee and compare it with your agreement.
How long can a payment stay stored offline?
There is no single industrywide storage period in the research. One documented reader setup stores transactions for up to 5 days, while other POS systems set their own time and volume limits. Check the actual limit configured for your device.