In 2013, if you blew up a forex account from India, you did it with your eyes open — dial-up lag, a clunky desktop terminal, and a brutally visible margin bar ticking down in front of you. In 2026 MT4 liquidates you in under 200 milliseconds and the only warning is a red entry in the Journal tab. If you do not know exactly what your broker has configured as your stop out level — not MT4's, your broker's — you are not managing risk. You are donating to it.

TL;DR

  • Stop out is a percentage, not a rupee amount.
  • Your broker picks the level, not MT4.
  • High leverage compresses the distance to liquidation.

Red Flag #1: You Think Stop Out Is a Fixed MT4 Setting

A trader Googles "MT4 stop out level" expecting to find a number baked into the platform, the way you'd find Tools > Options for chart colors. There isn't one. MT4 is a terminal. The stop out level is a server-side parameter your broker configures and ships to you on connection. It varies by broker, by account type, and sometimes by instrument — exotics and CFDs often carry a different threshold than majors on the same account.

The "Margin Level" percentage in your MT4 account state is calculated against a threshold you do not own. You cannot override it in Tools > Options. You find it in your broker's Execution Policy document — not on the marketing page.

The pattern we see across broker TOS documents is consistent: the stop out number is buried in a PDF labeled "Margin Requirements" or "Order Execution Policy," never on the landing page where the 1:2000 leverage number is printed in 60-point type.

Red Flag #2: Margin Call and Stop Out Are Not the Same Event

A reader thinks the red MT4 warning box is the same thing that liquidates her position. It isn't. MT4's margin engine fires two distinct server-side thresholds. The first is the margin call level — the equity-to-used-margin percentage at which the terminal warns you that you are running low. The second is the stop out level — the percentage at which the server starts closing positions without your consent, largest loser first on most deployments.

The two numbers are separate broker-configured values. If your broker sets them close together, or if a volatility tick jumps your equity through both levels between one quote and the next, the first thing you will see in your Journal is a closed trade, not a warning.

The margin call is a courtesy. The stop out is the mechanic. One of them is optional from the broker's point of view. Guess which.

Red Flag #3: 1:2000 Leverage Compresses the Distance to Liquidation

Exness advertises up to 1:2000 maximum leverage. FBS advertises up to 1:3000. Our Bangalore reader reads these numbers as "more buying power." They are not. They are a divisor on required margin.

Here's where it gets really interesting. At 1:2000, a standard lot of EUR/USD needs roughly $50 of margin against $100,000 of notional. A standard lot of EUR/USD moves roughly $10 per pip. The distance from full margin to a stop out somewhere in the range retail MT4 brokers typically publish is a handful of pips — find yours before you place the trade, not after.

A handful of pips is the same order of magnitude as a London open spread widening against Exness's 1.0 average standard-account spread. The same leverage that makes the landing page copy sing is the number most compressing your distance to liquidation. FBS's 1:3000 is FBS's most-advertised feature. It is also the single most effective way to get stopped out on a quiet Tuesday.

Red Flag #4: "Scalping Prohibited" Changes What Stop Out Even Means

AvaTrade is the example in our grounding. AvaTrade's listed weakness is that scalping is prohibited and its maximum leverage is capped at 1:400 — conservative by Indian offshore-broker standards. A reader sees "scalping prohibited" and assumes it's a pace rule about how often she can click Buy.

It's usually more than that. "Scalping prohibited" in a retail broker TOS typically gives the broker the right to reverse or void trades it deems scalping, which interacts with stop out logic in a way most traders never see. If MT4's server liquidates you at stop out, that close is final from the server's side. But if you were running a high-frequency strategy and the broker later decides to void the trades that triggered the liquidation cascade, you are now arguing in a support ticket about an event that already cost you real rupees.

AvaTrade's 1:400 cap is the conservative leg of this trade. Lower leverage means stop out fires less often in the first place, and AvaTrade carries tier-1 ASIC regulation if the worst happens.

Red Flag #5: The Pro-Account Zero Spread Is Not the Cost at Liquidation

Exness advertises 0.1 pip EUR/USD on its Pro tier. FBS advertises 0.0. HF Markets' zero-spread account goes to 0.0. FXTM's zero-spread tier prints 0.1. A reader imports these numbers into her stop out math and assumes her liquidation price is one tenth of a pip off her last quote.

When stop out fires, MT4 closes at whatever "market" is on the broker's server at that millisecond. "Market" during a liquidation event is almost never the advertised average. The numbers you should be sizing against are the broker's standard averages — AvaTrade's 0.9, Exness standard's 1.0, HFM's 1.2, FXTM's 1.5 — not the Pro-tier line at the top of the page.

Sized tightly against a 0.1 pip marketing number, a spread that briefly widens several-fold on a news print will close your trade whether or not the "average" says otherwise. The server does not care about the landing page.

Red Flag #6: Instant Withdrawal Is Not Liquidation Protection

Exness advertises instant withdrawal. FBS advertises instant-to-1-day. In Indian retail forums this reads as a quality-of-service flex, and a reader takes it as "if something goes wrong I can pull my money quickly."

