A margin call is a warning you can still act on; a stop-out is the broker acting for you, and conflating the two is the most expensive mistake a leveraged trader can make in 2026. The hook for anyone who has read the broker's email mid-session and wondered whether they had time is simple: by the time the email arrives, the broker has often already started closing positions.
A margin call is a notification. It fires when the margin level — equity divided by used margin — reaches a threshold the broker has set, typically 100% for ESMA-regulated retail brokers. The notification asks the trader to do something: deposit more funds, close positions, or accept that the next leg down will trigger the stop-out. The trader still has agency.
A stop-out is the action that follows when the trader does not (or cannot) restore margin. At most ESMA-regulated brokers, the stop-out fires when equity falls to 50% of the required margin. The platform closes positions automatically as soon as market conditions allow. The trader is not asked and is not consulted. The firm chooses which positions to close and at what price. The trader observes the result.
The psychological gap is the most important thing to internalise. Margin calls give the trader control. Stop-outs take it away.
Different brokers fire the margin call at different levels. The published thresholds for major retail platforms in 2026 cluster around three points:
Below 50%, professional clients on ECN platforms (IC Markets, Pepperstone) often have a 20% stop-out level rather than 50%, on the assumption that professional clients can manage their own risk more actively. That 30-percentage-point gap represents thousands of dollars in margin cushion for high-volume traders.
| Account state | Equity | Used margin | Margin level | Broker response |
|---|---|---|---|---|
| Open trade, $50k position at 30:1 | $5,000 | $1,667 | 300% | Healthy |
| Floating loss $3,333 | $1,667 | $1,667 | 100% | Margin call fires |
| Floating loss $4,167 | $833 | $1,667 | 50% | Stop-out begins |
| Floating loss $5,000 | $0 | $1,667 | 0% | Account closed |
A $50,000 position at 30:1 leverage on a $5,000 account reaches the margin call after roughly a 6.67% adverse move — about 667 pips on a four-decimal pair. The same account with a $100,000 position reaches the margin call after roughly 1.67% — and the 50% stop-out after roughly 3.33%. Position size relative to balance, not the leverage figure, determines how much room the trade has.
When a margin call arrives, the trader has four options. The first three preserve some control; the fourth accepts the broker's liquidation.
Three reasons margin calls become stop-outs:
The third reason is the most common in 2026. NFP, CPI and central-bank decisions now produce 50-pip moves in seconds, and a margin call at 100% margin level on a $5,000 account can reach the 50% stop-out within a single minute. By the time the trader's stop-loss or close-order is submitted and filled, the broker has already begun its own liquidation.
The broker's algorithm chooses positions to close based on its own logic — typically the largest unrealised loss first, or the largest position by margin impact. The trader may have a profitable position and a losing position; the broker closes the profitable one first because it has the largest gain to lock in, while the losing position stays open to do more damage. The result is counter-intuitive: the trader's best trade is closed, and the worst trade remains. This is the most common complaint in 2026 retail forums, and it is a structural feature of the broker's algorithm, not a bug.
How Margin Calls Work — Broker Champion 2026 walks through the warning level, the close-out level and the position-selection logic. The video is third-party; the controlling source is the broker's published trading conditions and the regulator's product intervention order.
Checked September 2026. Margin call thresholds vary by broker and jurisdiction. The figures above reflect ESMA-regulated retail broker practice as of mid-2026; CFTC-registered brokers in the US operate under a different framework with potentially longer response windows.