Offline Payment

What Is an Offline Payment?

An offline payment is any transaction that completes without the payment device or terminal needing an active internet connection at the moment of authorization. Instead of verifying the transaction in real time against a remote server, the payment system relies on locally stored credentials, pre-authorized limits, or bearer tokens to approve the transfer of value. The transaction data is recorded locally and forwarded for settlement once connectivity is restored.

Offline payments predate digital currency by decades. Credit card terminals have supported offline authorization since the introduction of EMV chip technology, and stored-value transit cards like Japan's Suica and London's Oyster have processed billions of offline contactless payments since the early 2000s. In the cryptocurrency space, protocols like Cashu and approaches like async payments on Lightning are extending offline capabilities to Bitcoin.

How It Works

Offline payment systems vary widely in their technical approach, but they share a common principle: moving enough trust and verification logic to the local device so that a network round-trip is not required at the point of sale. The tradeoffs between security, convenience, and risk tolerance differ across implementations.

EMV Chip Offline Authorization

EMV (Europay, Mastercard, Visa) chip cards were originally designed for markets with unreliable terminal-to-acquirer connectivity. The chip on the card stores issuer-configured parameters that govern offline behavior:

• A floor limit (EMV tag 9F 1B) defining the maximum amount that can be approved offline per transaction
• A cumulative offline transaction limit that caps total spending before the card must go online
• A maximum number of consecutive offline transactions allowed

When a cardholder taps or inserts their card, the terminal reads the chip and verifies the PIN against the PIN stored on the chip itself, requiring no network call. Terminal Action Codes (TACs) then govern the decision flow: check for critical failures (deny immediately), attempt online authorization if the transaction exceeds configured limits, and fall back to offline approval or denial if the issuer cannot be reached. In markets like the United States, most terminals set the floor limit to zero, forcing every transaction online. In regions with less reliable connectivity, issuers configure higher limits to enable offline commerce.

Stored-Value Transit Cards

Transit systems like Suica, Oyster, and Octopus use a fundamentally different model: the balance lives on the card itself, not on a remote server. The card's NFC chip stores the current balance, and the reader modifies it directly during each tap.

Suica cards use Sony's FeliCa technology operating at 13.56 MHz. When tapped, the reader and card mutually authenticate and generate a fresh encryption key for the transaction. The entire debit-and-rewrite process completes in under 200 milliseconds, which is essential for high-throughput transit gates processing thousands of passengers per hour. The card has no battery: the reader's electromagnetic field powers the chip just long enough to complete the transaction.

These systems are closed-loop: the card issuer controls the reader hardware, card issuance, and balance management. This constraint simplifies security because there is no need to interoperate with external payment networks.

Ecash Bearer Tokens

Cashu is an open protocol for Chaumian ecash on Bitcoin. A mint issues bearer tokens backed by Bitcoin or Lightning deposits, using blind signatures so the mint cannot link a withdrawal to a subsequent spend. Because tokens are bearer instruments (whoever holds the data owns the value), they can be transferred offline via QR code, NFC tap, or Bluetooth.

In 2025, developers demonstrated NFC tap-to-pay ecash transfers between phones without internet, and Bitchat showcased offline ecash transfers over Bluetooth at a Cashu developer retreat. The tradeoff is custodial risk: the mint holds the backing Bitcoin, and double-spend detection only occurs when the recipient redeems the token online.

Fedimint extends this model by distributing custody across a federation of guardians using Byzantine Fault Tolerant consensus, so no single party controls the backing funds. Ecash tokens issued by a Fedimint federation share the same offline transfer properties and double-spend limitations as Cashu tokens.

Lightning Async Payments

Standard Lightning payments require both sender and receiver to be online simultaneously. BOLT 12, formally merged into the Lightning specification in September 2024, introduces onion messages and blinded paths that enable async payments to often-offline recipients. A sender can initiate a payment via an onion message; if the recipient is offline, the protocol retries when the recipient reconnects.

This is particularly relevant for mobile wallets that cannot maintain persistent connections. As of mid-2026, three of the four major Lightning implementations support BOLT 12 in production, with async payment support continuing to progress through the specification process.

Pre-Signed Transactions

Partially Signed Bitcoin Transactions (PSBT), defined in BIP-174, provide a standardized format for creating and signing Bitcoin transactions on air-gapped devices. An online watch-only wallet constructs an unsigned transaction, transfers it to an offline signing device via microSD, QR code, or NFC, and receives the signed result back through the same physical channel.

