OQIRON
Assess the market first, then decide whether to take action
Oqiron continuously reads unified market data and generates trade candidates based on market conditions, strategy criteria, and client risk preferences. Candidate signals do not automatically become orders; they must first pass checks on the account, funds, risk limits, exchange status, and data integrity.
Systematic Execution and Post-Trade Protection
After verification, the trading engine creates orders according to strategy rules and tracks actual executions. New executions, partial executions, and position increases will continue to enter the protection process; if key protection criteria or order details cannot be confirmed, the system will halt the assumption of new risk rather than proceed with speculative execution.
Make sure to use the actual results for each step.
Order submission does not guarantee execution, and on-screen notifications do not constitute actual trades. The system continuously reconciles exchange orders, positions, executions, fees, and fund changes, then displays the results attributable to clients and bots in the client dashboard.
Create a sustainable, closed-loop system
The complete process is: Market Monitoring → Strategy Selection → Risk Assessment → Order Execution → Trade Protection → Status Verification → Client Results Display. The value of this closed-loop process is that it ensures every execution is rule-based, documented, and traceable.
Behind every trade, there’s more than just buying and selling
Behind every trade a customer sees, there are at least three key factors at play: whether market conditions are suitable for action, whether the account is authorized to take on new risk, and whether the order has actually been accepted and executed by the exchange. The system must link these three factors together; if any one of them is missing, it cannot be substituted with the “In Progress” status displayed on the page.
The work does not end once a trade is executed. For partial fills, the remaining quantity must be confirmed; open positions require corresponding hedging and exit strategies; fees and capital changes must be reconciled; and the final results must be attributed to the correct clients and bots. Only when these steps are seamlessly connected can a trade be considered truly complete.
After reading this, what should customers be able to do?
Truly understanding a knowledge article isn’t about memorizing a few terms, but about being able to make the right decisions based on actual page content and account status. Use the checklist below to verify whether you’ve grasped the key points.
- First, distinguish between candidate signals, submitted orders, and actual trades.
- Check whether the bot is in a state that allows for additional risk
- After the trade is executed, continue to monitor position protection and the exit process.
- Determine the outcome of this transaction based on the net result after reconciliation.
Frequently Asked Questions
These questions are directly related to the content of this article. Answers are based on current platform rules and actual operational standards; however, when it comes to packages, percentages, the scope of available features, or account status, the information displayed on the customer dashboard and official statements shall prevail.
- The bot has been launched, but why hasn’t it placed any orders yet? | Launching the bot simply means it has begun monitoring and checking conditions; it does not guarantee an immediate trade. Market direction, strategy conditions, fees, slippage, available funds, risk limits, data integrity, and exchange-specific factors must all be met simultaneously. It is normal for the bot to remain in a waiting state when conditions are not suitable.
- Why Are Trade Requests Rejected? | Common reasons include insufficient balance or margin, exchange minimum quantity limits, mismatched account or position modes, expired API permissions, non-compliant prices or slippage, insufficient risk limits, suspended trading pairs, and temporary exchange anomalies. Failed requests will not be displayed as executed trades for the customer.
- Why aren’t take-profit, stop-loss, or protective orders displayed in the system order history? | The system order history only displays orders that have been actually executed and can be attributed to Oqiron. Protective orders that have not yet been triggered or executed are not treated as trade records, but the system reads them from the regular order and conditional order fields for protection and reconciliation purposes.