Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Upgrades and scaling · Entry 206

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

AI-assisted research · separate automated verificationCorrections

Theme
Upgrades and scaling
Sources
11 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for On-chain Bitcoin versus Lightning: choose the correct payment route
FactDetailSource
On-chain recordA transaction enters the shared blockchain[1]
Lightning recordIndividual payments usually update channels[3]
AvailabilityA normal Lightning payment needs responsive nodes[2]
01

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.

02

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.

03

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.

Direct answers

Questions people ask

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.

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.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

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: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
On-chain record: A transaction enters the shared blockchain

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Lightning record: Individual payments usually update channels

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Availability: A normal Lightning payment needs responsive nodes

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. TransactionsBitcoin 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 · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.759ZOpen source
  2. The payment cycleLightning 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 · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.281ZOpen source
  3. The lifecycle of a payment channelLightning 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 · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.295ZOpen source
  4. URI SchemeBitcoin 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 · Version / scope: Pinned BIPs revision · Retrieved: 2026-10-02T18:53:54.108ZOpen source
  5. BOLT 11: Invoice Protocol for Lightning PaymentsLightning 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 · Version / scope: Pinned BOLTs revision · Retrieved: 2026-10-02T18:53:57.096ZOpen source
  6. BOLT 12: Negotiation Protocol for Lightning PaymentsLightning 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 · Version / scope: Pinned BOLTs revision · Retrieved: 2026-10-02T18:53:57.136ZOpen source
  7. Loop FeesLightning 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 · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.455ZOpen source
  8. Sending PaymentsLightning Labs

    LND initiated/in-flight/succeeded/failed statuses and safe retry semantics.

    Locator: Pathfinding; Dispatching Payments; Payment Fees; Monitoring Payments · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.437ZOpen source
  9. Recovery: Planning for FailureLightning Labs

    LND seed, static channel backups, safe channel recovery and external backups.

    Locator: aezeed; Static channel backups (SCB); Channel Database · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.272ZOpen source
  10. Payment ProcessingBitcoin developer documentation

    Payment request interpretation, confirmation checks and refund destination risks; historical protocol sections are dated.

    Locator: Requesting Payments; Verifying Payment; Issuing Refunds · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.958ZOpen source
  11. WalletsBitcoin 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 · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.756ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

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/