Forex Data Feed Explained: Prices, Ticks, Slippage & Execution

Illustration of forex data feeds flowing from liquidity providers and market venues through broker pricing to a EUR/USD trading platform.

Open EUR/USD at two forex brokers at exactly the same moment and you may see two slightly different prices. Which one is the real market price?

In spot forex, that question has no simple answer. There is no single centralized exchange producing one universal EUR/USD quote. Instead, trading is fragmented across dealers, liquidity providers and electronic venues, while brokers can receive, aggregate and distribute prices in different ways.

That means the price on your trading platform is not simply “the forex market.” It is a view of the market delivered through your broker’s particular pricing infrastructure.

That distinction matters once you start trading. It helps explain why prices can differ between brokers, why a MetaTrader Depth of Market is not necessarily the global FX order book, why a tick does not always represent a trade, and why the price you see when you click Buy or Sell may not be the price at which your order is ultimately executed.

We spent years working inside retail forex brokerages, where disputes over prices, slippage and execution were part of the job. So in this article, we are going to follow a forex price from the moment it enters a broker’s data feed to the moment it becomes an execution on a trader’s account.

What Is a Forex Data Feed?

A forex data feed is a stream of pricing and other market information transmitted from one system or market participant to another.

That definition is deliberately broad because the term can refer to different points in the pricing chain.

A forex broker, for example, may receive a price feed directly from a bank, non-bank liquidity provider, trading venue, Prime of Prime or dedicated market-data provider. The broker can then use one or several of those feeds to construct the prices it distributes to its own clients.

For most retail over-the-counter (OTC) forex trading, the information traders ultimately see revolves around continuously updated Bid and Ask quotes.

The Bid is the price at which you can sell, while the Ask is the price at which you can buy. The difference between them is the spread in forex.

Inside the Feed

What Can a Forex Data Feed Contain?

A data feed can carry considerably more than a single price. What is actually available depends on the source, instrument, market structure and type of feed.

01 · Updates

Tick Data

Individual updates to Bid, Ask or other available fields. A new tick means the incoming market data changed—it does not necessarily mean that a trade occurred.

Price updates

02 · Depth

Depth of Market

Additional Bid and Ask levels and, when the source provides them, quantities available at those prices. OTC depth does not necessarily represent the entire FX market.

Price levels + possible size

03 · History

Historical Data

Previously recorded ticks, quotes and bars that can be used to reconstruct price history, build charts or analyze past market behavior.

Stored market data

04 · Transactions

Trade & Volume Data

Information about completed transactions and their volumes, where the underlying venue or data source actually provides those records.

May be unavailable in OTC FX
FINANSIFIED · finansified.com

MetaTrader documents that OTC instruments can operate using streams of Bid and Ask quotes without data about actual executed deals. A changing EUR/USD quote therefore does not necessarily mean somebody has just traded EUR/USD at that price.

Where Do Forex Brokers Get Their Prices?

This is where a forex data feed becomes more interesting than simply a stream of numbers.

Banks, non-bank market makers and other participants in the foreign exchange market continuously generate, distribute or consume FX prices. A broker can connect to one or several of these sources and receive their prices electronically.

These incoming prices are themselves forex data or price feeds.

FXCM Pro, for example, describes liquidity providers streaming executable buy and sell prices to its systems through direct feeds. Its pricing engine then compares those incoming prices and selects the best available buy and sell prices. Cboe FX similarly distributes market-data feeds containing bids and offers contributed by participants on its own FX venue.

From Market to Screen

How a Forex Price Reaches a Retail Trader

A retail quote can be the end product of several upstream pricing relationships. The exact architecture varies by broker, but a simplified chain can look like this.

Possible Upstream Sources

Liquidity Providers Banks, non-bank market makers and other counterparties
Trading Venues Electronic venues and other sources of market pricing
Data Providers Reference or market-data feeds that may not be executable
incoming market-data / price streams

Broker Pricing Layer

Aggregation & Pricing where applicable

The broker may compare or combine several incoming feeds, select prices and apply its own pricing rules before publishing quotes to clients.

client-facing Bid / Ask quotes

Distribution

Trading Server & Platform

The client-facing quote stream is distributed through the broker's trading infrastructure and displayed in a platform such as MetaTrader.

Trader Sees the downstream client quote
FINANSIFIED · finansified.com

