Getting started
Quick start
The seller workflow consists of creating a product, filling in information, submitting it for moderation, and publishing updates afterward.
Create a product
Enter a name, category, description, and price.
Add materials
Upload images, the main file, and additional links.
Submit for review
A moderator will review the content and listing accuracy.
Publish versions
After approval, add new releases and changelogs.
Recommendation
Before submitting, review the listing from a buyer’s perspective: make sure the product purpose, file delivery terms, requirements, compatibility, and payment format are clear.
Product publishing
The product listing is the main page where the buyer decides whether to purchase. The more complete the information, the fewer questions arise before checkout.
Required information
- Product name and short description.
- Detailed description of functionality and purpose.
- Category, product type, and payment model.
- Main file, image, and current version.
Additional appearance settings
- Add a gallery with interface screenshots.
- Provide an FAQ and answers to common questions.
- Add links to the website, Discord, or documentation.
- Describe limitations, dependencies, and requirements.
Please note
Do not include false promises, unavailable features, hidden terms, or materials you do not have distribution rights for.
Moderation
After submission, the product enters the review queue. Until approved, it is not shown in the public catalog and is unavailable to new buyers.
Awaiting review
The listing was sent to a moderator and temporarily hidden from the catalog.
Approved
The product is published and available to platform users.
Rejected
Fix the listed issues and resubmit the product.
Versions and updates
Each new version may contain a separate file, release number, changelog, compatibility information, and additional buyer instructions.
Version example
v2.4.0
StableWhat should be included
- • A brief summary of the main changes.
- • List of fixed issues.
- • New requirements or dependencies.
- • Instructions for updating from an older version.
- • Supported platform or game versions.
Version history is displayed on the product page. The buyer can view the publication date, changelog, and files available to them.
Licenses and access
After a successful purchase, access to the product is linked to the user’s account. Purchased materials appear in the library and remain available under the seller’s terms.
What the buyer receives
- Access to the product in the personal library.
- Ability to download available files.
- Access to versions allowed by the payment model.
Seller liability
- Keep uploaded files functional.
- Clearly describe the usage rules.
- Respond to buyer questions and requests.
Product analytics
The product owner can track sales, views, and buyer activity. These data help evaluate listing, update, and advertising performance.
Views
Product page interest
Sales
Number of completed purchases
Revenue
Seller earnings amount
Reviews
Ratings and feedback
For developers
Developer Dashboard
The @@PROTECTED_1@@ section is intended for managing applications, access keys, callback addresses, and future API integrations with the platform.
Applications
Create a separate application for each website, dashboard, Discord bot, or other external service.
Access keys
The key identifies your application when calling permitted platform endpoints.
Callback URL
The callback address is used to return the user or pass the authorization result to an external application.
Events and webhooks
In the future, applications will be able to receive events about orders, licenses, updates, and other platform actions.
Never publish secret keys
Store keys only on the server. Do not put them in public JavaScript, GitHub repositories, screenshots, or support messages.
Security
Use a unique password, two-factor authentication, and regularly review active devices to protect your account and products.
Protect your account
Use a strong password and enable additional sign-in verification.
Restrict keys
Grant applications only the permissions they actually need.
Keep access up to date
If you notice suspicious activity, revoke the key and create a new one.
Need help?
Didn't find the information you need?
Check the profile sections and product page, or contact administration through the available channels. Include a description of the issue, a page link, and screenshots if they help explain the situation.