<h1>How to Spend Bitcoin Using a Merchant Invoice</h1><p>To spend Bitcoin through a merchant invoice, confirm the seller and order, select the supported Bitcoin payment route, review the requested amount and destination, then authorize the payment before the invoice expires. After sending, check the merchant's payment status and keep the transaction record. A wallet reporting sent and a store reporting order complete are different milestones, so do not assume one automatically proves the other.</p><p>The invoice is the bridge between a purchase and a cryptocurrency transfer. It tells the buyer what payment the merchant expects for a particular order under particular conditions.</p><h2>Make sure the invoice belongs to the purchase</h2><p>Begin from the merchant's genuine checkout rather than an unrelated message containing a payment address. Check the order description, total, and payment processor if one is involved. A technically valid Bitcoin address can still belong to the wrong recipient.</p><p>A payment request can contain an amount and other information as well as a destination. After scanning a QR code or opening a wallet link, inspect what the wallet has populated. Convenience does not remove the need to compare the proposed payment with the invoice.</p><p>Bit.Fan's guide to <a href="https://www.bit.fan/en/academy/category-3/how-to-spend-bitcoin-keyName-kw-prod-0003">spending Bitcoin and keeping payment records</a> places these checks before authorization. This is the useful moment to catch a mismatch, because a completed cryptocurrency transfer cannot be treated like editing an unsent shopping-cart entry.</p><h2>Identify the asset, route, and amount unit</h2><p>BTC on the Bitcoin network and a different asset with a similar name are not interchangeable. Likewise, an on-chain address and another supported payment mechanism may require different wallet capabilities. Follow the invoice's stated route rather than selecting whatever transfer option happens to be cheapest in the sending application.</p><p>Pay attention to units. A request for 0.0005 BTC is equivalent to 50,000 satoshis. Misreading a satoshi amount as whole BTC would be an enormous error, while rounding a small BTC amount to two decimal places could erase the payment amount from view.</p><p>An exchange withdrawal may also involve processing time or a minimum that does not fit the invoice. If the sending service cannot satisfy the requested amount and timing, resolve that before submitting a withdrawal. The merchant's timer will not necessarily pause while another provider processes the request.</p><h2>Leave enough balance for the sending fee</h2><p>The merchant needs the requested payment amount, while the wallet may also require a network fee. Suppose a hypothetical invoice asks for 50,000 satoshis and the wallet estimates an additional 3,000-satoshi fee. The sender would need 53,000 satoshis under that fee arrangement.</p><p>If an option instead subtracts the fee from the recipient's amount, the merchant might receive only 47,000 satoshis and treat the invoice as underpaid. Inspect the recipient amount and total wallet debit separately. Do not assume every interface handles fees identically.</p><p>The fee estimate can also change with network conditions and transaction size. A static example cannot establish today's appropriate fee. Use the wallet's current information and the invoice's requirements, recognizing that an estimate is not a guarantee of confirmation at a precise time.</p><h2>Treat expiration as part of the quote</h2><p>Some processors lock an exchange rate only for a defined payment window. As checked on September 8, 2026, BitPay's <a href="https://developer.bitpay.com/reference/invoices">invoice documentation</a> describes time-sensitive requests with a 15-minute expiration. That is a BitPay convention, not a universal Bitcoin rule or a guarantee that every merchant uses the same window.</p><p>If the invoice expires before payment is sent, obtain the merchant's current payment request. Do not reuse the old address and amount on the assumption that the original price remains valid. A new invoice may reflect a different exchange rate or order state.</p><p>If payment was already sent, check its status before paying again. The correct next action depends on whether the original payment was accepted, delayed, underpaid, or treated separately. A second payment can create an additional problem if the first one later completes.</p><h2>Reconcile the payment with the merchant's records</h2><p>Retain the order identifier, invoice information, transaction identifier, amount, and relevant timestamps. These let the merchant or processor investigate the actual payment rather than rely on a screenshot of a wallet balance. A public transaction record can establish a transfer, while the order identifier connects it with the intended purchase.</p><p>BitPay's <a href="https://support.bitpay.com/hc/en-us/articles/115003001363-What-if-I-sent-a-payment-to-an-expired-BitPay-invoice">expired-invoice support guidance</a> asks for transaction and invoice details when investigating a late payment. Other merchants may follow different procedures, so use the support route associated with the actual invoice.</p><p>Refund terms also deserve a look before paying. A merchant may request a refund destination through its verified process, and the refund's currency or amount can depend on the purchase terms. The spending process is complete when the seller recognizes the order's payment and you retain enough information to resolve any later question about it.</p>