ICT IPDA Explained: The Interbank Price Delivery Algorithm (Full Guide)

ICT IPDA — the Interbank Price Delivery Algorithm — is one of the most abstract but most important concepts in the ICT trading methodology. Most traders who hear the term get confused, file it under "advanced stuff for later," and move on. That is a mistake. IPDA is not a separate indicator or setup. It is the underlying logic that makes every other ICT concept work. Understanding IPDA is what separates traders who blindly apply rules from traders who actually understand why the rules work.

This guide explains exactly what IPDA means, how to recognize IPDA behavior on any chart, and how to use that recognition to improve your own trading.

What Is IPDA?

IPDA stands for Interbank Price Delivery Algorithm. It is the term Michael Huddleston (ICT) uses to describe the hypothesized algorithm that the major banks and institutional market makers use to "deliver" price from one level to another over time.

The core claim behind IPDA is that price does not move randomly. It moves algorithmically. Banks need to fill large orders without moving the market against themselves, which requires engineering price to specific levels where liquidity exists. The "algorithm" is not a single computer program — it is the aggregate behavior of thousands of institutional flows that collectively produce consistent, recognizable patterns.

In ICT's framing, IPDA is what actually delivers price to:

• Previous day's highs and lows (PDH/PDL)
• Weekly highs and lows
• Monthly highs and lows
• Old liquidity pools sitting above swing highs or below swing lows
• Fair value gaps and imbalances
• Order blocks from previous sessions

When price moves from one session's range to another, IPDA is doing the delivering. Every target it hits is a liquidity event. Every level it skips past is a sign that the algorithm has a different destination in mind.

Why IPDA Matters for Your Trading

The IPDA concept reframes how you look at charts. Instead of asking "which direction will price go?" you start asking "what level is IPDA delivering price to?"

This shift is more than semantic. It changes what you look for.

Traditional retail analysis looks at indicators, support/resistance, chart patterns, and tries to predict direction. IPDA-based analysis looks at where liquidity is resting — above recent highs, below recent lows, inside unfilled FVGs — and assumes price will be delivered to those liquidity pools because institutions need them.

The practical effect: you stop fighting moves that look wrong on your timeframe but make sense on a higher timeframe. A 15-minute bearish move feels like a trend, but if IPDA is clearly delivering price down to a daily order block 300 pips below, that 15-minute move is just a fraction of the larger delivery. Betting against it because "it looks extended" ignores what the algorithm is actually doing.

How IPDA Works in Practice

There is no published source code for IPDA — it is a conceptual framework, not a literal program. But the observable behavior is consistent enough to identify.

IPDA Delivers to Liquidity

Every significant price move has a destination. That destination is almost always a location where institutional size needs to be filled. In practice, this means:

• Old highs and lows where retail stops cluster
• Fair value gaps that represent inefficiencies to be rebalanced
• Order blocks where institutions left unfilled positions
• Session opens (London open, NY open) where new liquidity enters
• Quarterly shifts (weekly opens, monthly opens) that reset positioning

When you look at a chart and ask "where is price going?", IPDA-aligned analysis answers with a location, not a direction. The direction is implied by the location.

IPDA Uses Manipulation

Price does not travel directly to its target. It zig-zags, fakes out, sweeps in the opposite direction before committing. This is not noise — it is algorithmic efficiency. Sweeps generate liquidity that the algorithm needs to fill large orders. Fake-outs trap counter-trend traders whose stops become the fuel for the real move.

This is the same mechanic described by the AMD model (Accumulation, Manipulation, Distribution). AMD is the structural expression of IPDA — the three phases describe how IPDA delivers price within a single cycle.

IPDA Respects Timeframe Hierarchy

The algorithm does not work the same way on every timeframe. Daily IPDA targets override 4-hour IPDA targets, which override 1-hour targets, and so on. When a lower timeframe signal conflicts with a higher timeframe target, the higher timeframe usually wins.

This is why ICT traders always check the higher timeframe bias before taking a lower timeframe entry. The entry itself might be on a 15-minute chart, but the direction is dictated by what daily/weekly IPDA is doing.

What PD Arrays Does IPDA Use?

In ICT literature, IPDA uses a collection of reference points called a PD Array (Premium/Discount Array). These are the specific price structures IPDA uses to deliver price to its targets:

• Old Highs and Lows — external liquidity
• Fair Value Gaps — internal liquidity and imbalances
• Order Blocks — institutional origin points
• Breaker Blocks — failed order blocks that flip role
• Mitigation Blocks — order blocks that have been partially used
• Liquidity Voids — gaps in price delivery that IPDA tends to fill

When you see any of these structures on a chart, you are looking at a piece of the PD Array. IPDA uses them as waypoints, reference levels, and delivery targets.

