Refund draft · not operative
Cancellation, access, and money movement are distinct.
A pre-launch outline of cancellation and refund mechanics. Eligibility, request channels, deadlines, and jurisdictional rights still require operator policy and professional review.
Refund draft · not operative
No refund eligibility window or response promise is invented here. Before launch, the operator must adopt a lawful policy, configure a monitored request channel, align payment-provider settings, and obtain professional review for every sales jurisdiction.
Cancellation is not a refund
Cancellation and refund are separate actions. Cancelling prevents renewal according to the current subscription state; issuing a partial or full refund does not by itself cancel a subscription or fabricate a new entitlement status.
Access follows the current subscription object and any disclosed grace or period-end rules, not an assumption based only on a charge event.
Eligibility remains an operator decision
The final policy must state who is eligible, what evidence is required, how usage affects eligibility if lawful, which purchases are excluded, and how statutory cooling-off or consumer rights override the general policy.
Taxes, exchange-rate effects, processing times, and payment-method behavior must reflect the configured payment provider and customer jurisdiction.
Request and settlement path
A refund request must use a monitored channel that can identify the account and payment without asking for full card details. The final page must publish that channel and a realistic review expectation.
Approved refunds are returned through the original payment rail where supported. Actual timing is controlled by the payment provider and financial institutions and must not be presented as guaranteed.