Making lightning payments is the reason the entire lightning network exists — fast, cheap Bitcoin transactions for everyday use. You have learned how the protocol works in Lesson 4.1, how channels and routing function in Lesson 4.2, and which wallets are available in Lesson 4.3. Now it is time to put that knowledge into practice.
This lesson walks through the complete experience: sending your first payment, receiving sats, real-world use cases, bridging between on-chain and lightning, and troubleshooting when things go wrong. Whether you are buying coffee, tipping on Nostr, or accepting payments for your business, this is your hands-on guide to how to use the lightning network in daily life.
Making Your First Lightning Payment
Sending a lightning payment takes seconds once your wallet is set up. Here is the step-by-step process:
Step 1: Get a Lightning Wallet
If you have not already, install a lightning wallet on your phone. For your first experience, Phoenix Wallet is recommended — it handles all the channel management automatically so you can focus on actually using lightning.
Step 2: Fund Your Wallet
You need bitcoin in your lightning wallet before you can spend. Two options:
- Send on-chain bitcoin: Your wallet provides a Bitcoin address. Send from an exchange or another wallet. Phoenix uses swap-in addresses that splice the funds into your lightning channel after on-chain confirmation.
- Receive a lightning payment: If someone is willing to send you sats, generate an invoice and have them pay it. This requires inbound liquidity (see Lesson 4.2), which Phoenix and Breez handle automatically via their LSPs.
Step 3: Scan an Invoice
When you want to pay someone, they provide a lightning invoice — either as a QR code or a text string starting with lnbc. Open your wallet, tap “Send” or “Scan,” and point your camera at the QR code. Your wallet decodes the invoice and shows you the amount, description, and fees.
Step 4: Confirm and Send
Review the details and confirm. The payment completes in 1–3 seconds. You will see a confirmation screen with the payment amount and a payment preimage (proof of payment).
That is it. No block confirmations. No waiting. The recipient sees the funds instantly.
Receiving Lightning Payments
Receiving lightning payments requires generating an invoice that the sender can pay.
Creating an Invoice
- Open your wallet and tap “Receive”
- Enter an amount (or leave it blank for a zero-amount invoice where the sender chooses)
- Optionally add a description (e.g., “Freelance work — logo design”)
- Your wallet generates a BOLT11 invoice displayed as a QR code
- Share the QR code or copy the invoice text string and send it to the payer
Inbound Liquidity Requirement
Remember from Lesson 4.2: you can only receive up to your inbound liquidity — the remote balance across your channels. If you just opened your wallet and funded it with on-chain bitcoin, most of your capacity is outbound (local). You may not be able to receive large payments until you either spend some sats (converting outbound to inbound) or your wallet’s LSP opens additional inbound capacity.
Phoenix and Breez handle this automatically by splicing or opening new channels when needed, charging a fee for the added liquidity. If you run your own node through Zeus, you manage inbound liquidity manually.
Lightning Addresses
Some wallets support lightning addresses — email-like identifiers (e.g., [email protected]) that let people pay you without generating individual invoices. The sender enters your lightning address, and the wallet fetches a fresh invoice from your provider automatically. This is convenient for receiving tips or regular payments.
Lightning Payment Use Cases
The lightning network has moved far beyond a technical curiosity. Here are the real-world use cases driving adoption today:
Tipping and Social Media
Nostr — the decentralized social media protocol — integrates lightning natively. Users attach lightning wallets to their profiles and can send and receive tips (called “zaps”) on posts with a single tap. This is the first social media platform where creators earn directly from their audience without platform fees or algorithms controlling distribution.
Podcasting 2.0 apps like Fountain and Breez use streaming sats — listeners send a small number of sats per minute directly to podcast creators as they listen. No advertising revenue, no subscription gatekeeping — just direct value exchange.
Micropayments
Lightning enables payment amounts that are impossible with traditional payment rails. Sending 10 sats (a fraction of a cent) costs less than 1 sat in fees. This unlocks:
- Pay-per-article for online content (instead of monthly subscriptions)
- API calls priced per request
- Machine-to-machine payments for IoT devices
- In-game purchases measured in individual sats
Point of Sale
Physical businesses accept lightning payments using dedicated POS setups or wallet apps like Breez (which has a built-in POS mode). The customer scans a QR code, and the payment settles in seconds — faster than credit card processing. El Salvador’s Chivo wallet brought lightning POS to thousands of merchants nationwide.
Vending Machines and Physical Devices
Bitcoin-enabled vending machines use lightning for instant payments. The machine displays a QR code, the customer pays, and the product is dispensed. No card reader, no NFC, no middleman processing fees. Companies like LNbits provide open-source firmware for building lightning-enabled physical devices.
Online Purchases and E-Commerce
Online stores integrate lightning checkout through payment processors like BTCPay Server, OpenNode, or Strike. The checkout page shows a lightning invoice QR code, the customer pays from their wallet, and the merchant receives confirmation in seconds. Compared to on-chain Bitcoin payments (which require waiting for confirmations), lightning checkout is comparable in speed to credit card payments.
Gaming
Several gaming platforms use lightning for in-game economies. Players earn sats for achievements, trade items, or place bets — all settled instantly through lightning. THNDR Games and Zebedee are prominent players in this space.
Paying On-Chain Merchants With Lightning (and Vice Versa)
Sometimes you have funds on one layer but the recipient expects the other. Submarine swaps bridge this gap by atomically exchanging on-chain bitcoin for lightning sats (or the reverse).
Lightning to On-Chain (Loop Out)
If a merchant only accepts on-chain payments but your funds are in lightning channels, services like Boltz or Lightning Labs’ Loop perform the conversion. You send lightning sats to the swap service, and the service sends on-chain bitcoin to the merchant’s address. The swap is atomic — secured by HTLCs — so neither party can cheat.
On-Chain to Lightning (Loop In)
The reverse works too: you send on-chain bitcoin to the swap service, and the service sends lightning sats to your wallet. This is useful for funding your lightning wallet from an exchange that only supports on-chain withdrawals.
How Submarine Swaps Work
A submarine swap uses a hash lock to tie the on-chain and lightning payments together. The same preimage that unlocks the lightning HTLC also unlocks the on-chain smart contract. If one side completes, the other must also complete. If the swap times out, both sides get their funds back.
Swap fees typically range from 0.1% to 0.5% of the transaction amount, plus on-chain mining fees. This is more expensive than a pure lightning payment, but it enables interoperability between the two layers.
Troubleshooting Failed Lightning Payments
Lightning payments fail more often than on-chain transactions because routing depends on real-time channel states across the network. Understanding the common error messages helps you fix problems quickly.
“No Route Found”
Your wallet could not find a connected path to the recipient with sufficient capacity. Possible causes:
- The recipient’s node is offline
- The recipient has no public channels or routing hints
- Your node is poorly connected to the broader network
Fix: Ask the recipient if their node is online. If you run your own node, open channels to well-connected hubs. Try again in a few minutes — network topology changes constantly.
“Payment Timed Out”
A route was found, but the payment did not complete within the time limit. An intermediate node may have been slow or unresponsive.
Fix: Retry. Your wallet’s pathfinding algorithm will avoid the slow node on the next attempt. If payments consistently time out, your wallet or the recipient’s wallet may have connectivity issues.
“Insufficient Local Balance”
You are trying to send more than you have available in your lightning channels.
Fix: Fund your wallet with additional bitcoin (on-chain deposit or receive a lightning payment). Or reduce the payment amount.
“Channel Reserve” Error
Lightning channels require a minimum balance (the channel reserve) to remain on each side. This reserve ensures that both parties have something at stake to prevent cheating. Typically 1% of channel capacity.
Fix: You cannot spend your entire channel balance. The reserve is a protocol-level requirement. If the reserve prevents your payment, add more funds or use a different channel.
“Invoice Expired”
The invoice you are trying to pay has passed its expiry time (default is 1 hour for most invoices).
Fix: Ask the recipient to generate a new invoice. Invoices are cheap to create — there is no cost to generating a fresh one.
For a comprehensive troubleshooting reference covering edge cases and advanced diagnostics, see our lightning troubleshooting guide for failed transactions.
Lightning Payments Best Practices
Follow these guidelines to ensure reliable and secure lightning payments:
Keep Channels Balanced
If you only send payments, your channels will eventually deplete. If you only receive, your inbound capacity fills up. A healthy lightning wallet both sends and receives regularly, naturally keeping channels balanced. If you need to rebalance manually, review the strategies in our channel management masterclass.
Use the Right Wallet for Your Needs
Do not use a custodial wallet for large amounts. Do not use a complex node-connected wallet if you just want to buy coffee. Match the wallet to the use case — Lesson 4.3 covers the comparison in detail.
Keep Small Amounts on Custodial Wallets
If you use a custodial wallet for convenience (like Wallet of Satoshi), treat it like cash in your pocket — only keep what you are willing to lose. Move larger holdings to a non-custodial wallet or on-chain cold storage.
Back Up Regularly
Lightning channel state is more fragile than on-chain bitcoin. If you lose your channel state without a backup, you may need to wait for a force close or, in the worst case, lose funds. Ensure your wallet’s backup mechanism is active:
- Phoenix: Automatic encrypted cloud backup
- Zeus: Static Channel Backup (SCB) — export and store securely
- Breez: Greenlight handles state persistence
Verify Payment Proofs
Every successful lightning payment produces a payment preimage — a 32-byte value that serves as cryptographic proof of payment. If a merchant claims you did not pay, the preimage proves otherwise. Most wallets store payment history including preimages. For large payments, save this proof.
Key Takeaways
- Sending a lightning payment takes seconds: scan an invoice QR code, confirm the amount, done — no block confirmations needed
- Receiving requires inbound liquidity, which modern wallets like Phoenix and Breez manage automatically via LSPs
- Real-world use cases span tipping on Nostr, micropayments, point-of-sale, e-commerce, vending machines, and gaming
- Submarine swaps (Boltz, Loop) bridge on-chain and lightning, enabling payments across layers
- Common payment failures — no route, timeout, insufficient balance, channel reserve — each have specific causes and solutions
- Best practices: keep channels balanced, match wallet to use case, back up channel state, and keep only small amounts on custodial wallets
Frequently Asked Questions
How fast are lightning payments compared to on-chain Bitcoin?
Lightning payments settle in 1–3 seconds. On-chain Bitcoin transactions require at least one block confirmation (approximately 10 minutes on average), and most services require 3–6 confirmations (30–60 minutes). For everyday purchases, this speed difference is what makes lightning practical as a payment method.
Can I get a refund on a lightning payment?
Lightning payments are final — there is no built-in chargeback mechanism like credit cards. If you need a refund, the recipient must send you a new payment. BOLT12 offers include a refund mechanism where the recipient can initiate a return payment. For everyday commerce, this finality is a feature (no chargeback fraud), but it means you should verify payment details before confirming.
What is the maximum amount I can send over lightning?
There is no protocol-defined maximum, but practical limits exist. Your payment is limited by the capacity of channels along the route. A single channel can forward up to its capacity (minus reserves). Multi-Path Payments (MPP) help by splitting across multiple routes. In practice, payments up to a few hundred dollars route reliably. Payments in the thousands of dollars may require well-connected nodes with high-capacity channels. For very large transfers, on-chain transactions remain the better option.
Do I need to be online to receive lightning payments?
Yes — your lightning node (or wallet app) must be online to receive payments. This is different from on-chain Bitcoin, where funds arrive at your address regardless of whether your wallet is open. If you are offline when someone tries to pay you, the payment will fail. Some wallets offer workarounds: Phoenix can receive payments to an on-chain swap address that is later spliced into your channel, and services like lightning addresses can hold invoices briefly while your wallet comes online.
Is it possible to earn money by routing lightning payments?
Yes. If you run a lightning node with well-connected, well-funded channels, you can earn routing fees by forwarding payments for others. The income is typically small — a few sats per forwarded payment — and depends on your node’s position in the network, your channel capacity, and your fee settings. Running a profitable routing node requires active channel management and a reliable, always-online setup. Lesson 4.5 covers running your own node in detail.