Understanding the PD Array is what makes ICT analysis coherent. Without it, the individual concepts (order blocks, FVGs, breakers) feel disconnected. With it, you see that they are all parts of the same algorithmic system.

How to Read IPDA on Any Chart

IPDA is not something you "trade" directly. It is something you read, and then you use what you read to frame your setups.

Step 1: Identify Unfilled Liquidity

Scan your higher timeframes (daily, 4-hour) for:

• Recent swing highs and lows that have not been broken or swept
• Fair value gaps that remain unfilled
• Order blocks that have not been retested

These are potential IPDA delivery targets.

Step 2: Identify the Bias

Check the weekly and daily structure. Is IPDA in a bullish delivery (making higher highs) or bearish delivery (making lower lows)? The bias tells you which direction the algorithm is currently prioritizing.

Step 3: Map the Likely Path

Given the bias and unfilled liquidity, where is IPDA most likely to deliver price next? Example: if daily bias is bullish and the nearest unfilled liquidity is a 4-hour FVG at 1.0950 followed by a cluster of old highs at 1.1020, the likely path is to tag the FVG, then run to the highs.

Step 4: Use Lower Timeframe Setups to Enter

Once you have the likely path, use your standard setups (FVG entries, order block retests, displacement) to enter in the direction of the IPDA delivery. Your stop goes where the delivery would be invalidated. Your target is the next IPDA waypoint.

This process is what most ICT traders are doing without necessarily labeling it as "IPDA analysis." The framework just makes the logic explicit.

What IPDA Misconceptions Should Traders Avoid?

"IPDA is a specific algorithm banks use." This is the popular mythology but it is not literally accurate. No one has seen source code. IPDA is a conceptual model that describes the emergent behavior of institutional order flow. Whether there is a literal central algorithm or thousands of independent ones producing the same effect is unknowable — the behavior is what matters.

"IPDA makes trading deterministic." It does not. IPDA tells you where liquidity is and where price is likely to go. It does not tell you exactly when or by what path. Trading is still probabilistic, and plenty of IPDA setups fail.

"You need to memorize all of ICT to understand IPDA." Not true. The core concept is simple: price is delivered to liquidity. Everything else — PD arrays, order blocks, FVGs, breakers — are just the specific tools IPDA uses. You can understand the concept in a paragraph, even if mastering it takes years.

"IPDA only works on forex." It works on any liquid market with institutional participation. Forex is the clearest example because the interbank market is literally the context for the term. But IPDA-type behavior is visible on index futures, crypto majors, and large-cap stocks too.

How Is IPDA Different From Random Walk?

The IPDA framework directly contradicts the efficient market hypothesis and the random walk theory. In academic finance, price movements are treated as largely unpredictable. In ICT, price movements are treated as deliberate deliveries toward specific targets.

Which is right? The honest answer is that both capture part of the truth. Over long timeframes and on average, markets appear random to many statistical tests. Over shorter timeframes and at specific structural levels, institutional flows create patterns that look deterministic.

IPDA is most useful as a framework for decision-making rather than as a claim about underlying reality. You do not need to believe there is a literal algorithm pulling the strings. You just need to use IPDA thinking to identify where institutional size is concentrated, and trade with that awareness.

How Do You Read IPDA in Practice?

When you sit down to analyze a chart, ask these questions:

1. Where is the nearest unfilled liquidity on the daily timeframe? (Old high, old low, FVG, order block)
2. What direction is IPDA currently delivering? (Daily trend, weekly bias)
3. What PD Array structures are in the way? (Intermediate FVGs, OBs that might cause reactions)
4. Has recent price action respected or violated IPDA targets? (If violated, the bias may be shifting)
5. Where is the logical delivery path? (First to this, then to that)
6. Which lower-timeframe setup fits inside that delivery path? (Your actual entry)

Running this checklist before every trade forces you to think like the algorithm, not against it.

Final Takeaway

ICT IPDA is not a setup, not an indicator, and not a signal. It is a framework for thinking about why price moves. Every other ICT concept — order blocks, FVGs, liquidity sweeps, the AMD model — is either a tool IPDA uses or a side effect of its behavior.

Traders who understand IPDA stop looking for "the next move" and start looking for "the next delivery target." That shift is what makes the difference between reactive trading and anticipatory trading.

You do not need to believe the literal algorithm exists to use the framework. You just need to accept that price is not random, liquidity matters, and institutional flows leave repeatable patterns. From there, everything in ICT makes more sense.

For the structural framework that expresses IPDA delivery, see the AMD model / Power of 3 guide. For the specific PD array tools IPDA uses, see fair value gaps and order blocks. For the liquidity mechanics that motivate every IPDA delivery, see how liquidity sweeps work.