Manage Orders
Open Request List (Pending Requests)
Requests submitted by users that are not yet processed are classified as “pending”.
These remain active until the specified conditions (e.g., a certain price threshold) are met.
Once created, a request stays pending until matched with external network conditions.
When the condition is satisfied, the request is processed and recorded as completed.
Description
Successfully submitted requests appear in a list format similar to the example below.
Open Requests Table
Field | Description |
---|---|
Request Time | Displayed in the device's local time, sorted by creation time. |
Pair | Combination of the requested token paired with CROSS Coin. |
Request Type | Direction of the request: acquisition or release. |
Request Mode | Basic (limit/market) or advanced strategies (conditional, automated logic). |
Request Price | Price specified at the time of request submission. |
Requested Amount | Total quantity specified by the user. |
Processed Amount | Quantity of the request that has already been processed. |
Request Value | Total value calculated (amount × price). |
Trigger Condition | Activated when the external price reaches the specified trigger value. |
Validity Period | Duration the request remains active. |
Cancel Request | Requires a wallet signature to cancel a pending request. |
Request History
Request history displays a full log of past submissions, showing whether token acquisition or release requests were processed, including timing and conditions.
This helps users analyze patterns and make more informed decisions.
Description
The history includes fully processed, partially processed, canceled, and expired requests.
Users can filter results by 1 day, 1 week, 1 month, 3 months, or a custom date range.
You can select dates via a calendar and expand individual requests for details.
Request History Table
Field | Description |
---|---|
Request Time | Displayed in UTC, sorted by creation time. |
Token | Token paired with CROSS Coin. |
Request Type | Indicates acquisition or release. |
Request Mode | Limit, market, or strategy-based request. |
Average Fill Price | Weighted average price of processed parts. |
Initial Request Price | Price entered at the time of submission. |
Requested Amount | Full amount specified in the request. |
Request Value | Total value calculated (amount × price). |
Request Status | Completed, Partially Completed, Canceled, or Expired. |
Transaction Hash | View the transaction on a blockchain explorer. |
Single Fill Price | Price at which a specific portion was processed. |
Single Fill Amount | Amount filled during a partial match. |
Fee | Fee amount based on user level. |
Role (Fee Type) | Maker, Taker, Stop Maker, Stop Taker, etc. |
Request Reflection History
Reflection history shows only requests that were actually processed through smart contracts, summarizing outcomes.
This allows users to track how their signed requests were reflected on-chain.
Note: Canceled requests are not shown in reflection history.
Results can be filtered by 1 day, 1 week, 1 month, 3 months, or a custom date range.
Reflection History Table
Field | Description |
---|---|
Reflection Time | Time the request was processed on-chain (UTC). |
Pair | Combination of the token and CROSS Coin. |
Request Type | Acquisition or release. |
Processed Price | Price at which the request was executed. |
Processed Amount | Total amount successfully processed. |
Reflected Value | Final value of the processed request. |
Fee | Fee amount applied based on user level. |
Role (Fee Type) | Maker, Taker, Stop Maker, Stop Taker, etc. |
The CROSSx app does not conduct or broker digital asset transactions, nor does it support in-app purchases or payments.
All asset-related requests are processed externally through smart contracts, initiated by the user's own signature and consent. The app functions solely as a wallet interface and signing tool.
Updated about 1 month ago