Why Prop Firm Payouts Get Denied: 9 Rule Violations That Block Your Withdrawal

A trader books $5,000 on a funded account, clicks withdraw, and gets back two words: not eligible. The balance is still green. The account is still open. Nothing was wrong yesterday. What changed is that a payout request triggers an audit, and the audit looks at the entire history, not the part the trader remembers. Most payout denials are not the firm being shady. They are a rule that was breached weeks ago and never mattered until money tried to leave.

This is a problem-aware breakdown of the nine documented triggers that block prop-firm withdrawals, grouped into five categories, each with the concrete fix. The figures here are grounded where firms publish them and hedged where they come from aggregators rather than official sources. The goal is simple: know what gets caught before you submit the request, not after.

Denied vs delayed: which one you are actually facing

A denial means the firm has decided a rule was broken and the profit will not be paid; a delay means the payout is held pending a process step such as KYC review or a scheduled payout window. The two feel identical in the dashboard but require opposite responses. A delay is fixed by completing a step and waiting. A denial is fixed by understanding the cited rule, and sometimes it cannot be fixed at all.

The fastest way to tell them apart is to read the exact wording. "Pending verification," "processing," and "next payout cycle" are delays. "Violation," "not eligible," "voided," and "terminated" are denials. If the message is ambiguous, ask the firm to state in writing whether a rule was breached and which one. That single question converts a vague status into something you can act on, and it starts a paper trail you will want later.

Category 1: rule breaches you did not notice

The platform fills the order, the trade closes green, and weeks later an audit voids the profit it produced. Three triggers behave this way, and they share one nasty property: nothing warned you at the time, so you carry a breach you do not know about straight into the withdrawal request.

Trigger 1: news-window blackout. Many firms void trades opened or closed on an affected instrument inside a short window around a scheduled high-impact release. A common pattern is roughly two minutes before and after, a four-minute blackout, but it varies sharply: FTMO has cited 2 minutes on Standard accounts only, Alpha Capital Group around 5 minutes on most accounts (2 minutes on its Alpha Pro tiers), Audacity 3 minutes, and Ment Funding 6 minutes total split before and after. The windows are firm- and account-type-specific, so the number you must trust is the one in your firm's current rules.

Trigger 2: prohibited instruments. Trading a banned product silently voids the profit it produced. Topstep allows only futures listed on CME, COMEX, NYMEX and CBOT and prohibits stocks, options, forex and spot cryptocurrency, and reserves the right to "delete the trading day and all profits." FundedNext Futures bans spot forex such as EURUSD, crypto such as BTCUSD, commodities such as XAUUSD, CFD indices such as SPX500, and spot energy such as USOUSD. The trap is product-class confusion: a trader assumes "BTC futures equals futures equals allowed," touches spot crypto by mistake, and the entire day evaporates with no partial credit.

Trigger 3: historical drawdown breaches, position-size limits, and open positions at payout. A daily-loss or max-drawdown breach from any point in the funded period can block a payout even if the account later recovered, and the same goes for exceeding a maximum-contract or position-size cap on a single trade. Some programs also require the account to be fully flat when you request a withdrawal, and a single open trade at that moment can auto-deny the request. The exact contract caps and drawdown lines are set per account size and program, so the only number worth trusting is the one in your current rules.

The fix for all three is mechanical. Maintain a personal news-blackout buffer wider than your firm's stated window, keep a written list of exactly which products and what maximum size your specific program permits, and request payouts only when the account is flat and well clear of any drawdown line.

Category 2: group trading and hedging across accounts

Cross-account hedging is, by one industry breakdown, the single most-cited payout-denial cause, attributed to roughly 22% of denials. Hedging here means opening opposing positions across multiple accounts to lock directional exposure while limiting the downside any single account can show. FTMO's Forbidden Trading Practices forbids "simultaneously entering into opposite positions" across "connected accounts, accounts held with various operators/providers, or accounts held with other members of the Program Group," with the only exception being a single account.

Treat the 22% figure as one publisher's estimate rather than audited data. The mechanism behind it is not in dispute, though. If you are long ES on one funded account and short ES on another to guarantee one of them passes or pays, you are running the exact pattern firms built detection to catch, and they catch it across firms, not just within one.

