GOAT Funded Trader is facing two fresh customer disputes that put a similar question under scrutiny: when a trading rule can automatically terminate an account or invalidate a payout, how clearly must that rule be displayed and which version of the policy should apply?
In one October 13 complaint, a trader says a $5,000 Instant HERO account was terminated after floating losses reached $51.93 even though the trading dashboard prominently displayed a 3% daily drawdown limit equivalent to $150. GOAT’s published Instant HERO documentation does contain a separate 1% maximum floating-loss rule, meaning it would be inaccurate to describe the restriction itself as unpublished.
The narrower dispute is whether every limit capable of immediately closing the account was shown clearly enough on the live dashboard.
A separate payout dispute raises a different timing problem. A trader who purchased two $100,000 Premium Instant accounts on September 26 says GOAT paid $4,656 from one account but denied the payout and terminated the second for copy or coordinated trading, despite the customer claiming roughly 90% of the trades on both accounts were the same.
GOAT has publicly responded to both cases and offered further Risk Management Team reviews, without conceding that either original decision was wrong.
A $51.93 Floating Loss Triggered the Instant HERO Complaint
The first complaint came from trader Niyas Mkd, who said his active $5,000 Instant HERO dashboard displayed a 3% daily drawdown limit of $150.
According to the trader, the account was nevertheless closed when the floating loss reached $51.93. Support then cited a separate maximum floating-loss threshold of 1%, equivalent to approximately $50 on a $5,000 balance.
GOAT’s official Instant HERO rules currently list three distinct loss controls: a 3% daily drawdown limit, a 5% maximum overall loss limit and a 1% maximum floating-loss rule. The company states that the floating-loss threshold operates independently and that an account is permanently closed if unrealized losses reach 1% of the account balance.
On that basis, the rule itself is publicly documented.
What Niyas disputes is its visibility inside the account interface. He alleges that the dashboard displayed the $150 daily drawdown limit but did not show the separate $50 floating-loss ceiling alongside it.
GOAT’s response did not dispute the existence of different dashboard displays. Instead, the company said the limits are separate risk parameters, noted that account conditions are available before purchase, and explicitly acknowledged the customer’s concern about how those limits appear on the dashboard. GOAT said it had requested account information so its risk team could review the case.
Another October 13 reviewer made a substantially similar complaint about the 1% rule. GOAT again responded that the maximum floating-loss requirement is part of the Instant HERO rules and applies independently from daily and overall drawdown limits.
The Dispute Is About Interface Visibility, Not Whether the 1% Rule Exists
That distinction matters.
If a rule is clearly included in the product documentation but absent from a particular dashboard screen, the issue is different from a firm enforcing a rule that was never disclosed anywhere.
A trader still has a responsibility to understand the full account conditions. At the same time, a dashboard presenting live risk limits can reasonably influence how that trader manages positions in real time.
If one prominent gauge shows $150 of available daily loss capacity while another independent $50 threshold capable of permanently terminating the account is not displayed next to it, the interface could potentially create an incomplete picture of usable risk even though the underlying rule exists elsewhere.
This is part of a wider pattern in proprietary trading where backend controls can matter as much as market performance. Dave Finances recently reported how GOAT Funded Trader tightened its VPN and VPS restrictions across trading accounts, creating additional account-level risks that sit outside ordinary profit-and-loss management.
The easiest way to resolve the Instant HERO dispute would be straightforward: screenshots showing exactly which risk metrics were visible on the live account at the time of the breach, together with the server-side calculation showing when the $50 floating threshold was crossed.
A Second Trader Says One $4,656 Payout Was Paid While Another Account Was Terminated
The second case carries larger financial consequences.
A verified Trustpilot reviewer says he purchased two $100,000 Premium Instant accounts on September 26 and submitted payout requests for both on October 8.
The trader says approximately 90% of the activity across the accounts was identical because he personally replicated the same trades.
According to the review, GOAT paid a $4,656 payout on the account ending 452 but rejected the reward on the account ending 451 and terminated that account for alleged copy or group trading.
The customer argues that the different outcomes are inconsistent because the two accounts contained largely overlapping trading activity.
That argument does not by itself prove GOAT applied its rules incorrectly. Payout reviews can examine each account separately, and there may be differences in individual trades, execution methods, account connections or other risk signals that are not visible in the public complaint.
GOAT’s public response made essentially that point. The company said payout requests and trading activity undergo individual reviews and acknowledged the customer’s concern about the apparently different outcomes. It said the matter would be escalated to the Risk Management Team.
The case resembles a FundingPips copy-trading dispute involving a trader approaching another payout, where the central question was not whether firms are entitled to prohibit coordinated activity but what evidence distinguished legitimate account management from prohibited copying.
GOAT Changed Its Copy-Trading Rules Around the Same Period
The difficult part of the GOAT case is timing.
The disputed accounts were purchased on September 26 and the payouts were requested on October 8. GOAT subsequently formalized a broader internal copy-trading policy and launched its proprietary GOAT Trade Copier.
The firm’s current copy-trading documentation says traders may copy between their own GOAT accounts only through the GOAT Trade Copier and states that the rule applies from October 12, 2026.
An October 12 company announcement similarly described the firm as lifting restrictions on copying between traders’ own accounts while introducing the proprietary copier.
However, the historical record is not completely clean. A version of GOAT’s help documentation indexed several days earlier and marked updated October 6 already stated that copy trading between a trader’s own GOAT accounts was allowed, including between evaluation and funded accounts.
That earlier wording did not contain the same GOAT Trade Copier requirement now found in the October 12 version.
The result is an important policy-version question: precisely what rules applied to the trader’s activity between September 26 and October 8?
A Later Rule Change Cannot Automatically Decide an Earlier Payout
This is where the case becomes more interesting than an ordinary complaint about copy trading.
Current rules are useful for understanding GOAT’s position today, but they cannot automatically establish whether conduct was permitted several days earlier.
What matters is the contractual and help-center language in force when the relevant trades were executed.
If GOAT’s pre-change policy prohibited the way the trader replicated positions, then the fact that the firm later relaxed its rules would not necessarily invalidate the original breach. Companies are generally capable of changing trading conditions prospectively without retroactively legalizing previous conduct.
But if copying between personally owned accounts was already permitted under the applicable version of the rules, GOAT would need to explain what additional conduct caused account 451 to fail while account 452 produced a $4,656 payout.
The same evidentiary problem has appeared elsewhere in the sector. A recent FunderPro account-closure dispute centered on whether the customer had enough information to meaningfully challenge the technical evidence used by the firm’s compliance systems.
Paying One Account Does Not Necessarily Clear the Second
The $4,656 payment is important, but it is not conclusive proof that the second account should also have passed.
A firm’s compliance system could identify different account relationships, timestamps or execution behavior even where 90% of trades overlap. One account could potentially contain a specific event that the other does not.
There is also another possibility: the accounts may have been reviewed by different processes or at different points before the same trading pattern was fully investigated.
That is exactly why the account-level evidence matters.
If GOAT concluded that account 451 engaged in coordinated trading, the useful disclosure would identify the relevant trade sequence, the applicable policy version and the characteristic that made those transactions prohibited. It would not require GOAT to reveal its full fraud-detection methodology or another customer’s private data.
A similar problem exists with the 1% floating-loss complaint. Traders do not necessarily need access to the firm’s entire backend. They need enough information to reproduce the calculation that closed their account.
Prop-Firm Rules Are Becoming a Product-Design Issue
These two disputes look different on the surface. One involves a $51.93 floating loss. The other involves a $4,656 payout and allegedly replicated trades.
But both revolve around the same underlying problem: rules increasingly exist across several layers at once.
There is the formal terms document, product FAQ, dashboard, breach engine, payout-review process and support explanation. A rule can be correctly written in one place yet poorly communicated in another. A policy can also change while traders still hold accounts purchased under an earlier structure.
That matters more in retail proprietary trading because, as Dave Finances has previously explained, prop firms operate differently from conventional brokers. Traders commonly work with simulated accounts and become entitled to cash rewards only when they satisfy the firm’s contractual conditions.
The firm therefore controls not only the trading environment but also the interpretation of the conditions that determine whether profitable performance becomes payable.
That makes clarity unusually valuable.
For the Instant HERO complaint, screenshots could establish whether the 1% floating-loss threshold was visible with the same prominence as the 3% daily limit.
For the $4,656 payout dispute, the decisive evidence is the dated copy-trading policy that applied to the September and early-October trades, together with the specific activity that caused the two accounts to receive different risk decisions.
GOAT has not publicly admitted an error in either case. But by offering risk-team reviews and acknowledging the dashboard-display concern and the inconsistent-looking payout outcomes, the company has left both questions open to further examination.
The issue is not whether prop firms should enforce risk and anti-copying controls. They clearly need such controls. The harder question is whether a trader can see the rule before breaching it and reconstruct the evidence after the firm says it has been breached.
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