Skip to main content
All CollectionsGetting StartedProgram FAQ
Prohibited Trading Strategies at Topstep
Prohibited Trading Strategies at Topstep
Updated yesterday

At Topstep, we aim to provide a fair and transparent trading environment for all traders. To maintain the integrity of our trading programs and protect the community, certain trading styles and strategies are prohibited. These restrictions are in place to ensure compliance with our risk management policies and to promote sustainable trading practices. Please review this list of prohibited trading activities to stay informed and ensure your trading remains within our guidelines.

  • Account stacking. This is a trading practice where a trader repeatedly trades in an aggressive way, then hits the Maximum Loss Limit in one account, and switches to another account to repeat the process. The goal of this behavior is to continue making high-risk trades until a successful outcome results in a significant profit. This practice is not allowed as it exploits risk parameters and violates our trading guidelines.

  • Intentionally depleting the account balance in Live Funded Accounts to force a failure.

  • Performing trades in conflict with the terms and conditions of Topstep of the User Section and the terms and conditions of the Trading Combine.

  • Using any software, artificial intelligence, ultra-high speed, or mass data entry that might manipulate, abuse, or give User an unfair advantage while using the Site or Services.

  • Otherwise performing trades in contradiction with how trading is actually performed in the applicable futures markets, or in a way that establishes justified concerns that Topstep might suffer financial or other harm as a result of User’s activities.

  • Changing your trading style to become payout eligible.

  • Trading excessive or unrealistic number of contracts in the day.

  • Performing trades any time outside the best bid or offer.

For more information, please refer to our Prohibited Conduct and Professional Behavior policies.

Did this answer your question?