The bridge between your chart and your broker: who runs it and what it holds
Draw your levels in one piece of software, send the order through another, and an integration sits between them. Worth knowing who operates it, whose price it shows you and which machine is holding your stop.
What is actually joining the two windows?
Linking a charting platform to a broker account moves none of your money into the charting platform. The chart stays a client.
It draws the picture, collects your instruction and hands it over a connection the broker has agreed to accept. The account, the margin, the open positions and the legal relationship all sit at the broker, exactly where they would if you had typed the order into its own terminal.
Who operates the seam?
Two companies operate that seam, and it is a commercial arrangement rather than a standard. The broker decides which order types come through the door and can change them in a release note you will never read. The charting vendor owns the surface. When something misbehaves both point at the other, and the arrangement between them is not published anywhere you can read before depositing.
Two feeds can both be right
A chart is a picture of a price, and the price came from somewhere.
Some integrations display the broker’s own stream, so the line you trade off and the quote you deal on are the same object. Others carry a feed the charting vendor sources itself, which leaves you looking at two descriptions of one instrument that were never promised to agree tick for tick.
In quiet hours nobody notices which arrangement they are on. Around a scheduled release, quotes reprice fast and the distance between what you are watching and what your broker will deal at opens up at the moment you are most likely to click. An order sent at a price the broker will not honour comes back refused, or filled elsewhere.
What happens to an order in flight?
Press the button and a sequence starts. The instruction leaves the charting client, crosses to the broker’s gateway, is checked for margin, size and market state, gets executed or refused, and an acknowledgement travels back. Normally the round trip is quick enough to feel like one event. It is still a sequence with a middle, and the middle belongs to neither window.
The gap between send and acknowledgement
Lose the connection after the send and before the acknowledgement and your screen shows nothing while the broker may already hold a position in your name.
The instinct is to click again, which is how one intended trade becomes two real ones. Open the broker’s terminal and look first.
Execution speeds get published from the moment an order arrives, and the leg before that is timed by nobody.
Where does the instruction physically live?
One question settles most of this. Is a given instruction stored on the broker’s server, or held in the software in front of you?
A market order barely raises it, being gone inside a second either way. The instructions that wait are the ones to interrogate: a limit resting away from price, a stop-loss, the second leg of a bracket, a trailing stop.
Held at the broker, an instruction survives your laptop shutting, your broadband dropping and the charting platform crashing at four in the afternoon. Held in the client, it survives none of them. A stop that is really software watching a chart on your desk works only while the desk is on, and most people find out which kind they had on the morning it matters.
| What you set | If the broker’s server holds it | If the charting client holds it | The question that settles it |
| Limit resting away from price | Works with every device off | Triggers only while the software runs | Is it in the broker’s terminal with the chart closed? |
| Stop-loss attached at the ticket | Travels with the position | May exist nowhere but that window | Does the position screen show a stop price? |
| Stop dragged on the chart later | Amended and stored with the order | Redrawn locally, old level still live | Reopen the terminal: which level shows? |
| Second leg of a bracket | One fill cancels the other | Both can stay live if the client drops | Is the cancel link held server side? |
| Trailing stop | Ratchets on the broker’s price overnight | Ratchets on the chart feed, window open | Does it move when the app is shut? |
Two possible designs, one of which applies to you. No firm is described here: which column governs a given order type belongs to your broker’s integration, varies between order types at one broker, and can change without announcement.
The part of the stack nobody tests
Costs are testable, which is why cost is what gets tested. Open the account, place the trades, read the statement, and spread, commission and overnight financing come out as numbers somebody can check. The Investors Centre opens and funds live accounts with its own money to test UK trading platforms, rather than compiling rankings from providers’ published fee schedules, which is how testing in July 2026 was able to put GBP 4.50 round turn on one broker’s sterling MetaTrader account beside USD 7 through the charting route on the same account.
Failure behaviour resists all of that, and the gap is worth naming while the price figures are still in view. Nobody schedules a disconnection halfway through submitting a live order, and the accidental version happens too rarely to reach a review, so the funded testing goes quiet exactly where the bridge sits, however much of it you do. Every route price above came off a statement. None of it is evidence of how often either route drops.
What does reconciliation look like the morning after?
Both systems keep a version of your account and only one is the record. The broker’s ledger settles, gets audited and is what any complaint would be judged against. The chart’s view is a display assembled from messages it happened to receive. When the two diverge the cause is usually dull: a size rounded for display, a partial fill collapsed into one averaged line.
Dull causes still produce expensive habits. Reconcile from the chart and an error can ride along for weeks, because the display is rebuilt from the same imperfect message stream every time you look.
The averaged line is the one to watch, since it can hide half your size filling at a level you would have refused.
What should you check before sending real size through it?
Four checks, all cheap. Place the smallest permitted trade through the chart, then find that same trade in the broker’s own terminal. Set a stop, close the charting platform completely, and confirm at the broker that the stop is still there. Ask support in writing which order types are held server side. Then ask what happens to resting orders when a session ends.
The habit that is not a check
The fifth is a habit rather than a check. Know the manual route before you need it.
The broker’s terminal, the web portal and, at some firms, a dealing desk exist for the afternoon the integration will not connect. Traders who have placed an order that way once treat that afternoon as an inconvenience. The rest treat it as an emergency, and sizing discipline is the first thing an emergency takes.
A bridge is a broker choice wearing a software badge
The charting platform is identical for everyone, which is why it dominates the conversation and explains almost none of the variation. The bridge is where firms differ. Two brokers offering the same integration can disagree about which order types are server side, which price the chart shows and what becomes of resting orders.
So the comparison worth reading is a comparison of brokers, and the part of it you care about most is the part no comparison can finish for you. Put the four checks above to the two firms on your shortlist, in writing, before either of them holds a stop of yours overnight. The replies take a week to arrive and outlast every chart layout you will ever build.
