How to Send and Receive Payments on the Bitcoin Lightning Network? Wallets, Invoices, and Payment Verification

 / 
5

The core of sending and receiving payments on the Lightning Network is that the recipient generates an "invoice" or address, and the payer pastes or scans it in their own wallet and confirms. It does not use the Bitcoin main chain, so it usually completes within seconds, and fees are extremely low. However, "generating an invoice," "pasting an invoice," and "showing as paid" are only three intermediate states. The real standard for verifying that funds have arrived is that the recipient's wallet balance actually increases, or that the invoice status changes from pending to complete.

OKX Exchange
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!!

Wallets: What the Recipient and Payer Each Need

Lightning Network wallets come in two types. Self-custodial wallets let you control your own private keys, such as Phoenix, Zeus, Cake Wallet, and Breez. Custodial wallets are managed by a platform, such as exchange accounts or Wallet of Satoshi's custodial mode. For readers making their first payment, I recommend using a self-custodial wallet for the first small test, because you can see the balance change directly without relying on a third-party platform's deposit review.

The recipient needs a wallet that supports the Lightning Network. Cake Wallet's mobile and macOS versions enable Lightning by default and can be turned off in settings. Wallet of Satoshi assigns each new wallet a random Lightning address directly. If you use an exchange account, such as CoinCorner or Shakepay, their Lightning receiving features are embedded in the "Receive" or "Deposit" pages.

The payer also needs a wallet that can parse Lightning invoices or Lightning addresses. Modern wallets usually automatically recognize whether the pasted content is an on-chain address or a Lightning invoice. If the wallet does not support Lightning, pasting an invoice will not show a lightning icon, or it will simply prompt a format error.

Receiving: The Difference Between Generating an Invoice and a Lightning Address

When receiving, you are actually providing a payment request to the other party. There are two forms:

A Lightning invoice (BOLT11) is a one-time string that starts with lnbc (on mainnet), followed by information such as amount, timestamp, and payment hash. Its default validity period is 1 hour (3600 seconds), and a new one must be generated after it expires. An invoice can have a specified amount or no amount (zero-amount invoice), but zero-amount invoices are not necessarily supported by all payer wallets.

A Lightning address looks like an email, for example This email address is being protected from spambots. You need JavaScript enabled to view it.. Its underlying mechanism is usually LNURL-pay. Each time the payer's wallet scans or enters this address, it requests a new invoice from the server to complete the payment. This means a Lightning address can be reused, making it suitable for placing in social media bios or on a payment page without needing to regenerate it each time. Cake Wallet allows you to set a custom username, such as This email address is being protected from spambots. You need JavaScript enabled to view it..

The steps to generate an invoice (using a general process as an example):

  1. Find the "Receive" button in your wallet, and confirm that Lightning Network is selected, not on-chain Bitcoin. Some wallets use a lightning icon (⚡) to distinguish it.

  2. Enter the amount you want to receive (in sats, or switch to fiat display). If you want to generate a zero-amount invoice, leave it blank, but note that not all payers support it.

  3. Optionally fill in a note, such as "coffee" or "consulting fee," so the payer can see the purpose before confirming.

  4. After generation, you will get a QR code and a copyable invoice text. Show the QR code to the other party to scan, or copy the text and send it via chat.

Receiving with a Lightning address is simpler: share the address with the other party, and they enter or paste it in their wallet, enter the amount, and confirm.

Paying: Paste, Check, Confirm

The payer has one less "generate" step than the recipient. Open the "Send" page in the wallet, paste the invoice text provided by the other party, or scan the QR code directly. The wallet will automatically parse the amount, recipient node information, and validity period.

Check three pieces of information before confirming: the amount, the validity period, and whether the wallet shows a "Lightning" indicator. If a Lightning invoice is pasted, many wallets will show a lightning icon next to the input field as confirmation. If the other party provided a zero-amount invoice, you need to enter the amount yourself.

After confirming the send, Lightning payments usually complete within seconds. Routing nodes pass funds hop by hop through HTLCs (Hash Time-Locked Contracts), and the recipient releases the "preimage" to prove receipt before the payment is finally settled. If any hop fails, the funds automatically return and do not get stuck along the way.

Verifying Arrival: Three Different "Complete" States

This is the step most likely to mislead beginners. The "complete" you see may only be one of these stages:

Stage One: The payer's wallet shows "Sent." This means the payer signed the payment request and broadcast the HTLC. If routing fails, the funds will return, but the return may take from a few seconds to dozens of seconds. Seeing "send successful" on the payer's side does not mean the recipient has received it.

Stage Two: The recipient's wallet shows "Received" or the balance increases. This is the real arrival signal. A balance update in a self-custodial wallet is direct evidence. CoinCorner's documentation notes that after a successful payment, funds are reflected in the BTC balance "almost immediately." Cake Wallet also states that Lightning payments are "settled in seconds, never waiting for on-chain confirmation."