A green balance on each account does not mean you are clear. If the two accounts only look profitable as a pair, that is the pattern, and the audit sees the pair.

Trigger 4 is group hedging itself. The fix is to stop treating your accounts as one book with internal offsets. Trade each account on its own thesis, with its own risk, so that no account depends on another being on the opposite side. If your edge genuinely requires hedging, do it inside one account where the rules permit it, not by splitting the two legs across the firm's portfolio of accounts. For the broader question of running multiple accounts cleanly, the deeper treatment is in copying across multiple prop-firm accounts.

Category 3: identical fills and shared-IP flags

Copy-trading denials are triggered when a firm detects coordinated execution, and the two signals it reads most are identical sub-second fills and shared connection fingerprints. FTMO bans "trades executed at the same time on multiple accounts based on a copied signal." Aggregator write-ups describe firms combining IP fingerprinting, device fingerprints, session data, and millisecond timestamp matching, and cite an illustrative correlation threshold near 10 milliseconds for flagging coordinated activity. That 10ms number is an aggregator's characterization, not a firm-published threshold; no firm discloses its exact detection cutoff.

Trigger 5 is the identical-fill signature (same instrument, same direction, same size, same exit, within a sliver of time). Trigger 6 is the shared-IP or shared-device flag. The insider point that surprises most traders: when this pattern is flagged, every linked account is denied at once, including the source account, not just the followers. Copying your own multiple accounts can still trip it, even when every dollar is legitimately yours, because the fill signature and connection fingerprint link the accounts as one coordinated entity regardless of who owns the capital.

Shared-IP flags are also where false positives bite. Corporate networks, mobile carrier CGNAT, and security tools can all read as a VPN or a shared connection. In an April 2025 case, an Instant Funding trader's $2,000 payout was denied over alleged VPN/VPS usage; the trader said they traded mobile-only and that the flagged connection may have been ZScaler corporate security software. Reported as a trader's allegation rather than an adjudicated fact, it still illustrates the asymmetry: the burden of proof falls on you. The detection internals, including how timestamp correlation and fingerprinting actually work, are covered in how prop firms detect copy trading; this article stays on the withdrawal consequence.

Category 4: consistency-rule violations

The consistency rule does not close your account; it freezes the money until your profit is spread across enough days, and that gap is the trap. Most firms enforcing it cap a single day's share of total profit somewhere between 25% and 50%. Topstep defines Consistency % as largest single-day net profit divided by total net profit and requires it to be 40% or below to be payout-eligible on certain account paths. Apex requires that the single best day not exceed 50% of total profit for the cycle. FXIFY uses a 30% example. A FundedHive CEO publicly called the consistency rule "a payout trap."

Trigger 7 is the consistency lock. Here is the worked example, using a 40% gate like Topstep's, with the firm-specific caveat printed alongside it.

To unlock the payout the trader keeps trading and grows total profit so the best day falls to 40% or below: raising the total to $6,250 without exceeding that same $2,500 best day does it, which means booking an additional $1,250 spread across other days. At a 50% cap (Apex-style), the same $2,500 over $5,000 sits exactly on the line and could still be rejected if the rule reads "cannot exceed 50%." The caveat that matters: thresholds (30%, 40%, 50%), whether the gate applies at evaluation or at payout, and the exact formula vary by firm and program and change over time. Topstep is even reported to have no consistency gate on some account types. The example is illustrative; verify the live number in your firm's TOS.

Category 5: inactivity, minimum days and KYC gaps

The last category blocks payouts on procedure rather than trading behavior, and it catches people who think the trading is the only thing being judged. Two triggers sit here.

Trigger 8: inactivity and minimum active days. A widely cited threshold is no trading activity for 60 consecutive calendar days, which can mark a funded account inactive and in breach regardless of prior performance. Minimum active-day requirements exist on the evaluation and payout side too: FTMO has historically required around 4 minimum trading days, The5ers about 6 during evaluation, and Topstep has cited 3 trading days on a consistency path or 5 winning days on a standard path. These counts vary widely and firms revise them, so the 60-day figure is best read as "commonly around 60 days, varies by firm."

