Written by DROPS.ST.
Before telling a cannabis wholesale buyer to use a different payment route, verify the change owner, identify the affected orders and preserve the agreed treatment of existing payments. A convincing message does not establish authority to replace earlier instructions.
DROPS gives the review identifiable shop context: customer-linked order items, product units and wholesale packages, plus order references and payment status for configured Bitcoin and Monero checkout. That foundation helps your team explain which business transaction the notice concerns.
This guide uses a US cannabis-business context. The operator’s activity, proposed payment route and provider scope still need applicable review and approval; the worksheet does not authorize a new payment service.
Verify the request before drafting the notice
Establish who requested the change and who can approve it. Check the request through a trusted contact route established independently of the new message, especially when it supplies a new account, address or urgent deadline.
The FBI advises verifying changes in account numbers or payment procedures and independently looking up a company's contact number instead of using one supplied by a suspicious message. This is a verification precaution, not a guarantee that fraud cannot occur. FBI business-email-compromise guidance.
Keep preparation, approval and execution separate. Someone able to write the customer update does not automatically have permission to change financial settings.
Identify exactly which commitments change
Start with the affected order or approved commercial reference. Record whether the buyer has already paid, received earlier instructions or only requested a quotation.
A future payment-route change must not silently become a demand to pay an already settled order again. An unresolved payment needs its own evidence review before staff issue replacement instructions.
Use the payment reconciliation guide to distinguish the shop order, payment request and evidence of receipt. Similar amounts or matching names cannot establish that relationship.
Keep a payment-change notice record
This original aid belongs in the business's approved working process. It is not a native DROPS bank-change workflow or automatic notification tool.
| Record entry | Evidence to establish | Notice decision |
|---|---|---|
| Change authority | Request owner and independently checked approval | Hold an unverified request |
| Affected references | Orders, agreed invoices or quote revisions | State the exact scope |
| Earlier instructions | Version and actual payment state | Preserve unresolved or completed treatment |
| Proposed route | Approved method and applicable provider scope | Avoid unapproved alternatives |
| Effective condition | Verified date or event and responsible owner | Explain when the change applies |
| Buyer verification | Trusted contact and approved confirmation route | Make independent checking possible |
| Released version | Final wording, recipient and checked delivery | Retain accountable evidence |
Keep credentials and wallet secrets out of the notice record. Share only the information necessary for the authorized buyer to understand and verify the change.
Make the customer message precise
State the relevant reference, what changes, when it applies and which earlier instruction it replaces. Explain where the buyer can independently verify the request through the business's established process.
Describe any agreed alternative accurately. Its availability, eligibility and terms need their own approval; a listed payment option does not prove that every product or transaction is accepted.
Avoid combining a payment correction with a promotional offer. Review the actual message purpose and permitted channel separately from the financial decision. A buyer relationship does not establish unrestricted permission to send every kind of communication.
Hypothetical example: one order is already paid
A fictional wholesaler approves a payment-method change for future unpaid commitments. Staff find one completed payment and one unresolved request among the affected references.
They leave the completed payment's treatment intact and assign the unresolved request to its authorized reviewer. The notice identifies the approved future scope instead of instructing both buyers to pay again.
The example demonstrates a scope decision. It establishes no actual account change, provider approval, refund or native automatic exclusion.
Check the released instructions
Inspect the actual notice and affected shop instructions after the authorized change. Identify stale independent copies and give their correction to a responsible owner. A shared catalogue does not update every email attachment or earlier conversation.
Use the staff permissions guide when reviewing the full financial and customer-account powers behind the change.
Choose DROPS when wholesale selections and customer-linked orders should provide clear references for payment conversations. Explore the shop demos with a fictional changed-route notice, then demonstrate its order scope, decision owner and independent verification path before relying on the proposed arrangement.