Optional cookies require your permission.Privacy & cookies

A customer paid after the Bitcoin invoice expired. What happens next?

A checkout timer can expire before a payment appears. Match the transfer to the invoice before deciding whether to credit, return, or reprice the order.

Adam Juchniewicz, CEO, Bitcoin Lawyer9 min read
Sources cited in this essay (3)
An illuminated Bitcoin symbol hangs above the espresso counter at Bitcoin Coffee in Prague.
In this essay6 sections
  1. Preserve the offer the customer actually saw.
  2. Establish what actually reached the intended invoice.
  3. Compare the permissible outcomes before selecting one.
  4. Tell the customer what is known and what happens next.
  5. Close the exception in the order and in the records.
  6. The Bitcoin Lawyer take

Preserve the offer the customer actually saw.

The checkout timer reaches zero. A few minutes later, the customer reports that the Bitcoin has been sent. Meanwhile the price has moved. Support now faces a commercial decision wrapped in a technical status. The first useful action is to preserve the original order and quote, not issue another invoice immediately.

Consider a hypothetical $1,000 consulting order. The checkout quoted 0.01 BTC at an illustrative $100,000 per BTC and displayed an expiry time. The customer initiated payment after that expiry. A later illustrative rate is $125,000 per BTC. These invented figures make the arithmetic visible; they are not current market prices or a recommendation about the outcome.

Save the order terms, quote, asset, network, expiry, and customer-facing instructions as they were shown. Record the relevant time zone and whether the customer’s stated time concerns clicking withdraw, transaction broadcast, or another event. Those events may differ. A support decision based on an imprecise sentence such as paid at noon can miss the material timing.

Identify what the price represented. Was the service priced in dollars with a temporary Bitcoin payment quote, or was the commercial price itself expressed in Bitcoin? What did the accepted terms say about expiry, late payments, and refunds? The relevant contract and consumer rules need review for the merchant and customer. The invoice status does not supply a universal legal answer.

Keep any new quote separate from the old one. A fresh rate might imply a different Bitcoin amount, but it does not erase funds already sent or amend the earlier agreement automatically. Record a proposed adjustment as a proposal until it is properly authorized and communicated. Do not silently substitute a new calculation into the historical invoice.

This evidence pack should be available to the person authorized to decide the exception. Front-line staff can collect facts and explain the review. They should not have to invent a refund policy or choose which price movement the merchant will honor while the customer waits in a chat window.

Establish what actually reached the intended invoice.

Ask for the order reference and relevant transaction identifier through the normal support channel. If the customer used a service that reports withdrawal status, distinguish that report from the actual payment evidence. Do not request passwords, recovery phrases, or a complete account history when a limited transaction record will answer the question.

Compare the asset, network, destination, amount, and timing with the original invoice. Check the merchant’s own authorized records and the provider’s authoritative invoice information. A payment to a different invoice or destination is a different investigation. A screenshot can help locate a transaction, but it is not the final basis for treating the order as settled.

BTCPay’s current invoice guidance distinguishes expiry from payment exceptions, including a payment arriving late. The actual deployed version and settings still need checking. Do not assume that a label on one installation has exactly the same operational effect on another, or that a manual change proves the underlying payment met the required conditions.

Keep observation and settlement separate. The merchant may detect a transaction before its configured conditions for release are satisfied. Staff should state what is known and what remains pending. The fact that the quote expired does not justify skipping the normal verification process, and the fact that a payment was broadcast does not establish completed fulfillment.

Check for partial or multiple payments. The customer might have sent the quoted amount less a withdrawal fee, sent twice after receiving conflicting instructions, or split the amount across transactions. Preserve each payment reference and quantity. The commercial decision should be based on the total relevant evidence, without counting unrelated receipts or losing a second payment in a summary total.

If the provider is unavailable, keep the order under review and preserve the evidence already obtained. An unavailable status check is not proof that no payment exists. Asking the customer to start again in that situation can turn one uncertain order into two. The responsible operator should investigate through the approved recovery process.

Compare the permissible outcomes before selecting one.

The merchant may be able to accept the late payment and fulfill the original order, seek an agreed adjustment, or proceed with an appropriate refund or other resolution. Which options are available depends on the terms, applicable law, actual payment, and business circumstances. This article offers a decision framework, not a universal right to choose whichever outcome is most profitable.

Using the hypothetical figures, the original 0.01 BTC has a value of $1,250 at the later illustrative rate. A fresh $1,000 quote at that rate would request 0.008 BTC. Those calculations describe different bases. They do not establish that the customer is owed 0.002 BTC, that the merchant can retain the difference or that the original commercial price has changed.

If accepting the payment, record the authorized basis and any remaining delivery conditions. Ensure the order will be released only once and that the accountant receives the relevant values and timing. A support note saying accepted should identify who decided, what they reviewed and which order the decision concerns.