Not every broker uses exactly this architecture. A firm might rely on one pricing source, aggregate several liquidity providers, purchase a reference feed from a market-data vendor, generate its own client prices from external inputs, or use some combination of these approaches.

There is another important distinction hiding here: a price feed does not automatically mean executable liquidity.

Some feeds contain prices at which the provider is willing to transact, while others may be supplied primarily as market data or reference pricing. What matters for execution is not simply whether a price appeared somewhere in a feed, but whether that price was actually available to the broker for the relevant quantity and under the applicable trading relationship.

This is our first clue that the number appearing on a trader’s screen is only the end of a longer pricing chain.

And it leads to an obvious question:

If two brokers can receive different feeds and construct their client prices differently, should their EUR/USD quotes always be identical?

Why Can Forex Prices Differ Between Brokers?

Suppose Broker A shows EUR/USD at 1.08714 / 1.08716, while Broker B shows 1.08715 / 1.08717.

Which broker has the correct price?

Potentially, both.

Unlike a stock traded on one centralized exchange, spot forex is an over-the-counter market fragmented across dealers, liquidity providers and trading venues. BIS research describes customers as being able to access executable price streams from multiple liquidity providers and numerous electronic venues rather than one consolidated marketplace.

That means Broker A and Broker B do not necessarily begin with exactly the same inputs.

One may receive prices from a different group of liquidity providers. Another may aggregate several feeds, use a different venue, or apply different pricing arrangements before publishing its client quotes. Even two brokers ultimately referencing the same broader market can therefore show slightly different Bid and Ask prices at the same instant.

The differences may become more noticeable when liquidity is thin or prices are changing rapidly.

Economic releases can produce particularly fast repricing because markets react not simply to the number itself, but to how new information changes expectations about growth, inflation and monetary policy.

This is also why comparing your broker with a quote on a financial website can be misleading. The two prices may come from different sources, represent different liquidity pools, or even have different characteristics in terms of whether they are executable or merely indicative.

So a difference between two forex price feeds does not, by itself, prove that either price is wrong or manipulated.

That does not mean every discrepancy should be dismissed. A large, persistent or unusual divergence may justify asking where the broker’s prices come from and examining its execution policy and tick history.

But the starting point is important:

there is no single consolidated EUR/USD quote that every retail forex broker is required to reproduce tick for tick.

Once you understand that, another familiar feature of retail platforms becomes more interesting.

If MetaTrader shows a Depth of Market, whose market depth are you actually looking at?

Order Book and Depth of Market

Open the Depth of Market (DOM) window in MetaTrader and you will see Bid and Ask prices arranged vertically around the current market price.

It looks like an order book.

But what exactly are you looking at?

That depends on the instrument.

An order book records buying and selling interest at different price levels. Buy limit orders form the Bid side of the book; sell limit orders form the Ask, or offer, side. The highest Bid and lowest Ask sit closest to the current market.

On a centralized exchange, this distinction is fairly intuitive. MetaTrader documents that for instruments traded in exchange mode, its DOM can display real prices and order volumes submitted by market participants to the exchange.

Retail spot forex is different.

A Forex DOM Is Not the Global FX Order Book

Spot FX does not have one consolidated exchange where every EUR/USD order is submitted.

Instead, the market is fragmented across dealers, electronic venues, liquidity providers and other trading relationships. Some parts of the institutional market do operate central limit order books—EBS Market and Refinitiv Matching have historically been important examples—but those are only parts of a much larger decentralized market.

So when you open a retail broker’s EUR/USD DOM, you are not seeing every Bid and Ask available across the global foreign-exchange market.

MetaTrader explicitly says that for an OTC instrument, the DOM can instead be constructed from quotes supplied by the broker. The broker may provide different prices for different transaction sizes, depending on the data and liquidity available through its own arrangements.

That makes the terminology slightly deceptive if it is interpreted too literally.

The DOM is the display.

What lies underneath that display may be:

  • actual exchange orders and volumes;

  • broker-provided OTC prices and available quantities;

  • or simply calculated price levels around the current Bid and Ask.

Those are very different things.

What Does an Empty Volume Column Mean?

This leads to another common temptation.

Suppose MetaTrader shows several price levels but no corresponding volume. Can you conclude that the broker is B-booking your trades, acting as your counterparty or inventing the prices?