Stage Three: A custodial platform's "deposit" status. If you are receiving to an exchange account, the platform may need additional internal processing after receiving the Lightning payment. Coinbase's help page mentions that a Lightning invoice may remain in "pending" status in the transaction history for up to 72 hours until the sender completes the transaction. This means that if you generate a Lightning deposit invoice on Coinbase but the other party never pays, the invoice will remain in history for 72 hours before expiring.

Specific methods for verifying arrival:

  1. The recipient should open the wallet balance page and confirm that the sats balance has actually increased. Do not just look at the "sent" screenshot from the payer.

  2. If using a self-custodial wallet, check the status of the transaction in the transaction history. Wavelength's developer documentation describes the status change: after an invoice is created it is pending, after payment settles it becomes complete, and if it fails it becomes failed.

  3. If using a custodial platform, check the platform's Lightning transaction record. Coinbase's deposit standard is that the platform's internal status becomes "Complete."

Exceptions: Expired Invoices, Routing Failures, Wrong Network Selection

Expired invoices are the most common cause of failure. BOLT11 invoices default to a 1-hour validity period, and Binance's Lightning deposit invoices explicitly state that they expire in 30 minutes. If you scan an expired invoice, the wallet will directly reject it. Solution: have the recipient generate a new one.

Routing failures appear when the payer tries to send and receives a "payment failed" message, and the funds automatically return. Shakepay's help center lists possible causes: the invoice has expired, the receiving wallet has insufficient liquidity, or the LNURL address is offline or misconfigured. If failures repeat, try having the recipient generate a new invoice, or switch to an on-chain transfer.

Wrong network selection is a more serious situation. If you send on-chain Bitcoin to a Lightning invoice address, or send a Lightning payment to an on-chain address, the funds may not arrive. Shakepay explains that their system automatically detects the address type and only uses Lightning when it is valid. But not all platforms have such detection. Binance's warning is direct: entering incorrect information or selecting the wrong network may result in permanent loss of assets. If you are unsure, check before confirming whether the wallet or platform shows a "Lightning" or lightning icon.

Payer shows sent, but recipient has not received it: first have the recipient refresh the balance page. If it has not arrived after a few minutes, send the payer's transaction details (if available) to the recipient, and have the recipient look for the corresponding incoming record in their wallet. Lightning payments are atomic: either both sides complete, or they automatically roll back. Funds do not remain "stuck in the middle" for long.

One Test Transaction Before Everything

No matter which wallet or platform you use, when using the Lightning Network for the first time, send a small amount of 1000 sats or less to yourself first (for example, from an exchange to your own Lightning wallet, or from one wallet to another). After confirming the balance change and status display, then handle larger amounts. This step can expose all configuration problems: whether the wallet supports Lightning, whether the network matches, whether the invoice can be parsed, and whether arrival is normal.

OKX Exchange
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!!

References

  1. Blink Bitcoin Wallet·How do I receive bitcoin payments using the Lightning Network with Blink?, page published or updated: 2026-07-16; checked: 2026-10-02.
  2. Cake Wallet Docs·Bitcoin Lightning, page published or updated: 2026-07-22; checked: 2026-10-02.
  3. Lightning Labs·Understanding Lightning Invoices, page published or updated: 2021-07-05; checked: 2026-10-02.
  4. Shakepay Help Center·How to receive or withdraw bitcoin on the Lightning network, page published or updated: 2025-12-09; checked: 2026-10-02.
  5. Coinbase·Pending crypto transactions, page update date not indicated; checked: 2026-10-02.
  6. CoinCorner·Sending and receiving via Lightning, page published or updated: 2026-02-25; checked: 2026-10-02.
  7. Wallet of Satoshi·Lightning Addresses - How They Work and How to Create a Custom One, page published or updated: 2025-09-28; checked: 2026-10-02.
  8. Wavelength·Receive a Lightning payment, page published or updated: 2026-07-16; checked: 2026-10-02.
  9. Zelcore·Lightning for Bitcoin Merchants: Channels and LSPs, page published or updated: 2026-06-28; checked: 2026-10-02.
  10. Binance·How to Use the Bitcoin Lightning Network to Deposit and Withdraw BTC on Binance, page published or updated: 2023-06-30; checked: 2026-10-02.
  11. Klever Wallet·How to Receive Bitcoin (BTC) via Lightning Network, page published or updated: 2025-05-16; checked: 2026-10-02.
  12. Crypto.com·How to Pay With Bitcoin: Step-by-Step Guide, page published or updated: 2026-04-05; checked: 2026-10-02.
  13. GitHub·BOLT #11: Invoice Protocol for Lightning Payments, page update date not indicated; checked: 2026-10-02.
  14. LNbits Documentation·LNURLp, page published or updated: 2026-06-07; checked: 2026-10-02.