Written by DROPS.ST.
When a cannabis shop receives a crypto payment exception, check the order's payment record before changing fulfilment or asking the buyer to pay again. Separate a short payment, an excess amount and an expired request: each needs a different decision.
DROPS connects configured Bitcoin and Monero checkout with the shop order. Buyers get an order reference and payment status; staff can start from that context instead of treating a payment screenshot as a completed sale. Explore DROPS shop features.
Start with the order and the observed state
Find the original order reference, chosen asset, payment request and current shop status. Record when you checked them. A buyer's message may describe what they sent, while the shop is still checking what it received.
For Bitcoin, notification of a transaction and network confirmation are separate events. Confirmation timing varies; it does not support a fixed fulfilment promise. Bitcoin confirmation explanation.
Also separate payment status from the order's fulfilment status. Sufficient payment does not establish stock availability, buyer eligibility or permission to deliver. Your approved operating process determines the next step.
Use a short exception register
Keep this owner-managed register with the case. It is a practical worksheet, not a promise that DROPS supplies every column as a native report.
| Field | Record |
|---|---|
| Order reference | Original order being reviewed |
| Payment request | Asset, requested amount and relevant request reference |
| Observed result | Current status, credited amount and its currency/asset basis, check time |
| Difference | Shortfall, excess, expired request or conflicting evidence |
| Decision owner | Person authorized to resolve that exception |
| Buyer update | What was communicated and the next update point |
| Closure evidence | Final decision and supporting shop/payment record |
Use only the information needed to resolve the case. Never request a buyer's seed phrase, private key or wallet password.
Separate evidence gathering, the resolution decision and its execution. Name the authorized person for each; one duty does not grant the other powers. Restrict case records to authorized reviewers. For an accountant's exception summary, preserve the case type, relevant references, unresolved question and next action owner; share only the necessary evidence through the approved process.
Underpaid: establish the remaining amount first
When the current payment record shows an unresolved shortfall, do not override it as paid. Use its current amount basis and approved policy rather than calculating another payment from an old quote. Confirm whether the request remains usable under the actual checkout process.
The SHKeeper integration documentation distinguishes invoice balances, transactions and payment status. These are related pieces of evidence, rather than interchangeable labels. SHKeeper invoice documentation.
Before giving further instructions, establish the supported next step and who may authorize it. Avoid improvising a second address or copying an amount from an old conversation. Recheck the order before taking action if the status changes while the case is open.
Overpaid: review the excess separately
An excess payment creates a decision about the excess; it does not automatically authorize another purchase or a refund.
Have the authorized owner verify the credited amount, original request and applicable shop policy. Record the decision and its basis. Confirm the supported adjustment or refund process before promising a particular route, value or completion time.
Do not describe an overpayment notice as proof that a refund has already been sent. Keep the buyer update consistent with the recorded decision.
Expired: distinguish the request from any payment already sent
If the payment page says the request is expired, the buyer should stop using those instructions. When nothing was sent, follow the current checkout's supported next step.
When the buyer reports sending before or around expiry, inspect the original record before creating another request. A closed payment window does not establish where a reported transfer ended up, and a fresh order does not resolve the old case.
Keep the original and any replacement references connected in the case notes. Escalate missing or conflicting evidence to the named payment owner.
Hypothetical example: expiry and a buyer message
A buyer says they sent payment shortly before the timer ended. The shop now shows an expired request.
Staff record the original reference and current status, pause the fulfilment decision and hand the case to the payment owner. They explain that the original payment is being checked before giving further payment instructions. The owner closes the case only after the evidence and supported next step agree.
Bring the exception path into your shop evaluation
DROPS is a strong fit for owners who want crypto checkout tied to products, orders and a clear customer journey. Its configured payment panel presents the order reference and status, including detected-payment and expired-request guidance. That gives your team a useful starting point for support.
Use the payment-flow comparison to define receipt and fund-control responsibilities. Rehearse the handoff with the order exception training guide.
See DROPS and explore the demos. Bring one fictional short-payment case and one expiry case to your setup discussion. Confirm what the buyer sees, who reviews exceptions and how an agreed resolution reaches the order record.