No.

MetaTrader provides a much simpler explanation. If an OTC broker does not transmit volume information, the platform can generate additional price levels from the current Bid and Ask using the instrument’s minimum price increment. In that configuration, the DOM functions mainly as a convenient order-entry interface rather than a view of actual executable market depth.

An empty volume column therefore tells you something quite narrow:

the platform has not received volume information for those displayed levels.

It does not, by itself, tell you whether the broker:

  • internalizes your order;

  • hedges it externally;

  • routes it to a liquidity provider;

  • acts as principal;

  • or uses some combination of these models.

Those questions require other evidence—such as the broker’s execution policy, disclosures and actual order-routing arrangements.

The more interesting case is when real quantities are available.

Because even then, seeing EUR/USD offered at 1.08714 does not necessarily mean you can buy any amount you want at 1.08714.

To see why, imagine trying to buy €80 million when only €4 million is available at the best Ask.

How a Large Order Can Consume Several Price Levels

Suppose EUR/USD is showing a best Ask of 1.08714.

You want to buy at that price. But there is a catch: only €4 million is available there, while your order is for €80 million.

Can the entire order fill at 1.08714?

No—not if the displayed quantities represent the liquidity actually available to your order.

Worked Example

What Happens When Your Order Is Larger Than the Best Offer?

EUR/USD is offered at 1.08714—but only €4 million is available at that price. Follow an €80 million market buy through the available Ask levels.

Can the full €80 million order fill at 1.08714?

No—not if these displayed quantities represent liquidity actually available to the order. The order has to move through successive offers until the full quantity is filled.

Ask price Available quantity
1.08714 €4 million Filled · €4m @ 1.08714
1.08715 €12 million Filled · €12m @ 1.08715
1.08716 €13 million Filled · €13m @ 1.08716
1.08717 €51 million Filled · €51m @ 1.08717
Completed Order
Best Ask 1.08714
Total filled €80 million
Average execution price 1.087163875

The lesson: the best quoted price tells you where available liquidity begins. It does not necessarily mean your entire order can be executed at that price.

Illustrative example: actual OTC FX depth depends on the venue, liquidity source and broker. Displayed depth may represent only the liquidity visible through that particular source rather than the entire FX market.

FINANSIFIED · finansified.com

MetaTrader documents the same general mechanism: when the required quantity is larger than a single available offer, an order can be filled from several offers closest to the market, depending on the execution and fill policy being used.

Worked Example · Step 2

What Was the Average Execution Price?

Our €80 million order filled at four different Ask prices. To find the actual average execution price, each fill price must be weighted by the quantity executed there.

€4m @ 1.08714 5% of order
€12m @ 1.08715 15% of order
€13m @ 1.08716 16.25% of order
€51m @ 1.08717 63.75% of order
Execution price Quantity Price × quantity
1.08714 €4m 1.08714 × 4 = 4.34856
1.08715 €12m 1.08715 × 12 = 13.04580
1.08716 €13m 1.08716 × 13 = 14.13308
1.08717 €51m 1.08717 × 51 = 55.44567
Quantity-Weighted Average Execution Price
Step 1

Add the weighted prices: 4.34856 + 13.04580 + 14.13308 + 55.44567 = 86.97311

Step 2

Divide by the total quantity: 86.97311 ÷ 80

Execution Result
Best Ask 1.08714 Where the order started
Average fill 1.087163875 ≈ 1.08716
Difference from best Ask 0.23875 pip ≈ 0.24 pip

Where did the average price land?

1.08714 Best Ask
1.087163875 Average fill
1.08717 Final level

Why is the average so close to 1.08717? Because €51 million—or 63.75% of the entire order— filled at that price. A weighted average gives much more influence to the price where most of the quantity was executed.

FINANSIFIED · finansified.com

Nothing mysterious happened. The displayed best price simply did not contain enough quantity to satisfy the entire order.

This illustrates an important distinction:

The best quoted price tells you where liquidity begins—not necessarily the price at which your entire order can be executed.

For ordinary retail-sized orders, available quantity at the best price may be more than sufficient. And in retail OTC forex, the depth shown by a platform may not correspond to a transparent institutional order book in the first place.

But the principle becomes important later, when we discuss slippage: the price visible when an order is submitted and the average price ultimately obtained are not necessarily the same thing.

