The key difference between account modes lies not in the appearance of the pages, but in the location of funds, operational permissions, and day-to-day management responsibilities. Customers should understand each of these boundaries before opening an account.
Funds and permissions must be explained separately: the location of funds answers “Where is the money?”, the scope of permissions answers “What can the system do?”, and management responsibility answers “Who handles anomalies?”. Only when these three aspects are clearly understood can customers know what the account mode they’ve chosen truly entails.
Depending on the account mode, funds remain with the customer’s exchange or are transferred to the platform’s integrated account.
The principal for personal APIs is held at the customer’s exchange; funds from integrated accounts enter the platform’s management process and are recorded in the customer’s segregated ledger. The location of the funds must be determined first before we can discuss who is responsible for management and fees.
Execute trades only within the selected account mode, valid authorization, and risk limits.
Personal Mode uses limited read and trading permissions; Integration Mode handles account onboarding and operation through the platform. The system can only operate within the mode selected by the customer and within valid risk limits.
Do not bypass permissions, speculate on the ownership of funds, or interpret an unknown status as a success.
The platform must not bypass customer authorization or request unnecessary confidential information, nor may it make assumptions about outcomes when funds, orders, or ownership are unclear. If confirmation cannot be obtained, the system must display a "Pending" or "Exception" message.
What customers truly need is not just a promise that “funds are secure,” but the ability to verify, item by item, the location of their funds, the scope of permissions, management responsibilities, and procedures for handling anomalies. The differences between the two account modes should be compared within the same set of questions.
Customers retain control over their exchange accounts and funds; the platform uses an API—which does not include withdrawal permissions—to read account data and execute trades.
In Individual API Mode, funds remain in the customer’s own exchange account. The platform uses a limited API to read account information and execute trades; the customer retains control over logging in, managing funds, and disconnecting the API. The platform does not require and should not request withdrawal permissions.
The platform handles account onboarding and operational management, and uses independent customer records to track principal, returns, fees, and status.
While the platform handles the fund flow and trading account management for integrated accounts, each customer must still maintain clear ownership of their funds and independent records. The available balance, used balance, earnings, and fees displayed to customers cannot be simply calculated based on the platform’s total balance.
Customers should not send login passwords, email verification codes, or exchange keys to customer service or any individual; sensitive configurations should only be completed through official channels.
Login passwords, email verification codes, and API keys are not to be shared with customer service representatives. Customers should only complete sensitive configurations through the official secure portal at oqiron.com; any request for this information via chat is not part of the standard account activation process.
Accounts, funds, orders, and fees must not be replaced with demo data. When verification is not possible, an error or "pending" status should be displayed rather than showing false, normal results.
The funds, orders, and fees displayed on the account page must be derived from actual business records. If this cannot be confirmed at the moment, the correct approach is to display the status as “Pending,” “Restricted,” or “Abnormal” and continue verification, rather than using demo data or outdated statuses to make the page appear normal.
The trading principal, exchange login credentials, and API revocation rights belong to the customer. OQIRON reads balances, positions, orders, and trades via the API and executes strategy trades within the scope of authorization; the platform does not require customers to transfer principal and should not be granted withdrawal permissions.
After a customer revokes an API, the system can no longer verify account information and will therefore restrict operations; however, revoking the connection does not mean that existing positions on the exchange will automatically disappear. Customers must verify their actual positions and orders on the exchange and follow security procedures accordingly.
Clients do not configure exchange APIs themselves; the platform is responsible for account integration, operation and maintenance, and fund flows. In exchange, the platform must use client-isolated ledgers to account for principal, utilized funds, returns, fees, and withdrawal status; it cannot simply provide clients with a balance whose source cannot be verified.
Normal deposits are confirmed by the system based on actual fund transactions. Administrators primarily handle exceptions, freezes, retries, and reviews; manual approvals should not be used as a substitute for on-chain deposits, exchange deposits, or customer account allocations.
Official customer service representatives may verify customer IDs, public order numbers, page errors, and screenshots that do not contain confidential information, but they will never ask customers to send exchange passwords, API secrets, passphrases, private keys, mnemonic phrases, or email verification codes.
When funds, orders, or fees cannot be verified, the page should display "Pending," "Restricted," or "Exception." What is most valuable to customers is not that the page always displays a green status, but that the system clearly stops making assumptions when evidence is insufficient and preserves a path for subsequent verification.
Know which funding method is used
First, confirm whether the customer has chosen an individual API or an integrated account, as this step determines the location of funds, the integration method, maintenance responsibilities, and the fee structure.
Find out which capabilities are available
Withdrawal permission does not block API binding or robot Start, and OQIRON never uses a customer trading API to withdraw.
Connection and funding status are live and available
Connections, on-chain deposits, customer ledgers, and exchange statuses must be verified against actual facts. A successful page save or administrator action cannot substitute for formal confirmation.
Execute after risk conditions are met
The system will only enter operation once all conditions regarding funds, permissions, risk, and account status are met; any change in these parameters will trigger a new check rather than relying on the previous normal state.
Withdrawal permissions are neither required nor permitted.
Although customers choose to have the platform handle account onboarding and operational management, customer attribution and records must still be clearly defined.
No. Sensitive information should only be configured through the secure portal on the official client platform.
The system should display "Processing" or "Exception" and continue verifying; it must not speculate on the result.
OQIRON
