Guide Bitcoin basics

Before shipping: how to check a Bitcoin payment in BTCPay Server

A customer's message saying payment was sent is not enough to release an order. Match the order, payment request and detected funds, then check that the store's settlement conditions have been met. A short, recorded review also gives the next employee a clear account of what happened.

A small shop counter with blank receipts, checking points and a parcel against a light background
Illustration: payment checks before releasing a parcel, without customer data or a screenshot of a system.

This guide addresses a merchant's fulfillment decision, rather than server installation or wallet selection. In BTCPay Server, an invoice is a payment request and its tracking record. The name alone does not establish that a valid Israeli tax document has been issued. Keep the business's applicable accounting requirements separate from the technical payment status.

Start with the correct order

Open the store system through your saved address, rather than a link supplied by someone claiming to have paid. Find the order ID and its associated invoice. Check the selected store, amount, currency and payment method. A screenshot from the customer's wallet may help investigate a problem, but does not replace your own records.

According to BTCPay Server's documentation (Opens in a new tab), Processing means a full payment has been detected but settlement conditions are still pending. Settled means those conditions were met. Decide in advance which status permits fulfillment and who handles exceptions, instead of making a new decision under pressure from a waiting customer.

Do not turn an exception into automatic approval

An expired invoice can require investigation even if funds arrive later. Partial and excess payments require matching the requested amount with the amount received. Check the record before asking for another payment, so a coordination problem does not produce a duplicate charge.

The documentation also distinguishes an invoice manually marked as settled. That mark is not independent evidence of blockchain confirmation. If an employee changes the status, record who decided, the supporting information and what happened to the order. Changing the screen's label does not move funds.

Consider a hypothetical customer who pays for two similar orders while the store team opens the second invoice. Both sides see a plausible amount but are comparing different records. Matching order and invoice identifiers resolves the confusion more effectively than exchanging further screenshots.

Check confirmations without changing policy midstream

An on-chain Bitcoin payment may wait for confirmations under the store's configured policy. No single number suits every product and business risk. For background, see the explanation of Bitcoin fees and confirmations. Do not lower a confirmation threshold merely to clear a waiting order without understanding the changed risk.

If the system has not detected payment, give the technical operator the invoice ID, transaction ID if available, time and payment method. The customer's recovery phrase or private key is not needed. Before sharing a screenshot, hide unrelated orders and personal information unnecessary for the investigation.

Close the order as well as the payment

Once payment meets the policy, record who approved fulfillment and link that approval to the order. Check whether the product was already dispatched following an earlier notification. For automated systems, ask the developer how repeated events are prevented from triggering duplicate fulfillment. This is a requirement to review, not a claim that every plugin handles it correctly.

If a refund is needed, review the documented refund workflow separately from the business decision. Do not assume an address visible in the incoming transaction is an appropriate refund destination the customer controls. Record the reason and outcome, distinguishing a prepared refund from an executed one. The final record should identify what was paid, which order was closed and who authorized the action.

Correction and clarification

Found an error? Contact the editors

Share article Back to top