Eligibility requires an approved rule set
The final policy must define the circumstances in which a customer may request cancellation or a refund, including how payment confirmation, activation, delivery, technical compatibility, service use, and applicable law affect the review.
This draft intentionally does not invent a cooling-off period, money-back guarantee, or non-refundable category.
A privacy-safe request process
The approved workflow must use a verified support or secure order route, collect only the order reference and information needed to understand the request, and prevent one customer from accessing another customer’s order.
Customers should not publish banking information or send passwords, card data, or unrelated documents. Staff decisions must be recorded in the order history.
Manual, evidence-based decisions
A refund request is separate from payment-proof review. Authorized staff must compare the approved policy version, payment state, activation state, delivery facts, customer report, and any lawful exceptions before recording a decision.
No page should imply that a request has been accepted until the administrator records the outcome and the customer receives a verified notice.
Timing and return method remain unconfirmed
The final policy must describe realistic review and return timing, supported currencies, bank-transfer constraints, fees, and the method used to return eligible funds. Those values depend on the owner’s bank process and jurisdiction.
Until they are confirmed, the site must avoid countdowns, urgency, or a fixed refund-time promise.