Key points
Online, a payment is a question put to the payer’s bank about whether the card or account is genuine and whether there is enough money. Offline, nobody can ask that question at the moment of payment. Every offline design answers it in advance instead, with keys loaded into a card, limits configured by the issuer, value set aside on a device, or a merchant agreeing to carry the risk until it can check.
What separates the designs is how far each one goes. Some only delay the check by a few hours. Others never make it at all, because the value itself is protected by hardware.
Offline payment definition
A payment is offline when it takes effect without internet or telecom connectivity. That is the Reserve Bank of India’s definition in its 2022 framework for small value offline payments, which allows offline payments by card, wallet or mobile device, in proximity (face to face) mode only, with explicit customer consent.
In practice “offline” covers several different things:
- Offline approval. A chip card and terminal decide together to approve without contacting the issuer, and the transaction is sent on later.
- Store and forward. A till accepts the card, keeps the payment on the device and submits it for authorisation when the connection returns.
- Deferred authentication and alerts. A small prepaid balance is spent without the usual second factor, and the bank tells the user afterwards.
- Device-to-device value. Value held in secure hardware moves from one device to another and is settled there, with no online system involved at all.
The RBI notes the third case explicitly: a UPI Lite transaction is “offline to the extent that AFA is not required, and transaction alerts not sent in real time”.
EMV chip card offline approval
To approve a chip card payment offline, the terminal checks that the card is genuine using keys it already holds, checks its own risk limits, and then asks the card to decide. The EMV specifications, maintained by EMVCo, define each step.
Card authentication. EMV Book 2 defines offline data authentication. With Static Data Authentication (SDA), the terminal checks the issuer’s signature over data stored on the card, using a certification authority public key every terminal must hold, which detects data altered after the card was made. Dynamic Data Authentication (DDA) and Combined DDA/Application Cryptogram Generation (CDA) go further: the card signs data that includes values from the terminal, which EMVCo says authenticates the card itself and “precludes the counterfeiting of any such card”. Since a 2008 specification update, terminals that do offline data authentication must support both SDA and DDA.
Cardholder verification. EMV supports several cardholder verification methods, including offline PIN, where the card itself checks the PIN. EMVCo does not dictate which method is used; that depends on the card’s configuration and the terminal.
Terminal risk checks. Before asking the card to decide, the terminal runs terminal risk management:
- Floor limit. If the amount, plus recent approved amounts on the same card in the terminal’s log, reaches the terminal’s floor limit, the terminal flags the transaction.
- Random selection. Some transactions below the floor limit are picked at random to go online anyway.
- Velocity checking. The card counts consecutive offline transactions. After a lower limit the issuer asks for the next transaction to go online, and after an upper limit it may refuse anything that cannot. The count starts again after the card completes an online transaction with issuer authentication.
The card’s decision. The card answers with a cryptogram. EMV Book 3 defines a Transaction Certificate when the card accepts the transaction, an Authorisation Request Cryptogram when it asks for online authorisation, and an Application Authentication Cryptogram when it declines. A Transaction Certificate is the offline approval.
None of these steps looks at the account balance. The limits decide how much can be spent before the card next meets its issuer online.
Card terminal store and forward
When a shop’s card terminal loses its connection, many point-of-sale apps switch to store and forward: they accept the card, keep the payment on the device and submit it later. Square’s offline mode stores payments in the app and processes them automatically on reconnection. On Square Register, Terminal and Handheld they must be uploaded within 72 hours, and Square highly recommends doing it within 24 hours.
The cost of that convenience falls on the seller. Square says sellers are responsible for any expired, declined or disputed payments accepted offline, and several methods, including Tap to Pay on iPhone and Android and manually entered cards, do not work offline at all. How restaurants take orders during an outage covers what this means for a busy till.
UPI Lite offline payments
UPI Lite is a small prepaid balance on the phone, spent without the second factor that a normal UPI payment needs. The RBI describes it as an on-device wallet launched in September 2022, enabled under its framework for small value offline payments.
The rules come from that framework:
- Limits. Since the RBI’s circular of 4 December 2024, UPI Lite allows up to ₹1,000 per transaction and ₹5,000 in total at any point in time. Other offline instruments under the framework stay at ₹500 per transaction and ₹2,000 in total.
- Top-ups. Replenishing the balance is allowed only online, with an additional factor of authentication.
- Alerts. The issuer sends transaction alerts as soon as it receives the details, not necessarily one per payment.
- Liability. The acquirer carries liabilities from technical or security issues at the merchant’s end, and offline payments fall under the RBI’s limited customer liability rules.
In August 2023 the RBI proposed going further, with offline UPI Lite payments over Near Field Communication (NFC) for places where internet or telecom connectivity is weak or missing, and said instructions to NPCI would follow.
Offline digital euro design
The offline digital euro would let two devices settle a payment between themselves, with no bank, card network or central system involved at the time. It is a proposal, not a live product, and its legal basis is still being negotiated.
The ECB’s description of the design:
- Pre-funding. Users fund their offline digital euro holdings first, online or at a designated ATM.
- Settlement between devices. Payments would be settled directly between two devices, such as phones or smart cards, by transferring cryptographically secure tokens, with no online system involved.
- Secure hardware. The work has focused on embedded secure elements, integrated secure elements and eSIMs. The ECB excludes Trusted Execution Environments because they are more exposed to physical attacks. Battery-powered smart cards are being studied for people without smartphones.
- Privacy. Transaction details stay on the two devices and would be known only to the payer and the payee.
- Double spending. The ECB says funds recirculated into the system must be checked as genuine at funding and defunding, to detect and prevent double spending and counterfeit currency.
- Limits. Digital euro holdings would be subject to a holding limit. The ECB tested hypothetical limits of up to €3,000 per person at the co-legislators’ request; no limit has been set.
As of October 2026, the ECB says the Council adopted its position on 19 December 2025, the European Parliament adopted its position on 9 July 2026, and trilogue negotiations have started. The ECB aims to be ready for a potential first issuance during 2029 if the regulation is adopted by the end of 2026.
Offline double spending prevention
Offline payments cannot check a balance, so they limit what one device can spend before it is checked, or they make the value hard to copy. The table compares the four designs.
| Design | Where the value or credential lives | Checked at the moment of payment | What limits double spending | When the bank learns of it |
|---|---|---|---|---|
| EMV offline approval | Keys and counters on the card’s chip | Issuer and card signatures, PIN if used, terminal limits | Floor limit, random online selection, consecutive offline limits on the card | When the transaction is sent online; the card’s count resets at its next online transaction |
| POS store and forward | Card details stored on the merchant’s device | Whatever the card and app check locally | Upload deadline; the seller carries declines | When the device reconnects and submits |
| UPI Lite | A capped balance in an on-device wallet | No additional factor of authentication | ₹1,000 per payment and ₹5,000 total; top-ups only online with authentication | Alerts are not real time |
| Offline digital euro (proposed) | Tokens in a secure element, eSIM or smart card | Device-to-device token transfer | Tamper-resistant hardware, holding limits, checks at funding and defunding | Only the payer and payee see the details |
Designs that keep only a short delay (store and forward) put the risk on the merchant. Designs that spend real value offline either keep the amounts small (UPI Lite) or rely on hardware that resists copying (EMV chips, the digital euro’s secure elements). Whatever is spent offline has to be reconciled later, so every record needs a unique identifier that makes a resubmitted payment count once, which is the same idempotency any offline system relies on.
Offline Protocol’s role in payments
Offline Protocol does not move money, hold value or settle payments. It is not a card scheme, a wallet or a ledger, and nothing in it decides whether a payment is good. A payment product built alongside it would still need its own ledger, settlement, scheme or regulator approval, and compliance.
What the SDK does is the part around a transaction: it carries end-to-end encrypted messages (MLS, RFC 9420) between devices that identify each other by Ed25519 keys, and holds them in a store-and-forward queue, 24 hours by default, until a path appears. Its docs keep message delivery, durable acceptance by the receiving application and commit to a backend as separate outcomes, which is the same distinction an offline payment makes between a till accepting a card and the issuer settling it. In practice that suits records about work, such as an order, a receipt reference or a delivery confirmation, passed between nearby devices and reconciled with the system of record later.