PropŞikayet Case File · August 2026

Funding Pips CID-Ban Case: Mass Account Terminations

Mass funded-account terminations on "copy trading / arbitrage" (CID) grounds with balances frozen; public dispute clusters demonstrating inconsistent algorithmic application across identical trading footprints.

CASE NO: PRP-VAKA-2026-03 Date: August 2026 · Scope: Numerous funded accounts · Source file: PRP-FPIPS-2026

Mass bans CID and hardware-fingerprint terminations

Frozen balances Funds withheld on algorithmic arbitrage claims

Inconsistent filter Disparate treatment of identical market flows

Sequence of Events

In August 2026, Funding Pips terminated numerous funded accounts citing "arbitrage / copy trading" (CID).
Balances in terminated accounts were frozen; formal appeals were met with automated boilerplate rejections.
Public dispute records demonstrate that automated filters failed to apply consistently across comparable position profiles.

Context: Funding Pips survived the February 2024 MetaQuotes enforcement wave by restructuring under Dubai jurisdiction. While correlation auditing is standard practice, this inquiry focuses on automated, non-appealable mass enforcement without human review.

File Status & CID Filter Mechanism

Under Active Watch: 47.5% Trust Score (B-Book Execution Model). Following the February 2024 MetaQuotes regulatory shutdown, Funding Pips restructured operations out of Dubai, migrating trader flows onto cTrader and Match-Trader. However, the Correlation ID (CID) and Reverse Trading detection algorithms deployed during the August 2026 purge flagged traders sharing local subnetworks, utilizing identical internet service providers, or executing widespread technical signals as "syndicate traders," leading to blanket account terminations.

Desk Assessment: Under internal B-Book clearing architecture, trader profit distributions represent direct operational liabilities paid out of company equity. Clustering distinct customer accounts under blanket correlation flags constitutes an effective liquidity defense mechanism during periods of high aggregate withdrawal demand.

August 2026 Report: Funding Pips Section →

Trader Protection Guide: Avoiding CID and Correlation Flagging

[!] Never Execute Trades on Shared Networks: Public Wi-Fi connections in cafes, hotels, or shared co-working spaces route through identical gateway IP addresses. Counter-directional positions taken by other traders on the same network trigger immediate correlation flags on both accounts.

[!] Refrain From Using Factory-Default EA / Bot Parameters: Commercial trading robots purchased online enter markets with identical millisecond timestamps. Broker risk desks automatically categorize identical execution bursts as unauthorized pool trading.

[!] Archive Order Timestamps and Chart Screenshots: Maintain timestamped TradingView analytical snapshots for every executed setup. Objective pre-execution evidence is the only viable defense against retroactive algorithmic correlation claims.