Lightning is Bitcoin's second layer for instant payments: channels between parties hold funds and settle balances off-chain, with the Bitcoin ledger as judge only when a channel closes. Payments route across channels in milliseconds for fees near zero.
The trade is capacity for complexity: Lightning excels at small, fast payments and demands liquidity management that on-chain settlement does not. For coffee it is unbeatable; for payroll, on-chain still wins.
Lightning is a second layer over Bitcoin that moves value through payment channels instead of waiting for every transfer to hit the base chain. Two parties open a channel with an on-chain funding transaction, then pass signed balance updates between themselves instantly and at negligible cost. Only the closing state ever reaches the chain. Multi-hop routing chains these channels together so parties without a direct channel can still pay through a path of peers.
The properties that follow are what payments people want from Bitcoin: settlement in milliseconds rather than block times, fees that are basis points of cents, and throughput unbounded by block space. The tradeoffs are channel liquidity management for routing nodes and the requirement that participants stay reasonably online to watch their channels.
For receivers, the practical shape is an invoice: a payment request that can be paid from any Lightning wallet. Settlement is final once the payment traverses the route, which is what makes it usable at a retail counter.
A coffee paid over Lightning settles before the customer pockets the receipt: the payment routes through channels, updates balances, and completes in milliseconds at a fee near zero. The base chain records nothing about the coffee.
Lightning is a first-class rail on U.CASH checkouts: instant Bitcoin beside the bank rails and the cards, settled on-chain, non-custodial.
Lightning is Bitcoin's answer to the retail queue: instant, near-free finality that cards cannot undercut on cost. Checkout with the Lightning option lets Bitcoin holders pay at counter speed while other buyers use chains or cards. Two practical notes for enabling it: liquidity on your receiving side determines how large a single Lightning payment can be before routing struggles, so size expectations accordingly, and fees, while tiny, are not literally zero, which the invoice conveys before the buyer pays. Neither caveat changes the core math: for small-ticket, high-frequency retail, nothing else settles this fast at this cost.
Every term behind the rails, the assets, and the settlement.