Trigger 9: KYC and verification gaps. KYC must be complete before any payout processes, and firms reject documents that are unclear, expired, or name-mismatched, such as a nickname against a full legal name. VPN or VPS use during verification can trigger fraud detection and even permanent bans. The fix is to complete KYC early, with clear documents that match your legal name exactly, from a clean and consistent connection that you also trade from.

There is a sixth thing worth naming because it is not your behavior at all: retroactive rule changes. In December 2025, FundingTicks (Funding Pips) changed rules for existing account holders, introducing a 1-minute minimum hold where there had been none, raising the minimum daily profit to $200 from $150, requiring 6 profitable days instead of 5, and cutting the split to 80% from up to 90%. Traders reported up to roughly $21,000 in profits removed retroactively, and the Trustpilot TrustScore fell from about 4.1 in October to 3.2. Reported as trader claims, the episode still underscores the lesson: read the current TOS, not the one you signed up under, and screenshot the version you agreed to.

How server-side copying with per-account variance stays clear of the fill/IP triggers

Server-side copying with realistic per-account fills and your own broker credentials avoids the identical-fill and shared-IP patterns that get payouts denied, because each account executes through its own connection with its own fill variance rather than as a cloned signal from one machine. That is the structural difference between a server-based copier and a local script broadcasting the same order from one home PC over one IP.

The two flagged signals from Category 3 are fill correlation and connection fingerprint. A server-based copier like Thor routes each follower through its own broker session, applies per-account sizing so positions are not byte-identical, and uses realistic per-account fills rather than stamping the same price and millisecond across every account. Combined with each account using its own credentials, that reduces the fingerprint overlap that triggers a coordinated-activity flag. It is the same reason funded traders on Apex, Topstep, and MyFundedFutures care which layer the copying happens on.

Be honest about where this is not the answer. Server-side copying does not make hedging legal, does not exempt you from the consistency rule, and does not complete your KYC. It changes the execution fingerprint, nothing more. And on raw latency a Chicago-colocated local copier sitting next to the exchange gateway will beat a general server-side service on the wire; if microsecond execution is your only metric, colocation wins. For the broader compliance picture, including what firms actually permit, the companion piece on how prop firms detect copy trading is the deeper read.

The pre-withdrawal audit checklist

Run this checklist before every withdrawal, because a five-minute audit is cheaper than a denied payout. Each line maps to one of the nine triggers above.

1. Re-read the current TOS and screenshot it. Confirm the rules have not changed since you started.
2. Scan for news-window trades on affected instruments inside the firm's blackout, plus your own wider buffer.
3. Confirm every instrument you touched is permitted on your specific program. No spot crypto, no CFD indices, no forex on a futures account unless explicitly allowed.
4. Check no drawdown line was breached at any point in the funded period, even if recovered.
5. Verify no cross-account hedging, no offsetting legs split across your accounts.
6. Check execution patterns and IPs are not identical across accounts; trade each on its own connection.
7. Run the consistency math: largest single day divided by total profit, against your firm's current cap.
8. Confirm minimum active days are met and the account is not flagged inactive.
9. Verify KYC is complete with name-matched, in-date documents, submitted from a clean connection.
10. Flatten the account so there are zero open positions when you submit the request.

If all ten pass, submit with a clear conscience and a screenshot trail. If one fails, you just found the denial before it found you.

What to do if you have already been denied

If you have already been denied, your first move is to get the firm to name the specific rule and the exact trades it cited, in writing, then check those against the TOS version you agreed to. A denial without a named rule is not a denial you can dispute, so the written reason is the foundation of everything that follows.

From there, gather your own evidence: order timestamps, the connection and device you traded from, the products you touched, and any screenshots of the rules as they stood at signup. If the cited rule was introduced after you joined, that is a retroactive change, and the FundingTicks episode shows you are not the first to face it. If the firm cannot point to a real breach, escalate through their formal dispute channel and keep every message. Adjudication of these disputes usually comes down to which side has the cleaner record, so be the side that does. For the mechanics of how payouts are processed end to end, see how prop firm payouts work, and for the drawdown rules that quietly cause many denials, trailing vs static vs EOD drawdown. If you want a neutral regulatory reference point on managed futures, the National Futures Association publishes the relevant guidance.

Frequently asked questions