Topstep — Verification Record

This is the complete, dated record of every independent verification pass this corpus has run against Topstep's own published rules, beyond the initial read: what was checked, what the check found, what changed, and what was preserved for the record even where two readings disagreed. See how a number gets checked twice for the method behind every entry below.

• 2026-09-18 Correction applied

  Two independent readers, each working blind to the other’s output and to the stored value

  Field-by-field: 1 noted (1 field touched this pass).

  PKG-ASTRA-10 payout mode backfill: two blind agents, no shared state (each ran independently, neither read the other's output or this repo's stored value), both landed on the identical sentence of the firm's official payout-policy article (single first-party source, help topstep com/en/articles/8284233-topstep-payout-policy) -- 'Request Payouts in the Express Funded Account (XFA) and Live Funded Account (LFA) via your Topstep Dashboard.' mode=on request added, activating the on-request branch of payoutwindow (funded-file-sections js ~248) for this firm for the first time.

  Sources consulted: https://help.topstep.com/en/articles/8284233-topstep-payout-policy — checked 2026-09-18
• 2026-09-13 Partial

  First party single pass

  Field-by-field: 3 noted (3 fields touched this pass).

  PKG-E payout/reset-fee provenance backfill. Topstep's Trading Combine sells under two live pricing paths (no single initial fee), pays out on a winning-day requirement (not a fixed cycle), and has no discrete reset product distinct from its own monthly subscription. Left all three fields null with documented omissions rather than pick an arbitrary path/number.

  Sources consulted: https://help.topstep.com/en/articles/14289835-topstep-pricing-and-payment-questions, https://help.topstep.com/en/articles/8284233-topstep-payout-policy — checked 2026-09-13
• 2026-09-13 Documented-absent

  First party single pass

  Field-by-field: 1 noted (1 field touched this pass).

  trader-relations review CONCERNS: pricing reset price after breach was documented-absent off the payout-policy article, which is not a reset/pricing page (the pricing-and-payment article was already cited for initial fee) -- the same off-topic source url pattern the TradeDay cycle-days note was already corrected for on this branch. Re-fetched (r jina ai) the pricing-and-payment article and found it does have a dedicated "Reset Pricing" section, priced identically to the monthly subscription per path (Standard 50K $49/100K $99/150K $199, No Activation Fee 50K $95/100K $149/150K $229) -- so the field is not truly source-absent, it carries the same two-track path ambiguity as pricing initial fee. Re-sourced source url to the pricing article and reworded the note to describe the real reason the value stays null (unresolved path, not an absent reset product).

  Sources consulted: https://help.topstep.com/en/articles/14289835-topstep-pricing-and-payment-questions — checked 2026-09-13
• 2026-07-31 Correction applied

  Modeled from prior run 2 finding

  Field-by-field: 1 corrected (1 field touched this pass).

  Converted a run-2 (2026-07-22) finding that sat unmodeled for 9 days into a proper ambiguities[] entry. Live value UNCHANGED (see basis) to avoid breaking build-firm-presets js consistency-percentage calculation exact-match wiring.

  Sources consulted: https://help.topstep.com/en/articles/8284208-consistency-at-topstep — checked 2026-07-31
• 2026-07-22 Confirmed, one discrepancy flagged

  Two independent readers, each working blind to the other’s output and to the stored value

  Field-by-field: 11 confirmed · 2 preserved for the record (13 fields touched this pass).

  Confirmed by both blind passes: targets $3k/$6k/$9k (=6%), MLL $2k/$3k/$4.5k, EOD-balance trail locking at starting balance, DLL optional and size-fixed, 5PM CT reset, min 2 days, no time limit. Discrepancy noted, not entered: consistency rule effect - both passes read "If it exceeds that, your Profit Target increases... not a rule break"; corpus stores effect:"block". Entering "raise target" would silently DELETE the constraint, because js maps only effect==="block" to a live consistencyPct. Our "block" is a CONSERVATIVE approximation (overstates difficulty, never understates) and is retained deliberately pending an engine that can express a rising target. Also flagged: both passes independently found Topstep stating two different values across its own pages on the denominator - prose "50% of your Profit Target" vs its own formula "Best Day Profit / Total Profit". Topstep publishes NO percentages; our pct values are exact arithmetic on published dollars.

  Sources consulted: https://help.topstep.com/en/articles/8284197-trading-combine-parameters, https://help.topstep.com/en/articles/8284204-what-is-the-maximum-loss-limit, https://help.topstep.com/en/articles/8284208-consistency-at-topstep, https://help.topstep.com/en/articles/10490293-daily-loss-limit-in-the-trading-combine-and-express-funded-account — checked 2026-07-22

Rules and their verification status change without notice; the firm's own documentation is always the final authority. This page is independent research, not investment or trading advice, and PropSurvival is not affiliated with, endorsed by, or sponsored by Topstep.