Withdrawal speed is a funding-channel metric, not a margin metric. When MT4 stops you out, the event has already happened. You cannot withdraw faster than the server closed the position. The instant-withdrawal claim is relevant to the Section 206C(1G) side of the trade — your 20% TCS on outward remittance above ₹7 lakh was collected by your bank on the way in, not on the way out — but it tells you nothing about the server-side mechanic of MT4 closing your trade at the broker's configured percentage.

Fast withdrawal says something about the broker's counterparty-side treasury. It says nothing about your stop out level, which lives on an entirely different system and fires regardless of how quickly treasury can wire INR back to HDFC.

Red Flag #7: INR-Denominated Accounts Add a Second Currency to Your Margin Math

FXTM is the example in our grounding — its listed best-for is Indian rupee account support, meaning you can fund and denominate your account in INR. A reader takes this as pure convenience and assumes her stop out calculation is unchanged.

It isn't. If your account is INR-denominated and you trade EUR/USD, your equity is being marked to market in two currencies at once. Position PnL is in USD pips. Equity balance is in INR. A move in USD/INR between your entry and the moment of liquidation is invisible in your MT4 margin column but absolutely changes the rupee value of your free margin.

Stop out fires on the ratio of equity to used margin, and equity is calculated in account currency at the broker's internal conversion rate — not Google's. This is the kind of detail that makes Indian CAs stare blankly when you bring them a P&L statement. Schedule FSI on the ITR has no column for "FX conversion drag between entry and server liquidation."

Red Flag #8: The Tier-1 Regulator on the Homepage Is Not the Entity Holding Your Account

Every broker in our grounding lists a tier-1 regulator. Exness lists FCA. FBS lists ASIC. AvaTrade lists ASIC. FXTM lists FCA. HF Markets lists FCA and DFSA. A reader treats "regulated" as a yes/no field and assumes her recourse after a disputed stop out is the same regardless of where the broker books her account.

It is almost never the same. Indian residents are rarely onboarded under the tier-1 entity. They are onboarded under whichever licensed arm accepts Indian residency — FSCA, FSA, FSC — and that is the entity whose execution venue fired your stop out. The FCA or ASIC licence on the homepage is a group-level claim. Your account number is issued against one specific subsidiary, and that subsidiary is the one on the complaint form.

If a stop out fires at a level you think is wrong, your realistic escalation ladder is (1) broker internal complaint, (2) home regulator of the booking entity, (3) SEBI SCORES, (4) civil suit. Only step 1 is actually available to most retail traders in practice.

The Verdict

Stop out level on MT4 is a broker-configured server setting, not a platform-wide default. For an Indian resident trading through an offshore entity, the number that matters is whatever is printed in the broker's Margin Requirements document under your specific account type — Pro, Standard, Cent, Islamic, zero-spread. Find that number before you fund the account. The five brokers in our grounding — AvaTrade, Exness, FBS, FXTM, HF Markets — each set it independently, and the variance matters more than the spread comparison that dominates Indian retail forums.

The enthusiastic-nerd version is that the stop out line is the single most interesting paragraph in a retail broker's policy document. It is where the broker's B-book risk desk and the trader's risk-of-ruin meet on one number. Read the Order Execution Policy. Then read the Margin Requirements. Then trade a size that assumes the effective threshold is tighter than whatever is printed. The reader who survives her first year of offshore MT4 trading is the reader who over-estimates her liquidation distance.

FAQ

What is the default stop out level on MT4?

MT4 itself has no default. The stop out percentage is a server-side setting the broker configures and your terminal reads on login. Different brokers set different levels, and many vary the number by account type, symbol, or volatility regime. If you want the number for your specific account, the only authoritative source is your broker's Margin Requirements or Order Execution Policy document — not the MT4 help menu, not a YouTube tutorial, and not the "common answer" floating around retail forums. Check the PDF your broker filed with its licensing regulator before you fund.

Can I change the stop out level on my own MT4 terminal?

No. The stop out level is pushed from the broker's server to your terminal. The MT4 interface you see locally has no toggle for it, and any third-party EA or "tweak" that claims to override it is either a local stop-loss overlay marketed as a stop out (which is a completely different thing), a misunderstanding of how the margin engine works, or a scam. The only way to meaningfully change your effective liquidation exposure is to reduce leverage usage — smaller position size, lower lot count, wider personal stops set well before the broker's server does it for you.

Does stop out fire on the bid or the ask?

Stop out fires on the current mark-to-market value of your position, which uses the bid for long trades and the ask for shorts. During volatile moments the bid/ask spread can widen materially beyond the broker's advertised average — Exness's 1.0 pip EUR/USD standard-account average is, per its own disclosures, an average — and the tick that fires your stop out can sit several pips outside normal conditions. This is exactly why sizing tightly against the Pro-tier 0.1 pip marketing line is so genuinely dangerous for leverage-heavy accounts.

The legality question is more specific than the Reddit consensus suggests. Indian residents operating under the Liberalised Remittance Scheme can remit up to $250,000 outward per year under FEMA, with 20% TCS above ₹7 lakh under Section 206C(1G) of the Income Tax Act. Whether CFD trading on an offshore MT4 server falls inside permitted LRS purposes is where the grey area lives, and we think it is one of the few cases in this space where a CA-level review is genuinely warranted. Stop out exposure is a separate, purely mechanical question — the server will liquidate you at the configured threshold regardless of what your CA concludes about characterization.