While PSBTs enable offline signing, the signed transaction still must be broadcast to the Bitcoin network for confirmation. This makes PSBTs more of an offline security mechanism (keeping private keys in cold storage) than a true offline payment system.

The Double-Spend Problem Offline

The core challenge for any offline digital payment system is double spending. Physical cash solves this naturally: when you hand someone a banknote, you no longer have it. Digital tokens are data, and data can be copied. Online systems prevent double spending by checking every transaction against a central ledger or blockchain. Remove that connectivity and there is no authoritative state to verify against.

Several mitigation strategies exist, each with distinct tradeoffs:

• Deferred online verification: accept the token offline, then redeem it with the mint or broadcast it to the network as soon as connectivity returns. The first redemption wins; duplicates are rejected. The recipient bears the risk during the offline window.
• Cryptographic locking: Cashu's Pay-to-Pubkey (P2PK) feature locks ecash tokens to a specific recipient's public key, so only they can redeem the token. This reduces double-spend risk but does not eliminate it entirely.
• Tamper-resistant hardware: trusted execution environments or secure elements on user devices enforce that tokens can only be spent once. CBDC researchers consider this the most promising approach for high-assurance offline payments.
• Small-value thresholds: limit offline transactions to amounts where the double-spend risk is commercially acceptable, similar to EMV floor limits. India's offline UPI system, for example, caps transactions at Rs 2,000 (approximately $24 USD).

Use Cases

Unreliable Connectivity Environments

Rural and remote areas, developing regions, and locations experiencing natural disasters often lack reliable internet. Offline payment capability ensures that commerce can continue regardless of network conditions. India's Reserve Bank expanded its Digital Rupee pilot in 2025 to target over 600,000 villages with limited connectivity, and the country's NPCI is developing NFC-based offline tap-and-pay for UPI.

High-Throughput Point of Sale

Transit systems processing thousands of taps per minute at rush hour cannot tolerate network latency. Stored-value cards like Suica complete transactions in under 200 milliseconds because all verification happens locally on the card and reader, with no server round-trip.

Privacy-Preserving Payments

Bearer token systems like Cashu and Fedimint combine offline transfer capability with strong privacy properties. Blind signatures ensure that the mint cannot link a deposit to a later spend, providing cash-like privacy for digital payments. This makes offline ecash relevant not only for connectivity-constrained environments but for any user who values transaction privacy.

Mobile-First Bitcoin Payments

Mobile Lightning wallets frequently go offline as users close apps, lose signal, or conserve battery. BOLT 12 async payments and protocols like Spark that support offline receiving address this by allowing payments to complete even when the recipient's device is temporarily unavailable.

Risks and Considerations

Fraud and Double-Spend Exposure

Every offline payment system accepts some fraud risk in exchange for availability. EMV offline transactions can be exploited if a card's offline limits are not properly configured. Ecash tokens can be copied and spent multiple times before the recipient goes online to redeem them. UK contactless fraud reached 46.8 million GBP in 2025, an 8% year-over-year increase, underscoring the need for strong authentication even in offline scenarios.

Custodial Trust in Ecash Systems

Cashu mints and Fedimint federations are custodial: they hold the backing Bitcoin. Users must trust that the mint or federation will honor redemptions. While Fedimint distributes this trust across multiple guardians, both models introduce custodial risk that does not exist in on-chain Bitcoin payments.

Settlement Delay

Offline payments defer settlement until connectivity returns. During this window, the merchant or recipient has no guarantee that the payment will clear. For traditional card payments, the issuer bears this risk. For ecash systems, the recipient bears it. The length of the offline window directly correlates with the risk of fraud or failed settlement.

Regulatory Uncertainty

Offline CBDC payments and offline ecash transfers raise questions about KYC/AML compliance. Regulators are actively debating how to balance financial inclusion (which requires low-friction offline access) with anti-money-laundering requirements (which typically assume online verification). The Bank for International Settlements ranks offline capability as the most important CBDC feature for financial access in emerging markets, but implementation standards remain in flux.

Offline Payments and Spark

Spark, built on statechain technology with Lightning compatibility, supports offline receiving: service providers can hold payments conditionally until the recipient comes online. Unlike Lightning, Spark does not require persistent payment channels, which reduces the always-online requirement for participants. Combined with ecash protocols that operate on top of Bitcoin and Lightning, the ecosystem is converging on multiple complementary approaches to offline Bitcoin payments, each optimized for different trust models and use cases.

For a deeper look at how async and offline payment mechanisms work on Lightning and Spark, see the research article on Lightning async and offline payments and the overview of Chaumian ecash mints on Bitcoin.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.