SHARKRULE / Learn

Binance Spot minimum orders: check value, quantity and rounding

A Binance Spot order must satisfy several separate rules for its trading pair: permitted quantity, quantity increments, price rules and order value. Having enough money in the wallet does not prove that an order meets them. Check the pair’s current parameters, then recalculate after rounding. If no permitted quantity fits your spending cap, stop for review instead of automatically spending more.

SharkRule · Reviewed

Minimum quantity and minimum order value are different checks

Quantity counts units of the asset being traded, often called the base asset. Notional value measures the order in the quote asset: for a standard fixed-price limit order, multiply the submitted price by the quantity. Neither is the same as the total balance shown in a wallet.

Binance’s Spot Filters documentation defines the checks below. Use the filters returned for the actual symbol; do not assume every pair has the same minimum or that a rule for futures, Convert, P2P or withdrawals applies to Spot. A minimum is an exchange constraint, not a suggested trade size.

Read the rule and its unit before changing an order
RuleWhat it checksWhat to distinguish
LOT_SIZEQuantity stays within minQty and maxQty and follows stepSizeAsset units, not the money value
PRICE_FILTEREnabled price bounds and tickSizePrice increments, not quantity increments
MIN_NOTIONAL / NOTIONALMinimum value; NOTIONAL also has a maximumPrice × quantity, before fees
MARKET_LOT_SIZEQuantity rules for market ordersCheck the applicable market-order filters too

Find the current rules for the exact pair

Use Binance’s trading parameters for the chosen Spot pair. For API-based checks, its Exchange information documentation describes GET /api/v3/exchangeInfo, which supplies symbol information and current trading rules. Read filters by their filterType name rather than assuming a fixed position in a list.

Record the base and quote assets, order type, price and quantity constraints, and any applicable notional bounds. Record when you checked them. A saved screenshot, another pair’s settings or the wallet’s displayed decimal precision is not a substitute for the current pair’s order increments.

Worked example: rounding down fails, rounding up breaks the cap

All amounts and rules in this example are hypothetical. Imagine an invented asset quoted in generic quote-currency units. A fixed-price limit buy has a price of 2.37, a price tick of 0.01, a minimum quantity of 0.1, a quantity step of 0.1 and a minimum notional of 10.00. The order-value cap is 10.00 before fees. Assume other exchange checks do not constrain this example; these are not live Binance parameters.

First calculate 10.00 ÷ 2.37 ≈ 4.219409 asset units. That raw quantity is not a multiple of 0.1. The table compares the adjacent permitted quantities without changing the price.

Hypothetical quantity choices at the same limit price
QuantityOrder valueResult
4.24.2 × 2.37 = 9.954Within cap; below the 10.00 minimum
4.34.3 × 2.37 = 10.191Above the minimum; exceeds cap by 0.191
  1. Round down to a quantity step: floor((10.00 ÷ 2.37) ÷ 0.1) × 0.1 = 4.2. Here floor means take the whole number below the result.
  2. Recheck value after rounding: 9.954 is 0.046 below the minimum. Passing the quantity step does not make the order valid.
  3. Check the next step only to diagnose the conflict: 4.3 costs 10.191. It cannot fit the unchanged 10.00 cap.
  4. At this fixed price, every lower permitted quantity also fails the minimum and every higher one exceeds the cap. There is no quantity satisfying both constraints. Pause or skip for review; a rule must not silently increase the user’s authorization.

Common mistakes that hide the real problem

Do not fix every rejection by adding decimal places or increasing the amount. For an invented step of 0.05, 1.23 has two decimal places but is not a valid multiple; 1.20 and 1.25 are. Quantity formatting must match the increment as well as the bounds. Decimal arithmetic helps avoid accidental rounding differences in an automated calculation.

Fees do not lift an undersized order above the notional minimum. In the example, paying a separate fee would not change 9.954 into a valid 10.00 order value. Check the applicable fee and its payment asset separately. If the cap includes fees, the available order value may be lower still.

A rejected request and an accepted order that has not filled need different responses. Binance’s error documentation identifies LOT_SIZE, PRICE_FILTER and notional failures separately. Read the actual error before changing the instruction. A timeout can leave execution status unknown. Pause all further Binance submissions until the original order’s state and any fills are reconciled.

A market order needs a different value check

A market order has no submitted limit price. Check whether the notional filter applies to it through applyToMarket, or applyMinToMarket and applyMaxToMarket. Under the current Spot specification, valuation uses a non-null reference price when available; otherwise it uses the volume-weighted average over avgPriceMins, or the last price when that interval is zero. The chart price alone does not establish this check.

That validation price does not promise an execution price. Available liquidity and price changes can cause slippage, partial execution or rejection. Do not switch order type simply to try to make an error disappear; the intended behavior and the user’s limits still need review.

A practical checklist for an automated instruction

Use this as an order-review worksheet. It describes checks to require of a workflow, not a claim that SharkRule exposes every exchange parameter or supports every order type.

  1. Confirm the venue, Spot product, exact pair, account eligibility and supported order type.
  2. Write down the authorized price or order behavior, quantity or spending cap, and whether fees are included.
  3. Read current pair rules and identify each applicable filter. Check bounds and increments for the submitted fields.
  4. Recompute notional after rounding. Check the minimum, any maximum, available balance and fees against the unchanged authorization.
  5. If the constraints conflict, record the reason and pause or skip for review. Do not repeatedly submit an unchanged rejected request.
  6. After a submission, distinguish rejection, acceptance and actual fills. An unknown Binance order status must block all further Binance submissions until it is reconciled.

Passing these checks does not guarantee a trade or prevent loss

The example isolates rounding and notional. A real order also faces permissions, symbol status, price bands, open-order limits, available funds and other exchange checks. Rules can change between a local calculation and submission. A valid limit order can remain unfilled or fill partially; an acquired asset can lose value. Fees, slippage, outages and exchange custody or access problems remain risks.

SharkRule is independent exchange automation software, not affiliated with or endorsed by Binance. Available connections, strategies and controls depend on the current dashboard, account and location. This guide does not establish that a specific filter-validation feature is available. We are not financial advisors: the calculations explain mechanics, not which asset to trade, how much to invest or what strategy to use. No execution or profit is guaranteed.

Frequently asked questions

Is Binance Spot’s minimum order always 5 or 10 USDT?

No universal amount should be assumed. Read the current notional and quantity rules for the exact pair and product. The 10.00 in this guide is an invented value in generic quote units, not a live minimum or recommended budget.

Why can a balance be large enough but an order still fail?

Balance and order validity are separate. The quantity may fall between allowed steps, the rounded value may be too small, or a price or account constraint may fail. Funds reserved for other orders and fees can also affect what is available.

Does rounding up fix a minimum-notional error?

It can increase the value, but may exceed the spending cap, available balance or another limit. Recheck the entire instruction. In the worked example, no allowed quantity meets both the minimum and the unchanged cap.

Does passing a filter check mean the order filled?

No. Validation, acceptance and execution are different stages. Check the exchange’s order status and recorded fills. An accepted limit order can have no execution. An uncertain Binance response must be reconciled before any further Binance submission.

Official documentation and references

Prepared with AI assistance from the linked official documentation. Examples are hypothetical; no live account tests or return comparisons were performed.