# On-chain Bitcoin versus Lightning: choose the correct payment route

An on-chain Bitcoin payment creates a transaction for inclusion in the public blockchain. A Lightning payment changes channel balances through a separate payment protocol, usually without recording each payment on-chain. Both can transfer bitcoin, but they use different payment requests, fee models and recovery procedures. Choose the method the recipient actually supports and inspect the wallet’s final amount and fees.

Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md); [The lifecycle of a payment channel](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/lifecycle-of-a-payment-channel.md)

Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-onchain-vs-lightning/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **On-chain record:** A transaction enters the shared blockchain ([Transactions](https://developer.bitcoin.org/devguide/transactions.html))
- **Lightning record:** Individual payments usually update channels ([The lifecycle of a payment channel](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/lifecycle-of-a-payment-channel.md))
- **Availability:** A normal Lightning payment needs responsive nodes ([The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md))

## Use the right kind of payment request

An ordinary Bitcoin address describes an on-chain destination. A Lightning invoice provides information for a Lightning payment. A payment link can offer several methods, but its QR shape does not tell you which method the wallet selected.

Check the decoded amount, network and payment method. A wallet may arrange a swap or open a channel behind the interface; those extra operations can add costs and waiting time.

Evidence: [URI Scheme](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0321.mediawiki); [BOLT 11: Invoice Protocol for Lightning Payments](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/11-payment-encoding.md); [BOLT 12: Negotiation Protocol for Lightning Payments](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/12-offer-encoding.md); [The lifecycle of a payment channel](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/lifecycle-of-a-payment-channel.md); [Loop Fees](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lightning-terminal/loop-fees.md)

## Compare the whole cost of a small payment

Suppose a shop accepts 20,000 satoshis. One hypothetical wallet quotes 800 satoshis for an on-chain transaction; another quotes 15 satoshis for routing a Lightning payment over existing channels. The quoted totals are 20,800 and 20,015 satoshis. These are examples, not typical or guaranteed fees.

If the second wallet also requires an on-chain setup transaction or a service charge, include that cost. A routing fee alone is not the complete price of every Lightning workflow.

Evidence: [Sending Payments](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/payments.md); [Loop Fees](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lightning-terminal/loop-fees.md); [Transactions](https://developer.bitcoin.org/devguide/transactions.html)

## Completion and recovery look different

For on-chain payments, watch transaction inclusion and the recipient’s confirmation policy. For Lightning, check the wallet’s final payment status. A pending payment is not equivalent to a confirmed failure.

An offline recipient can receive an on-chain output. Ordinary Lightning payments need the receiving node or its service online. A Lightning node’s channel recovery can require information beyond the seed used for its on-chain keys.

Evidence: [Sending Payments](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/payments.md); [Recovery: Planning for Failure](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/recovery-planning-for-failure.md); [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html); [The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md); [Wallets](https://developer.bitcoin.org/devguide/wallets.html)

## Questions

### Does every Lightning payment create a Bitcoin transaction?

No. Normal channel payments update channel balances without placing each payment on the blockchain. Opening, closing and some recovery or liquidity operations can involve on-chain transactions.

Evidence: [The lifecycle of a payment channel](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/lifecycle-of-a-payment-channel.md)

### Can I paste a Lightning invoice into any Bitcoin wallet?

Only a wallet that supports the relevant Lightning payment format and method can use it. A shared Bitcoin brand or QR scanner does not establish compatibility.

Evidence: [BOLT 11: Invoice Protocol for Lightning Payments](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/11-payment-encoding.md); [URI Scheme](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0321.mediawiki)

## Claims and scope

### bitcoin-onchain-vs-lightning-quick-answer

An on-chain Bitcoin payment creates a transaction for inclusion in the public blockchain. A Lightning payment changes channel balances through a separate payment protocol, usually without recording each payment on-chain. Both can transfer bitcoin, but they use different payment requests, fee models and recovery procedures. Choose the method the recipient actually supports and inspect the wallet’s final amount and fees.

Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### bitcoin-onchain-vs-lightning-fact-on-chain-record

On-chain record: A transaction enters the shared blockchain

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### bitcoin-onchain-vs-lightning-fact-lightning-record

Lightning record: Individual payments usually update channels

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### bitcoin-onchain-vs-lightning-fact-availability

Availability: A normal Lightning payment needs responsive nodes

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [Transactions](https://developer.bitcoin.org/devguide/transactions.html) — Bitcoin developer documentation. Inputs, outputs, authorization, change, coinbase exceptions and fee accounting. Locator: Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse. Retrieved: 2026-10-02T18:53:53.759Z.
- [The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md) — Lightning Labs. Invoice-first Lightning flow, routes and settlement preimages. Locator: Introduction: sender and receiver interaction; Create invoice; Make the payment; Check the payment; Other payment types. Retrieved: 2026-10-02T18:53:57.281Z.
- [The lifecycle of a payment channel](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/lifecycle-of-a-payment-channel.md) — Lightning Labs. Cooperative versus unilateral closes and confirmation/delay requirements. Locator: Opening a channel; Sending funds through a payment channel; Closing a channel; Cooperatively; Non-cooperatively. Retrieved: 2026-10-02T18:53:57.295Z.
- [URI Scheme](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0321.mediawiki) — Bitcoin Improvement Proposals. Successor payment URI scheme and wallet-dependent payment instructions. Locator: General rules for handling (important!); General Format; Query Keys; Transfer amount; Forward compatibility; Backward compatibility. Retrieved: 2026-10-02T18:53:54.108Z.
- [BOLT 11: Invoice Protocol for Lightning Payments](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/11-payment-encoding.md) — Lightning specification contributors. Invoice amounts, payment hashes, expiry, signing and feature constraints. Locator: Human-Readable Part; Data Part; Tagged Fields; Payer / Payee Interactions; Payer / Payee Requirements. Retrieved: 2026-10-02T18:53:57.096Z.
- [BOLT 12: Negotiation Protocol for Lightning Payments](https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/12-offer-encoding.md) — Lightning specification contributors. Reusable offers produce separate invoice requests and authenticated invoices. Locator: Limitations of BOLT 11; Payment Flow Scenarios; Offers; Invoice Requests; Invoices; Payer Proofs. Retrieved: 2026-10-02T18:53:57.136Z.
- [Loop Fees](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lightning-terminal/loop-fees.md) — Lightning Labs. Service, chain and routing fees must be included when evaluating a swap. Locator: Loop Out: Estimated fees, Actual fees; Loop In: Estimated fees, Actual fees. Retrieved: 2026-10-02T18:53:57.455Z.
- [Sending Payments](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/payments.md) — Lightning Labs. LND initiated/in-flight/succeeded/failed statuses and safe retry semantics. Locator: Pathfinding; Dispatching Payments; Payment Fees; Monitoring Payments. Retrieved: 2026-10-02T18:53:57.437Z.
- [Recovery: Planning for Failure](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/recovery-planning-for-failure.md) — Lightning Labs. LND seed, static channel backups, safe channel recovery and external backups. Locator: aezeed; Static channel backups (SCB); Channel Database. Retrieved: 2026-10-02T18:53:57.272Z.
- [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html) — Bitcoin developer documentation. Payment request interpretation, confirmation checks and refund destination risks; historical protocol sections are dated. Locator: Requesting Payments; Verifying Payment; Issuing Refunds. Retrieved: 2026-10-02T18:53:53.958Z.
- [Wallets](https://developer.bitcoin.org/devguide/wallets.html) — Bitcoin developer documentation. Wallet types, generated keys, deterministic wallets and offline signing. Locator: Wallet Programs; Full-Service Wallets; Signing-Only Wallets; Wallet Files; Hierarchical Deterministic Key Creation; Loose-Key Wallets. Retrieved: 2026-10-02T18:53:53.756Z.

## Revision history

- 2026-10-02: First publication after primary-source research and separate automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “On-chain Bitcoin versus Lightning: choose the correct payment route.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-onchain-vs-lightning/