Written by DROPS.ST.
Before offering customer wallet payments, define what the shop balance represents, where each entry came from and which actions the customer and staff are permitted to take. A displayed total alone cannot explain whether value is eligible for a particular order, subject to a promotion's terms or awaiting review.
DROPS gives the review a practical account and order foundation. Customer-linked order items identify the purchase, configured BTC/XMR checkout provides payment context, and the website and connected Telegram shop share the order system. Its account and credit-related scope makes balance ownership and permissions relevant to the operating review.
Exact allocation, refund, cash-out and expiry behaviour needs a separate demonstration and approved terms; account context does not establish those financial rules.
Explain which wallet the shop means
A shop-account balance and a customer's external cryptocurrency wallet are different records. The external wallet is involved in the customer's payment activity; the shop balance needs its own unit, source and permitted-use explanation.
Avoid showing an unexplained number under “wallet.” Identify its unit and the terms relevant to the actual arrangement. Do not imply that displayed shop value is a cryptocurrency holding, a cash balance or redeemable money unless the evidence and governing terms establish that meaning.
If the proposed arrangement has several origins of value, keep them distinguishable in the review. Purchased value, promotional value and an approved correction may need different treatment. These are policy questions, not a claim that every category exists natively in DROPS.
Keep a balance-policy worksheet
This original aid records what must be explained before the balance is presented as a usable checkout option.
| Policy question | Evidence to record | Customer explanation |
|---|---|---|
| Unit and meaning | Actual balance unit and governing terms | What the displayed value represents |
| Entry origin | Source reference and approved reason | Why the entry exists |
| Order eligibility | Demonstrated permitted use and restrictions | Which relevant use is available |
| Adjustment authority | Actual role and approved decision process | Who reviews a disputed entry |
| Reversal or return | Supported behaviour and applicable terms | What the buyer can request, without a refund promise |
| Expiry or cash-out | Explicit supported rule, if any | Avoid suggesting rights that have not been established |
| Records and questions | Relevant entry/order references and responsible owner | How to raise a specific issue |
Record unresolved rules honestly. Do not turn “not yet demonstrated” into “never expires,” “cash out anytime” or another convenient claim.
Check origins before combining totals
Keep an approved entry associated with its source reference. An internal note about a possible credit should not be mistaken for an applied balance adjustment.
Where different types of value are combined visually, demonstrate how the setup preserves any relevant restrictions. Do not assume that a single display means every entry has identical terms or can be used for every purpose.
For permission scope, use the staff access checklist. A person who can edit product information may have broader account or credit access than the business intended; review the actual role before assigning responsibility.
Hypothetical example: one total, different entry meanings
A fictional policy worksheet contains an entry of CAD 30 described as purchased shop value and another of CAD 10 described as promotional value. Its displayed example total is CAD 40.
The reviewer asks whether both entries are eligible for the intended order and whether their terms remain distinguishable. They do not assume the CAD 40 is withdrawable cash or that the promotional entry follows the purchased-value rules.
All figures are illustrative CAD amounts. The example does not describe current DROPS prices, a native credit classification or a customer's balance.
Separate policy from applying value at checkout
This worksheet defines the balance's meaning. The repeat-buyer checkout guide checks what happens when eligible value is applied to a particular order, including any remaining obligation.
Keep a balance adjustment, payment request and refund decision identifiable as separate actions. A customer asking to cancel an order does not itself establish the resulting account entry or return-of-funds process.
For disagreements, locate the relevant account, entry reference and order relationship through the approved record process. Assign the unresolved policy question instead of changing a figure merely to close the support conversation.
Make account value understandable with DROPS
Choose DROPS when customer and order context should sit behind the balance discussion, with configured crypto payment status tied to the shop order. Its connected channels give the team a common business reference for investigating the actual case.
Open the DROPS demos with a fictional policy sheet. Ask for the supported balance views, entry references and permission scope relevant to your setup. Demonstrate the rules before presenting the wallet option to buyers; explain usable value from its actual evidence rather than a total alone.