1. When a request can be made
A refund request may be made if payment was confirmed but the promised tier was not provided, or if an incorrect charge occurred.
Specific conditions may be refined depending on the chosen tier and the launch model.
This page collects the general principles for refund handling after the paid part of FSON launches.
A refund request may be made if payment was confirmed but the promised tier was not provided, or if an incorrect charge occurred.
Specific conditions may be refined depending on the chosen tier and the launch model.
The request period will be published together with the launch of the paid part.
Before payment goes live, this page remains informational.
A request is submitted through the published payment contact channel.
The review may require the checkout time, chosen tier, and a short description of the situation.
Each request is reviewed separately according to the actual checkout result.
If a refund is approved, the following steps and timing are communicated separately.
The same backend session is used by the site, launcher, and OAuth sign-in.
Or continue with
Google and Discord can be linked to this same local account.
Free
₽250 / month
₽500 / month
₽1000 / month
For now, you can review what the tier includes and return to the list. Real checkout will open later.
The site is already prepared for this path. For now, you can browse the project, download the launcher, and choose a support tier.
The button is already in its final place. Once the file is published, the download path will open without rebuilding the site.
The page already shows the tiers and what they include. Real payment will be added later without breaking the user path.
Once checkout goes live, this is where a calm waiting state will appear without feeling broken.
After payment goes live, this is where the clean success state will appear.
If something goes wrong, this is where the honest non-empty fallback state will appear.