Before we get there, however, we need to clarify what causes those prices on the screen to update in the first place.

That brings us to ticks.

What Are Ticks in Forex Trading?

Every time the price on your trading platform updates, you are looking at the result of a new tick.

A tick is simply a new market-data update received by the platform. In retail OTC forex, that most commonly means a change in the Bid, the Ask, or both.

Suppose EUR/USD changes from:

1.08714 / 1.08716

to:

1.08715 / 1.08717

That second quote is a new tick.

But here is the important part:

a new forex tick does not necessarily mean that a trade just occurred at that price.

MetaTrader distinguishes OTC instruments from exchange-traded instruments. For OTC symbols, the platform may receive only Bid and Ask quote streams, without data on actual executed deals. By contrast, exchange instruments can also contain Last prices and real transaction volume.

This is why historical forex tick data should be interpreted as a record of quote updates, not automatically as a tape of completed transactions. Tick-level data also becomes important when testing automated trading strategies, particularly when a strategy is sensitive to spreads, execution delays or very small price movements.

A Tick Is Not the Same as Tick Size

The terminology becomes confusing because traders often use tick and tick size as though they mean the same thing.

They do not.

A tick is an incoming market-data event.

Tick size is the minimum price increment by which an instrument is allowed to move. MetaTrader stores this separately as SYMBOL_TRADE_TICK_SIZE, which its documentation defines as the instrument’s minimum price change.

For example, if an instrument can move from 1.08714 to 1.08715 but cannot be quoted between those two values, its tick size is 0.00001.

So:

Tick = a new update

Tick size = the smallest permitted price step

That distinction matters because defining a tick simply as “the smallest possible price movement” describes tick size, not the market-data update itself.

What Is Tick Volume?

There is one more similar-sounding term: tick volume.

Tick volume measures the number of ticks received while a price bar is forming.

If a five-minute candle contains 800 ticks, that means the platform received 800 market-data updates during those five minutes.

It does not mean that 800 lots, contracts or any other fixed quantity of currency changed hands.

MetaTrader explicitly separates tick volume from real volume. Real volume represents the amount actually traded and may not be available for OTC instruments at all.

That distinction is especially important in spot forex, where there is no single exchange recording every EUR/USD transaction worldwide.

So when a retail forex chart shows high tick volume, what it is really telling you is:

the broker’s feed was updating frequently.

It is not giving you consolidated global FX trading volume.

Ticks may sound like a small technical detail, but they connect directly to execution. If the market can update several times between the moment you click Buy and the moment your order is processed, the price available at execution may already be different.

That is where slippage begins.

Execution Walkthrough

What Is Slippage in Forex Trading?

The quote you see when you click Buy and the price available when your order is actually executed do not have to be identical. Follow a market buy through a simple EUR/USD example.

EUR/USD Quote on Screen
Bid 1.08714 Sell side
Ask 1.08716 Your starting price for this buy
1 You see the quote The displayed Ask is 1.08716.
2 You submit the order The market-buy instruction enters the execution process.
3 The available price can change The Ask at execution may differ from the quote you saw.

Before Execution

The available Ask changes

Choose what happens to the Ask before the market order is filled.

Displayed Ask 1.08716
Execution Price
Slippage
Negative Slippage Worse execution than expected

For this buy order, negative slippage means the execution price is higher than the Ask displayed when the order was submitted.

Positive Slippage Better execution than expected

For this buy order, positive slippage means the execution price is lower than the Ask displayed when the order was submitted.

FINANSIFIED · finansified.com

Slippage itself is therefore not evidence that something improper happened. It is a possible consequence of trying to execute an order in a market whose prices continue changing while that order is being processed.

The NFA describes precisely this problem in its guidance for U.S. retail forex dealers: price slippage can occur between the time a customer submits an order and the time the order reaches the dealer’s system. Dealers may then requote the customer or execute within predefined slippage parameters.

Slippage tends to become more noticeable when prices are moving quickly, liquidity is thin, an order is large relative to available liquidity, or execution takes longer. For short-term traders, these effects matter because spreads, commissions, slippage and other trading costs can consume an otherwise small statistical edge.

We have actually encountered one of those mechanisms already.

In our €80 million example, there simply was not enough liquidity at the best Ask to fill the entire order. Most of the trade had to execute at higher prices. The result was an average execution price above the best quote.

