Written by DROPS.ST.
A Bitcoin payment can be detected before it is sufficiently confirmed for the shop's payment process. Give the buyer a current status and an order reference, while staff keep the payment decision separate from the decision to prepare or dispatch the order.
For a cannabis shop offering configured BTC checkout, DROPS brings that information into the shopping journey. Its payment panel connects the order reference, requested amount and current payment status, so the next support conversation can begin with the order. Explore DROPS features.
What does a confirmation mean?
Bitcoin transactions receive their first confirmation when included in a block. The observed confirmation count can grow as further blocks are added. Seeing a transaction announced is an earlier event; it does not establish that the required confirmation condition has been met.
The time varies with network conditions and the transaction. Bitcoin.org describes block discovery as probabilistic, so an average cannot become a guaranteed completion time for one customer's order. Bitcoin confirmation explanation.
Use the payment process configured for your shop. Establish who owns that configuration and how staff recognize a completed payment. Do not improvise a different threshold for a buyer who is in a hurry.
Explain the stages a buyer actually sees
Use this worksheet to review the configured checkout, rather than inventing status labels the shop does not display.
| Observed stage | Buyer needs to understand | Staff checkpoint |
|---|---|---|
| Preparing details | Wait for usable payment instructions | Correct order and asset |
| Waiting for payment | Follow the current payment request | Amount and request remain current |
| Detected or confirming | Payment is being checked; do not send again merely because it is waiting | Current recorded payment state |
| Complete | The payment process has reached its completion state | Order's next operating step |
| Expired or unresolved | Stop using closed instructions and follow the supported help path | Original request and any reported transfer |
DROPS' configured BTC payment panel includes order references, detected-payment guidance and an expired-request message. When confirmation progress is available, the panel can show the count against the configured requirement. Availability and exact behavior depend on your setup.
Keep payment completion and fulfilment distinct
An order can be paid and still require a stock, pickup or delivery decision. Your staff need to know who makes that decision and where its outcome is recorded.
Define the handoff in plain language: which payment state allows the team to start the next step, which other checks apply and who reviews an exception. Keep customer instructions consistent with that process.
For wider differences in payment receipt and control, use the payment-flow comparison.
Answer “I sent it—what happens next?”
Start with the order reference. Check the current shop status and the original request before replying. A buyer's screenshot is useful context, but it should not replace the shop's payment record.
Explain the observed state without promising an exact network time. If payment is detected and being checked, say that clearly. If the evidence conflicts, identify the review owner and when the buyer will receive another update.
Avoid asking the buyer to resend merely because confirmation is taking longer than expected. If they report sending around expiry, keep the original case open while the authorized owner investigates the supported next step.
Never ask for a wallet seed phrase, private key or password to investigate an order.
Hypothetical example: detected but still confirming
A buyer returns to their order page after sending BTC. The shop shows detected payment, but completion has not yet been recorded.
Staff check that order and explain the current state. They keep the agreed fulfilment handoff pending and avoid sending another payment request. Once the payment process records completion, the team follows the shop's next operating checks.
Evaluate the whole order journey
DROPS is a strong fit when you want Bitcoin checkout connected to products, the cart and the order the buyer can return to. Clear status, an order reference and a defined support handoff are practical parts of that value.
See DROPS and explore the demos. During setup, review a fictional payment journey on a phone: waiting, detected, completed and expired. Confirm both the buyer's wording and the staff decision at each step.
For XMR-specific context, see Monero payment confirmations. Practise staff handoffs with the order exception training guide.