Sellers / affiliates

Affiliate promotion availability depends on Store's affiliate program structure and your seller terms. Where supported, affiliates can promote your seller profile, individual products or your Copy strategies through their channels. Provide clean shareable URLs, promotional images and "Trial" badges to make affiliate work easier.

No. Buyers receive access to use the product through their cTrader ID, not the source code. Each .algo file is encrypted and bound to the buyer's cTrader ID, so even the distributed copy is not readable.

Yes. cBot sellers can attach backtesting results to product pages to show historical performance. Past successful performance does not guarantee future results, and overpromising backtesting results are a common reason for products being flagged. Use realistic spread, commission and execution settings and pair backtesting with live or demo-forward performance where possible.

Yes. Sellers can attach a trial version to a paid product, with seller-defined limits — time-limited, feature-limited or backtesting-only. Trials reduce buyer hesitation and improve review quality because users buy after confirming compatibility. The "Trial" badge surfaces this on the product card.

Yes. Free product publishing has lighter seller requirements than paid publishing. Free products help build seller reputation, gather reviews and demonstrate quality — but they still need accurate descriptions, compatibility information and risk-aware copy. Free does not mean unsupported.

Yes, after completing seller verification (KYC). Paid product pages need enough information for buyers to evaluate fit and risk before purchase — strategy or feature explanation, supported apps, limitations, backtesting results or live evidence and clear setup expectations. Exaggerated performance claims will be rejected at review.

Yes. cBots are one of the core paid product categories in Store. A strong cBot listing covers strategy logic, supported symbols and timeframes, recommended account conditions, risk settings, cloud vs local compatibility, backtesting results, live or demo statistics and explicit limitations. Avoid profit guarantees — they fail review.

Yes. Indicator selling is open through Store, with the constraint that Store custom indicators run on cTrader Windows and Mac only. The product page should state desktop-only support up front, explain signal logic, disclose any repaint behaviour and show realistic chart examples rather than perfect cherry-picked screenshots.

Yes. You can publish either multi-platform plugins (Web, Mobile, Windows, Mac) using the WebView plugin SDK or desktop plugins for Windows and Mac. The page should state which plugin type it is, where the plugin appears in the interface, what permissions it needs, whether it can trade and what data leaves cTrader. Video helps plugin pages convert.

Yes. Sellers can attach live or demo-forward account performance to a product page, which is stronger evidence than backtesting results because it reflects real execution. Live performance still represents one broker, one period and one parameter set — disclose these for transparency. Performance shown on the product card improves filtering and conversion.

Yes. A seller profile in cTrader Store functions as a landing page for traffic from external channels. It includes your best products, categories, ratings, video previews and Copy strategies if applicable. Optimise the profile bio, choose strong featured products and link consistently from external content.

Yes. Products may be removed from cTrader Store if their descriptions are incomplete, unclear or misleading, if they breach Store rules or if user reports surface policy violations. Sellers receive notice when a product is removed and can correct issues and resubmit.

.algo files in cTrader Store are generated locally on the seller's machine, encrypted and distributed as unique buyer-bound copies. They execute inside cTrader or in the cloud without exposing readable code. Source is never uploaded to Store or the cTrader cloud.

To become a seller, create a Store seller profile, prepare a product that meets Store requirements and submit it for review. Paid sellers complete identity verification; free product publishing has lighter requirements. Strong seller pages explain use case, supported apps, settings, limitations and what users should test on a demo account — not just feature lists.

Use your seller profile URL as a landing page in external channels — YouTube, Reddit, Telegram, trading communities, your own website, paid ads. The profile should display best products, video previews, live performance where available and clear descriptions. Maintain consistency across the channels you promote on.

Seller payouts in cTrader Store depend on Store's payout schedule and seller agreement. Verified paid sellers receive payouts from product sales according to the published terms. For exact payout rules, payment methods and timing, refer to your seller agreement and Store seller documentation.

cTrader Store generates each .algo file locally on your machine in cTrader Windows or Mac, encrypts it and distributes a unique copy bound to each buyer's cTrader ID. Source code is never uploaded to Store or the cTrader cloud. cBots run locally inside cTrader or in the cloud, never in a readable or accessible form to buyers.

Name the product by what it does, in language buyers actually search. A clear, specific name that includes the product type ("Risk Manager cBot", "Order Block Indicator", "Trade Journal Plugin") outperforms a generic brand name. Avoid names that imply guaranteed profit, no risk or broker-independent execution — those fail review and damage trust.

No. Your source code is never uploaded to cTrader Store or the cTrader cloud. The .algo file is generated locally in cTrader Windows or Mac, encrypted on your machine and only the encrypted unique copies are distributed.

Misleading descriptions typically overpromise results (guaranteed profit, no risk), hide critical limitations (desktop-only indicator sold as multi-platform), inflate backtesting evidence (perfect historical curves without disclosure) or omit material information (broker dependence, prop-firm restrictions, repaint behaviour). Be specific about what the product does and does not do.

Store ranking weighs product quality and engagement signals — completeness of description, supported apps, video, trial availability, live performance, user reviews, ratings, installs and active usage. Misleading descriptions or profit guarantees damage ranking even if early reviews are positive. Focus on accurate, complete pages and real performance evidence.

Trust comes from concrete detail: clear description of what the product does and does not do, realistic screenshots, video, supported apps and brokers, live or demo performance with the underlying account visible, risk disclosure, trial availability and seller profile completeness. Profit guarantees and cherry-picked screenshots reduce trust even when the product is good.

Sellers can publish cBots, custom indicators, multi-platform plugins and desktop plugins, with Copy strategies handled through cTrader Copy's separate provider workflow. Each product type has its own page requirements and compatibility constraints; pick the type that matches what the tool actually does, not the type with the most search traffic.

A cBot description should cover strategy type, supported symbols and timeframes, recommended account conditions, risk settings, cloud vs local compatibility, backtesting results, live or demo statistics and explicit limitations (instruments not supported, conditions where the strategy underperforms, broker-dependent behaviour).

A plugin description should state plugin type (multi-platform or desktop), which UI areas it appears in, what permissions it needs, what data it sends to external services, whether it can place trades and what the user sees after installation. Video helps plugin descriptions more than any other product type because plugins are visual.

A strong product description includes what the product does in one sentence, who it is for, where it works (supported cTrader apps), what permissions it needs, what settings matter, what limitations apply and what the user should test on a demo account. Add backtesting results or live evidence where available and avoid profit guarantees.

An indicator description should state supported apps (Store custom indicators are Windows/Mac only), explain signal logic, disclose repaint behaviour, list alert types if any, show realistic chart examples and describe how the indicator behaves in different market regimes (trending vs ranging, low vs high volatility).

Developers and trading-tool creators with a verified Store seller profile can publish products. Paid product publishing requires seller verification (KYC); free products have lighter requirements. Approval depends on product quality, accurate description and compliance with Store publishing rules — misleading or unsafe products are rejected.

Common rejection reasons include misleading or incomplete descriptions, profit guarantees, exaggerated performance claims, missing supported-apps information, lack of risk disclosure, broken functionality or rules violations (e.g. payment forms inside a WebView plugin).

Video reduces buyer uncertainty by showing what happens after installation — interface, settings, behaviour, expected outcome. For plugins and dashboards, video is almost essential because static screenshots cannot show interactive behaviour. For cBots, video can demonstrate the bot in action on a chart with realistic settings. The "Video" badge on a product card also signals seller commitment.