Written by DROPS.ST.
A cannabis-business website should separate the order total, any independently applicable service charge and an external wallet's network-fee estimate. Use a clearly hypothetical example to explain the relationship, while keeping the actual payment request and its current amount basis identifiable.
DROPS gives the explanation concrete shop context through product units, customer-linked order items and configured BTC/XMR order references and payment status. The website and connected Telegram shop share the catalogue and order system.
This US business-planning example establishes no current fee, exchange rate, provider eligibility or native DROPS fee display, allocation or conversion rule; those need actual evidence and review.
Separate the amounts before adding them
Start with the recorded order total and state what it includes. An example should not silently omit required charges or add a charge already included in the total.
Identify who assesses each additional charge, which event it relates to and whether it is already part of the requested payment. A fee described by a customer's external wallet may concern a different event from a shop service charge.
Bitcoin.org explains that transaction fees vary with network demand and transaction size, rather than simply tracking the amount of bitcoin sent. That supports avoiding a fixed network-fee promise or an invented percentage of the cart. Bitcoin.org: transaction fees.
Do not apply Bitcoin's explanation as a universal rule for every asset or provider. Inspect the actual supported method and evidence.
Keep a fee-example preparation sheet
This original aid gives the author a basis for a reviewable nontransactional illustration.
| Example element | Evidence or assumption to state | Check before publishing |
|---|---|---|
| Order total | Unit, included charges and pricing basis | No required component silently omitted |
| Separate service charge | Assessor, event and actual approved rule | Not already included or invented |
| Payment request | Relevant asset and current amount basis | Not confused with an earlier quote |
| External network estimate | Source and observation basis | Clearly variable and outside any guarantee |
| Currency comparison | Stated common illustrative basis | No unsupported live conversion implied |
| Version and review | Source dates and responsible approver | Wording matches the actual arrangement |
If the amounts are not on comparable bases, explain them separately instead of producing a misleading grand total. Keep the source or assumption visible beside each figure.
Hypothetical example: one stated USD-equivalent basis
An entirely fictional illustration uses these USD-equivalent planning figures, all on the same explicitly assumed valuation basis:
| Component | Hypothetical figure | Meaning in this example |
|---|---|---|
| Order total | USD 100.00 | Complete assumed order-total basis |
| Separate approved service charge | USD 2.00 | Assumed to be additional, not included above |
| Payment-request subtotal | USD 102.00 | 100.00 + 2.00 under those assumptions |
| External network estimate | USD 1.50 equivalent | Assumed separate wallet-side amount |
| Illustrative combined outlay | USD 103.50 equivalent | 102.00 + 1.50 on the common example basis |
These are not live quotes, actual charges, exchange rates or amounts payable through DROPS. A real crypto payment is denominated in its actual asset; the illustration does not claim the wallet debits US dollars or that the platform performs this calculation.
If the separate service charge were already included in the order total, adding it again would be wrong. If the network estimate changes, the illustrative combined outlay would also change under the stated assumptions.
Review the buyer's likely interpretation
Ask whether a reader can distinguish an example from the actual current payment request. Keep the example label and assumptions close to the numbers, including on a phone.
Do not use “zero fees” merely because one component is absent. Do not promise that a different wallet, provider or payment time will produce the illustrated amount.
Keep any refund, reversal or dispute terms separate from fee arithmetic. An explanation of what a charge means does not establish that it is refundable or that the shop can reverse a network transaction.
Match support questions to the right record
For an actual difference, locate the order, request and relevant charge evidence. Use payment reconciliation to preserve amount bases and fee records.
A short receipt, excess amount or closed request needs the payment exception review. Do not instruct another payment from an old example or adjust a record to make its total look familiar.
For this US planning scope, keep the actual federal, state, local and provider requirements under appropriate review. The hypothetical example supplies no permission for the underlying activity.
Give fee explanations identifiable order context with DROPS
Choose DROPS when the buyer's payment question should connect to the selected items, order reference and configured payment state. Its common web and Telegram shop foundation gives the explanation a concrete business record.
Open the DROPS demos with the fictional fee sheet. Inspect the supported amount and status presentation, then request evidence for the actual charge and valuation rules your setup uses. Publish a clear illustration without turning it into a promised price.