An order can exceed the minimum amount and still fail an increment check. Treat the price grid, quantity grid and notional amount as separate questions. Passing one says nothing by itself about the other two, and fixing the wrong input can change your intended trade without solving the rejection.
Price increments and quantity increments measure different things
A price increment controls the permitted spacing of unit prices. A quantity increment controls the permitted spacing of order sizes. If a fictional market uses a price tick of 0.01 and a quantity step of 0.001, those values are not interchangeable.
Decimal places are not a complete test either. With a step of 0.05, both 0.15 and 0.17 have two decimal places, but only 0.15 is an integer multiple of the step. Adding trailing zeros changes the presentation of a number, not whether it lies on the allowed grid.
Binance’s official filter definitions separate price, quantity and notional constraints. Actual parameter values belong to the specific pair and can change. The numbers below are original exercises, not a claim about any currently traded asset.
An amount that passes while quantity fails
Take a price of 100, quantity of 0.1055, minimum notional of 10, price tick of 0.01 and quantity step of 0.001. The price fits its tick. The notional value is 10.55, which meets the assumed minimum. But 0.1055 divided by 0.001 is 105.5, not a whole number.
| Check | Calculation | Result |
|---|---|---|
| Price grid | 100 / 0.01 = 10000 | Pass |
| Quantity grid | 0.1055 / 0.001 = 105.5 | Fail |
| Minimum value | 100 × 0.1055 = 10.55 | Pass |
Changing the quantity to 0.105 puts it on the assumed grid and gives a value of 10.5, still above this example’s minimum. That demonstrates how to recheck a candidate value. It is not an instruction to reduce your order, because changing the quantity also changes the amount you intend to trade.
Rounding is a decision with consequences
Rounding quantity upward may require more funds than planned. Rounding downward may bring the amount below its minimum. Moving a buy price upward or a sell price downward also changes the range of execution prices you accept. A validator should identify a problem rather than silently choosing those changes for you.
Consider a second fictional case: price 99, quantity 0.101 and minimum value 10. The product is 9.999. It falls short even though the quantity fits a step of 0.001. A display rounded to two amount decimals might show 10.00, but a display convention is not the underlying value used in the calculation.
For that reason, recheck all affected conditions after changing any input. An adjustment that solves the first reported problem can expose another. Keep the exact input alongside the error message instead of relying on a rounded total remembered from the screen.
Try the five example inputs in the checker
In the parameter exercise, enter price 100, quantity 0.1055, minimum value 10, price tick 0.01 and quantity step 0.001. The quantity check should fail. Change only the quantity to 0.105 and compare the new value, 10.5, with the original 10.55. The checker uses your inputs; it does not fetch current exchange rules.
The supported precision is eight decimal places. Invalid input, unsupported precision and nonpositive increments are rejected explicitly. A Serbian decimal comma can represent the same input value, but do not mix decimal and thousands separators or assume the tool will infer your intended number.
A three-check pass is deliberately narrow. It does not establish sufficient account balance, account permission, minimum and maximum quantity, price bounds, dynamic price bands, open-order limits or every other exchange condition. It is a useful way to isolate an input issue, not a complete order-acceptance simulator.
A market order needs its own rule context
A limit instruction supplies a particular price for the simple notional example. A market instruction does not have an equivalent user-set limit. Its applicable amount checks may use a defined reference price or price statistic, with parameters determining whether the condition applies.
Multiplying the last price on your screen by quantity therefore does not necessarily reproduce the platform’s market-order validation. Preserve the order type when recording an error. A problem that appears only through one entry point may involve a different supported parameter combination or a rule specific to that type.
Match the error name to the input
If these names appear in the error, the official error list points to:
PRICE_FILTER: price bounds and tick.LOT_SIZE: quantity bounds and step.MIN_NOTIONAL: minimum value;NOTIONAL: both value bounds.
This is not a complete error list. An app may use different wording. Adding funds will not fix every LOT_SIZE rejection.
Change the input named by the evidence
- Confirm the full pair, market, side and order type.
- Save the exact error and submitted values.
- Check when and where the pair-specific parameters were obtained.
- Identify the failed condition before editing a value.
- Recalculate affected checks, then review the new target quantity and price.
An explicit rejection and an uncertain network response are different cases. If the response is unknown, query the order records before assuming the order was rejected. Repeated submission can create a separate quantity problem on top of the original input question.
Keep enough context to explain a later change
Copied values deserve another look before validation. A spreadsheet may display a shortened decimal or scientific notation, while a message may insert spaces or use a different decimal separator. Check the original value rather than assuming the copied display preserves every digit. If an input cannot be interpreted unambiguously, return to its source and enter the supported format explicitly.
When keeping a result, save the full set of inputs beside it. A screenshot containing only a green pass message cannot reproduce the check or show whether the quantity was changed afterwards. The result belongs to that particular combination of values and rules, not to the account as a whole.
If an input worked previously but no longer works, compare the pair, type and current parameters. A copied value from another market or an old screenshot is not proof that the rule is unchanged. Store the parameter source and observation date with your private notes.
A clear record might say: “At price 100, quantity 0.1055 is not a multiple of the assumed step 0.001; its value 10.55 separately meets the assumed minimum 10.” That preserves the basis of the conclusion. If the parameters later change, you can still reproduce what was checked instead of mistaking a teaching example for a permanent exchange rule.
Acceptance checks and execution are separate stages. If an accepted order remains open, move to the price-and-quantity diagnosis. If some quantity already traded, inspect the active remainder before building a new instruction from the apparent difference.