Alpha Capital Group is facing a fresh series of customer complaints over its use of MetaTrader 5 device identifiers to detect suspected account sharing, including an allegation that the proprietary trading firm terminated a funded account on payout day and withheld approximately $7,000 USDT.
Three separate reviews published on October 12, 2026, describe disputes involving MetaQuotes client identifiers, commonly referred to as CIDs. The traders allege that Alpha Capital Group linked their accounts to other users through device records but failed to provide sufficient supporting evidence when challenged.
One reviewer reproduced what he described as correspondence from the firm’s risk team identifying three device identifiers associated with nine other users. However, that customer also acknowledged using a virtual private server (VPS), an arrangement that Alpha Capital Group permits only under specific conditions.
The allegations remain unverified. There is no independent evidence establishing that the company’s device matches were incorrect or that the reported account closures were deliberately timed to avoid payouts.
Taiwanese Trader Alleges $7,000 USDT Payout Was Withheld
The most financially significant complaint came from a Taiwan-based reviewer identified as Jalen hu, who accused Alpha Capital Group of terminating his funded trading account on the day a performance payout was scheduled.
According to the October 12 Trustpilot review, the trader was expecting approximately $7,000 USDT when the firm cited prohibited account management under Schedule 3 of its rules and an alleged overlap involving MetaQuotes device identifiers.
The reviewer claimed that Alpha Capital Group’s risk team had identified the suspicious activity retrospectively through older trading accounts rather than through the account on which he was requesting payment.
He said he submitted biometric identification, local hardware records and network information, and offered to complete a recorded video verification call.
According to his account, the firm nevertheless maintained its decision and declined to disclose the specific CID values, timestamps or account IDs underlying the allegation.
These claims have not been supported by independently authenticated risk-team correspondence, complete login records or account histories.
The reference to historical accounts is particularly important. If the relevant device activity occurred before the disputed payout account was established, investigators would need to determine whether the earlier access demonstrated prohibited third-party management or another breach that legitimately affected the customer’s subsequent eligibility.
The public review does not establish that distinction.
Second Review Identifies Three Device IDs Linked to Nine Users
A second October 12 complaint, posted by Italian reviewer umberto, provides more technical detail about Alpha Capital Group’s alleged detection process.
The trader reproduced correspondence purportedly sent by the company’s risk team stating that three device identifiers used to access his MetaTrader 5 accounts had also appeared on accounts belonging to other customers.
The notice listed three hashed identifiers, each accompanied by partially obscured email addresses associated with supposedly overlapping users.
According to the reproduced message, the three identifiers connected the reviewer’s accounts with nine other user accounts.
The trader disputed the conclusion that this constituted prohibited account sharing and suggested that his use of a VPS explained the overlap.
That admission is important because Alpha Capital Group’s rules distinguish authorized use of hosted trading infrastructure from unreported or improperly configured connections.
The review does not establish whether the VPS had a dedicated static IP address, whether the trader notified Alpha Capital Group before using it or whether the identified CIDs originated from the VPS environment.
Nor does it establish whether the other accounts were accessed by the same individual, through a common service provider or through genuinely separate devices.
Without those details, the reproduced identifiers demonstrate the type of evidence allegedly used in the enforcement decision but cannot independently establish whether the decision was justified.
Third Trader Says CID Finding Followed an Earlier IP Dispute
A third reviewer, noeh leemans from Belgium, described a similar account termination after Alpha Capital Group allegedly identified a CID associated with another customer.
The trader claimed that an earlier IP-related dispute had been resolved and that he subsequently received a payout.
However, he said another problem emerged the following week when the company accused him of sharing account access based on device-identifier information.
The reviewer denied sharing his account and said he requested login locations, timestamps and IP records to understand the allegation.
He claimed the firm declined to provide the requested information and maintained its decision.
The three October 12 reviews are separate customer accounts, but they do not independently establish that the underlying device-identification system produced false matches.
No case-specific public response from Alpha Capital Group addressing these three allegations was identified during the review of the complaints.
Alpha Capital Group Allows VPS Use Only With Advance Notification
Alpha Capital Group’s official IP, VPN and VPS policy confirms that customers may use hosted trading infrastructure, subject to strict conditions.
A VPN or VPS must have a dedicated static IP address, and the trader must notify the company’s support team by email before using it, identifying the relevant accounts.
The firm says using those services without advance notification can trigger account closure and a potential permanent ban.
It also prohibits account sharing, unauthorized third-party management and coordinated trading between different customers.
These restrictions are designed to prevent customers from outsourcing evaluations or allowing other people to operate accounts registered in their names.
The distinction matters because the Italian reviewer’s acknowledged VPS usage does not automatically demonstrate mistaken enforcement. It could be relevant to a legitimate rule violation depending on the configuration and notification history.
Other proprietary trading companies impose different restrictions. Dave Finances recently reported on GOAT Funded Trader’s decision to prohibit VPNs and VPSs across all accounts, highlighting how remote trading infrastructure has become an increasingly important compliance issue.
What Does a Matching MetaQuotes CID Actually Prove?
The central technical question is whether matching device identifiers establish that multiple customers were using the same physical device or that the accounts shared a computing environment.
A device identifier can provide useful evidence of account relationships, but its interpretation depends on how the identifier is generated, what it represents and whether the underlying environment can be shared or replicated.
A VPS, for example, is a remotely hosted computing environment. Depending on its configuration, different users may access infrastructure operated by the same provider, while separate virtual machines may have different identifiers.
It would therefore be incorrect to assume that every shared hosting arrangement necessarily produces the same CID.
Equally, a CID match does not by itself establish who was physically operating the terminal when a particular account was accessed.
Stronger evidence could include session timestamps, IP histories, remote-access records, account ownership information and trading patterns showing coordinated activity.
The precise CID-generation mechanism involved in these complaints has not been independently verified, so the available reviews cannot establish whether shared infrastructure explains the reported matches.
Payout Timing Makes Historical Account Checks More Consequential
The most troubling element of the Taiwanese complaint is the allegation that Alpha Capital Group relied on historical account activity when a substantial payout became due.
That timing naturally creates suspicion for traders. They may complete an evaluation, trade a funded account successfully and only discover an alleged historical violation when a performance fee is requested.
But payout timing alone is not evidence that a company is acting improperly.
A compliance review conducted before money is paid can be a legitimate safeguard against account sharing, outsourced trading and other prohibited conduct.
The relevant question is whether the review identifies a genuine contractual breach and whether the customer receives enough information to challenge an incorrect finding.
Similar concerns emerged in FundingPips complaints involving post-evaluation identity and device checks, where traders questioned why certain eligibility issues allegedly became decisive only after successful evaluations.
The present allegations also resemble a separate FundingPips copy-trading suspension dispute involving a customer approaching a second payout.
Neither case establishes wrongdoing by Alpha Capital Group. They illustrate the wider importance of explaining how and when compliance findings affect a trader’s reward eligibility.
Prop Firms Need Strong Fraud Detection Without Unchallengeable Decisions
Proprietary trading firms have legitimate reasons to investigate shared devices and unusual login activity. If one professional trader could secretly manage dozens of accounts for different customers, the evaluation model would lose much of its purpose.
However, a detection system becomes difficult to assess when its conclusions cannot be independently examined.
Firms do not necessarily need to disclose every fraud-detection technique or reveal private information belonging to other customers. Doing so could expose their controls to abuse.
But there is a meaningful difference between protecting proprietary detection methods and refusing to explain the essential evidence supporting an account closure.
For example, a firm might provide relevant dates, the category of suspicious access and an explanation of whether the finding involved simultaneous sessions or historical device reuse, while withholding third-party personal information.
That would give customers a more practical opportunity to identify a mistake without making the surveillance system completely transparent.
The financial implications are also distinct from ordinary brokerage disputes. As explained in Dave Finances’ analysis of how retail prop firms differ from regulated brokers, many funded-trader programs operate through simulated accounts, with cash rewards determined by contractual performance rules.
Consequently, a disputed $7,000 performance fee is not necessarily equivalent to $7,000 in customer-owned brokerage funds being withheld.
Alpha Capital Group’s Session Records Could Resolve the Disputes
The October 12 complaints raise questions that should be technically testable.
For the Taiwanese trader, the most useful evidence would establish which historical accounts triggered the finding, when the relevant access occurred and how the alleged breach applied to the funded account.
For the Italian reviewer, investigators would need to determine whether the three CIDs reflected a properly disclosed VPS arrangement, unauthorized shared access or another technical explanation.
For the Belgian complaint, login records could clarify whether the CID finding was connected to the previously resolved IP issue or represented genuinely new evidence.
The publicly available material does not prove that Alpha Capital Group fabricated device matches, incorrectly terminated these accounts or deliberately avoided paying profitable customers.
It does establish that three customers publicly challenged CID-based enforcement decisions on October 12, including one involving an alleged $7,000 USDT payout.
A substantive response explaining how the company interprets device-ID overlaps, handles shared hosting environments and reviews disputed findings would do considerably more to resolve the uncertainty than the identifiers alone.
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