To receive Bitcoin over Lightning, open a Lightning-capable wallet, choose its receive or request-payment option, create a payment request, and share the invoice or its QR code. The payer scans or imports the request and sends the payment; you should confirm its status in your wallet rather than relying on a screenshot or copied invoice.
If you are asking, “How do I receive Bitcoin over Lightning?” the key is that you create the request before the payer sends anything. The request can be shared as text or as a QR code, but the payer’s wallet must understand the format. Check the amount, network, and expiry before sharing, then verify the payment in your own wallet.
As an Amazon Associate I earn from qualifying purchases.
What you need to receive a Lightning payment
You need a wallet that can receive Lightning payments and a way to deliver its payment request to the sender. The request is commonly a BOLT 11 invoice: a signed, encoded payment instruction. A wallet may show it as text, a QR code, or both. The QR code is only a convenient way to convey the request; it does not create a separate payment network or replace the invoice inside it.
In other words, receiving over Lightning is not the same as handing someone a Bitcoin address and waiting. You ask your wallet to create a request, then give that request to the payer. The payer’s wallet reads it and can use its details to prepare a Lightning payment. The receiver creates the request; the payer initiates the payment.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
The protocol documents define invoice and URI formats, but they do not establish which current wallets support each format. Check that your wallet explicitly identifies the request as a Lightning payment, and follow the labels and information it actually displays. Do not assume that a wallet can receive every type of payment request just because it can scan a QR code.
Before sharing anything, decide whether the request should be for a fixed amount. If the wallet lets you leave the amount open, check how it presents that choice and whether it suits the payment you expect. Also check the network and any expiry setting shown by the wallet. These checks help avoid sending a payer a request for the wrong amount, the wrong payment route, or one that is about to expire.
How to create and share a Lightning invoice
- Open your Lightning wallet. Choose the receive, request payment, or equivalent function. The exact label varies by wallet, so use the wallet’s own navigation rather than relying on a universal button name. You are looking for the action that creates an incoming payment request, not the action for sending a payment.
- Set the amount if the request should be fixed. Enter the amount the payer is expected to send if the wallet asks for one. If the wallet allows an amount to be left open, decide whether that is appropriate. An invoice may include an amount, but the amount is not a mandatory BOLT 11 field. Check the displayed network and any expiry setting before creating the request.
- Review any description or note. BOLT 11 can include a description or a description hash, and a wallet may offer a place to identify what a payment is for. Review the information the wallet presents before generating the invoice. The payer should also review the request details their wallet shows; a label or description is not a substitute for checking the amount and payment type.
- Create the payment request. The wallet generates an invoice, usually with an option to copy its text or display a QR code. BOLT 11 invoices include a timestamp and can include an amount, description or description hash, and expiry. They also contain a network prefix and payment hash. See the BOLT 11 payment-encoding specification.
- Give the payer the request. Share the invoice string or show its QR code for the payer to scan. Bitcoin.org describes this basic flow as displaying the wallet’s QR code for the other party to scan: Bitcoin for individuals. If you send the text, make sure you share the complete request rather than a shortened or altered string. If you show a code in person, give the payer a clear view so their wallet can scan it.
- Have the payer check the details before sending. They should verify that their wallet recognizes the request as Lightning and review the amount and description. If they are using a Bitcoin URI, they should also make sure the Lightning request—not an on-chain fallback—is the payment method they intend to use. The format they scan or import and what their wallet displays both matter.
- Check your wallet for the payment status. Treat the wallet’s status as confirmation. A screenshot, message, or copy of the invoice only shows that a request was shared; it does not prove that a payment completed. Wait for your own wallet to show the payment status before treating the transfer as received.
This is the basic answer to “How do I make a Lightning invoice?”: use your wallet’s receive function, set or omit an amount as appropriate, generate the request, and share it. The invoice is the request; copying it or displaying it does not itself move Bitcoin. The payer still needs to act on it, and you still need to confirm the result on your side.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What a BOLT 11 invoice contains—and when it expires
A BOLT 11 invoice is not simply a Bitcoin address. It is an encoded, signed payment request containing fields such as a network prefix, timestamp, and payment hash; it may also include an amount, description or description hash, and expiry. These fields make the invoice a particular request rather than a general destination to reuse indefinitely. The wallet uses the details to present a request the payer can act on.
The amount field is optional. If a request includes an amount, the payer should check that it matches what you expect. If no amount is encoded, the payer’s wallet may let them enter an amount, but how that is presented depends on the wallet. Do not assume that every wallet handles an amount-free request in the same way; the payer should confirm the amount shown before sending.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
The invoice timestamp and expiry determine how long the request is valid. If the invoice has no explicit expiry field, BOLT 11 specifies a default of 3,600 seconds—one hour. This is a protocol default, not a promise that every wallet will display a countdown or use the same interface to show expiry. If your wallet displays an expiry setting or validity period, check it before you share the request.
The BOLT 11 specification says a payee “SHOULD NOT accept a payment after the timestamp plus expiry has passed.” That is why an expired invoice should not be treated as an evergreen payment instruction. If the invoice expires before it is paid, create a fresh request in your wallet and share that one. Make sure the payer uses the new invoice rather than an old message, QR image, or copied string. If you are unsure whether the original request is still valid, check the wallet rather than asking the payer to rely on a stale copy.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Expiry also explains why a one-off invoice may be inconvenient when a person needs a longer-lived way to request payment. Other mechanisms such as BOLT 12 offers or DNS payment instructions are separate formats, not a way to make an existing BOLT 11 invoice permanent. Their availability and behavior depend on wallet support.
Invoice, QR code, Bitcoin URI, offer, and address: what differs?
These terms describe different parts of the payment flow. An invoice is the payment request; a QR code is one way to pass it to a wallet. A Bitcoin URI can package Lightning information alongside other payment details. Other mechanisms, such as offers and DNS payment instructions, work differently from a one-off BOLT 11 invoice and depend on wallet support.
The most useful comparison is not just the name of each format. Ask whether it is intended as a one-off or reusable instruction, whether the amount is fixed or supplied later, what expiry behavior applies, whether the payer’s wallet can scan or resolve it, and whether it includes an on-chain fallback. Those points determine what the payer must do and what you need to check before sharing it.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
| Format | How it is used | Amount and expiry | Compatibility considerations |
|---|---|---|---|
| BOLT 11 invoice | An encoded payment request, often shared as text or a QR code. It is ordinarily the request for a particular payment, not a general reusable name. | Can include an amount and expiry; includes a timestamp. If expiry is omitted, the protocol default is 3,600 seconds (one hour). | The payer needs a wallet that can pay BOLT 11 requests and must use the request before it expires. |
Bitcoin URI with lightning= |
Packages a BOLT 11 invoice in a Bitcoin URI. It may include an on-chain fallback as well, so the URI can present a choice of payment route. | Depends on the included invoice and any other URI details. The included invoice’s amount and expiry still matter. | The payer’s wallet must understand the URI and its Lightning parameter. The payer should verify that Lightning, rather than the fallback, is selected. BIP 321 defines this parameter and shows URI examples. |
BOLT 12 offer in a Bitcoin URI with lno= |
Packages a BOLT 12 offer as a payment instruction rather than sending a one-off BOLT 11 invoice. An offer can be used as a reusable payment instruction where supported by wallets. | Not established here as having the same amount or expiry behavior as a BOLT 11 invoice. Do not apply BOLT 11’s one-hour default to an offer. | Wallet support for BOLT 12 and the URI format is not universal. BIP 321 defines the lno parameter. |
| Lightning Address or BIP 353 DNS payment instructions | Uses a separate resolution mechanism to obtain payment instructions, instead of sharing a single invoice string directly. | Not established here as matching a BOLT 11 invoice’s fixed amount or expiry behavior. | BIP 353 describes DNS payment instructions as intended to extend and subsume the existing Lightning Address scheme; that does not establish universal wallet support. |
The URI parameters and examples are defined in BIP 321. It specifies lightning as the parameter for a BOLT 11 invoice and lno for a BOLT 12 offer. Its examples include a Bitcoin URI with a Lightning invoice and on-chain fallback, as well as a URI that carries only a Lightning invoice. In practice, the payer’s wallet needs to understand the parameter and present the route clearly enough for the payer to choose correctly.
DNS payment instructions and their relationship to Lightning Address are described in BIP 353. It describes DNS-based instructions as intended to extend and subsume the existing Lightning Address scheme. That is a description of the mechanism and its intended relationship, not evidence that every wallet can resolve it. These specifications describe formats, not proof that a particular wallet implements them.
So, which should you share? For a straightforward one-time payment, use the receive request your wallet generates and confirm that the payer can process it. If you are considering a Bitcoin URI, an offer, or a DNS-based instruction, first check that both sides’ wallets support the format and that the payer can see the payment route and amount. A familiar-looking QR or address is not enough to establish compatibility.
Can someone pay by scanning a QR code?
Yes, if the QR contains a request format their wallet can process. A QR may encode an invoice directly or a Bitcoin URI. Ask the payer to confirm that their wallet interprets the code as a Lightning payment and shows the intended amount before sending. This is the practical answer to “Can someone pay me by scanning a QR code?”: scanning is a way to transfer the request, but the wallet has to recognize what the code contains.
A QR code is a visual container for data, not a guarantee that a payment will work. The same-looking square could contain an invoice, a Bitcoin URI, or a URL. The payer’s wallet may handle some of those formats and not others. If the wallet displays a payment method or amount that does not match what you expected, the payer should stop and clarify rather than sending based on the image alone.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Not every QR containing payment-related information behaves the same way. Some QR codes contain a URL that leads to a payment request. BIP 73 describes wallets that can scan a QR code and retrieve either a Bitcoin URI or a payment request from a URL, but says direct handling of payment-request URLs depends on the QR-scanning wallet implementing that behavior. Its alternatives include a QR containing a Bitcoin URI or a general QR scanner that opens a webpage with a wallet link. See BIP 73.
Because QR behavior varies, have the payer check the wallet screen before authorizing payment. If the scan does not open a request, you can share the invoice text if their wallet supports importing it, or use a compatible URI or another format both wallets support. Do not assume that every QR scanner retrieves a payment request from a URL, and do not treat successful scanning as proof that a payment has been sent or received.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common problems and what to do
- The invoice expired. Generate a new request in your wallet and send the new invoice or QR code. The old request’s timestamp and expiry define its validity period. With no explicit expiry field, BOLT 11 defines a one-hour default. Make sure the payer is not using an older copy from a previous message or image.
- The payer’s wallet does not recognize the QR. Share the invoice text if the payer’s wallet supports importing it, or use a payment format both wallets support. A QR code does not guarantee compatibility. If the QR contains a URL rather than an invoice or URI, the wallet may not implement the behavior needed to retrieve the request.
- The payer sees an on-chain option instead of Lightning. If the request is a Bitcoin URI with an on-chain fallback, the payer should explicitly select Lightning if that is the intended route, then verify the amount and network in their wallet. BIP 321’s URI examples demonstrate that the fallback and Lightning request can appear together; they are not the same payment method.
- The payer scanned a URL but no payment request opened. Their wallet may not support retrieving payment requests from QR-encoded URLs. Try sharing the invoice itself or a compatible Bitcoin URI instead. BIP 73’s described behavior depends on support in the QR-scanning wallet, so a failed URL scan does not by itself mean the underlying invoice is invalid.
- The amount is missing or looks wrong. Recheck whether you intended to create a fixed-amount invoice or an amount-free request. The BOLT 11 amount is optional, and the payer should review the amount their wallet shows before sending. If the displayed amount or request is not what you intended, create or share the correct request instead of asking the payer to guess.
- You have only a screenshot of a payment confirmation. Check the payment status in your own wallet. The screenshot is not confirmation that your wallet received the payment. The invoice or QR image itself is also only a request, not proof that it was paid.
- You are not sure whether the payer sent Lightning or on-chain funds. Ask what their wallet showed and check the status in your receiving wallet. If a URI offers both an invoice and an on-chain fallback, the payer must select the intended route. A shared QR image alone cannot tell you which route the payer used.
Fees and timing
Bitcoin.org characterizes Lightning payments generally as near-instant with minimal fees, but that is not a guarantee for an individual transfer. The protocol material cited here does not establish a specific transaction’s fee or completion time. Do not promise a precise payment speed or cost based on the fact that a request is a Lightning invoice.
For receiving, the practical check is the status in your wallet. A payer’s screenshot, a “sent” message, or the fact that they scanned the QR does not confirm that your wallet received the payment. Wait for the wallet’s own status before treating it as complete. If the payment has not appeared, check the invoice validity, confirm that the payer used the intended network and request, and avoid asking them to reuse an expired invoice.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to receive Bitcoin over Lightning safely
Keep the process simple and verify each handoff. Create the request in a Lightning-capable wallet; check the amount, network, description, and expiry details the wallet shows; share the invoice or QR; and ask the payer to check what their wallet recognizes before sending. If you use a URI with a fallback, make sure the payer intends to choose Lightning. If the request expires, generate a new one rather than relying on the old copy.
Remember the distinction between request and payment. An invoice string, QR code, Bitcoin URI, offer, or payment address is a way to communicate or resolve payment instructions. It is not evidence that payment has completed. Confirm the receiving wallet’s status yourself, and use only formats both wallets can process.
Frequently Asked Questions
How do I receive Bitcoin over Lightning?
Open a Lightning-capable wallet, choose its receive or request-payment function, create a request, and share the invoice text or QR code. Ask the payer to verify the amount and that their wallet recognizes Lightning, then confirm the payment status in your own wallet.
How do I make a Lightning invoice?
Use the receive or request-payment function in your Lightning wallet. Set an amount if you want a fixed-amount request, check the network and expiry information, then create and share the invoice your wallet generates.
Can someone pay me by scanning a QR code?
Yes, if the QR contains an invoice or payment URI their wallet understands. QR codes can also contain URLs, and support for retrieving a payment request from a URL depends on the payer’s wallet. Have the payer verify the route and amount before sending.
Why did my Lightning invoice expire?
A BOLT 11 invoice includes a timestamp and may include an expiry. If the expiry field is omitted, the protocol default is 3,600 seconds, or one hour. If the request expires before payment, create a fresh invoice and share that one.
Does a QR code prove that someone paid me?
No. A QR code conveys payment information; it does not prove payment. Check the payment status in your own wallet, and do not rely on a screenshot or a copy of the invoice as confirmation.
Can I reuse a BOLT 11 invoice?
Treat a BOLT 11 invoice as a particular payment request with a timestamp and expiry, not as an evergreen instruction. For a reusable payment instruction, BOLT 12 offers or DNS payment instructions are distinct alternatives, where supported by the wallets involved.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesThe Bottom Line
To receive Bitcoin over Lightning, create a request in your Lightning wallet, check its amount, network, and expiry, then share the invoice or a QR code. The payer’s wallet must support the format and show the intended Lightning payment. If the invoice expires, create a new one—and confirm receipt in your own wallet rather than trusting a screenshot or shared request.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
