← Back to Evidence Hub

This article reviews public complaint signals, visible company response behaviour, and audit-style evidence notes. It is not a legal finding or accusation. Readers should review the evidence and decide for themselves.

PROPFIRM EVIDENCE WEEKLY

What Traders Need to Know This Week

Sunday, 1 November 2026 — Issue 9

Published by PropFirm Evidence | 01/11/2026

This edition examines trader reviews and company responses collected in the supplied review document. It is not a legal finding or an accusation. Statements about individual accounts, payments and correspondence remain attributed to their sources unless independently established.

Every week, PropFirm Evidence reviews payout disputes, company explanations, account restrictions and other public signals across the prop-firm industry.

A negative review does not establish wrongdoing. A company response must also be considered.

Our focus is straightforward:

What happened? What evidence is available? What does the company say? And what remains unresolved?


THE BIG STORY

Alpha Capital Group Traders Question Device-ID and IP Findings Behind Account Closures

[Company: Alpha Capital Group | Evidence: Several trader reviews in the supplied document | Status: Disputed account closures and payout decisions]

Several reviewers describe Alpha Capital Group account closures or payout refusals involving device identifiers, shared IP addresses or identity checks.

Their accounts raise a common question: what information can traders obtain when they dispute a technical association between their profile and another customer?

The reviews contain different circumstances and should be assessed individually. Their appearance together does not establish that the underlying decisions were incorrect.

Mattia Boffo — A Device Identifier Allegedly Linked to 12 Other Users

Mattia Boffo says he had traded with Alpha Capital Group for approximately 18 months, completed verification interviews and received multiple payouts.

According to his review, the company subsequently closed his accounts and withheld a pending payout after a device identifier, described as a CID, was allegedly associated with 12 other users.

Boffo disputes account sharing. He says he consistently used the same VPS and requested an explanation of whether its infrastructure could account for the connection.

He also reports losing dashboard access, preventing him from retrieving invoices and trading records.

The review does not specify the pending payout amount.

Source: pp. 9–11.

Tey Chamroeun — A Question About the Dates Used in an IP Review

Tey Chamroeun says he purchased a challenge on 30 June 2026 and received his Qualified Analyst Account on 16 July 2026.

He reports that Alpha Capital later raised shared-IP concerns affecting his payout. His principal objection concerns the investigation timeline: he says the information supplied included activity from December 2025 and January 2026, before his challenge purchase.

The reviewer states:

“As of 30 October 2026, I have submitted my formal appeal and am awaiting a response.”

The document does not independently establish which accounts the earlier records concerned or how those records were used in the decision.

Source: pp. 6–7.

Bahaa — Approximately $6,000 Requested From a $200,000 Account

A reviewer using the name Bahaa reports that a $200,000 funded account was terminated while an approximately $6,000 payout was pending.

He says the company identified a residential IP address shared with another trader’s account. He disputes knowing the other trader or sharing account access.

Bahaa also describes the company’s correspondence and its interpretation of the connection. However, that description is the reviewer’s account of the exchange; the underlying correspondence is not independently reproduced in the reviewed passage.

The $200,000 figure describes the account size. The reported payout dispute concerns approximately $6,000.

Source: pp. 16–18.

Company Response

No direct Alpha Capital Group reply to these three cases appears in the reviewed section.

The reviewers describe explanations received privately, but those descriptions should not be presented as independently authenticated company statements.

What the Document Establishes

The document contains several reviews disputing device-ID, IP or verification findings. It also records specific names, timelines and, in some cases, requested payout amounts.

It does not independently establish whether the technical findings were accurate, whether contractual violations occurred or whether the requested payouts were payable.

Questions for Clarification

  • Which account activity and dates supported each decision?
  • How were shared infrastructure and account access distinguished?
  • What account-specific findings were supplied to the affected traders?
  • Can traders obtain their records after dashboard access ends?
  • What appeal options remain available?

MULTIPLE DISPUTED CASES — ACCOUNT-SPECIFIC EVIDENCE NEEDED


PAYOUT CASE OF THE WEEK

FXIFY Reviewer Reports $40,000 Payout Dispute Over Arbitrage Classification

[Company: FXIFY | Reviewer: Aashish | Reported payout: $40,000 | Evidence: Trader review and company reply | Status: Unresolved in the supplied record]

A reviewer named Aashish reports that FXIFY rejected a $40,000 payout and closed his account after classifying the trading as arbitrage.

He describes himself as a discretionary trader and denies using latency exploitation, automated high-frequency scripts or feed manipulation.

The review identifies account 8007455 and says he requested technical information supporting the decision, including trade references, execution records and pricing discrepancies.

These statements remain the reviewer’s allegations. The document does not include the underlying execution data needed to assess the classification.

Source: p. 443; repeated account of the same dispute on pp. 451–452.

FXIFY’s Response

In a reply accompanying the repeated review, FXIFY states that it could not identify the account through the reviewer’s Trustpilot username and invited him to provide account details.

That reply does not resolve the arbitrage allegation or establish whether the requested payout qualified for payment.

Although the captured review contains an account number, the document does not establish whether that information was available when FXIFY posted its response.

Source: p. 452.

A Separate $2,400 Case Includes a More Detailed Company Explanation

