Most brokers quote major pairs with five decimal places (three for JPY pairs). The extra digit is a fractional pip, also called a pipette or point.
What it means:
EURUSD at 1.10235: the pip is the fourth decimal (3), the fractional pip the fifth (5).
1 pip = 10 points in MT4/MT5.
A 20-point stop is 2 pips, not 20.
Common confusions:
EA settings in points vs pips — a stop of "50" may mean 5 pips.
Spread indicators showing points instead of pips.
Different conventions for gold, indices and crypto.
Writing all risk calculations in one unit, and noting which one, prevents expensive mistakes.
For gold, indices and crypto, a "pip" has no universal definition. Checking the tick size and tick value in the symbol specification is the only reliable way to calculate risk on these instruments.
Do you work in pips or points, and have you ever mixed them up?
I work in pips on majors and force every EA input through a single conversion note at the top of the file. The one time I left a stop of 50 meaning points on a five digit feed, the live stop was 5 pips and the backtest had been running 50 pips, which is an expensive kind of silence.
Gold is where the language falls apart. Tick size and tick value from the symbol spec are the only numbers I trust, and I write risk in account currency rather than inventing a gold pip.
Spread widgets that display points have fooled me on a quick glance more than once. I renamed the label to show pips only so I stop translating under pressure.
For indices I do the same: money risk first, then lots from tick value. Mixing conventions across symbols was the habit that took longest to break.
Have you standardised on one unit across FX and metals, or do you keep separate journals so the words never collide? I tried the separate journal route and still mixed them on a tired Friday.
One case that trips EAs even after the units are sorted is tick size that differs from point size. On one feed a cross was quoted to five decimals but only moved in steps of 0.00005, so a stop calculated at 1.10232 was rejected as an invalid price.
The fix was rounding every price to the symbol's tick size before sending, not to the point. It is one line of code, but I only found it after a morning of silent order rejections in the journal.
Gold has the same issue in a different form. Two brokers I compared quoted it with two and three decimals, so an EA input of 300 points meant 3 dollars on one and 30 cents on the other.
For JPY pairs the old trick of multiplying by ten when the symbol has three or five digits still works. It breaks on metals and indices, which is why my code now pulls the tick size and tick value straight from the specification and ignores digits entirely.
Have you seen a broker change the number of decimals on a symbol without notice? That is the scenario I still have no automatic guard for.
Many brokers quote prices to five decimal places for most pairs, or three for yen pairs, where the last digit is a fraction of a pip, often called a pipette or point. This finer pricing makes spreads appear tighter and allows smaller stop and target increments.
For scalpers, the adjustment brings pitfalls. Strategy parameters written for four-digit quotes may be misinterpreted by code expecting five digits. A stop of 10 might mean one pip or ten pips depending on the platform's unit of measurement.
Misunderstanding this unit is a common cause of suddenly poor automated results after a change of broker. Checking the symbol specification for digits and point size, and confirming how the platform interprets distances, avoids mistakes. Calculating costs in account currency rather than in points offers an unambiguous comparison between brokers. Any code that references pip values should compute them from the symbol's digits property rather than assuming a fixed multiplier.