Cancellations and access
Refund policy
How the current Demo purchase records cancellation, revokes access, and preserves order history.
The current course checkout uses a Demo gateway and does not charge a payment card or contact Stripe. Its refund action records a server-authoritative change against a confirmed paid Demo order, revokes the related entitlement, delivers a signed revocation event to Academy, and preserves the original order and access history.
Only an authorised superuser can perform that action. Repeating the same operation does not create a second revocation or duplicate delivery record.
For a live course purchase, the applicable cancellation window, eligibility, processing time, fees, partial-refund rules, access consequences, and contact route must be presented with the course and checkout terms before payment.
What the Demo refund records
Validate the order
The action requires a confirmed paid Demo order and an authorised administrator.
Revoke the entitlement
Access changes state without deleting the order, payment, entitlement, or activation history.
Deliver the event
A versioned signed record is retried safely until Academy confirms the same idempotent result.
Refund boundaries
Does the Demo action contact Stripe?
No. It records application state only and must not be represented as a provider refund.
Can the same order be revoked twice?
No. State-transition and idempotency checks prevent duplicate revocations and events.