GOAT Funded Trader is facing a more detailed challenge to a copy-trading payout rejection after a Turkish customer questioned an apparent mismatch in the firm’s reported trade counts and asked whether its risk review considered the time his pending orders were originally placed.
Burkay Özkaynak, who says he purchased two $100,000 Premium Instant accounts on September 26, updated a public complaint on October 18 with specific XAUUSD order timestamps. He alleges GOAT paid a $4,656 reward on an account ending 452 but rejected a reward request and terminated a second account ending 451 after accusing it of coordinated trading with unrelated users.
The records published in the complaint are the customer’s account of events, not authenticated server logs. The central questions are whether the firm can reconcile an alleged count of 11 matching trades with a breakdown totaling 10, and whether identical execution times could result from independently placed pending orders.
Why Does the Trader Dispute an 11-Versus-10 Trade Count?
In an October 18 update to his Trustpilot review, Özkaynak says GOAT’s original breach notice identified 11 matching trades with other traders. But he says the accompanying summary grouped those matches as four, three and three trades, totaling 10.
The numerical inconsistency is clear on the face of the figures he describes: 4 + 3 + 3 = 10, one less than the alleged total. His account of the notice has not been independently checked against a complete, unredacted original report. Different counting conventions, duplicated categories, a missing row or a simple reporting mistake could each explain the gap.
Nor would a one-trade discrepancy automatically invalidate a coordinated-trading determination. The relevant question is whether GOAT’s underlying evidence still identifies prohibited conduct after all of the cited trades, counterpart accounts and decision criteria are reconciled.
Özkaynak says he has asked the company’s risk team to identify the specific trades and technical criteria behind the decision but has received general responses rather than a trade-by-trade explanation. The company has not provided a public, case-specific reconciliation of the disputed count in the material reviewed for this article.
What Do the XAUUSD Pending-Order Timestamps Show?
The customer points to two XAUUSD Buy Limit orders that, according to the timestamps he published, were submitted well before their eventual execution. One was placed on September 30 at 20:48:25 and executed on October 1 at 03:19:02, a gap of six hours, 30 minutes and 37 seconds.
A second order was reportedly placed on October 6 at 03:40:47 and executed at 05:35:14, a gap of one hour, 54 minutes and 27 seconds. In both examples the order’s creation time precedes the trade’s execution time by a substantial period.
Those examples concern the other account, ending 452, for which Özkaynak says the $4,656 reward was paid. They are not independently verified examples from the terminated account ending 451. The trader argues that GOAT should inspect original pending-order creation timestamps for the account it actually sanctioned before drawing conclusions from matching fills.
This distinction matters because a Buy Limit order can wait on a platform until the market reaches the specified price. Several unrelated traders placing orders in advance around common price levels could receive fills at similar moments without having placed their instructions together. However, that possibility alone cannot exclude coordination or copied trading instructions.
Does Matching Execution Time Prove Copy Trading?
Not by itself. Simultaneous executions may reflect the same price level being reached, particularly in a heavily followed market such as gold. A stronger assessment would compare original order placement, order prices, modifications, direction, size, risk, stop levels and a wider pattern of behavior.
Conversely, differing original placement times do not necessarily disprove copying. Traders could follow shared signals with different delays, or coordinated accounts could use common pending-order strategies. A meaningful analysis needs the complete sequence and context rather than a single timestamp field.
GOAT’s current help-center guidance prohibits copying trades from unrelated traders, third-party services and signal groups. It also sets conditions for copying between an individual’s own GOAT accounts. The company updated parts of its copy-trading documentation in October, including a rule change effective October 12; the disputed order examples predate that update, so the terms in force for those transactions must be established separately.
Özkaynak says approximately 90% of his trading across his two personally controlled accounts was identical or very similar. That self-described similarity is not, on its own, evidence of copying unrelated traders. At the same time, GOAT can assess the conduct on separate accounts individually, so paying one account does not legally or technically guarantee approval of the other.
Why Was One $100,000 Account Paid and the Other Terminated?
According to the complaint, the trader bought both $100,000 Premium Instant accounts on September 26 and requested rewards on October 8. The reported outcome was split: $4,656 paid on the account ending 452, and a rejected payout and termination on the account ending 451.
The $100,000 figures refer to the nominal sizes of the prop trading programs, not amounts the customer deposited, lost or was owed. The payout amount requested on account 451 was not established in the information reviewed. The $4,656 payment is also the customer’s account of the outcome, rather than an independently authenticated transfer record.
The case follows earlier DaveFinances reporting on complaints about GOAT’s loss-limit display and copy-trading rules. It adds a narrower test of how an allegedly coordinated trade was counted and how order sequencing was evaluated, not simply another general claim that a payout was denied.
GOAT has previously faced other public complaints linking copy-trading allegations to rejected payouts. Those separate allegations do not establish that this decision was wrong, that the firm employs an erroneous detection system or that all affected accounts shared the same facts.
What Evidence Would Settle the Technical Dispute?
The essential records are the complete breach notice, its trade-by-trade appendix and server-side histories for account 451. Those should identify every allegedly matching order, the comparison accounts, original creation and modification times, execution times and the criteria used to classify the conduct.
A useful independent review would first establish whether GOAT counted 10 or 11 distinct matches and how any overlapping groups were treated. It would then compare when the challenged orders were created, not merely when they filled, against the relevant unrelated accounts. Similar market entries, execution times and position sizes would need to be weighed together.
The trader says his terminated account is restricted, limiting access to the records he wants to use in his appeal. Whether GOAT can provide a suitably redacted report without exposing other customers’ private data is an important procedural question. A refusal to reveal counterpart identities would not necessarily prevent a firm from disclosing sufficient anonymized timestamps and order characteristics to explain its finding.
GOAT’s rules permit account action over prohibited practices, but the public review does not give enough independent evidence to determine whether its application was justified in this case. Prior reporting on a separate GOAT copy-trading payout dispute similarly underscores the difference between an allegation of improper denial and a verified conclusion.
For prop trading customers, the broader issue is auditability: a decision made using proprietary risk signals becomes difficult to challenge when only an abbreviated summary is disclosed. That is especially consequential when a payout and continued access to a simulated funded account are at stake.
For now, the confirmed new development is the customer’s October 18 public update detailing the alleged count mismatch and two pending-order timing examples. Neither the one-trade arithmetic difference nor the timestamps from his paid account prove the firm’s decision was erroneous. A resolution depends on GOAT’s full underlying order records, the rules applicable at the time and a specific response to the appeal.
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