Pay a Bitcoin invoice on the right rail
A merchant can accept bitcoin on the base chain, on the Lightning Network or both. Read the checkout method and invoice status before deciding what to scan and when to consider the order paid.
Read the checkout before scanning
An onchain Bitcoin payment sends BTC to an address and becomes part of the base-chain transaction history. The sender’s wallet estimates the fee; the merchant chooses how many confirmations it requires. A Lightning payment typically uses a payment request from the recipient and passes through funded payment channels. A compatible wallet and a usable route with enough liquidity are necessary. Both methods use bitcoin, and neither automatically converts an incompatible request.
Check the merchant, order identifier, payment rail, amount and quote expiry in the original checkout. A satoshi, or sat, is one hundred-millionth of a BTC. A value shown in sats can look dramatically different from the same amount in BTC. Compare the currency unit and decimal places before authorizing. If an invoice specifies a local-currency amount, the checkout may only hold its BTC quote for a limited period.
Keep payment status separate from order status
For an onchain transaction, retain the transaction identifier and verify the amount and recipient output. A wallet can show the transaction immediately after broadcast while the merchant is waiting for confirmations. For Lightning, hold onto the invoice and successful payment reference furnished by the wallet. A typical Lightning invoice payment does not create a separate public onchain transaction for that individual purchase.
Wait for a clear wallet result and check the merchant’s order status. A Lightning attempt that cannot find sufficient routing liquidity can fail even when the sender’s total balance exceeds the price. A pending attempt calls for checking status, not switching instantly to a second wallet and trying again. If the request has expired, obtain a new invoice from the same verified checkout after confirming the old attempt did not settle.
Resolve the exception with the merchant
Payment processors can distinguish expired, partially paid, overpaid, processing and settled orders. A late onchain payment may eventually be confirmed even after a rate quote expires. Contact the merchant with the invoice identifier and the relevant receipt before sending another amount. Where a wallet deducts the sending fee from a selected total, check the amount actually sent to the invoice.
A refund is a new transfer controlled by the merchant or its payment processor. Provide a fresh destination through the original authenticated order flow when requested. The sender may have used a shared exchange wallet, so the original sending address can be unsuitable for a refund. Save the merchant’s agreement on whether the refund equals the original BTC amount or a local-currency equivalent.
Worked example
The café checkout still says “processing”
Your wallet shows an onchain BTC payment and the cashier has not received a settled notice. Verify the destination and amount against the order and ask how many confirmations the processor requires. Paying the Lightning option as well could create a second valid payment. If timing matters, the merchant must decide how to handle the existing order first.
What to remember
- Match the rail and units to the merchant’s current invoice.
- Keep separate evidence of the wallet result and merchant settlement.
- Resolve ambiguity with the merchant before replacing a payment.
Sources and further reading
- Bitcoin project · Payment characteristics and confirmations
- Lightning Labs · Lightning invoices and payment lifecycle
- BTCPay Server · Invoice status and exceptions
- BTCPay Server · Merchant-managed refunds
Sources checked 21 November 2026 · De Leon Coin