For a small retail order, time rather than size may be the more important source of the difference: by the time the order is processed, the quote may have changed.

But there is another complication.

The Same MetaTrader Platform Can Execute Orders Differently

Seeing the MetaTrader logo does not tell you exactly how your order will be handled.

MetaTrader 5 supports four execution modes: Instant, Request, Market and Exchange Execution, and the broker determines which mode applies to each instrument.

Consider two of them.

Under Instant Execution, the order contains the current requested price. If the price moves beyond the permitted deviation while the request is being processed, the server can reject that price and return a requote with a new one.

Under Market Execution, the trader instead submits an instruction to trade at the price available through the broker’s execution process. MetaTrader describes submission of such an order as advance consent to execution at the resulting price rather than requiring the previously displayed quote to be honored.

So even on the same trading platform, the journey can differ:

  1. Displayed quote
  2. Order submitted
  3. Order processed
  4. Execution price

The displayed price is the starting point. It is not necessarily a guarantee of the eventual fill.

That still does not give a broker unlimited discretion.

If prices can move against the trader during execution, an obvious question follows:

What happens when the price moves in the trader’s favor?

That distinction turns out to be important—because regulators have taken action against brokers that treated positive and negative slippage differently.

Broker-Specific Execution Delays and Price Checks

The basic slippage example makes execution look simple. Quote changes, order reaches the broker, order fills at the new price. In practice, another layer can sit between receiving the order and deciding which price can be used for execution.

We know this from first-hand experience.

At some retail forex brokers we worked with, the trading infrastructure included server-side execution rules aimed at very short-duration or latency-sensitive trading. Depending on the configuration, an order could be held briefly or the system could wait for additional incoming price updates before deciding which price was valid for execution.

In some configurations we encountered, the delay could be defined by time. In others, it could effectively depend on receiving one or more subsequent ticks.

So the sequence might look more like this. First a client submits an order, the broker receives the execution request, then it goes through price/execution checks, then one or more new ticks may arrive and only then the order is processed.

This matters because the market can continue moving during that interval.

Suppose a trader submits a Buy order when the Ask is 1.08716. If several new quotes arrive before the broker’s execution logic completes its checks, the relevant price may no longer be 1.08716.

That can contribute to a difference between the price the trader saw and the eventual execution price.

But the qualification here is crucial:

These were broker-specific practices we encountered. They are not universal rules of MetaTrader or forex execution.

Different brokers can use different bridges, liquidity arrangements, pricing engines, execution plugins and internal controls. Even two brokers using MetaTrader may therefore process similar orders differently.

Regulatory guidance provides some useful context. The NFA expressly recognizes that retail forex dealers may use disclosed slippage parameters and requoting practices when the price has changed between order submission and arrival at the dealer’s system. It also requires electronic trading systems to have sufficient integrity and says slippage should reflect genuine market conditions rather than being configured to systematically disadvantage the customer.

Is This the Same as “Last Look”?

Not necessarily.

A related concept exists in institutional electronic FX called last look. Under the current FX Global Code, a liquidity provider using last look has a final opportunity to accept or reject a trade request against its quoted price. The Code says this should be used as a risk-control mechanism for validity and/or price checks, and that firms should disclose how the process works.

A price check can ask whether the requested price is still consistent with the price currently available to the client. A validity check can address operational factors such as whether the trade request is valid and sufficient credit is available.

That sounds superficially similar to some of the price-validation logic we encountered inside retail brokerages, but we should not collapse the two concepts.

A retail broker waiting for additional ticks or applying an execution delay is not automatically using “last look.”

The contractual relationship, technology and purpose may be different.

The broader lesson is simpler:

An order reaching a trading server does not necessarily mean it is instantly executed against the first price visible at that moment.

There may be additional execution logic in between.

And once brokers are allowed to use slippage tolerances, requotes or other execution controls, an important question follows:

Are those rules applied the same way when the market moves in the trader’s favor as when it moves against them?

Slippage Parameters, Requotes and Fair Treatment

Suppose you click Buy at 1.08716.

By the time your order reaches the broker’s system, the market has moved.

What should happen next?

There is no single universal answer. Depending on the broker and execution model, the order might be filled at the new price, executed within a predefined tolerance, rejected, or returned to the trader as a requote.