Another reviewer, İsmail Cansu, reports that a $2,400 payout was cancelled following a latency-arbitrage allegation.

Cansu denies violating the rules and says his account purchase fee was refunded. He also disputes the level of technical detail provided and describes delays in receiving a further review.

FXIFY responds that its Compliance and Risk teams identified prohibited trading practices and that the account was closed on 23 October.

The company states that refunding the account fee was consistent with its terms and did not contradict the compliance finding. It also says it could not disclose its internal detection methods and risk parameters.

This is a separate case. FXIFY’s explanation to Cansu should not be treated as its account-specific response to Aashish.

Source: pp. 446–448.

What the Document Establishes

The document records an identifiable $40,000 complaint, a company request for identifying information, and a separate $2,400 dispute with a substantive company response.

The repeated appearances of Aashish’s review concern the same reported amount and account. They should not be counted as separate $40,000 claims.

Neither a reviewer’s assertion of manual trading nor a company’s classification independently resolves whether prohibited activity occurred.

Questions for Clarification

  • Has FXIFY identified and reviewed account 8007455?
  • What is the current status of the $40,000 request?
  • Which contractual provision and account activity supported the decision?
  • What explanation can be supplied without disclosing confidential detection methods?
  • Has any subsequent review changed the outcome?

REPORTED $40,000 DISPUTE — OUTCOME NOT ESTABLISHED


PROGRAM TRANSITION OF THE WEEK

Apex Traders Describe How Moving to Live Changed Their Payout Expectations

[Company: Apex Trader Funding | Reviewers: James and donald | Evidence: Two trader accounts | Status: Disputed expectations surrounding live transitions]

Two Apex Trader Funding reviewers describe a change in their trading arrangements after being moved from simulated funded accounts to the company’s live program.

Their complaints concern the relationship between accumulated simulated profits, potential future payouts and the risk allowance available after transition.

The figures describe different measures. A simulated profit buffer, a requested withdrawal and a live drawdown allowance are not interchangeable.

James — Previous Payments Acknowledged, Future Opportunities Disputed

A reviewer named James says he spent approximately $185,000 on accounts and fees since 2022 and received approximately $120,000 in payouts.

He describes the difference as a roughly $65,000 net loss, while expressly stating that he does not blame Apex for his trading losses.

James says he held 20 accounts by September 2026. In early October, he received a $15,000 payout from a group of 10 accounts, with the money reaching his bank within days.

His review states:

“My complaint is not about payout processing.”

Instead, James says a move to the live program deactivated his simulated accounts when he believed he was approximately two trading days from qualifying for another $30,000.

That $30,000 was an anticipated payout opportunity, not an approved unpaid withdrawal established by the document.

According to his account, the live program began with one account and a $3,000 end-of-day drawdown allowance. He also describes conditional treatment of eligible simulated profits through a “Bonus Vault.”

Those program details are presented here as his description; the applicable agreement is not independently examined in this article.

Source: pp. 929–931.

donald — An $89,000 Simulated Buffer and a $3,000 Live Loss Allowance

A second reviewer, using the name donald, says he received two payouts and accumulated approximately $89,000 in simulated account profits before being transferred to live.

He reports that the live account provided a $3,000 maximum loss allowance and says the transition changed his opportunity to pursue further simulated-account payouts.

The document does not establish that $89,000 was an approved withdrawal, a cash deposit or an amount immediately payable to him.

The reviewer disputes the effect and timing of the transition, while acknowledging that he cannot establish the company’s internal intentions.

Source: pp. 919–921.

Company Response

No direct Apex response to these two reviews appears in the relevant passages.

James himself acknowledges that, under his understanding of the rules, Apex retained discretion to move traders live before they completed six payouts.

His disagreement concerns the practical consequences and the expectations customers may form when purchasing multiple accounts.

What Remains to Be Established

The document does not independently resolve:

  • Which program terms applied to each reviewer.
  • How accumulated simulated profits were treated after transition.
  • Which amounts, if any, remained eligible for conditional future payment.
  • What transition information each trader received before purchasing accounts.

Questions for Clarification

  • What determines the timing of a live transition?
  • How are accumulated simulated profits treated?
  • Which payout opportunities end when simulated accounts close?
  • What conditions govern any bonus arrangements?
  • How are these consequences explained before account purchase?

LIVE-TRANSITION QUESTIONS — CONTRACTUAL DETAILS NEEDED


EDITORIAL RECORD

Right to Reply

The company responses above are those contained in the supplied document. PropFirm Evidence has not obtained additional statements for this edition.

Companies and reviewers may provide account-specific correspondence, applicable policy versions, trading records and subsequent outcomes to clarify the cases.

Any correction or resolution should be reflected in the published record.

The PropFirm Evidence Principle

A review establishes what its author reports. It does not, by itself, establish the underlying events.

A company response explains its position. The supporting records remain relevant to assessing that explanation.

Follow the evidence. Attribute the claims. Give both sides the right to reply.

Source Reference

All page references refer to Reviews_paginated_reference.pdf, the 1,176-page consultation copy rendered from the supplied Reviews.docx. Pagination may differ from the original Word view. Repeated reviews are not counted as independent cases.

PROP FIRM EVIDENCE
Weekly — Sunday, 1 November 2026

Scroll to Top