Opening an account does not mean you can start trading immediately after registration. Customers must complete email verification, select an account mode, specify their risk tolerance, meet service eligibility requirements, and connect the necessary accounts or funds.
Onboarding is a comprehensive process that takes you from identity verification to readiness for operation; it is not simply a matter of filling out a registration form and starting to trade immediately. Each step addresses a specific issue: verifying the customer’s account, determining the method of fund management, completing service setup and connections, setting risk limits, and finally verifying that the system can securely access and operate.
Each stage displays the current task, completion status, and next step.
The activation process includes identity, mode, eligibility, connection, and operational checks. If the page displays only “Not Complete,” it is difficult for customers to determine which step is missing. Each stage should clearly indicate the current status and the next action required.
Verify the connection scope and account status before running.
Incorrect permissions, position modes, or account identities in the personal API will prevent the system from securely reading and executing commands. Performing these checks before startup can prevent configuration issues from being exposed only after the bot has begun running.
Registration only creates a customer account; it does not result in automatic charges or automated trading.
Registration only creates a customer account; it does not automatically deduct funds, automatically add funds, or automatically start trading. Separating these steps helps prevent customers from mistakenly believing that their funds have entered the market once they have filled out the information.
Registration, payment, connection, and launch are not the same steps. The complete activation process requires establishing, step by step, your identity, service eligibility, funding methods, risk preferences, account connections, and operational security status.
Customers use their own email addresses to receive verification codes, set passwords, and confirm the relevant terms and conditions; the system then creates a unique customer account.
The email verification code is used to confirm that the registered email address is controlled by the customer themselves, while the password and terms of service confirmation are used to establish a secure, unique customer account. The referral code is used solely to determine the referral relationship during registration and cannot be re-linked or modified after registration is complete.
First, decide on your risk management strategy, then choose a risk level that you understand and can tolerate.
The account mode determines the location of funds and management responsibilities, while risk preference defines the risk limits the system allows. Customers should first read the explanations regarding funds, permissions, and fees for both modes, then make a choice based on their actual needs, rather than deciding solely on the basis of “convenience.”
Individual API customers should apply for a trial or purchase a subscription and connect their exchange; account-based customers should follow the platform’s process to complete fund and account onboarding.
Individual API customers must obtain a valid trial or subscription and create an exchange connection with the correct permissions; integration account customers must complete the onboarding process according to the official funding procedures. The two paths differ, but both require the use of live accounts and real fund balances.
The system verifies service eligibility, account connections, funds, risks, and necessary configurations; it will not proceed directly to execution if any conditions are incomplete.
Prior to going live, the system will verify service eligibility, account connections, fund status, risk tolerance, and necessary permissions. Successful registration, successful payment, or funds in transit—none of these factors alone indicates that the system is ready for operation.
Customers use their own email addresses to receive verification codes, set passwords, and acknowledge the current legal documents. If an invitation code is entered, it is used to determine the referring party only during the formal registration process; it cannot be added or modified after registration is complete.
After logging into the client platform, first compare personal API accounts with integrated accounts. The account mode determines the location of funds, integration methods, and fee structure; you should not proceed directly to launching a bot without fully understanding these parameters.
Individual API customers must contact customer service to obtain trial access or purchase a currently valid subscription; they must then create a dedicated API with the correct permissions on their own exchange. Account integration customers should complete the integration process according to the funding procedures currently supported by the official platform.
Trial periods, subscription activation, API setup, and fund deposits are just a few steps in the process. The system must also verify account access, trading permissions, fund ownership, and availability; a single successful page does not constitute full readiness.
Before launch, the system will verify your risk assessment, service eligibility, account mode, funds, API or integration status, exchange-specific data, and existing order and position holdings. The fact that a button is clickable does not mean the system will bypass these security requirements.
Orders are not guaranteed to appear immediately after startup. The system first loads market data and account information, and new trades are only executed when both strategy and risk conditions are met. Customers should primarily monitor the system’s operational status, risk alerts, and notifications on a daily basis, and address any account or permission anomalies promptly.
Create a Unique Customer Account
Use the customer’s own email address to verify the code, set a password, and confirm the terms and conditions; the system will then establish a unique customer identity. If an invitation code is used, its ownership is also confirmed here at this time.
Select a risk management strategy
Compare personal APIs with integrated accounts, decide on your approach to capital management, and then select a risk tolerance that you understand and can handle. These two choices will influence subsequent integration and operational parameters.
Connect an Account or Complete the Funding Process
Complete the trial or subscription and API verification in Individual Mode; integrate accounts following the official funding process. Each status must be supported by actual accounts and funding records.
Launch after all checks have passed
The backend system will re-verify eligibility, connections, funds, risk, and existing open positions; new trades will only be permitted after all checks have passed. These conditions will continue to be monitored after the system is launched.
No. You still need to select a mode, complete the service setup and integration, and pass the conditions check.
Contact customer service to apply; the duration and scope are subject to the actual account issuance records.
No. Referral relationships are established only at the time of registration and cannot be re-linked after registration.
Contact support through the official customer platform or at support@oqiron.com.
OQIRON