U.S. NFA guidance explicitly recognizes both requoting and slippage parameters. A broker may, for example, define a range within which an order can still be executed even though the market has moved since it was submitted.

The existence of such a tolerance is not, by itself, the problem.

The crucial question is what happens in both directions.

Imagine the trader submits a Buy order at 1.08716 and, before execution, the market moves by 0.2 pip.

There are two possibilities:

If the ask rises to 1.08718 , it is worse for the trader

IF the ask falls to 1.08714, it is better for the trader

An execution system should not be deliberately configured so that the trader routinely receives the first outcome while the broker prevents them from receiving the second.

That is asymmetric slippage.

The NFA requires Forex Dealer Members using slippage parameters to apply them uniformly regardless of which direction the market moves. It also says slippage should reflect real market conditions rather than an execution setting designed to favor the dealer.

This is not merely theoretical.

In one NFA case, FXDD used an execution setup under which sufficiently favorable market movements for customers could cause orders to be rejected, while equivalent movements unfavorable to customers did not receive the same treatment. NFA concluded that the asymmetric practice disadvantaged customers and required the firm to correct its parameters.

An even larger example involved FXCM.

According to a 2011 CFTC order, customers experienced negative slippage when prices moved against them but did not consistently receive the benefit when prices moved in their favor. The CFTC found that this affected more than 57,000 customers and deprived them of approximately $8.26 million in favorable price movements.

The distinction is therefore important:

Slippage can be a normal consequence of a moving market.

Asymmetric slippage can be an execution-practice problem.

European regulators have examined the same issue. ESMA’s CFD guidance specifically asks supervisors to assess whether firms use execution technology or configurable tools that permit systematic asymmetric slippage, as part of their best-execution oversight.

So when a trader receives a worse price than the one displayed when the order was submitted, the right question is not simply:

“Was there slippage?”

A better set of questions is:

  • Did the underlying market actually move?

  • What execution mode and slippage parameters applied?

  • Would the same rules have applied if the price had moved by the same amount in the trader’s favor?

  • Does the broker disclose how requotes and slippage are handled?

  • Are comparable orders treated consistently?

That leads to a more useful conclusion than either extreme.

A different execution price does not automatically mean the broker cheated you—but “slippage is normal” is not a blanket excuse for every execution outcome.

Does Slippage Mean Your Broker Cheated You?

You clicked Buy at 1.08716 and were filled at 1.08722.

Was the broker cheating you?

That single fact is not enough to know.

A different execution price can result from ordinary market movement, limited liquidity, transmission latency, the broker’s execution mode, or the rules governing how the order is processed. NFA guidance explicitly recognizes that the price available when an order reaches a dealer’s system may differ from the price shown when the customer submitted it.

But traders should not simply accept every explanation involving the word slippage, either.

If an execution looks unusual, you shouldn’t be asking: 

“Did I get slippage?”

What you should be asking instead:

“Does the execution make sense given what happened in the market and how this broker says it handles orders?”

A sensible investigation would look at:

  1. The timestamps. When was the order submitted, received and executed?

  2. The tick history. How did the broker’s Bid and Ask actually move during that interval?

  3. Liquidity and volatility. Was the market moving rapidly, trading thinly, or reacting to important news?

  4. The execution mode. Was this Market Execution, Instant Execution, a stop order, or another order type with different rules?

  5. The broker’s execution policy. What does it disclose about slippage, requotes, gaps and price validation?

  6. Symmetry. Does the same system allow favorable price improvements, or do execution differences consistently work against clients?

  7. Consistency. Were comparable orders handled in the same way?

That last pair is especially important. Regulators have not treated “the market moved” as a universal defense. NFA rules require slippage settings to reflect real market conditions and to be applied uniformly regardless of the direction of the price move.

And there are documented cases where the problem was not slippage itself but how the execution system treated it. The CFTC found, for example, that FXCM customers suffered unfavorable slippage while not consistently receiving corresponding favorable price improvements.

So the useful distinction is:

A worse fill is evidence that execution differed from the displayed quote. It is not, by itself, evidence of misconduct.

To determine whether something more serious happened, you need the surrounding market data, timestamps and the broker’s actual execution rules.

That distinction becomes even more important when prices do not move smoothly from one level to the next at all.

