Most orders go straight to the order book. When one does not, the spot market says why in a single line above the order form, and nothing is reserved on your balance. This page explains what those lines mean.
The amount or the price needs adjusting
Quantity is below the minimum for this pair. Every pair has a smallest order size. The message names both your quantity and the minimum, so raise the amount to at least that figure.
Quantity is above the maximum for this pair. A single order cannot be larger than the pair allows. Split it into several smaller orders, or lower the amount.
Quantity must be a multiple of the step. Quantities move in fixed increments. With a step of 0.1 you can order 1.5 or 1.6, but not 1.55.
The amount is below one step for this pair. What you asked for is smaller than the pair's smallest increment, so there is nothing to trade. Enter at least one full step.
Price must be a multiple of the tick. Prices move on a fixed grid. With a tick of 0.01 you can bid 53.10 or 53.11, but not 53.105.
Price is above the maximum, or outside the allowed range. Each pair keeps prices within a band around its current reference price — the property valuation at first, then the last traded price — which guards against typos. Move your price closer to the current best bid and ask.
The order total is below the minimum. Quantity multiplied by price has a floor of its own. Increase the quantity or the price until the total reaches it.
The order total is too small to reserve a nonzero amount. The total is so small that it rounds down to zero. Increase the quantity.
The amount is not aligned to the expected decimal precision. You entered more decimal places than the token supports. Shorten the figure.
The amount must be a positive number. The amount field was empty, zero or negative.
Not enough funds
Insufficient balance for this order. Your wallet does not hold enough to cover it — and what your open orders already reserve counts against you. Top up, or cancel an open order to free the funds.
Insufficient token allowance. The wallet holds enough, but the spot market is not yet approved to spend that much of the token. Approve a higher amount in your wallet and place the order again.
Verification and access
Sign in to continue. Your session has expired. Sign in with your wallet and repeat the action.
Complete identity verification to start trading. Trading opens once verification is passed. Finish it in your profile and come back.
Identity verification is temporarily unavailable. We could not confirm your status right now. Nothing is wrong with your account — try again in a few minutes.
This property requires your wallet to be verified on-chain. Tokenised properties keep their own list of approved wallets on the blockchain, separate from your profile verification, and yours is not on it yet.
Transfers for this property are currently disabled. The property token is temporarily frozen by the issuer, so a matched order could not be delivered. Trading resumes once transfers are switched back on.
No Binaryx account is linked to this address. The wallet is connected but has no Binaryx account behind it. Complete registration with this wallet first.
Your wallet signature
Every order is signed by your wallet before it is accepted. These messages mean the signature and the order no longer agree, and reloading the page almost always clears them.
The order owner does not match the signed-in wallet. You switched accounts in the wallet without refreshing the page.
The order signature does not match the signed-in wallet, or could not be verified. Reconnect the wallet and sign again.
The order signature is invalid, or the order hash does not match the signed payload. Something changed between signing and sending, so the signature no longer covers the order. Sign a fresh one.
The order expired before it was sent. A signed order is valid for a short window only. Sign a new one.
The order nonce is out of sequence. Orders from one wallet are numbered in sequence and a later one was already accepted. Refresh the page so the numbering catches up.
The order was signed for a different contract. The signature belongs to another network or an older contract address. Reconnect the wallet.
The order side does not match the signed order. The request says buy while the signature says sell, or the reverse. Reload and sign again.
The order met one of your own
Your order would have matched against your own order. Trading with yourself is not allowed, so the order was stopped rather than filled. Cancel the order of yours that stands in the way, or move your price past it.
Not enough liquidity
Not enough liquidity for the requested size. There are not enough resting orders to fill the amount you asked for at market. Try a smaller size, or place a limit order and wait for a counterparty.
The order could not be filled in full. You asked for all or nothing, and the book did not hold enough at that moment. Lower the amount, or place a regular order that can fill in parts.
An order you already placed
The order is already filled, cancelled or expired. It closed before your request arrived — sometimes because you acted in another tab. Check your order history to see what happened to it.
The order was not found, or the id is not valid. No order with that identifier belongs to your account. Copy it again from your order list.
The order belongs to a different user. It exists, but not on your account, so it cannot be cancelled or inspected from here.
The order expiry is already in the past. The order carries an expiry that has passed, so it could never rest on the book. Check the clock on your device.
The page cursor is not valid. The marker used to page through history is malformed. Reload the list and start from the first page.
The pair or the chart
Unknown trading pair. The pair does not exist. It may have been renamed or delisted — pick one from the market list.
No trading pair exists for these two tokens. They are not traded against each other. Check which pairs the property is listed in.
Trading is currently halted for this symbol. The pair is suspended, so no new orders are accepted. Orders already in the book stay in place until trading resumes.
Invalid timeframe. The chart was asked for an interval that is not available. Choose 5m, 1h or 1d.
Messages you should not normally see
These mean the request did not arrive in the shape the spot market expects. On the website that points at a stale browser tab, and reloading the page clears it. If you trade through your own API client, they point at the request it built.
The order payload is malformed. The request did not carry a complete signed order.
The order signature is malformed. What arrived cannot be a wallet signature at all.
The order is missing a required amount, or a required field. Part of the order never arrived.
The order carries an invalid number. A numeric field could not be read. The offending value is quoted back to you.
Side must be buy or sell. The request asked for a side that does not exist.
The client order id is too long. Your own identifier for the order exceeds the allowed length.
The wallet address must be checksummed. The address was sent in plain lower case instead of the mixed-case form.
Unsupported order type, time-in-force or self-trade rule. The order asked for an option that is not offered. If you see this on the trading form itself, the spot market is mid-update and the option will work again shortly.
Something on our side
Nothing in this group is caused by you, and every one of them is safe to retry.
The service is temporarily unavailable. Trading is briefly unreachable. Your funds and open orders are untouched.
Trading is not available right now. Order placing is switched off on this environment. Nothing you change will help — it clears from our side.
The request timed out. No answer came back in time. The order most likely never reached the book — check your order list before retrying, so you do not place it twice.
The order could not be confirmed. We could not read back what happened to it, so it may or may not be live. Open your order history first, and place it again only if it is not there.
An internal error occurred. The message carries a request id. Quote it if you write to support — it points them at your exact case.
