Some traders might think the problem begins with a loss, but it often starts with a small, seemingly insignificant detail: the price you placed your order doesn't match what appears on the platform's timeline, a trade entered unusually late, or a closing price that doesn't reflect the market's movement. At this point, investigating the manipulation of trades becomes a proactive step, not just a reactive one, to determine whether the glitch is temporary or if there's a deliberate error in execution.
Where do you first look in the pricing and execution history?
The first mistake many people make is being satisfied with the final result. That's not enough. Profit or loss hides the story rather than explains it; what you really need is a clear timeline: when the price appeared, when you sent the order, when the platform received it, and when the execution actually occurred. The interval between these moments is crucial because even a small, unexplained gap could indicate a deliberate delay or improper order processing.
Start with the exact price history, not the abbreviated charts. Observe the exact candlestick, or even real-time updates if available, and then compare it to the execution history. If the price displayed at the moment you click buy is significantly different from the price at which the order was executed, first inquire about the normal slippage during the price fluctuation, and then examine whether this occurred only at the entry point or also at the exit point. Repeated occurrences are more reliable than a single strike.
There's a clear difference between a volatile market and a system manipulating data. In a volatile market, you see sharp movements across multiple channels and potentially across multiple assets. However, if the problem is confined to a single trade, or if a pattern is triggering certain orders while others remain unaffected, this is a sign that warrants investigation. Note the trade number, the order type, the bid price, and the execution price. It's the small details that make the case.
How to read the differences that reveal the flaw
Incomplete data can easily mislead you. Therefore, don't rely solely on the platform's internal price history; compare it with an independent price source whenever possible, especially for quick trades or pending orders. If external candles show a price level that the platform hasn't touched in its history, or vice versa, then the real question arises regarding the accuracy of the price feed.
Signs you shouldn't ignore
- If execution is repeated after a nearly constant delay each time, the problem may be in the order flow, not the market.
- If requotes appear more frequently at potential profit levels than at loss levels, this is a pattern that needs careful review.
- If you find a clear difference between the time the command was sent and the time it was recorded within the system, check the time zone, clock synchronization, and server log before drawing any conclusions.
- If your trades are closing faster than usual under the same conditions that allowed other trades to continue, there may be an unbalanced execution filter.
The most important step here is to consolidate the numbers. Put them in a single file, trade by trade, with three clear layers: the price you see, the execution price, and a reference price from an independent source. When you see them side by side, the pattern becomes immediately apparent. Sometimes the gap is small, but it recurs with a specific type of order, such as stop-loss orders or market orders during news releases. This is not a minor detail.
Let's be realistic; market depth matters if it's available. When liquidity is low, deviations may seem large, but they're still understandable. However, if liquidity is sufficient, prices are stable, and then deviations appear that don't align with the movement, the meaning changes. Here, don't look for an emotional explanation, but rather for a correlation between the data and the execution time. If they don't match, the issue requires further investigation.
What makes you build a strong objection file?
The strongest objection isn't the longest; it's the clearest. When contacting support or the dispute reviewing the issue, don't send vague impressions like "the market was strange." Send a verifiable sequence of events. Include the trade number, time, screenshots, and update history if available, then link it to an external price file. This transforms the conversation from a complaint into a verifiable comparison.
Ensure that the screenshots are complete, not cropped. The time, asset name, order type, and both prices should be visible on the screen, if possible. If you have a download history or a CSV file from the platform, this is preferable to individual screenshots, as the file allows you to track the difference second by second. Also, keep your previous correspondence, especially if the problem started after a change in execution conditions or a sudden increase in requotes.
Reviewing the log isn't just a defensive measure after a loss. It's a way to determine if the platform is handling your orders fairly or if there's an unusual pattern that warrants action. If you want someone to help you organize the evidence and understand where the sequence went wrong, working with a team that understands price and execution logs saves you a lot of guesswork and allows you to enter any dispute with a clear, well-defined case that isn't solely based on memory.