Sometimes the market simply gaps.

Worked Example

What Happens to a Stop Order When the Market Gaps?

A stop can trigger even when no executable price existed at the stop level itself. Watch what happens when EUR/USD jumps over a Buy Stop after a major announcement.

Current EUR/USD Ask 1.08720 The market is still below the pending order.
Buy Stop 1.08750 The stop level sits above the current Ask.

EUR/USD Price Path

The important question is not whether the chart crosses the stop visually, but whether an executable price was actually available there.

Last Ask 1.08720
Buy Stop 1.08750
Next Ask 1.08800
Before the announcement, quoted prices might progress incrementally: 1.08720 → 1.08721 → 1.08722 → …
The next Ask in this example is 1.08800 .
No executable Ask shown between 1.08720 and 1.08800
What Just Happened?
Last quoted Ask 1.08720
Buy Stop threshold 1.08750
Next available Ask 1.08800
Stop level 1.08750
Illustrative execution 1.08800
Difference +5.0 pips

The market jumped from a quoted Ask of 1.08720 to 1.08800 in this simplified example. The Buy Stop threshold of 1.08750 was therefore crossed, but that does not mean liquidity existed at 1.08750.

Once the Buy Stop is triggered, the resulting buy operation is subject to the applicable execution process. If 1.08800 is the next valid executable Ask, an execution there would be 5.0 pips above the stop level.

FINANSIFIED · finansified.com

What We Saw Inside Retail Brokerages

There is another layer that traders generally cannot see from the terminal.

At some of the retail forex brokers we worked with, unusually large price jumps could trigger additional price-validation logic before the new level was accepted for execution.

The system would not necessarily treat one isolated quote far away from the previous market as immediately trustworthy.

Instead, that incoming price could initially be treated as potentially anomalous.

For example:

1.08720 → 1.08800

Rather than immediately accepting 1.08800 as an established new market level, some systems we encountered could wait for additional incoming ticks around that area:

1.08800 → 1.08802 → 1.08798

Once subsequent quotes indicated that the market really had moved into the new range, the system could begin treating prices around that level as valid for execution.

Under those particular configurations, the first isolated tick after a large jump would therefore not necessarily trigger or execute every affected customer order immediately.

This is where descriptions such as executing at the “first market prices after the gap” could become more complicated than they initially sound.

This Is Not a Universal Forex Rule

This distinction is important enough to state explicitly.

We encountered this price-validation behavior at particular retail brokers. It is not a universal MetaTrader rule, nor are we claiming that every broker or liquidity provider handles gaps this way.

MetaTrader’s standard documentation does not prescribe a rule requiring brokers to wait for several confirming ticks after a gap. Its documented mechanics are considerably simpler: once the relevant stop condition is reached, the corresponding market operation is generated and execution takes place according to the applicable prices and execution rules.

A broker may, however, have additional infrastructure around that process, including:

  • quote aggregation;

  • liquidity bridges;

  • stale-price filters;

  • price-tolerance rules;

  • sanity checks;

  • execution plugins;

  • and broker-specific risk controls.

The exact behavior therefore depends on the broker’s technology, liquidity relationships, execution policy and regulatory obligations.

Price validation itself is not unique to retail brokerage systems. In institutional electronic FX, the FX Global Code recognizes last look, under which a liquidity provider may perform validity and price checks before accepting or rejecting a trade request. The Code describes the price check as assessing whether the requested price remains consistent with the current market price.

That does not mean the retail-broker process we encountered was necessarily last look. The mechanisms and trading relationships can be different.

The broader point is simply that electronic FX systems may perform additional checks before treating an incoming price as executable.

Why the “First Price” After a Gap Can Be Ambiguous

This explains a dispute we encountered frequently in brokerage environments.

A trader looks at historical tick data and says:

“There was a quote at 1.08800. My order should have been executed at 1.08800.”

But the appearance of a price in a historical feed does not, by itself, prove that every order could have been executed at that price.

Several questions still matter:

  • Was the quote considered valid by the broker’s pricing system?

  • Was it executable or merely indicative?

  • How long did it remain available?

  • Was sufficient liquidity available?

  • Had the order reached the execution stage yet?

  • Were additional price-validation rules applied?

  • What does the broker’s execution policy say about gaps, stale prices and erroneous quotes?

