Written by DROPS.ST.
A licensed cannabis business needs a payment-continuity plan that distinguishes new payment requests from obligations already paid or still under review. An unavailable account or service can affect the next checkout without deciding what happens to earlier orders.
DROPS provides a useful shop-side foundation: customer-linked order items identify the purchase, while configured BTC/XMR checkout carries an order reference and current payment status. The website and connected Telegram shop share the catalogue and order system, giving the team common transaction context during a disruption.
The plan is an external responsibility and dependency record, not native automatic failover, an approved alternative payment service or a guarantee of recovery.
Identify the dependency and affected activity
Record which service, account or operational dependency is unavailable and the evidence for that conclusion. Distinguish a provider notice, a technical observation and a customer report. Each can lead to a different next check.
Write down whether the issue affects new requests, existing receipts, conversion, account access or the ability to complete a particular order task. “Payments are down” is too broad to guide the team.
Keep the actual product, market, channel and provider scope beside the dependency. An alternative that works technically is not automatically approved for the business's authorised activity.
Use an obligation-and-owner sheet
This original continuity aid records work that must remain accountable while the interruption is investigated.
| Activity or obligation | Evidence to preserve | Responsible next decision |
|---|---|---|
| New payment request | Intended route and current availability | Decide whether the supported path remains available |
| Reported but unresolved payment | Order/request references and checked state | Assign the payment reviewer; avoid duplicate instructions |
| Accepted payment | Actual accepted result and linked order | Preserve its treatment and remaining fulfilment work |
| Merchant receipt or conversion | Separate evidence and external dependency | Finance owner checks availability and unresolved conditions |
| Existing customer question | Relevant reference and previous response | Case owner gives a factual update |
| Proposed alternative | Applicable provider/product/market approval | Hold until the actual arrangement is established |
| Restoration | Current service evidence and outstanding cases | Review reopening separately from incident closure |
These are business review categories, not native DROPS states or controls. Keep an owner and next review point for every unresolved row.
Preserve earlier instructions and outcomes
Locate orders that already have payment requests or accepted results. Do not treat disabling a new-payment option as proof that those obligations disappeared.
Before issuing replacement instructions, reconcile the relevant record. Use the payment reconciliation guide for order/request/receipt relationships and the exception guide for closed or amount-discrepancy cases.
An already accepted payment must not quietly become another demand to pay. If its fulfilment or financial treatment is disputed, identify that exact question and the authorised reviewer.
Hypothetical example: new requests pause, old work remains
A fictional licensed business receives a verified notice affecting one payment arrangement. The reviewer identifies three cases: a proposed new request, an accepted payment with fulfilment outstanding and an unresolved earlier request.
The new request is held under the approved process. The accepted payment's treatment remains identifiable, with fulfilment still assigned. The unresolved request goes to its payment reviewer before any further instructions are given.
No alternative is advertised until its actual scope is approved. The incident sheet preserves all three cases instead of reducing them to one “disabled” label.
This example demonstrates continuity ownership, not a native pause switch, failover service, refund or live account change.
Give the team a factual communication basis
Record the checked limitation, affected scope and next responsible person. Avoid a restoration time unless it has a supported basis, and distinguish a provider estimate from the business's own commitment.
If payment procedures are changing, independently verify the authority and route. FBI guidance recommends verifying changes to account numbers or payment procedures and independently locating a company's contact details. FBI: business email compromise.
Communicate through the permitted process with only the information necessary for the affected case. A disruption does not create unrestricted permission to message every contact or expose financial records.
Reopen from evidence, not reassurance
Check the actual restored arrangement and any changed conditions before revising the continuity decision. Keep source inspection, a non-funded demonstration and live payment acceptance distinct.
Review earlier cases separately. Restored service does not automatically reconcile an old receipt, resolve a disputed amount or update an independent instruction sheet.
Use the staff permissions checklist to review the supported access behind each task. Financial and provider authority remain separate from ordinary shop access.
Keep payment interruptions accountable with DROPS
Choose DROPS when the continuity discussion needs identifiable products, customer-linked orders and configured payment status. Its shared web and Telegram shop context gives the team concrete records to preserve while external dependencies are reviewed.
Explore the DROPS demos with the three fictional cases. Inspect their shop-side references, then complete the external owner and dependency sheet without invoking a provider or moving funds. Select the arrangement whose outstanding obligations remain explainable during the interruption.