If discussing an adjustment, state the calculation and proposed terms clearly. Preserve the original payment as part of the same case. Do not request another transfer until the relevant review has determined what is due and how it will be linked. A new invoice should not accidentally make the customer appear to owe the full original price again.

If a refund is the approved outcome, use the normal recipient-confirmation and authorization process. The amount and basis should follow the reviewed obligation and policy. A refund link or approved request is not a completed outgoing payment. Track the later transaction and its completion separately, then connect it to the original order.

Account for service availability too. The original appointment or limited-capacity product may no longer be available by the time the late payment is resolved. That commercial fact belongs in the decision and customer communication. It should not be concealed by marking an invoice settled and allowing the customer to discover the delivery problem afterward.

Late-payment decision table: outcome requires case-specific review
Observed positionNext checkPossible authorized pathEvidence to retain
Full late payment locatedTerms, settlement, and service availabilityAccept and fulfill where appropriateDecision and single release record
Amount differs from reviewed obligationActual receipts and permitted adjustmentAgree and link any adjustmentCalculation and customer communication
Refund approvedAmount basis and recipient processCreate, approve, and complete payoutSeparate refund completion evidence
Payment evidence unavailableProvider and transaction investigationKeep review openKnown facts and next owner
Payment linked to another invoiceIdentity and order mappingResolve allocation before releaseBoth original records and correction trail

Tell the customer what is known and what happens next.

The first reply should acknowledge the order and the review without claiming a result. For example: We have your payment report for order A104. The original quote expired before the reported payment time. We are checking the transaction against the invoice and will update you through this support case. Please do not send another payment while we complete that check.

Use that wording only when those facts are established. If the team has independently detected the payment, say so and identify whether confirmation remains pending. If the payment cannot yet be located, say that the team is checking the supplied reference. The message should follow the evidence, rather than using detected as a comforting synonym for reported.

After an authorized acceptance, a reply might say: We have verified the payment and accepted it for order A104. Your order is now ready for the next delivery step shown in your account. If that step is scheduling, avoid saying the appointment is booked until the scheduling system confirms it. Payment and booking remain different milestones.

For an approved refund path, a reply might say: We have approved a refund for order A104 on the basis described below. Please use the secure claim process to provide the required receiving information. We will confirm the outgoing payment separately once it has been processed. Include the actual approved amount and basis; do not leave the customer to infer them from a link.

Set an update expectation supported by the real operating arrangement. If the business promises a particular response window, staff need a way to meet it or explain a delay. Do not invent an immediate settlement or recovery time, and do not describe BitSettle as offering continuous support unless that service has actually been agreed for this merchant.

Keep the conversation attached to one case. Multiple channels can produce conflicting instructions, especially when one person sees the expired invoice and another sees a wallet receipt. Assign a case owner and ensure the next shift can see the facts, decision authority, and last customer message without reconstructing the incident from personal inboxes.

Close the exception in the order and in the records.

The case is not complete when the support conversation becomes quiet. Update the order according to the authorized decision, preserve its history, and verify any delivery or refund action. The payment record should remain linked to the original invoice even if a later adjustment or replacement document is required.

Give the accountant the original commercial amount, quoted Bitcoin quantity, actual payments, relevant dates, rate evidence, fees, and final decision. The professional should determine the applicable accounting and tax treatment. A price movement in the illustrative example does not establish the merchant’s tax result or the correct entry for another jurisdiction.

Reconcile any additional payment separately. Identify why it was requested, what the customer agreed to, and how it satisfies the remaining obligation. Check that automation cannot release the service twice because two invoices or payment records exist. A human exception decision should still pass through the merchant’s controlled order process.

For a refund, preserve the approved amount, receiving instructions confirmation, authorization, transaction reference, and completion evidence. Do not close the case merely because a refund was created in software. If the customer has not claimed it or the payout remains pending, retain that status and the person responsible for the next step.

Review why the late payment occurred. The checkout wording may be unclear, a customer’s exchange may introduce delay, or support may have given incomplete instructions. Improvements should address the observed cause without promising that all late payments can be prevented. Keep the published policy aligned with the actual process and applicable obligations.

A resolved case should let another person explain the original offer, actual payment, authorized outcome, and completed actions. That evidence is more useful than forcing the invoice into a preferred status. The merchant can then improve the workflow while preserving a reliable account of how this customer’s order was handled.

The whole picture

The Bitcoin Lawyer take

Establish the amount received and the time and terms of the quote. Then compare the outcomes the sale terms and merchant policy actually permit.

Give the customer one clear answer and reconcile it to the order. If a refund follows, authorize and record it as a separate outgoing payment.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “A customer paid after the Bitcoin invoice expired. What happens next?” https://www.bitcoinlawyer.com/journal/the-customer-paid-after-the-bitcoin-quote-expired-now-what