That leads to one of the most important distinctions in this entire article:

A price appearing in a data feed is evidence that the price was quoted. It is not automatically proof that a particular customer order could have been executed there.

The big takeaway

What Traders Should Take From This

Most of the confusion around forex prices, ticks, slippage and execution comes from treating several different layers of the trading process as though they were the same thing.

The central distinction

Seeing a price is not the same thing as being able to execute any order at that price.

Think of the process as three separate layers:

1

Market Data

Tells you what prices and other information are being transmitted through the broker's pricing arrangements.

2

Liquidity

Determines what quantity may actually be available at those prices when an order needs to be filled.

3

Execution

Determines what happens after you submit an order and which price ultimately becomes your fill.

Different price does not automatically mean wrong price.

Two brokers can show slightly different EUR/USD quotes because they may receive, aggregate or construct their prices differently. A MetaTrader DOM may also represent only the depth supplied through that broker rather than the global FX market.

A quote or tick does not automatically prove executability.

A tick may simply be a quote update, while an order can fill away from the price first displayed because liquidity changed, the market moved, or execution occurred after that quote was no longer available.

If an execution looks wrong, investigate the evidence.

Do not stop at the screenshot of the price you remember seeing. Reconstruct what actually happened around the order.

Tick history
Order timestamps
Execution mode
Liquidity conditions
Execution policy

The mental model to remember

Market data tells you what the broker is showing. Liquidity determines what may actually be available. Execution rules determine what happens when you try to trade it.

Knowledge Check

How Well Do You Understand Forex Data and Execution?

Ten questions covering price feeds, market depth, ticks, liquidity, slippage and gap execution.

Question 1 of 10 Score: 0

Question 1

Quiz Complete

0/10

References 8 sources · documentation, research and regulatory material

The article draws on platform documentation, institutional FX research, regulatory guidance and enforcement records. First-hand brokerage experience is identified separately rather than presented as a universal industry rule.

  1. MetaQuotes Platform Documentation

    MetaTrader 5 Help — Price Data

    Primary platform documentation for Bid, Ask and Last prices, OTC quote streams, exchange data, tick volume and the distinction between real transaction volume and OTC pricing.

    View source
  2. MetaQuotes Platform Documentation

    MetaTrader 5 Help — Depth of Market

    Documents the difference between exchange and OTC Depth of Market, broker-supplied OTC quotes and volumes, and how larger orders can consume liquidity across several price levels.

    View source
  3. MetaQuotes Platform Documentation

    MetaTrader 5 Help — Executing Trades

    Supporting documentation for execution modes, market orders, pending orders, stop triggers, fill policies, requotes and the possibility that execution can differ from a requested or triggering price.

    View source
  4. BIS 2025

    The FX Trade Execution Landscape Through the Prism of the 2025 BIS Triennial Survey

    Institutional evidence for the decentralized and fragmented structure of spot FX, multiple venues and liquidity providers, executable streaming prices and the role of liquidity aggregators.

    View source
  5. NFA Regulatory Guidance

    Compliance Rule 2-36(e): Supervision of the Use of Electronic Trading Systems

    U.S. regulatory guidance covering electronic forex execution, slippage and requotes. It states that slippage should reflect real market conditions and addresses consistent treatment of favorable and unfavorable price movements.

    View source
  6. CFTC 2011 Enforcement

    Forex Capital Markets LLC — Slippage Enforcement Action

    Real-world enforcement example involving more than 57,000 customer accounts. The CFTC found that customers did not consistently receive favorable price movements while unfavorable slippage was passed through.

    View source
  7. GFXC December 2024

    FX Global Code

    Current wholesale-FX good-practice framework. Relevant here for electronic execution, transparency and the use of validity and price checks within last-look processes.

    View source
  8. ESMA 2017 · Historical Guidance

    Q&A on CFDs and Other Speculative Products Under MiFID

    Historical European supervisory guidance discussing execution quality, asymmetric slippage, timestamps, bridges and plugins, and practices that can disadvantage retail CFD and rolling spot-forex clients.

    View source

Sources reviewed September 2026.

Ready to analyze the macro behind your pairs like institutions do?

Explore how inflation, growth, policy rates, liquidity, confidence, and Taylor Rule benchmarks shape economies behind FX pairs and influence their behaviour. The BETA is live NOW!