loader

Custom Developer Policy & Guidelines

Last updated December 15, 2025

This page explains what a Custom Developer can do in X‑Store, what is not allowed, how withdrawals work, how support and reports are handled, and how your account status is affected by ratings and verified reports.

Joining & Email Verification

Email verification is required to activate and keep your developer capabilities. Unverified accounts may be limited and cannot receive full privileges. Always verify your email promptly after registration and keep it up to date.

A valid email is required for all Custom Developer accounts. For security, when logging in from a new IP you will be asked to enter a one‑time verification code sent to your email.

Allowed Permissions

  • Publish, update, and manage your own products and services.
  • View sales, reports, and analytics for your own products.
  • Receive earnings from your products and request withdrawals via available methods.
  • Respond to support tickets related to your own products.

Product Upload & Review

Important: Developers must upload their original decoded files for security review before publication. This allows us to verify that your submission does not contain any backdoors or bad code that may harm customers’ chats.

We require decoded sources to integrate our Store Licenses API, which grants customers the permissions they need to license their addons for any domain they choose.

After review and API integration, we will encode your files with the latest ioncube encoder version 15 using dynamic keys to protect your work. You do not need to worry about the security of your files.

Reviews of uploaded products are usually completed on the same day or by the next day at maximum.

  • Upload original decoded files for a thorough security review.
  • No backdoors, harmful logic, or unsafe practices are allowed.
  • Decoded sources are used to integrate license checks and domain permissions.
  • Final deliverables are encoded with ioncube v15 using dynamic keys.
  • Your files will not be used for other products or projects.
  • We accept and process developer reports concerning misuse or issues related to their files.

If Store Owners find that a custom developer has integrated bad code, backdoors, or anything that harms customers’ chats, the Store Owners have full rights to suspend the developer’s account and freeze the wallet balance. The developer cannot request a withdrawal of any frozen balance.

By submitting a product, you acknowledge and agree to this process. Please read this section carefully.

Product Updates

This section explains how Custom Developers publish updates for their addons and how customers receive and install them, including how the update price works and how changelogs should be maintained.

For Custom Developers
  • To publish a new version, open Store Manager → Products → Edit Product, set the new Product Version (e.g. from 1.0 to 1.1 or 2.0), upload the updated package, and provide a clear Changelog describing fixes and features.
  • Minor updates (e.g. 1.0 → 1.1) are typically provided free to existing buyers. Major updates (e.g. 1.x → 2.0) may optionally require an update price if you define it in the product settings.
  • Upload original decoded sources for security review. After approval, final deliverables are encoded and released to customers with license checks intact. The store increments the product updates count and marks the product as Updated in public views.
  • Keep the Changelog consistent and accurate. Use concise bullet points that explain what changed, what was fixed, and any breaking changes or migration notes if applicable.
  • Security fixes must be released promptly. If the update solely addresses security, it should be offered without additional update fees to protect customers’ deployments.
Update Price (Developer)
  • You can set an update price for major versions to compensate significant new functionality or rewrites. This fee applies only to customers who already own the product and wish to upgrade to the new major version.
  • The store commission applies to update transactions. Customers see the update offer before paying and retain their existing license after upgrading.
  • Clearly communicate in the Changelog and product description when an update fee is required and what benefits the major update includes.
For Customers
  • When a product is updated, customers will see the Updated badge and can access the new package from the product page or their account area after license validation.
  • Minor updates are downloadable at no extra cost for existing buyers. Major updates may require paying the update price shown on the product page. After paying, the account is granted access to the new version.
  • Your existing license and domain permissions remain valid. After upgrading, re‑download and follow the product’s installation/update instructions.
  • If an update addresses a security fix, it is delivered free to protect your environment.
Changelog Requirements
  • List changes using short, clear bullet points.
  • Indicate whether the update is minor or major and whether an update price applies.
  • Note any breaking changes and include simple migration notes.
  • Highlight security fixes explicitly.

By following these rules, updates remain predictable for customers and manageable for developers. The store surfaces update badges and counts to help buyers identify actively maintained products.

Prohibited Actions

  • Editing, interfering with, or making decisions about products you do not own.
  • Replying to support tickets for products you do not own.
  • Manipulating ratings, reviews, or report outcomes.
  • Abusing the report system, spamming, or harassing customers or other developers.
  • Attempting to bypass store policies, security controls, or payment flows.

Withdraw Methods & Commission

Withdrawals are available through the methods currently exposed in the store manager. These methods can be extended later. Each withdrawal request is subject to a 30% Store commission which is deducted from the developer’s payout.

  • Check the manager for the currently supported withdrawal methods.
  • Commission is applied to the withdrawal amount before the payout is processed.
  • Processing times may vary depending on method and verification checks. Some withdrawals may take longer based on the payment processor/company and chosen method.
  • Additional methods for Egypt developers: Mobile Wallets and Instapay.
  • Crypto withdrawals are accepted in USDT only.
  • Store Owners are not responsible for requests sent to wrong addresses, invalid bank accounts, or wrong numbers. You must ensure all withdrawal details are correct before submitting.

For security, withdrawal requests require OTP verification. A one‑time code is sent to your email and the request is processed only after entering the correct code within the time limit.

Support Tickets Rules

You must respond only to tickets and reports related to your own products. Do not handle issues for products you do not own. Violations may lead to punishment including account restrictions or suspension.

  • Provide clear, respectful, and timely support for your customers.
  • Do not disclose sensitive information or request credentials beyond what is necessary.
  • Escalate platform or billing issues through official support channels rather than handling them directly.

Suspension Consequences

If your account is suspended for breaking developer collaboration rules, your wallet balance is frozen permanently. You will not have the right to request withdrawal of any remaining funds. Suspended accounts lose access to developer features and cannot participate in the store.

Report System & Ratings

Customers and owners can submit reports. Verified reports may affect your account standing. Ratings reflect your product quality and support performance. Consistently poor ratings or verified reports may negatively impact your account and in some cases lead to suspension.

  • Maintain high product quality and responsive support.
  • Address valid reports quickly and professionally.
  • Avoid behavior that could trigger negative ratings or verified reports.

Account Impact

Your privileges and access depend on policy compliance, support quality, ratings, and verified report outcomes. Repeated violations escalate from warnings to restrictions and eventually suspension.

Policy Changes

This policy may be updated at any time according to Store Owners’ decisions and our future vision. Check this page regularly for the latest version.

Contact Us

Need to talk with us?

Contact us Log-in now