futures / rule

Apex 50% Consistency Rule Explained

How Apex's 50% consistency gate can keep the payout request option unavailable even when the account remains active.

Last checked 2026-05-07 Official sources reviewed

Short answer

Apex’s 50% consistency rule is a payout-readiness gate. If the largest profitable trading day is 50% or more of total net profit in the current payout window, the payout request option may not be available, but the account can remain active.

Why this rule matters

This rule matters most for traders who make one large winning day and then expect payout to unlock. The practical consequence is not just a percentage. It is whether the payout request path appears when the trader expects it.

The official Apex wording uses profit since the last approved payout, or since account inception if no payout has been approved. After a payout is approved, the consistency calculation resets for the next payout window.

How the worksheet calculates it

The attached checker uses this field model:

  • Largest profitable trading day divided by total net profit.
  • Result must be below 50%.
  • Minimum net profit needed equals largest profitable day divided by 0.5.
  • Losing days can make the percentage worse because they reduce total net profit.

Example: if the largest profitable day is $1,500, the minimum net profit needed under the 50% gate is $3,000.

Other payout gates to check

For the intraday Performance Account worksheet, the checker also uses the official account-size table for:

  • Five qualifying trading days.
  • Minimum daily profit per qualifying day.
  • Minimum balance to request.
  • Six approved payouts maximum per Performance Account.

What to check

  • Which Apex account family and rule version applies.
  • The largest profitable day in the current payout window.
  • The total profit basis used by the current official rule.
  • Qualifying days, minimum daily profit, safety net, and payout count.

What this does not prove

This page does not prove payout approval, payout denial, or account safety. It explains a rule gate that must be checked against the current official source and dashboard state.