An Apex Trader Funding reviewer alleges that his wife’s multiple Performance Accounts were closed shortly after she requested her first payouts, with a fraud warning on the dashboard and company messages that did not identify a consistent, account-specific reason for the decision.
The October 20 Trustpilot complaint, posted by Igor Kerzner, says the trader completed about 12 trading days over two weeks and believed she had satisfied Apex’s payout conditions before submitting requests on a Friday morning. The reviewer says the accounts subsequently became inaccessible and that one dashboard message displayed “Fraudulent Activity Detected.”
The allegations have not been verified against the trader’s order history, balance records, payout requests or the correspondence described. The timing does not establish that requesting payment caused the closure, or that the fraud message was an accurate finding of misconduct.
What Did the Apex Trader Funding Reviewer Allege?
In the public October 20 review, Kerzner says he is describing his wife’s experience, not his own trading account. He reports that she traded for 12 days and sought her first withdrawals after reaching what they understood to be the required milestones.
According to the reviewer, no violations had appeared on the account dashboard before the requests, and she did not place further trades afterward. He says all of her Performance Accounts were subsequently closed, access was restricted, and the interface displayed a fraud-related label without explaining which specific conduct triggered it.
He describes two different communications: one mentioning open positions after the trading cutoff or a trailing-drawdown breach as potential liquidation reasons, and another stating that the accounts had been permanently closed after a review, with no further details or reconsideration available.
The full emails were not provided in a form independently authenticated for this article. It is therefore not possible to establish whether the first communication was a generic list of possible causes, an account-specific determination, or a different type of automatic notice from the later review outcome.
Nor does the complaint disclose the exact number or sizes of accounts, the amount requested, the account product type or which trade, if any, Apex flagged. Those omissions are important because different Performance Account products have different operating requirements.
What Do Apex’s Published Performance Account Rules Allow?
Apex describes its Performance Accounts as simulated funded accounts, rather than a conventional brokerage account where a trader owns the nominal balance shown on screen. Approved payouts are subject to trading and compliance requirements specified in the relevant program.
Its End-of-Day Performance Account guidance says breaching the maximum drawdown threshold results in account closure. It also warns that prohibited activities, including certain hedging or rule-circumvention practices, can lead to immediate closure.
Under its separate intraday-trailing product, the drawdown threshold is monitored in real time and can also trigger a permanent account closure. Accounts created under legacy terms may have additional or different requirements. The review does not identify which type the trader had, so none of these provisions can be assumed to explain her case.
One particularly important distinction is the Daily Loss Limit. Apex says hitting that daily limit pauses trading until the next session in its applicable products, whereas touching the overall drawdown threshold can close the Performance Account. The different consequences mean that a reference simply to a risk limit or liquidation is insufficient to reconstruct the alleged violation.
The firm also makes clear that eligibility to request a payout is not identical to a final payment approval. Passing an initial dashboard test does not rule out further account or trading-conduct reviews, but an adverse decision should still be assessed against the applicable contract and available evidence.
Does a First Payout Request Explain the Closures?
The sequence alleged by Kerzner is noteworthy: payout requests came first, then the account closures. But chronology by itself is not proof of retaliation or an unfair refusal to pay. There could be a separate rule violation detected during a manual audit, an automated threshold event, an account-security check, or an incorrect flag. The present public record cannot distinguish among them.
For example, a trader could unintentionally hold a contract beyond a required cutoff despite believing the session was over, or the displayed balance might temporarily diverge from a drawdown calculation that includes unrealized profit and loss. Equally, a compliance label might be displayed incorrectly. These are possibilities, not explanations established in this complaint.
Apex’s payout documentation states that traders may ordinarily continue trading after submitting a request, although subsequent account losses can affect payout eligibility. The reviewer explicitly says his wife did not trade after requesting payment. Without account logs, that statement cannot be independently confirmed or used to rule out a condition triggered by earlier activity.
Similar tensions over payout decisions have arisen across the prop-trading industry. DaveFinances previously documented complaints involving OFP Funding and a disputed $10,000 payout. That separate case does not corroborate an Apex failure; it illustrates the need to distinguish customer claims from contractual grounds for denial.
Why Does the Alleged Fraud Message Matter?
A dashboard warning alleging fraudulent activity carries a different implication from an ordinary failed trading evaluation. But the wording of a software label is not itself proof that the customer committed fraud, supplied false documents or violated a particular law.
If the label corresponds to a trading-conduct finding, the relevant evidence might include execution times, device and account associations, trade-copying records or breaches of published rules. If the account was instead closed because of a drawdown threshold, timestamps and balance calculations should identify when the level was reached.
Apex’s rules permit audits and action for prohibited trading practices. They do not establish, from the public review alone, which policy was invoked against this trader or whether the firm communicated a specific finding privately.
The problem of checking abbreviated compliance summaries is not unique to Apex. An earlier GOAT Funded Trader dispute over matching-trade counts and order timestamps raised a separate question about whether the supporting data could be reconciled with the stated reason for termination.
What Records Could Resolve the Apex Dispute?
The primary evidence would be the account IDs and plan versions; complete payout eligibility screens; the time and amount of each request; all platform trading executions and open-position records; daily and trailing drawdown snapshots; and the unredacted communications explaining closure.
Those records would allow a chronological comparison of the trader’s last position, the alleged cutoff or drawdown event, the payout requests and the compliance-review decision. A clear explanation should also distinguish any automated liquidation from a later discretionary or fraud-related determination.
The reviewer has asked for an explanation and clarification about pending payouts. No public reply to that specific account of events was independently established during this review, and it would be inappropriate to claim that the company has not communicated through private channels.
The broader principle is a familiar one in complaints about prop-firm account rules and dashboard metrics: a customer’s understanding of a displayed threshold and the firm’s internal compliance records can differ, sometimes materially.
For now, the substantiated news is that an October 20 reviewer alleges multiple Apex Performance Accounts were closed after initial payout requests and says the available messages did not identify a consistent reason. Without the underlying evidence, neither wrongdoing by Apex nor compliance by the trader can be independently determined.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574