Systems and methods for mobile digital currency future exchange

Abstract

This invention discloses a system for mobile digital currency transactions. The system can receive login information. The system can generate an authentication request based on the login information. The system can receive authentication information. The system can display a trading interface including a portfolio drawer based on the authentication information, wherein the portfolio drawer displays tool details and account summaries.

Description

Technical Field

[0001] This invention generally relates to mobile devices, and more particularly to systems and methods for mobile and automated commands and controls for exchange trading platforms and applications. Prior Technology

[0002] Traditionally, exchanges and electronic trading platforms are connected via dedicated networks and proprietary terminals. These platforms often have limited performance and are only accessible during market trading hours, or may be subject to geographical or time-based availability limitations. Furthermore, options for viewing positions and executing orders may be limited. Therefore, there remains a need to improve mobile trading platforms, such as those for trading cryptocurrency derivatives. Summary of the Invention

[0003] In various specific embodiments, systems, methods, and articles (collectively, the "System") for mobile digital currency transactions are disclosed. In various specific embodiments, the System may receive login information. The System may generate an authentication request based on the login information. The System may receive authentication information. The System may display a trading interface including a portfolio slideshow based on the authentication information, wherein the portfolio slideshow constitutes a display of tool details and account summaries.

[0004] In various embodiments, the system may receive tool detail selections. The system may initiate an order flow process upon receiving these tool detail selections. The system may receive order input. The system may generate a platform command set based on this order input. The system may control the trading platform based on this platform command set. In various embodiments, the order input may include at least one of a buy order, a sell order, an order modification, a leverage setting, or a close position command. In various embodiments, the system may initiate an anonymous mode process upon receiving login information. In various embodiments, the system may determine user identity based on authentication information, including biometric data.

[0005] Unless otherwise expressly indicated in the specification, the foregoing features and elements can be combined in various combinations without exclusivity. These features and elements, and the operation of the disclosed specific embodiments, will become clearer from the following embodiments and accompanying drawings. The content of this paragraph is intended as a brief summary of the disclosure and is not intended to limit the scope of any patent application. Simple Explanation of the Diagram

[0006] The main points of this invention are specifically pointed out and clearly claimed in the concluding section of this specification. However, a more complete understanding of the invention can be obtained by referring to the embodiments and the claims, together with the accompanying drawings, in which like numbers denote similar elements.

[0007] Figure 1 is a block diagram illustrating various system components of a mobile digital currency transaction system according to various specific embodiments;

[0008] Figure 2 illustrates the start interface of a mobile digital currency transaction system according to various specific embodiments;

[0009] Figure 3 illustrates currency pair display in a mobile digital currency transaction system according to various specific embodiments;

[0010] Figure 4 illustrates the registration interface of a mobile digital currency transaction system according to various specific embodiments;

[0011] Figure 5A illustrates the login interface of a mobile digital currency transaction system according to various specific embodiments;

[0012] Figure 5B illustrates the authentication interface of a mobile digital currency transaction system according to various specific embodiments;

[0013] Figure 5C illustrates push notification prompts in a mobile digital currency transaction system according to various specific embodiments;

[0014] Figure 6 illustrates the current price / portfolio interface of a mobile digital currency trading system according to various specific embodiments;

[0015] Figure 7A illustrates the account configuration interface of a mobile digital currency transaction system according to various specific embodiments;

[0016] Figure 7B illustrates the notification settings interface of a mobile digital currency transaction system according to various specific embodiments;

[0017] Figure 7C illustrates the cybersecurity settings interface of a mobile digital currency transaction system according to various specific embodiments;

[0018] Figure 7D illustrates a user guide page for a mobile digital currency transaction system according to various specific embodiments;

[0019] Figure 7E illustrates a help request page of a mobile digital currency transaction system according to various specific embodiments;

[0020] Figure 8A illustrates the account balance page of a mobile digital currency transaction system according to various specific embodiments;

[0021] Figure 8B illustrates a position details page of a mobile digital currency trading system according to various specific embodiments;

[0022] Figure 8C illustrates a position details page of a mobile digital currency trading system according to various specific embodiments;

[0023] Figure 8D illustrates the position modification interface of a mobile digital currency trading system according to various specific embodiments;

[0024] Figure 9A illustrates a current price data page of a mobile digital currency trading system according to various specific embodiments;

[0025] Figure 9B illustrates a current price data page of a mobile digital currency trading system according to various specific embodiments;

[0026] Figure 9C illustrates the order book page of a mobile digital currency transaction system according to various specific embodiments;

[0027] Figure 10A illustrates the leverage interface of a mobile digital currency transaction system according to various specific embodiments;

[0028] Figure 10B illustrates the leverage interface of a mobile digital currency transaction system according to various specific embodiments;

[0029] Figure 11A illustrates the order interface of a mobile digital currency transaction system according to various specific embodiments;

[0030] Figure 11B illustrates the order interface of a mobile digital currency transaction system according to various specific embodiments;

[0031] Figure 11C illustrates the order interface of a mobile digital currency transaction system according to various specific embodiments;

[0032] Figure 11D illustrates the order interface of a mobile digital currency transaction system according to various specific embodiments;

[0033] Figure 11E illustrates the order interface of a mobile digital currency transaction system according to various specific embodiments;

[0034] Figure 11F illustrates the order interface of a mobile digital currency transaction system according to various specific embodiments;

[0035] Figure 12A illustrates the position clearing interface of a mobile digital currency transaction system according to various specific embodiments;

[0036] Figure 12B illustrates the position clearing interface of a mobile digital currency transaction system according to various specific embodiments;

[0037] Figure 13A illustrates the order confirmation display of a mobile digital currency transaction system according to various specific embodiments;

[0038] Figure 13B illustrates the order confirmation display of a mobile digital currency transaction system according to various specific embodiments;

[0039] Figure 13C illustrates the order return display of a mobile digital currency transaction system according to various specific embodiments;

[0040] Figure 14A illustrates a portfolio view page of a mobile digital currency transaction system according to various specific embodiments;

[0041] Figure 14B illustrates a portfolio detail view page of a mobile digital currency transaction system according to various specific embodiments;

[0042] Figure 15A illustrates the advanced long position interface of a mobile digital currency trading system according to various specific embodiments;

[0043] Figure 15B illustrates an advanced long position interface of a mobile digital currency trading system according to various specific embodiments;

[0044] Figure 15C illustrates editing a long position in the advanced long interface of a mobile digital currency trading system according to various specific embodiments;

[0045] Figure 15D illustrates editing a long position in the advanced long interface of a mobile digital currency trading system according to various specific embodiments;

[0046] Figure 16A illustrates the advanced short position interface of a mobile digital currency trading system according to various specific embodiments;

[0047] Figure 16B illustrates an advanced short position interface of a mobile digital currency trading system according to various specific embodiments;

[0048] Figure 16C illustrates editing a short position in the advanced short interface of a mobile digital currency trading system according to various specific embodiments;

[0049] Figure 16D illustrates editing a short position in the advanced short interface of a mobile digital currency trading system according to various specific embodiments;

[0050] Figure 17 illustrates the details of dynamic margin position indicators in mobile digital currency trading systems according to various specific embodiments;

[0051] Figure 18A illustrates the operation of the dynamic margin position indicator in terms of short positions in the advanced short position interface of a mobile digital currency trading system according to various specific embodiments;

[0052] Figure 18B illustrates the operation of the dynamic margin position indicator in reducing short positions in the advanced short interface of a mobile digital currency trading system according to various specific embodiments;

[0053] Figure 18C illustrates the operation of the dynamic margin position indicator in clearing short positions on the advanced short interface of a mobile digital currency trading system according to various specific embodiments;

[0054] Figure 18D illustrates the operation of the dynamic margin position indicator in terms of short positions in the advanced short interface of a mobile digital currency trading system according to various specific embodiments;

[0055] Figure 19A illustrates the operation of the dynamic margin position indicator in terms of long positions in the advanced long position interface of a mobile digital currency trading system according to various specific embodiments;

[0056] Figure 19B illustrates the operation of the dynamic margin position indicator in reducing long positions in the advanced long interface of a mobile digital currency trading system according to various specific embodiments;

[0057] Figure 19C illustrates the operation of the dynamic margin position indicator in terms of clearing long positions in the advanced long interface of a mobile digital currency trading system according to various specific embodiments;

[0058] Figure 19D illustrates the operation of the dynamic margin position indicator in terms of long positions in the advanced long interface of a mobile digital currency trading system according to various specific embodiments;

[0059] Figure 20 illustrates the quantity input interface of a mobile digital currency transaction system according to various specific embodiments;

[0060] Figure 21 illustrates the first start procedure of a mobile digital currency transaction system according to various specific embodiments;

[0061] Figure 22 illustrates the current price check procedure of a mobile digital currency transaction system according to various specific embodiments;

[0062] Figure 23 illustrates the leverage setting procedure of a mobile digital currency transaction system according to various specific embodiments;

[0063] Figure 24 illustrates the second start procedure of a mobile digital currency transaction system according to various specific embodiments;

[0064] Figure 25 illustrates the tool list of a mobile digital currency transaction system according to various specific embodiments;

[0065] Figure 26 illustrates the position closing procedure of a mobile digital currency transaction system according to various specific embodiments;

[0066] Figure 27 illustrates the third start procedure of a mobile digital currency transaction system according to various specific embodiments;

[0067] Figure 28 illustrates a portfolio sliding screen procedure of a mobile digital currency trading system according to various specific embodiments;

[0068] Figure 29A illustrates the commission modification procedure of a mobile digital currency transaction system according to various specific embodiments;

[0069] Figure 29B illustrates the commission modification procedure of a mobile digital currency transaction system according to various specific embodiments;

[0070] Figure 30A illustrates the maintenance procedures of a mobile digital currency transaction system according to various specific embodiments;

[0071] Figure 30B illustrates the maintenance procedures of a mobile digital currency transaction system according to various specific embodiments;

[0072] Figure 31A illustrates the login procedure of a mobile digital currency transaction system according to various specific embodiments;

[0073] Figure 31B illustrates the login procedure of a mobile digital currency transaction system according to various specific embodiments;

[0074] Figure 32A illustrates the login procedure of a mobile digital currency transaction system according to various specific embodiments; and

[0075] Figure 32B illustrates a biometric authentication procedure for a mobile digital currency transaction system according to various specific embodiments. Implementation

[0076] The following description is merely a series of exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the following description is intended to provide convenient illustrations for implementing various embodiments, including the best mode. It will be more apparent from the outset that various modifications can be made to the function and arrangement of the elements described in these embodiments without departing from the scope of the claims herein.

[0077] For simplicity, conventional techniques used in the design and implementation of mobile device applications, as well as conventional mobile device communication technologies, interface components, and / or their analogues, may not be described in detail in this specification. Furthermore, the connecting lines shown in the various diagrams contained herein are intended to illustrate exemplary functional relationships and / or physical or communication couplings between various components. It should be noted that many alternative or additional functional relationships or communication connections may be illustrated in practical systems or related usage methods (e.g., mobile trading applications for cryptocurrency derivatives).

[0078] By configuring mobile device applications and / or related cloud systems using the principles disclosed in this invention, various shortcomings of mobile device applications can be overcome. For example, by optimizing the display to execute platform activities including setting leverage, by providing a single assembly process for any order type, monitoring balances, order sets, and each of the relevant account's positions, and by visualizing the risk level of specified positions, the system of this invention can improve upon existing technologies.

[0079] In various exemplary embodiments, this system can provide a higher degree of sophistication and / or control for digital currency trading systems. For example, data can be collected from multiple data sources containing multiple different columns and rows and can be distributed across multiple platforms. While prior art systems typically include technical problems such as limited availability, execution of an order or viewing display under multiple user interactions, confusion regarding position-specific risk, and / or similar issues, this current system provides a technical solution by favoring a single process independent of order type and displaying position-specific risk levels graphically. In this regard, the system can accelerate trading through integrated order placement and optimized data presentation. Thus, the system can eliminate or reduce information gaps, reduce data re-entry, reduce record duplication, and reduce development time. The system can also reduce development costs or system processing time for data entry, reduce network utilization, and / or reduce data storage load. By enabling more frequent comparisons of data across different environments, the system can improve data reliability and / or accuracy. The system can also reduce redundant or repetitive comparison tasks, thereby reducing the demand on system resources. By reducing the number of user interactions (e.g., for a given order, compiling and explaining all options for all supported order types to quickly view all details and modify only necessary options, thus eliminating the need for the user to switch order types and reset previous selections), this system simplifies data retrieval and enhances the user experience. Furthermore, the benefits disclosed in this invention are applicable to any suitable electronic trading or trading platform.

[0080] The procedures disclosed in this specification improve the operation of the computer. In various embodiments, order processing speed can be accelerated by reducing the set of interactions enabled under a single inline order. The system can further reduce input by enabling a universally accessible portfolio swipe screen, thereby connecting order functionality with the background of data display. In various embodiments, the system can reduce the graphics processing load by minimizing the need for multiple scrolling and clicking to access the most frequently viewed data. For example, the system can display a standardized data set including balances and current positions upon login. Similarly, the procedure improves the reliability and speed of data presentation by enabling real-time data comparisons between environments based on metadata elements. The system can automatically update its background to help provide information on current position size and contract-specific uPnL. The system improves the reliability and speed of analysis by enabling real-time viewing of positions and margin levels across asset classes. For example, the system can initiate position modification actions with a single click by displaying buy, sell, close positions, close orders, and close stop-loss orders in the background of the contract display. Therefore, the system can be optimized to enable context-based user input prediction and further accelerate order placement. In this respect, the information utility of the data is improved and errors are reduced through the procedures for transmitting, storing, and / or accessing data as described in the user manual. This improvement also enhances the network's efficiency by reducing repetitive work through the identification of additional data sources for comparison.

[0081] In various specific embodiments, and referring specifically to FIG1, system 100 may include an application server 102, a user device 104, and a trading platform 200. Any of these components may be outsourced and / or communicate with the data comparator application server 102 and / or the trading platform 200 via a network (e.g., a first network 106 and a second network 108).

[0082] System 100 may be computer-based and may include a processor, a tangible non-transitory computer-readable memory, and / or a network interface, along with other suitable system software and hardware components. As described in the specification, instructions stored in the tangible non-transitory memory allow system 100 to perform various functions. In various specific embodiments, application server 102 and / or trading platform 200 may be configured as a central network element or hub for accessing the various systems, engines, and components of system 100. Application server 102 may include a network (such as network 106), a computer-based system, and / or software components, constituting an access point provided to the various systems, engines, and components of system 100. Application server 102 may operate and / or electronically communicate with user device 104 via first network 106 and with trading platform 200 via second network 108. In this respect, application server 102 can enable communication from user devices 104 to the systems, engines, and components (e.g., trading platform 200) of system 100. In various specific embodiments, application server 102 can receive commands and / or metadata from user devices 104 and can transmit responses to user devices 104.

[0083] In various specific embodiments, application server 102 may include one or more computing devices, rack servers, and / or virtual machines as described above, which provide load balancing, application services, web services, data query services, data transmission services, reverse proxy services, or facilitate the delivery and reception of data across the network (106, 108).

[0084] In various embodiments, a user device 104 may include software and / or hardware that communicates with system 100 via a network (such as network 106), the network including hardware and / or software configured to allow a user and / or the like to access application server 102. The user device may include any suitable means configured to allow a user to communicate with a network and system 100. The user device may include, for example, a personal computer, personal digital assistant, mobile phone, kiosk, and / or the like, and may allow the user to transmit comparison requests to system 100. In various embodiments, the user device 104 described in the specification may execute a web application or a native application to communicate with application server 102. The native application 110 may be installed on user device 104 via, for example, download, physical media, or an app store. Native application 110 can utilize the development code library provided for the operating system and capable of making system calls to manipulate data stored and displayed on user device 104, and communicate with application server 102. Web application is compatible with web browsers and is specifically written for execution on web browsers. Therefore, the web application can be a browser-based application that operates in conjunction with application server 102.

[0085] In various embodiments, the native application 110 running on user device 104 may communicate with application server 102 to support real-time updates. For example, data about trading platform 200 can be synchronized across various user devices 104 used by any number of users interacting with application server 102 and / or trading platform 200. In this regard, application server 102 can supply data from trading platform 200 to each of the user devices 104 and can transmit commands from the user devices 104 to trading platform 200. In various embodiments, application server 102 may apply access permissions to restrict data transmission between the various components of the networks (106, 108) and / or system 100. Users can authenticate on native application 110, for example, via username, password, two-factor authentication, private key, one-time password, security questions, biometrics, or other suitable authentication technologies known to those skilled in the art.

[0086] In various specific embodiments, a trading platform 200 in a digital currency futures trading system (such as system 100) is disclosed. The trading platform 200 may include an application programming interface (API), an order book, an order processing engine, a leverage engine, a matching engine, and / or the like.

[0087] Please refer to Figure 2, which illustrates the start interface 202 of the trading platform 200 according to various specific embodiments. The system 100 can display the start interface 202 when the native application 110 is executed via the user device 104. In various specific embodiments, the system can determine the connection status 204 between the trading platform 200 and the user device 104 and display the connection status indicator via the start interface 202. The system can display one or more details of current price data 206, such as currency prices, currency pairs, derivative financial product prices, index prices, and / or the like. The start interface 202 can be configured to receive one or more inputs from the user device 104, such as registration and login actions. For example, the system can receive a registration action from the user device 104 upon sensing user interaction with the registration button 208, and can receive a login action from the user device 104 upon user interaction with the login button 210. In various specific embodiments, the start interface 202 can be configured to enable interaction with the elements of the current price data 206. As the system determines the interaction with the element that provides the current price data, it can generate a current price detail request associated with that element.

[0088] For example, the system can register interactions with Bitcoin (XBT) current price data 206, and upon such interactions, can generate (e.g., via the native application) a Bitcoin (XBT) current price data detail request (which can be received through the trading platform 200). Upon receiving this current price data detail request, the system can display expanded current price details associated with the request. For example, the system can display a currency pair display as illustrated in Figure 3. Referring to Figure 3, the currency pair display 300 can incorporate the Bitcoin (XBT) current price data and be displayed upon receiving the associated current price detail request. The currency pair display 300 can include various current price details associated with the currency pair, such as a current price 302, an index price 304, a 24-hour percentage change in price 306, a trading volume 308, an open instrument value 310, and / or the like. In various embodiments, the currency pair display 300 may include a real-time graphical display of one of the current prices (i.e., a current price chart 312). In various embodiments, the current price chart 312 may be a candlestick chart and may span various time intervals. The currency pair display 300 may be configured to receive the current price chart time interval input via a radio button 314. In various embodiments, the currency pair display 300 may include order book data 316.

[0089] In various embodiments, and referring specifically to FIG4, a registration interface 400 of system 100 is illustrated according to various embodiments. The system can display the registration interface 400 upon registration. The registration interface 400 may consist of one or more elements for receiving registration data (which can be associated with a user profile and / or the like through the system). In various embodiments, the system may consist of receiving an email address 402, a password 404, a country or region 406, a first name 408, a last name 410, biometric information (such as fingerprints, faceprints, voice samples, iris images, etc.), device fingerprints (such as metadata associated with the user device 104, such as MAC addresses, operating system information, network information, version information, etc.), and / or the like. Upon receiving the registration data, the system can generate a user account and associate the registration data with it as account information. In various embodiments, the system can generate an authentication token and associate the authentication token with the user account. In this respect, the system can support token authentication, such as two-factor authentication and / or the like.

[0090] In various embodiments, and referring specifically to FIG5A, a login interface 500 of system 100 is illustrated. Login interface 500 may be configured to receive login information. For example, the system may receive an email address 502, a password 504, and a dual-identity token 506 via login interface 500. In various embodiments, the system may generate a login request via user device 104 upon interaction with login button 508. This login request may include login information that can be compared with account information as part of an authentication process. In various embodiments, the system may generate an authentication request based on this login information.

[0091] In various embodiments, and referring immediately to FIG5B, an authentication interface 510 of system 100 is illustrated. The system may display authentication interface 510 in response to an authentication request. Authentication interface 510 may include a prompt to set or enter authentication information, such as a numeric password, a touch pattern, biometric data, and / or the like. In various embodiments, authentication interface 510 may be configured to receive the authentication information (which, in conjunction with the user data, serves as account information). For example, authentication interface 510 may be configured to receive a numeric password via numeric keypad 512. The system may receive the authentication information along with login information and compare the authentication information and login information with the account information to enable access to various systems, features, and engines of trading platform 200. Referring immediately to FIG5C, the system may display a push notification prompt 514 upon receiving the authentication information. The system may enable push notifications from trading platform 200 to user device 104 upon receiving an "Allow" interaction with push notification prompt 514.

[0092] In various specific embodiments, and upon receiving the authentication and login information, the system may display the initial screen illustrated in Figure 6 and / or the current price / portfolio interface 600. The current price / portfolio interface 600 may include optional current price data for cryptocurrency 602 and / or currency pair 604. The system may display optional current price data for one or more instruments associated with cryptocurrency 602 and / or currency pair 604. For example, the system may display futures contracts 606 (such as perpetual contracts) associated with cryptocurrency 602, or various finite contracts 608 (such as those settled within a one-month period "September 27", "December 27", and / or the like). The system may display current price data 610, index price data, strike price data, trading volume data, velocity data, or any other current price data associated with such cryptocurrency 602, currency pair 604, and / or instrument. In various specific embodiments, the current price / portfolio interface 600 may constitute a sliding screen 612 displaying account balance. In various specific embodiments, the current price / portfolio interface 600 may be configured to display an account settings diagram 614. Upon receiving interaction with the account settings diagram 614, the system may display an account configuration interface.

[0093] Please refer to Figure 7A, which illustrates the account configuration interface 700 of system 100 according to various embodiments. The account configuration interface 700 can display various elements of account information associated with the user account, such as username 702 and email address 704. In various embodiments, the account configuration interface 700 can be configured to enable access to one or more configuration settings pages of the system, for example, through interaction with the notification settings button 706, security settings button 708, user guide button 710, and help request button 712. In various embodiments, the account configuration interface 700 can be configured to display an information page upon receiving a term via the service button 714 and privacy notification button 716. In various embodiments, the system can be configured to terminate the authentication dialogue upon receiving an interaction with the logout button 718. In this respect, the system can disable access to various systems, features, and engines of the transaction platform 200 upon this interaction with the logout button 718. In various specific embodiments, the account configuration interface 700 may constitute a sliding screen 612 for displaying account balance.

[0094] In various specific embodiments, and referring specifically to FIG. 7B, the system can display a notification setting interface 720 upon interaction with the receive and notification setting button 706. The notification setting interface 720 can be configured to receive notification setting input and, consequently, enable or disable various push notifications from the trading platform 200 to the user device 104. For example, the notification setting interface 720 can be configured to receive interaction with one or more switches to enable / disable notifications related to pending deposits 722, deposit confirmations 724, auto-delivery events 726, clearing events 728, withdrawal confirmations 730, and alternative device logins 732. For example, the system can compare a device fingerprint associated with a user account as account information. If the device fingerprint received along with the login data does not match the device fingerprint stored as account information, the system can generate an alternative device login notification. In other words, the system can receive a first device fingerprint and first login data from a first user device, and a second device fingerprint and the first login data from a second user device. The system can generate an alternative device login notification upon receiving the second device fingerprint and the first login information from the second user device. The system can transmit the alternative device login notification to the first user device. In various specific embodiments, the notification settings interface 720 can constitute a sliding screen 612 displaying the account balance.

[0095] In various embodiments, and referring specifically to FIG7C, upon receiving interaction with the security setting button 708, the system can display a security setting interface 734. The security setting interface 734 can enable and / or disable the authentication interface 510 and associated system procedures. For example, the authentication interface 510 can be disabled upon receiving interaction with the enable / disable command switch 736. In various embodiments, the security setting interface 734 can enable editing or reconfiguring the authentication data. For example, the system can enable editing of the numeric password via interaction with the edit password button 738. In various embodiments, the security setting interface 734 can configure a drawer 612 to display account balance.

[0096] In various embodiments, and referring specifically to FIG7D, upon receiving the interaction with the user guide button 710, the system can display the user guide page 740. In various embodiments, the system can initiate a web page punch-out process, and the native APP 110 can communicate with one or more web servers to display the user guide page 740.

[0097] In various embodiments, and referring specifically to FIG7E, upon interaction with the receive and help request button 712, the system can display a help request page 742. In various embodiments, the system can initiate a web page recording process, and the local APP 110 can communicate with one or more web servers to display the help request page 742. In various embodiments, the help request page 742 can constitute receiving help request information. This help request information may include text input, such as an email address 744, a subject line 746, a problem description 748, and / or the like. In various embodiments, the help request information may include graphic data or data files, which may include an attachment 750.

[0098] In various embodiments and in response to interaction with the account balance slider 612, the system can display an account balance page 800. For example, the system can receive and interact with the user device 104, such as by dragging the account balance slider 612 upwards, thereby expanding the account balance slider 612 to display the account balance page 800. In various embodiments, the account balance page 800 can be configured to display account balance and position information associated with the user's account. The account balance page can display total available balance 802, total margin balance 806, total margin composition indicator 808, total PnL 804 (which may or may not be implemented), and / or the like. The total margin composition indicator 808 can be a graphical indicator, such as a bar chart displaying the total value of all positions and all current orders as a portion of the total available margin. Each component can be displayed in a different color, thereby used to quickly distinguish the all position values, the open order values, and the total available margin values. For example, the bar chart can fill to the right of the account balance page 800 as margin is used for various open positions and orders, thereby reducing the relative size of the total available margin displayed in the bar chart.

[0099] In various specific embodiments, the account balance page 800 may include a portfolio, broken down by currency pairs that provide details of the components of the overall portfolio associated with the user's account, such as portfolios categorized by currency pair. For example, the system may display XBTUSD portfolio details 810 and ETHUSD portfolio details 812. These portfolio details displays (810, 812) may include associated current price data, such as a count of one of the valid orders and / or order types 814, position size 816, commission calculation 818, PnL (profit and loss) calculation 820, position value 822, and a settlement details box 824.

[0100] In various embodiments, and referring specifically to Figures 8B and 8C, upon receiving interaction with one of the position details (810, 812), the system can display a position details page 826. Figure 8B illustrates a first portion of the position details page 826, and Figure 8C also illustrates a second portion of the position details page scrolled to reveal additional details of the effective stop-loss orders. In various embodiments, the position details page 826 may be configured to display position-specific information associated with the user's account, such as all positions associated with the selected currency pair. The position details page 826 may include a specific margin composition indicator 828. The specific margin composition indicator 828 may be configured to function in the same manner as the total margin composition indicator 808, but may be calculated and displayed only based on those positions associated with the selected position details (e.g., only XBTUSD positions). The position details page 826 may include an order details box 830, which can display details of all valid orders 832, all valid stop losses 834, and the triggering closing conditions 842 associated with such valid stop losses 834.

[0101] In various specific embodiments, the position details page 826 can configure the order trading platform 200 to close all positions associated with the selected currency pair upon interaction with the close positions button 836. Upon receiving interaction with the close positions button 836, the system can automatically generate one or more orders constituting an unwind trade of the associated positions, and accordingly, multiple trades can be executed based on such orders. Similarly, the position details page 826 can configure the order trading platform 200 to cancel all orders and / or cancel all stop-loss orders associated with the selected currency pair upon interaction with the corresponding cancel all orders button 838 and cancel all stop-loss orders 840. Upon receiving interaction with the cancel all orders button 838, the system can remove all valid orders associated with the selected currency pair from the order book of the trading platform 200. Upon receiving interaction with the cancel all stop-loss order button 840, the system may remove all valid stop-loss orders associated with the selected currency pair from the order book of the trading platform 200. In various specific embodiments, the position details page 826 can be configured to initiate the order placement process of the system. For example, the position details page 826 may include a buy button 844 and / or a sell button 846, and the system can initiate the order placement process in response to receiving interaction with these buttons (844, 846). In various specific embodiments, the order details box 830 can be configured to receive interaction with any of the valid orders 832, valid stop-loss orders 834, and / or triggered close-position conditions 842 displayed therein.

[0102] In various specific embodiments, and referring specifically to FIG8D, the system may display a modified position interface 848 in response to receiving interaction with the order details box 830. The modified position interface 848 may be configured to enable modification of various data associated with the discrete order displayed in the order details box 830. This discrete order may be determined based on the interaction; for example, the discrete order may be determined based on the system's registration of touch interaction with the discrete order. The modified position interface 848 may be configured to receive size input via size input field 850 and / or limit input via limit input field 852. The modified position interface 848 may display the current values ​​for these inputs and may display a keyboard 854 in response to receiving interaction with these input fields (850, 852). In this respect, the modified position interface 848 may facilitate modification of these current values ​​to new values ​​via registered keyboard input 854. In various embodiments, the position modification interface 848 may prompt for confirmation, and upon receiving the confirmation, the current value can be set to the new value. For example, the position modification interface 848 may display a "confirm amend" scroll bar 856 and may receive interaction (such as dragging the scroll bar across the position modification interface 848). In various embodiments, the position modification interface 848 may enable the cancellation of the separate order. For example, the system may receive interaction with the cancel order button 858 and remove the associated order from the order book of the trading platform 200.

[0103] In various specific embodiments, and referring immediately to Figures 9A, 9B, and 9C, the current price data page 900 of system 100 is illustrated. The current price data page 900 may be configured to display various current price data for a selected currency pair. For example, the current price data page 900 may display current price data related to the XBTUSD pair. In various specific embodiments, the current price data page 900 may display data 902, such as a current price, a 24-hour percentage change in price, an index price, a trading volume, a short-term yield, a funds window, an open instrument volume, a yield / loss indicator chart, and / or the like. Referring immediately to Figure 9C, the current price data page 900 illustrates the display of an order book data box 908. In various specific embodiments, the order book data box 908 may be displayed in response to interaction with the current price data page 900 (e.g., scrolling down or swiping down on the user device 104).

[0104] The current price data page 900 may include a real-time graphical display of the current price (i.e., a current price chart 904). The current price chart 904 may display various current price data that change over time, such as the spot price labeled "XBTUSD" and the index price ".BXBT". In various embodiments, the current price chart 904 may be a candlestick chart and may span various time intervals. The current price data page 900 may be configured to receive the current price chart time interval input via a radio button 906. As shown in FIG9A, the current price chart 904 is displayed in a one (1) minute interval selected by the "1m" radio button. Referring briefly to FIG9B, the "15m" radio button is displayed and illustrates the corresponding change in the current price chart 904. In various embodiments, the current price data page 900 may be configured to initiate the order placement process of system 100. For example, the current price information page 900 may include a buy button 910 and / or a sell button 912, and the system may initiate the order placement process in response to interaction with these buttons (910, 912). In various specific embodiments, the current price information page 900 may be configured to initiate the leverage setting process of system 100. For example, the current price information page 900 may include a leverage setting button 914, and the system may initiate the leverage setting process upon receiving interaction with the leverage setting button 914.

[0105] In various embodiments, and referring specifically to Figures 10A and 10B, the system can display a leverage setting interface 1000 upon receiving interaction with the leverage setting button 914. The leverage setting interface 1000 can be configured to enable leverage settings across orders generated in the order placement process. The leverage setting interface 1000 may include an available margin display 1002, settlement information, a leverage type selector 1004, and a leverage ratio 1008, and the like. The leverage setting interface 1000 can be configured to receive leverage type input via interaction with the leverage type selector 1004 and leverage ratio input via the keyboard 1006. In various embodiments, the available margin display may be a bar chart. In various embodiments, the leverage setting interface 1000 may prompt for confirmation, and upon receiving the confirmation, the current leverage information can be set to the new information. For example, the leverage setting interface 1000 can display a "Set leverage" scroll bar 1010 and can receive interactive input (such as dragging the scroll bar across the leverage setting interface 1000).

[0106] Please refer to Figures 11A to 11F for various pages and frames of the order placement interface 1100 of system 100, illustrated according to various specific embodiments. Upon initiation of the order placement procedure, the system can display the order placement interface 1100. The order placement interface 1100 is configured to receive various order placement inputs generated from defined platform commands. For example, the order placement interface may be configured to receive data or inputs associated with buy orders, sell orders, order modifications, leverage settings, or position closing orders. The system can generate the platform command based on these inputs. The platform command can be received through the trading platform 200 (which may subsequently execute one or more transactions based on the platform command). In various specific embodiments, one or more platform commands can be processed in batches through the system, or generated as a set of platform commands that can be executed simultaneously or sequentially through the trading platform 200.

[0107] In various specific embodiments, the order interface 1100 includes an order details box 1102 that displays current order details, such as a current position, a position after executing the current order, a liquidation estimate, a calculated PnL, an estimated execution price, and / or the like. The order interface 1100 includes a limit setting button 1104, a stop-loss setting button 1106, and an edit order button 1108. Upon interaction with the edit order button 1108, the system can display a prompt to edit the order quantity 1110. For example, as shown in FIG11B, the system can display a keyboard 1112 and receive the order quantity via the keyboard 1112. The edit order button 1108 can display a "preview," and the system can display this effect on the order details box 1102 for the new order quantity 1110.

[0108] Upon interaction with the stop-loss setting button 1106, the system can display the stop-loss setting box 1114 shown in FIG11C. The stop-loss setting button 1106 can display an illustration indicating the expansion of the stop-loss setting box 1114. The stop-loss setting box 1114 may constitute a receiving order input for defining a stop-loss order. The stop-loss setting box 1114 can receive and display order input, such as trigger price 1116, trigger-close condition switch 1118, and last price setting button 1120. For example, upon interaction with trigger price 1116, the system can display the keyboard and receive the trigger price input. Upon interaction with trigger-close condition switch 1118, the system can set the trigger-close condition for the order. In various specific embodiments, upon interaction with last price setting button 1120, the system can set the trigger price to the last executed order price for the currency pair on trading platform 200.

[0109] In response to interaction with the limit setting button 1104, the system can display the limit setting box 1122 shown in FIG11D. The limit setting button 1104 can display an illustration indicating the expansion of the limit setting box 1122. The limit setting box 1122 can be configured to receive order input for defining a limit order. The limit setting box 1122 can receive and display order input, such as limit price 1124, post-only condition switch 1126, and reduce-only condition switch 1128. With interaction with the post-only condition switch 1126, the system can set the post-only condition for the order. In this respect, the system can generate a platform command to the trading platform 200 to accept the associated order, as long as it is not immediately executed through the trading platform 200. With interaction with the reduce-only condition switch 1128, the system can set the reduce-only condition for the order.

[0110] In various embodiments and as shown in FIG11E, the system can simultaneously display both the stop-loss setting box 1114 and the limit setting box 1122 in response to interaction with both the limit setting button 1104 and the stop-loss setting button 1106. In various embodiments, the order interface 1100 can prompt for confirmation, and upon receiving the confirmation, can generate the platform command based on the received order input. For example, the order interface 1100 can display a "sell" or "buy" scroll bar 1130 (which may depend on the interaction with the buy button 910 and the sell button 912), and can receive interactions (such as dragging the scroll bar across the order interface 1100). In response to receiving the confirmation, the system can display a "submit" notification in the scroll bar 1130 illustrated in FIG11F. In various embodiments, the system can generate one or more alerts 1132 in response to receiving the confirmation, and can prompt for reconfirmation of the input. The system can receive this reconfirmation input, for example, through interaction with the "Submit" button 1134.

[0111] In various specific embodiments, and referring specifically to Figures 12A and 12B, a position-closing interface 1200 of system 100 is illustrated. The position-closing interface 1200 may be configured to receive order input for closing an entire position in a selected currency pair. In this respect, the position-closing interface constitutes a set of platform commands that control the trading platform to execute multiple transactions to close such associated positions. In various specific embodiments, the position-closing interface 1200 may display a notification box 1202 explaining the set of platform commands. The position-closing interface 1200 may include a new limit price button 1204. In response to interaction with the new limit price button 1204, the system may display a limit setting box 1208 that constitutes receiving a limit price input (displayed in field 1212). The system may receive this limit price input via a keyboard 1210 (which may be displayed upon interaction with field 1212). In various embodiments, the system can remove the price limit and restore the current price order in response to interaction with the Remove Price Limit button 1214. In various embodiments, the closing position interface 1200 can prompt for confirmation, and upon receiving the confirmation, can generate the platform command set based on the received order input. For example, the closing position interface 1200 can display a scroll bar 1206 and can receive interactions (such as dragging the scroll bar across the closing position interface 1200).

[0112] In various specific embodiments, and referring specifically to Figures 13A, 13B, and 13C, the order feedback display 1300 of system 100 is illustrated. The order feedback display 1300 may include various box-shaped notifications that fly in from the top of the screen of the user device 104. For example, an order submission notification 1302 may include data or a summary of submitted orders (such as "Close XBTUSD at Market by buying 100 contracts"). As shown in Figure 13B, a second execution notification 1304 flies over a first execution notification 1306. These execution notifications (1304, 1306) may include information about the execution status of the associated order, such as "68 contracts remaining" or "53 contracts remaining." As shown in Figure 13C, the fully executed order notification 1308 can display details of the complete executed order (such as price and quantity), such as "53 XBTUSD contracts bought at 10344.5".

[0113] In various specific embodiments, and referring specifically to Figures 14A and 14B, an illustration of the portfolio view page 1400 of system 100 is provided. The portfolio view page 1400 may be configured to display the composition of the portfolio associated with the user's account. For example, the portfolio view page 1400 may include one or more instrument detail boxes 1402 associated with various instruments (such as currency pairs like "XBTUSD", contracts like "XBT7D_U105", and / or their analogies) containing the portfolio. These instrument detail boxes 1402 may display instrument-related and / or calculated data, such as position size, liquidation price, entry price, ROE, PnL, numerical values, active / open orders, stop-loss orders, and / or their analogies. In various specific embodiments, and upon receiving interaction with the instrument detail boxes 1402, the system may display the portfolio detail view page 1404 as shown in Figure 14B. The portfolio details view page 1404 may include an additional details box 1406, which may display a margin composition indicator 1408 associated with the tool. In various specific embodiments, the portfolio details view page 1404 may include a position-closing button 1410. The system may initiate a position-closing procedure upon receiving interaction with the position-closing button 1410, and may display a position-closing interface 1200.

[0114] In various specific embodiments, and referring specifically to Figures 15A to 20, an advanced position interface of platform 200 is illustrated. This advanced interface may include components defining a long position interface 1500 and a short position interface 1600. The advanced position interface may include a current price depth chart 1502, a buy / sell switch 1504, a currency pair indicator 1506, a leverage setting button 1508, an order type display 1510, a mark price indicator 1512, a quantity selection button 1514, and a quantity input box 1516. In various specific embodiments, the advanced position interface may include a dynamic margin position indicator 1700. This dynamic margin position indicator displays the real-time calculation of existing positions relative to the maximum position associated with the trading account and currency pair (based on the current position value and available margin). The dynamic margin position indicator also displays the real-time effect of new orders on the existing positions and the maximum position.

[0115] The dynamic margin position indicator may include a background bar 1702. The system can calculate and display the size of this background bar based on the corresponding maximum margin values ​​in the long and short directions 1712 and 1714. The system can calculate a zero position 1704 based on the long and short directions and display the zero indicator on the background bar. In this respect, the background bar can be scaled to indicate the maximum margin available to the account holder in the long and short directions (i.e., the zero-point side). The system can determine the current position value and display a current position bar 1706 based on the magnitude of the current position value relative to the corresponding maximum margin value. The system can overlay this current position bar on the background bar. The system can receive order information including a currency pair and a quantity. The system can calculate a new position value based on the current position and the quantity. The system can display an arrow 1708 on the background bar indicating the new position value.

[0116] In various embodiments, the arrow may point in either a long or short direction depending on the order type and quantity. In various embodiments, the system may display a new position bar 1710 overlaid on the background bar. The new position bar may be scaled to correspond to the background bar and displayed based on the difference between the current position and the new position. In various embodiments, the new position bar may be displayed relatively brighter than the current position bar. In various embodiments, the new position bar and the current position bar may be color-coded based on the long and short directions. For example, if displayed in the long direction, the current position bar and the new position bar may have a green hue and saturation, while if displayed in the short direction, they may have a red hue and saturation. In various embodiments, the system may dynamically change the length of the new position bar and / or the current position bar based on the order data. In this regard, the dynamic margin position indicator may indicate the margin currently (or will be) allocated to the user's position. Furthermore, this dynamic margin position indicator may thus indicate the margin that will be returned to the user's available balance after an order to reduce the position is executed.

[0117] In various embodiments, the system may receive requests to change the quantity of orders and recalculate margin requirements based on the last traded price or by using the received order data, thereby updating the dynamic margin position indicator. The system may receive requests to add limit prices. Consequently, the system may change the margin calculation of the dynamic margin position indicator from an estimate based on the last traded or order book data to an absolute price based on the limit price received in the order data. In various embodiments, the system may receive requests to change the limit price and recalculate the margin requirements based on the new limit price. In various embodiments, the system may receive requests to add or change trigger prices. Consequently, the system may change the margin calculation of the dynamic margin position indicator to use the trigger as the estimated execution price. As the system recalculates the margin requirements and / or changes the margin calculation, it may update the display of the dynamic margin position indicator, including any of the current position bar, the new position bar, the background bar, and / or the arrow.

[0118] In various embodiments, the system may receive quantity data via a quantity input interface 2000. In various embodiments, the quantity input interface may display a keyboard including numeric buttons, a number toggle, a decimal point button, and a backspace button. In various embodiments, the quantity input interface may include an interface type switch 2002, configured to switch between a numeric type and a percentage type. As the user selects the percentage type switch, the system may display a percentage scale 2004. This scale may extend between 0% and 100% positions. The system may receive percentage type input based on, for example, the desired position that the user drags along the scale. The system may display a numeric indication of the selected percentage input.

[0119] Please refer to Figure 21 for an example of the start procedure 2100 of system 100 according to various specific embodiments. The system may receive a start command including login information. The system may determine the operating mode 2102 based on the login information. If the login information does not include authentication information, the system may start the anonymous mode procedure 2104. Subsequently, the system may start the authentication setup procedure 2106, which may generate an authentication request based on the login information. In various specific embodiments, upon receiving authentication information 2108, the system may start the trading interface procedure 2110. The system may display a trading interface including a portfolio slideshow. The portfolio slideshow can display portfolio information associated with the authentication information and / or login information.

[0120] In various embodiments, and referring specifically to FIG22, the market view page program 2200 of system 100 is illustrated. Upon receiving the authentication data 2108, the system may display a startup screen 2202, and then display the market view page 2204. The system may initiate a connection 2206 with the trading platform 200 and receive data from the trading platform 200. For example, the system may fill the market view page 2204 with a cryptocurrency list 2208 and / or a list of deactivated cryptocurrencies 2210. In various embodiments, the market view page 2204 may be configured to receive one or more inputs from the user device 104. For example, the market view page 2204 may be configured to receive an account and settings section 2212, proceed to tool selection 2214, and proceed to portfolio selection 2216.

[0121] In various specific embodiments, and referring specifically to FIG23, the lever setting page program 2300 of system 100 is illustrated. In response to receiving initial lever setting input 2302 from user device 104, the system may display a lever setting page 2304, such as lever setting interface 1000. The lever setting page 2304 may be configured to receive and / or display one or more inputs to initialize lever-related input states, such as an isolated lever input 2306, a cross lever input 2308, and a lever receiving preview 2310. Upon initializing these lever-related input states, the system may display either a tool details page 2312 or a commission modification page 2314.

[0122] In various embodiments, and referring specifically to FIG24, a second start procedure 2400 of system 100 is illustrated. User device 104 may receive a command 2402 to start native application 110. Subsequently, the system may determine whether native application 110 is partially cached on user device 104 (2404). If the system determines that it is not cached, it may display a startup screen 2406 and continue caching native application 110. If not, the system may determine a login status (2408). If the login status fails, the system may continue with anonymous mode procedure 2410. Otherwise, the system may continue with authentication procedure 2412 and display an authentication page (such as authentication interface 510). In various embodiments, the system may determine whether authentication is restricted 2414 and proceed to restricted procedure 2416, which may force a logout event 2418 and return to anonymous mode procedure 2410. If authentication is not restricted, the system may perform a deep link check 2420. Subsequently, the system can begin the entry and portfolio review procedure 2422 or the creation / modification of order procedure 2424.

[0123] In various specific embodiments, and referring specifically to FIG25, the tool detail page program 2500 of system 100 is illustrated. The system can receive a tool viewing action 2502, and subsequently display a tool detail page 2504. The tool detail page 2504 can be configured to generate an initial leverage action 2506, an initial buy / sell order action 2508, or a portfolio access action 2510. The system can receive interaction with a price chart 2512 or interaction with an order book 2514 via the tool detail page 2504. Subsequently, the system can initiate an order placement process. For example, the system can generate an initial draft buy / sell order with size action 2516, or it can generate an initial draft buy / sell order with price action 2518.

[0124] In various specific embodiments, and referring specifically to FIG26, the closing position page procedure 2600 of system 100 is illustrated. The system can receive an initial closing position action 2602 and subsequently display a closing position page 2604 (e.g., closing position interface 1200). The procedure can be initialized to close at the current price 2606 and can be changed to closing at a limit price based on the received state selection 2608. The system can receive a limit price input 2610. The system can determine whether the limit price input is entered (i.e., a non-zero value) 2612. Upon determining that a limit price has been entered, the system can wait for confirmation of the limit closing status 2614. Otherwise, the system will wait for confirmation of the current price closing status 2616.

[0125] In various embodiments, and referring specifically to FIG. 27, a third start procedure 2700 of system 100 is illustrated. Procedure 2700 includes the steps, system, and features of procedure 2400, but incorporates a restricted mode procedure. Upon determining the login state 2702, the system may perform a restricted authentication soft check 2704. In response to the restricted authentication soft check, the system may set a restricted warning state 2710 or a preset state 2712 for authentication procedure 2708. In various embodiments, the system may perform a hard check 2714 to determine whether authentication is restricted. The system may proceed to a restricted procedure 2716 upon receiving a restricted result from the hard check. In various embodiments, restricted procedure 2716 may enable a restricted mode 2718 for the current price and portfolio review procedure.

[0126] In various specific embodiments, and referring specifically to FIG28, the system 100 illustrates a portfolio sliding screen program 2800. The system can display a portfolio sliding screen page 2802 in response to interactions with the current price view page 2804, the account and settings page 2806, and / or the tool details page 2808. In response to these interactions with the current price view page 2804 and the account and settings page 2806, the system can display an overview page 2810 of the portfolio sliding screen page 2802. In response to these interactions with the tool details page 2808, the system can display a tool portfolio details page 2812. The overview page 2810 can generate a tool details view action 2814. In response to generating the tool details view action 2814, the system can display the tool details page 2808. In various specific embodiments, the portfolio details page 2812 of the tool can be configured to generate an initial closing position action 2816, a modification order or stop-loss action 2818, and a view tool details action 2814. In various specific embodiments, the system can display the closing position interface in response to the initial closing position action 2816, and can display the order interface in response to the modification order or stop-loss action 2818.

[0127] In various embodiments, and referring specifically to Figures 29A and 29B, the order modification procedure 2900 of system 100 is illustrated. In various embodiments, this order modification procedure may be triggered in response to receiving any of the following: an initial draft buy / sell order action 2902, an initial draft buy / sell order initial action 2904, or an initial draft buy / sell order with price action 2906. The system may then display an order modification page 2908. The system may receive size input 2910. The system may check the limit price setting 2912 and may check the stop-loss trigger setting 2914. In response to the limit price setting 2912, the system may wait for the limit price input 2916. With the stop-loss trigger setting 2914, the system may wait for the stop-loss trigger input 2918 and the trigger type input 2920. Upon receiving these inputs (2916, 2918, 2920), the system can check if a limit price has been entered (2922), and if not, check if a trigger price has been entered (2924). If no trigger price has been entered, the system can display a preview of the current price order (2926) and generate a confirmed buy / sell order action (2928).

[0128] If a trigger price is input, the system can execute directional procedure 2930 based on the input trigger price and the input trigger type. Based on the result of directional procedure 2930, the system can display a preview of a profit-taking order at the current price (2932) or a preview of a stop-loss order at the current price (2934), and continue to generate a confirmed buy / sell order (2928). If a limit price is input, the system can determine the only pending order option (2936). If no trigger price is input, the system can display a preview of a limit order (2938) and continue to generate a confirmed buy / sell order (2928). If both a limit price and a trigger price are input, the system can execute directional procedure 2930 based on the input trigger price and the input trigger type. Based on the result of directional procedure 2930, the system can display a preview of a profit-taking limit order (2940) or a preview of a stop-loss limit order (2942), and continue to generate a confirmed buy / sell order (2928).

[0129] In various specific embodiments, and referring specifically to Figures 30A and 30B, a maintenance procedure 3000 of system 100 is illustrated. Native application 110 can be launched on user device 104 and determines a connection to wide area network 3002. Upon determining a connection failure, the system can enter a disconnected state 3004 and display a disconnected status. Upon entering the disconnected state 3004, the system can begin a reconnection procedure 3006. Upon determining a connected state, the system can check for updates 3008. Upon determining an available update, the system can enter a forced update state 3010 and wait for an immediate update action 3012. If not, the system can check for server maintenance status 3014. Upon determining valid server maintenance, the system can enter server maintenance status 3016 and generate a status page recording action 3018. With the status page recording action 3018, the system can launch a web browser 3020 on user device 104. In server maintenance status 3016, the system can check that server maintenance is complete 3022. Upon determining that server maintenance is complete, the system can check the login process status 3024. If login has not been performed, the system can check the logged-in status 3026. If the logged-in status is true, the system continues to check the previous status data of the local APP 110 (3028). If the previous status data exists, the system can determine whether the previous session is still valid 3030. If the previous session is still valid, the process proceeds to enable the previous session 3032.

[0130] In various specific embodiments, and referring specifically to Figures 31A and 31B, the login procedure 3100 of system 100 is illustrated. The system may receive a login action 3102 and subsequently display a login screen 3104. The system may receive an email address and password 3106. The system may receive an authentication token 3108. The system may determine the success status of the login based on the email address and password 3110. If the success status fails, the system may display an error message 3112 and return to the login screen 3104. Otherwise, the system may proceed to determine the receipt of the authentication token 3114. If no token is entered, the system may proceed to a five (5) minute waiting state 3116 for entering the authentication token. The system may exit the waiting state 3116 to the login screen 3104. Upon receiving the authentication token, the system may determine the mobile device verification status 3118. In response to the determination that the device is not verified, the system may initiate a device verification subroutine 3120. Otherwise, the system may proceed to setting a new password prompt 3122. The system may receive the password and prompt for re-entry 3124. The system may compare the passwords to determine a match 3126. The system may return an error if there is a mismatch 3128. Otherwise, the system may determine that biometric authentication is available 3130. If biometric authentication is unavailable, the system may proceed to displaying the main screen 3132. Otherwise, the system may check if Touch ID is available 3134. If it is, the system may begin the biometric authentication process 3136. Otherwise, the system may prompt for Touch ID permissions 3138 and start or disable the biometric authentication process based on those permissions.

[0131] In various specific embodiments, upon initiating the device verification subroutine 3120, the system can transmit a verification link 3140 for mobile device verification. The system can enter a 30-minute waiting state 3142 while waiting for interaction with this verification link. During this waiting state 3142, the system can retransmit the verification link 3144. The system can determine whether the retransmission was successful 3146, and if unsuccessful, can display an error message 3148. The system can determine interaction with the verification link 3150. The system can determine whether the interaction with the verification link is via mobile device 104 (3152). If not, the system can generate a web browser recording action 3158. With this recording action, the system can display an error message 3160. If successful, the system can launch the native app 110 (3154) of mobile device 104. The system can check whether the verification link is invalid 3156. If valid, the system can display a verification link invalidation message 3162 and loop to transmit a new verification link. Otherwise, the system can determine that the device has been verified 3164. If not, the system can generate a verification error message 3166.

[0132] In various specific embodiments, and referring specifically to Figures 32A and 32B, the biometric authentication procedure 3200 of system 100 is illustrated. The system can determine a biometric authentication enabled state 3202. If not, the system can determine a password enabled state 3204. If not, the system can enter a loop procedure 3206 and loop back to the previous state or proceed to the main screen. Upon determining that biometric authentication is enabled, the system can check a device-specific authentication state such as Face ID state 3208, Touch ID state 3210, or Fingerprint ID state 3212. Subsequently, the system can begin the corresponding device-specific biometric authentication procedure. For example, Face ID authentication procedure 3214, Touch ID authentication procedure 3216, and Fingerprint authentication procedure 3218. Any of these authentication procedures 3214, 3216, and 3218 can return a biometric verification state 3220, and the system can proceed to the loop procedure 3206. In various embodiments, with the password enabled state 3222, any of the authentication procedures 3214, 3216, and 3218 may prompt for a password 3224. The system may receive the password and determine a verified password state 3226. With the verified password state and the biometric verified state, the system may proceed to the re-loop procedure 3206. Otherwise, the system may proceed to the failed attempt procedure 3228 and increment the failed attempt state counter 3230. As the failed attempt state counter exceeds a threshold, the system may force a logout event 3232. Subsequently, the system may display an error message 3234 and return to the login screen. In various embodiments, any of the authentication procedures 3214, 3216, and 3218 may return a biometric failure state 3236. Subsequently, the system may prompt for the password 3224.

[0133] By using the interfaces, procedures, and technologies shown in Figures 1 through 32, users of this system may more easily visualize and understand the effects of the proposed transactions. Thus, the user can make faster and / or more informed decisions regarding these proposed transactions, leading to transactions that more closely track the user's desired outcomes (e.g., by reducing and / or eliminating delays in inputting transaction details, reducing and / or eliminating delays associated with the user's consideration or evaluation of the proposed transaction, and / or the like). Furthermore, by reducing the amount of time that the mobile application implementation and / or utilization of this system might require to operate on a mobile device to execute the desired transactions, device battery life can be improved, network congestion can be reduced, and / or other improvements to the operation of the mobile device or other computing or communication systems may be achieved.

[0134] The various embodiments described in this specification are illustrated with reference to the accompanying drawings and images. While these various embodiments are sufficiently detailed to enable those skilled in the art to implement the disclosed content, it should be understood that other embodiments can be implemented and logical and communication changes can be achieved without departing from the spirit and scope of the disclosure. Therefore, the embodiments in this specification are described for illustrative purposes only and not for limiting purposes. For example, the steps stated in any of the methods or procedures described can be performed in any suitable order, and are not limited to the order in which they are described. Moreover, certain functions or steps can be outsourced to or performed through one or more third parties. Modifications, additions, or omissions can be made to the systems, devices, and methods described in this specification without departing from the scope of the disclosure. For example, the components of such systems and devices may be integrated or separated. Moreover, the operation of such systems and devices disclosed in this specification can be performed through more, fewer, or other components, and the described methods may include more, fewer, or other steps. Furthermore, the steps can be performed in any suitable order. As used in this specification, "each" means each member of a set or each member of a subset of a set. Furthermore, any singular reference includes a plurality of embodiments, and any reference to more than one component may include a singular embodiment. Although specific advantages have been listed in the specification, various embodiments may include some, none, or all of those listed advantages.

[0135] Systems, methods, and computer program products are provided. In the embodiments described in this specification, references to "various embodiments," "a specific embodiment," "a particular embodiment," "an exemplary embodiment," etc., may include a specific feature, structure, or characteristic, but each embodiment may not necessarily include that specific feature, structure, or characteristic. Furthermore, these terms do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in conjunction with a specific embodiment, it is considered that this is within the knowledge of those skilled in the art, and that this feature, structure, or characteristic can be affected by other embodiments, whether explicitly described or not. After reading this specification, those skilled in the art will understand how to implement the disclosed content in alternative embodiments.

[0136] As used in this specification, terms such as "satisfy," "conform to," "match," "associated with," or similar expressions may include an equivalent match, a partial match, conforming to certain criteria, a subset of matched data, an association, satisfying certain criteria, a correspondence, an association, an algorithmic relationship, and / or the like. Similarly, as used in this specification, terms such as "certification" or similar expressions may include an exact certification, a partial certification, a subset of certified data, a correspondence, satisfying certain criteria, an association, an algorithmic relationship, and / or the like.

[0137] Terms and expressions similar to "associated" and / or "related" may include tags, flags, associations, which use a lookup table or any other method or system for indicating or establishing relationships between elements (e.g., (i) a trading account and (ii) an order (such as a contract, security, futures), and / or a digital channel). Moreover, the association may occur at any point in time with any suitable action, event, or period. The association may occur within a predetermined interval, periodically, randomly, once, more than once, or upon a suitable request or action. Any information may be distributed and / or accessed via any suitable method (e.g., software-enabled links), wherein such links may be transmitted via email, text, posts, social network input, and / or any other method known in the field.

[0138] The process flows and screenshots depicted in these illustrations are merely specific embodiments and are not intended to limit the scope of the disclosure. For example, the steps stated in any of the methods or procedures described may be performed in any suitable order, and are not limited to the order in which they are described. It will be understood that the following description takes into account not only the steps and user interface elements depicted in the illustrations, but also the various system components illustrated above with reference to FIG1. ​​It should be understood from the outset that although exemplary embodiments are illustrated in the illustrations and described below, the principles of the invention disclosed herein can be implemented using any number of techniques (whether currently known or not). The disclosure of this invention should by no means be limited to the exemplary implementations and techniques illustrated in the drawings and described below. Unless otherwise specifically mentioned, objects depicted in the drawings are not necessarily drawn to scale.

[0139] The computer program (also known as computer control logic) may be stored in main memory and / or auxiliary memory. The computer program may also be received via a communication interface. When executed, this computer program enables the computer system to perform the features discussed in the specification. In particular, when executed, the computer program enables the processor to perform the features of various specific embodiments. Therefore, this computer program represents the controller of the computer system.

[0140] These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to generate a machine, such that the instructions, which execute on the computer or other programmable data processing apparatus, establish means for performing the functions specified in the flowchart blocks. These computer program instructions can also be stored in computer-readable memory that can direct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory generate an article of work including instruction means (which perform the functions specified in the flowchart blocks). These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to generate a computer-executed program, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for performing the functions specified in the flowchart blocks.

[0141] In various embodiments, the software may be stored in a computer program product using a removable storage disk drive, hard disk drive, or communication interface, and loaded into the computer system. When executed by the processor, the control logic (software) causes the processor to perform the functions described in the various embodiments of the specification. In various embodiments, the hardware components may take the form of an Application Specific Integrated Circuit (ASIC). Those skilled in the art will understand that implementing this hardware state machine to perform the functions described in the specification is necessary.

[0142] Those familiar with this art will understand that the system can take the form of a customized existing system, an add-on product, a processing device executing upgrade software, a standalone system, a distributed system, a method, a data processing system, a device for data processing, and / or a computer program product. Therefore, any part of the system or module can take the form of a processing device executing code, an internet-based implementation, a completely hardware implementation, or a combination of internet, software, and hardware. Furthermore, the system may take the form of a computer program product on a computer-readable storage medium (having computer-readable code embodied in that storage medium). Any suitable computer-readable storage medium may be used, including hard drives, solid-state storage devices, optical storage devices, magnetic storage devices, and / or the like.

[0143] In various specific embodiments, the components, modules, and / or engine of system 100 may be implemented as micro-applications or micro-apps. Micro-apps are typically deployed in the context of mobile operating systems, including, for example, Windows Mobile, Android, Apple iOS, Blackberry, and the like. The micro-app may constitute a set of predetermined rules governing the operation of various operating systems and hardware resources, utilizing the resources of the larger operating system and associated hardware. For example, when the micro-app needs to communicate with devices or networks outside the mobile device or mobile operating system, the micro-app may utilize the communication protocols of the operating system and associated device hardware under the predetermined rules of the mobile operating system. Furthermore, when the micro-app requires user input, the micro-app may constitute a request for a response from the operating system (which monitors various hardware components and then communicates the detected input between the hardware and the micro-app).

[0144] The system and method are described in the specification according to functional block components, screenshots, selections as needed, and various processing steps. It should be understood that this functional block can be implemented by any number of hardware and / or software components that perform the specified functions. For example, the system may employ various integrated circuit components, such as memory elements, processing elements, logic elements, lookup tables, and the like, capable of performing multiple functions under the control of one or more microprocessors or other control devices. Similarly, the software components of this system can be implemented using any programming or scripting language, such as C, C++, C#, Java, Javascript, Javascript Object Notation (JSON), VBScript, Macromedia Cold Fusion, Cobol, Active Server Pages (ASP), Perl, Assembly, PHP, awk, Python, Visual Basic, stored procedures, PL / SQL, any Unix shell scripting language, and / or Extensible Markup Language (XML), where various algorithms are implemented using any combination of data structures, objects, programs, conventions, or other programming elements. Furthermore, it should be noted that the system may employ any number of conventional techniques used for data transmission, messaging, data processing, network control, and the like. Moreover, the system can be used to detect or prevent security issues related to user-side scripting languages ​​(such as Javascript, VBScript, or the like).

[0145] The system and method are described in this specification with reference to screenshots, block diagrams, and flowcharts of methods, devices, and computer program products according to various specific embodiments. It will be understood that each functional block of the block diagrams and flowcharts, as well as combinations of functional blocks in the block diagrams and flowcharts, can be implemented separately through computer program instructions.

[0146] Therefore, the function blocks of these block diagrams and flowcharts support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each function block of these block diagrams and flowcharts, and combinations of function blocks in these block diagrams and flowcharts, can be implemented through a dedicated hardware-based computer system or a suitable combination of dedicated hardware and computer instructions to perform the specified functions or steps. Furthermore, the flowcharts and their descriptions can be referenced from user-defined applications, web pages, websites, web forms, prompts, etc. Those skilled in the art will understand that the illustrated steps described in this specification may include any number of configurations, including using window applications, web pages, web forms, pop-up window applications, prompts, and the like. It should be further understood that the multiple steps illustrated and described may be combined into a single web page and / or window application, but have been expanded for simplicity. In other cases, the multiple steps illustrated and described as a single program step may be separated into multiple web pages and / or applications, but have been combined for simplification.

[0147] In various specific embodiments, these software components of the system may also be implemented using a JavaScript execution-time environment that enables the execution of JavaScript code outside a web browser. For example, these software components of the system may also be implemented using Node.js components. A Node.js program may implement several modules to handle various core functionalities. For example, a package management module (such as NPM) may be implemented as an open-source library to help organize the installation and management of third-party Node.js programs. A Node.js program may also implement program managers, such as Parallel Multithreaded Machine (PM2); resource and performance monitoring tools, such as Node Application Metrics (appmetrics); library modules for building user interfaces; and / or any other suitable and / or required modules.

[0148] Middleware can include any hardware and / or software appropriately configured to facilitate communication and / or program transactions between different computing systems. Middleware components are commercially available and known in the art. Middleware can be implemented using commercially available hardware and / or software, custom hardware and / or software components, or a combination thereof. Middleware can reside in various configurations and may exist as a standalone system or as software components residing on an internet server. Middleware can be configured for any of the purposes disclosed in this specification to handle transactions between various components of an application server and any number of internal or external systems. IBM's WebSphere MQ™ (formerly MQSeries) is an example of a commercially available middleware product. Enterprise Service Bus (ESB) applications are another example of middleware.

[0149] The computers discussed in this specification can provide user-accessible suitable websites or other Internet-based graphical user interfaces. In one embodiment, Microsoft's Internet Information Services (IIS), Transaction Server (MTS) service, and SQL Server database are used in conjunction with Microsoft operating systems, Windows web server software, and Microsoft Commerce Server. Furthermore, components such as Access software, SQL Server database, Oracle software, Sybase software, Informix software, MySQL software, and Interbase software can be used to provide an Active Data Object (ADO) compatible database management system. In one embodiment, the Apache web server is used in conjunction with a Linux operating system, MySQL database, and Perl, PHP, Ruby, and / or Python programming languages.

[0150] For simplicity, the conventional data network connections, application development, and other functionalities (and components of the individual operating components of these systems) may not be described in detail in this specification. Furthermore, the connection lines shown in the various diagrams included in this specification are intended to illustrate exemplary functional relationships and / or physical couplings between the various components. It should be noted that many alternative or additional functional relationships or physical connections can be illustrated in practical systems.

[0151] In various specific embodiments, the methods described in the specification are implemented using the various specific machines described in the specification. As will be immediately apparent to those skilled in the art, the methods described in the specification can be implemented in any suitable combination using the following specific machines and machines developed in the following specification. Furthermore, as will be apparent from the disclosure, the methods described in the specification may lead to various transformations of certain objects.

[0152] The various system components discussed in this specification may include one or more of the following: a host server or other computing system, including a processor for processing digital data; a memory coupled to the processor for storing digital data; a digitizer coupled to the processor for inputting digital data; an application stored in the memory and accessible through the processor (for guiding the processing of digital data by the processor); a display device coupled to the processor and the memory (for displaying information derived from the digital data processed by the processor); and multiple databases. The various databases used in this specification may include: client data; merchant data; financial institution data; and / or similar data useful in the operation of the system. As will be appreciated by those skilled in the art, a user computer may include an operating system (such as Windows, Linux, Unix, Solaris, MacOS, etc.) and various conventional support software and drivers, which are typically associated with the computer.

[0153] The system of the present invention, or any part thereof or its functions, may be implemented using hardware, software, or a combination thereof, and may be implemented in one or more computer systems or other processing systems. However, the manipulations performed through the various embodiments may be generally referred to in terms associated with mental tasks performed by an operator (such as matching or selecting). In most cases, any of the operations described in the specification do not require or necessitate the operator's ability. Rather, the operations may be machine-operated, or any of the operations may be performed or enhanced through artificial intelligence (AI) or machine learning. AI generally refers to the study of agents (such as machines, computer-based systems, etc.) that perceive their surrounding world, formulate plans, and make decisions to achieve their goals. The foundations of AI include mathematics, logic, philosophy, probability, linguistics, neuroscience, and decision theory. Many fields fall within the scope of AI, such as computer vision, robotics, machine learning, and natural language processing. Useful machines for performing these various embodiments include general-purpose digital computers or similar devices.

[0154] In various embodiments, these embodiments are directed to one or more computer systems capable of performing the functionalities described in the specification. The computer system includes one or more processors. The processors are connected to communication infrastructure (such as communication buses, cross-over bars, networks, etc.). Various software embodiments are described according to this exemplary computer system. After reading this description, those skilled in the art will understand how to implement various embodiments using other computer systems and / or architectures. The computer system may include a display interface that forwards graphics, text, and other data from the communication infrastructure (or from an undisplayed frame buffer) for display on a display unit.

[0155] The computer system also includes a main memory, such as Random Access Memory (RAM), and may also include secondary memory. The secondary memory may include, for example, a hard disk drive, a solid-state drive, and / or a removable disk drive. The removable disk drive writes to and / or reads from the removable storage unit in a conventional manner. As will be understood, the removable storage unit includes a computer-usable storage medium in which computer software and / or data are stored.

[0156] In various specific embodiments, auxiliary memory may include other similar devices for allowing computer programs or other instructions to be loaded into a computer system. This device may include, for example, a removable storage unit and an interface. Such examples may include a programmable module and interface (as found in video game devices), a removable memory chip (such as an erasable programmable read-only memory (EPROM) or programmable read-only memory (PROM)), and associated slots or other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to a computer system.

[0157] The terms "Computer Program Medium," "Computer Usable Medium," and "Computer Readable Medium" are generally used to refer to media, such as removable disk drives and hard drives installed in hard drives. These computer program products provide software to computer systems.

[0158] The computer system may also include a communication interface. The communication interface allows software and data to be transferred between the computer system and external devices. Examples of a communication interface may include a modem, a network interface (such as an Ethernet card), a communication port, etc. The software and data transmitted via the communication interface are in the form of signals (which may be electronic, electromagnetic, optical, or other signals that can be received through the communication interface). These signals are provided to the communication interface via a communication path (such as a channel). This channel carries signals and can be implemented using wires, cables, optical fibers, telephone lines, cellular chains, radio frequency (RF) chains, wireless, and other communication channels.

[0159] As used in this specification, an "identifier" can be any suitable identifier that uniquely identifies an item. For example, the identifier can be a globally unique identifier ("GUID"). The GUID can be an identifier established and / or implemented under this universally unique identifier standard. Moreover, the GUID can be stored as a 128-bit value that can be displayed as 32 hexadecimal digits. The identifier may also include a primary number and a secondary number. The primary number and secondary number may each be a 16-bit integer.

[0160] In various specific embodiments, the server may include an application server (such as WebSphere, Weblogic, jBoss, Postgres Plus Advanced Server, etc.). In various specific embodiments, the server may include a web server (such as Apache, IIS, Google Web Server, and / or the like).

[0161] A web client includes any device or software that communicates via any network (such as any device or software discussed in this specification). The web client may include internet browsing software installed on a computing unit or system to perform online transactions and / or communications. These computing units or systems may take the form of computers or clusters of computers, but other types of computing units or systems may be used, including personal computers, laptops, notebook computers, tablets, smartphones, mobile phones, personal digital assistants, servers, pooled servers, mainframe computers, distributed computing clusters, information stations, terminals, point-of-sale (POS) devices or terminals, televisions, or any other device capable of receiving data via a network. The web client may include an operating system, as well as various conventional support software and drivers, which are typically associated with a computer. The web client may also run Microsoft Edge, Internet Explorer, Mozilla Firefox, Google Chrome, Apple Safari, or any other of the numerous software packages available for browsing the internet.

[0162] As those skilled in the art will understand, the web client may or may not directly interact with the server (such as the application server, web server, etc. discussed in the specification). For example, the web client may access the server's services through another server and / or hardware components (which may have a direct or indirect connection to the internet server). For example, the web client may communicate with the server via a load balancer. In various specific embodiments, the web client access is via a network or the internet through a commercially available web browser software package. In this respect, the web client may be in a home or commercial environment with access to the network or the internet. The web client may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). The web client may implement several application layer protocols, including HTTP, HTTPS, FTP, and SFTP.

[0163] These various system components can be coupled to the network independently, separately, or collectively via data links, including, for example, a connection to an Internet Service Provider (ISP) via a local loop (typically used with standard modem communications, cable modems, ISDN, Digital Subscriber Line, DSL, or various wireless communication methods). It should be noted that the network may be implemented as other types of networks, such as interactive television (ITV) networks. Furthermore, the system is intended for the use, sale, or distribution of any goods, services, or information through any network with similar functionality as described in the specification.

[0164] The system envisions applications related to web services, utility computing, ubiquitous and personalized computing, cybersecurity and identity solutions, autonomous computing, cloud computing, commodity computing, mobility and wireless solutions, open source, biometrics, grid computing, and / or mesh computing.

[0165] The communications, inputs, storage, databases, or displays discussed in this specification can be facilitated by a website with web pages. As used in this specification, the term "web page" is not intended to limit the types of files and applications that may be used to interact with the user. For example, in addition to standard HTML files, a typical website may include various forms of Java applets, Javascript programs, Active Server Web Pages (ASP), Common Gateway Interface (CGI), Extensible Markup Language (XML), Dynamic HTML, Cascading Style Sheets (CSS), Asynchronous JavaScript and XML (AJAX) programs, helper applications, plug-ins, and the like. A server may include a web server that receives a request from another web server, the request including a URL and an IP address (such as 192.168.1.1). The web server retrieves the appropriate web pages and sends the data or applications used for those web pages to the IP address. Web services are applications that can interact with other applications via communication methods (such as the Internet). Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL, and UDDI. Web service methods are well-known in this field and are covered in many standard texts. For example, Representational State Transfer (REST) ​​or RESTful, web services provide a way to enable interoperability between applications.

[0166] The web client's computing unit may further include an internet browser that connects to the internet or corporate intranet using standard dial-up, cable, DSL, or any other internet protocol known in the field. Transactions originating from the web client can be protected by a firewall to prevent unauthorized access from users on other networks. Furthermore, additional firewalls can be deployed between these different components of the CMS to further enhance security.

[0167] Encryption can be performed using any of the technologies currently available or becoming available in this field, such as Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, GPG (GnuPG), HPE Format-Preserving Encryption (FPE), Voltage, Triple DES, Blowfish, AES, MD5, HMAC, IDEA, RC6, and symmetric and asymmetric cryptosystems. These systems and methods can also be incorporated into SHA family cryptographic methods, elliptic curve cryptography (such as ECC, ECDH, ECDSA, etc.), and / or other post-quantum cryptographic algorithms under development.

[0168] The firewall may include any hardware and / or software appropriately configured to protect CMS components and / or enterprise computing resources from users on other networks. Furthermore, the firewall may be configured to restrict or limit access to various systems and components behind the firewall for web users connecting through a web server. The firewall can be resident in different configurations, including stateful inspection, agent-based access control lists, and packet filtering. The firewall may be integrated into a web server or any other CMS component, or it may be resident as a separate entity. The firewall may implement Network Address Translation (NAT) and / or Network Address Port Translation (NAPT). The firewall may accommodate various tunneling protocols to facilitate secure communication, such as for users in virtual private network connections. The firewall may implement a demilitarized zone (DMZ) to facilitate communication with public networks (such as the Internet). Firewalls can be integrated as software within an internet server or any other application server component, reside on another computing device, or take the form of a standalone hardware component.

[0169] Any database discussed in this specification may include relational, hierarchical, graphical, blockchain, object-oriented structures, and / or any other database configuration. Any database may also include a flat file structure, where data can be stored in a single file in column and row format (without a structure for retrieval and no structural relationships between records). For example, a flat file structure may include bounded text files, comma-separated value (CSV) files, and / or any other suitable flat file structure. Common database products that can be used to implement such databases include IBM's DB2 (Armonke, NY), various database products from Oracle (Redwood City, California), Microsoft Access or SQL Server from Microsoft (Redmond, Washington), MySQL AB (Uppsala, Sweden)'s MySQL, MongoDB, Redis, Apache Cassandra, Apache hBase, MapR-DB from MAPR, or any other suitable database product. Furthermore, any database can be organized in any suitable manner, such as as a table or lookup table. Each record can be a single file, a series of files, a series of data fields, or any other data structure.

[0170] As used in this specification, big data can refer to a partially or fully structured, semi-structured, or unstructured dataset comprising millions of columns and hundreds of thousands of rows. Big data datasets can be compiled, for example, from time-varying transaction records, website registrations, social media, Record of Charge (ROC), Summaries of Charges (SOC), internal data, or other suitable resources. Big data datasets can be compiled without descriptive metadata such as row types, counts, percentiles, or other interpretable data points.

[0171] Certain data correlations can be achieved through any required data correlation techniques (as known or used in the field). For example, this correlation can be achieved manually or automatically. Automatic correlation techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key value field in such tables to speed up the search, sequentially searching all such tables and files, sorting records in a file according to a known order to simplify the search, and / or similar methods. This correlation step can be achieved, for example, through a database merge function using a "key value field" in a pre-selected database or data block. Various database tuning steps are considered to optimize database performance. For example, frequently used files (such as indexes) can be placed on a separate file system to reduce input / output (I / O) bottlenecks.

[0172] More specifically, the "key value field" categorizes the database based on the high-level category of the object defined by that key value field. For example, certain types of data can be designated as key value fields in multiple related tables, and these tables can then be linked based on the type of data in the key value field. The data corresponding to the key value fields in each of the linked tables is preferably the same or of the same type. However, tables with similar but not identical data in those key value fields can also be linked using, for example, AGREP. According to one embodiment, any suitable data storage technology can be used to store data without a standard format. Data sets can be stored using any suitable technology, including, for example, storing individual files using an ISO / IEC 7816-4 file structure; implementing a domain by selecting a dedicated file that discloses one or more basic files containing one or more data sets; using data sets stored in individual files using a hierarchical archiving system; storing data sets as records in a single file (including compressed, SQL-accessible, hashed via one or more keys, numeric, alphabetically ordered via tuples, etc.); storing data as Binary Large Objects (BLOBs); storing data as ungrouped data elements encoded using ISO / IEC 7816-6 data element encoding; storing data as ungrouped data elements encoded using ISO / IEC Abstract Syntax Notation (ASN.1) such as in ISO / IEC 8824 and 8825; and other proprietary technologies, including fractal compression methods, image compression methods, etc.

[0173] In various specific embodiments, the ability to store a wide variety of information in different formats is facilitated by storing the information as BLOBs. Thus, any binary information can be stored in storage space associated with a data set. As mentioned earlier, this binary information can be stored in association with the system or external to the system but closely associated with it. The BLOB method can store a data set as ungrouped data elements formatted as binary blocks using fixed memory offsets, circular queue techniques, or best practices regarding memory management (such as the less recently used paging memory). The ability to store various data sets with different formats using the BLOB method facilitates the storage of data in the database or associated with the system by multiple, unrelated owners of such data sets. For example, a first data set that can be stored may be provided by a first party, a second data set that can be stored may be provided by an unrelated second party, and a third data set that can be stored may be provided by a third party unrelated to the first and second parties. Each of these three exemplary data sets may contain different information stored using different data storage formats and / or technologies. In addition, each dataset can contain subsets of data, which may differ from other subsets.

[0174] This data set annotation can also be used for other types of status information and various other purposes. For example, the data set annotation may include security information that establishes access levels. These access levels may, for example, allow only certain individuals, levels of employees, companies, or other entities to access the data set, or allow access to a specific data set based on the transaction, instrument, contract details, issuer, buyer, seller, user, or the like. Furthermore, the security information may only restrict / allow certain actions, such as accessing, modifying, and / or deleting the data set. In one example, the data set annotation indicates that only the data set owner or the user is allowed to delete the data set, possibly allowing various identified users to access the data set for reading, while other users are completely excluded from accessing the data set. However, other access restriction parameters may also be used, thereby allowing various entities to access the data set through various appropriate permission levels.

[0175] Those familiar with this art will also understand that, for cybersecurity reasons, any database, system, device, server, or other component of that system may be comprised in a single location or in any combination thereof, wherein each database or system includes any of a variety of suitable cybersecurity features, such as firewalls, access codes, encryption, decryption, compression, decompression, and / or the like.

[0176] Professionals will also understand that there are various ways to display data within browser-based documents. Data may be represented as standard text or in fixed lists, scrollable lists, drop-down lists, editable text fields, fixed text fields, pop-ups, and the like. Similarly, there are various methods for modifying data on web pages, such as using free text input from the keyboard, selecting menu items, checkboxes, option boxes, and the like.

[0177] As used in this specification, the term "network" includes any cloud, cloud computing system, or electronic communication system or method, incorporating hardware and / or software components. Communication between these parties can be achieved through any suitable communication channel, such as telephone networks, corporate extranets, corporate intranets, the Internet, interactive points of sale (point-of-sale devices, personal digital assistants, smartphones, information stations, etc.), online communication, satellite communication, offline communication, wireless communication, answering machine communication, local area network (LAN), wide area network (WAN), virtual private network (VPN), network connection or link device, keyboard, mouse, and / or any suitable form of communication or data input. Furthermore, although the system is repeatedly described in this specification as operating via the TCP / IP communication protocol, the system can also operate using IPX, AppleTalk, IP-6, NetBIOS, OSI, any tunneling protocol (such as IPsec, SSH, etc.), or any number of existing or future protocols. If the network is essentially a public network (such as the Internet), it is assumed that the network is insecure and may have an advantage in being open to eavesdroppers. Generally, those skilled in this art are already familiar with the specific information related to the protocols, standards, and application software used with the Internet, so there is no need to describe them in detail in the manual.

[0178] "Cloud computing" includes a model that enables convenient, on-demand network access to a shared pool of configurable computing resources (such as networks, servers, storage, applications, and services) that can be rapidly provisioned and deployed with minimal management effort or service provider interaction. Cloud computing can include location-independent computing, thereby sharing servers to provide resources, software, and data to computers and other devices on demand.

[0179] As used in this specification, "transmission" can include the transfer of electronic data from one system component to another system component via a network connection. Furthermore, as used in this specification, "data" can include information such as commands, queries, files, data for storage, and the like in digital or any other form.

[0180] The term "non-transitory" should be understood to mean only removing the transmitted transient signal itself from the scope of the claim, and does not assign rights to all standard computer-readable media that transmit more than just transient signals. In other words, the terms "non-transitory computer-readable media" and "non-transitory computer-readable storage media" should be understood to exclude only those types of transient computer-readable media found in the In re Nuijten case that fall outside the scope of patentable subject matter as defined in 35 USC § 101 of the U.S. Patent Act.

[0181] The disclosures and claims in this case not only describe specific outcomes and order placement procedures for mobile digital currency transactions, but also include specified rules for implementing such outcomes and order placement procedures, and for presenting information in a specified format for subsequent use and application to establish such desired outcomes and order placement procedures for mobile digital currency transactions, as described in McRO, Inc. v. Bandai Namco Games America Inc. (U.S. Court of the Federal Circuit No. 15-1080, September 13, 2016). In other words, the outcome of such mobile digital currency transactions can be achieved through many different types of rules and combinations of rules, and the disclosures include various specific embodiments with specified rules. Although the absence of complete preemption does not guarantee eligibility of the claims, the disclosures in this case do not fully preempt the field of mobile digital currency transactions. The disclosures in this case are intended to narrow, limit, or constrain the disclosed content, and are not merely intended to encompass a general abstract idea of ​​mobile digital currency transactions. Clearly, other systems and methods may exist for mobile digital currency transactions, therefore it would be inappropriate to assert that this case will preemptively occupy or monopolize such basic tools for mobile digital currency transactions. In other words, the disclosures do not prevent others from providing mobile digital currency transactions, as other systems have already performed this functionality in ways different from the claimed invention. Moreover, the claimed invention includes an inventive concept that can be found in a non-customary and non-general configuration of known custom in Bascom v. AT&T Mobility, 2015-1763 (U.S. Court of the Federal Circuit, 2016). The disclosures and the scope of the patent applications are not merely about any custom of any of these systems, as the interaction and synergy of these systems result in additional functionality not provided by any of these systems operating independently. The disclosed content and the claims may also include the interaction between multiple different systems; therefore, the disclosed content cannot be considered as an implementation of a general-purpose computer, or merely "applied" to an abstract program. The disclosed content and the claims may also be directed at improvements to software by specifying implementations of solutions to problems in the software field.

[0182] Advantages, other benefits, and solutions to the problems have been described in the specification with respect to specific embodiments. However, these advantages, benefits, solutions to the problems, and any elements that may make any advantage, benefit, or solution apparent or more apparent should not be construed as key, required, or necessary features or elements of the disclosure. Therefore, the scope of the disclosure is limited only by the appended claims, wherein the singular reference element is not intended to mean "one and only" unless expressly stated otherwise, but rather "one or more". Moreover, where similar terms such as "at least one of A, B, and C" or "at least one of A, B, or C" are used in the claims or specification, such terms are intended to be interpreted as meaning that only A may exist in a specific embodiment, only B may exist in a specific embodiment, only C may exist in a specific embodiment, or any combination of elements A, B, and C may exist in a single specific embodiment; for example, A and B, A and C, B and C, or A and B and C. Although the disclosed content includes a method, it is conceivable that it may be embodied as computer program instructions on a physical computer-readable medium, such as a magnetic or optical memory or a magnetic disk or optical disc. All structural, chemical, and functional equivalents of the elements of the various embodiments described above, known to those skilled in the art, are explicitly stated in the specification and included for reference and are intended to be covered by the claims of this invention. Furthermore, the apparatus or method need not attempt to solve every problem that is sought to be solved by the disclosure of this invention, as it will be covered by the claims of this invention. Moreover, any element, component, or method step disclosed in this invention is not intended to be made public, whether or not such element, component, or method step is explicitly stated in the claims. Any claim element is not intended to invoke the provisions of U.S. Patent 35 USC § 112(f) unless the element is explicitly stated using the terms "...component" or "...step". As used in this specification, the terms “comprising,” “containing,” or any other variations thereof are intended to cover a non-exclusive inclusion, such that a procedure, method, article, or apparatus that comprises a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to the procedure, method, article, or apparatus.

[0183] 100: System 102: Application Server 104: User Device 106: First Network 108: Second Network 110: Native Application App 200: Trading Platform 202: Start Screen 204: Connection Status 206: Current Price Data 208: Register button 210: Login button 300: Currency Pair Display 302: Current Price 304: Index Price 306: Price 308: Trading Volume 310: Unresolved tool value 312,904: Current Price Chart 314,906: Radio button 316: Authorization Book Information 400: Registration Page 402,502,744: Email address 404, 504: Password 406: Country or region 408: Name 410: Surname 500: Login screen 506: Dual-factor standard 508: Login button 510: Authentication Interface 512: Numeric keypad 514: Push Notification 600: Current Price / Portfolio Interface 602: Cryptocurrency 604: Currency Pair 606: Futures Contract 608: Limited Contract 610: Current Price Information 612: Account Balance Swipe Screen 614: Account Setup Diagram 700: Account Configuration Interface 702: Username 704: Email 706: Notification settings button 708: Cybersecurity Settings Button 710: User Guide Button 712: Help Request Button 714: Service Button 716: Privacy Notification Button 718: Logout button 720: Notification Settings Interface 722: Deposits pending 724: Deposit Confirmation 726: Automatic Delivery Event 728: Liquidation Event 730: Withdrawal Confirmation 732: Alternative Device Login 734: Cybersecurity Settings Interface 736: Enable / Disable command switch 738: Edit Password Button 740: User Guide Page 742: Help Request Page 746: Main Idea List 748: Problem Description 750: Attachment 800: Account Balance Page 802: Total Available Balance 804: Overall PnL 806: Total Margin Balance 808: Total Margin Composition Indicators 810: Position Details 812: Position Details 814: Valid entrustment and / or entrustment type 816: Position Size 818: Compensation Calculation 820:PnL Calculation 822: Position Value 824: Settlement Details Frame 826: Position Details Page 828: Indicators for specific margin composition 830: Request Details Box 832: Valid Delegation 834: Effective Stop Loss 836: Close out positions button 838: Cancel all delegates button 840: Cancel all stop-loss buttons 842: Closing conditions triggered 844,910: Buy button 846,912: Sell button 848: Modify the holdings interface 850: Size input field 852: Restrict input fields 854,1006,1112,1210: Keyboard 856: Confirmed modification of the scroll wheel 858: Cancel Delegation Button 900: Current Price Data Page 902: Data 908: Authorization Book Data Frame 914: Lever Setting Button 1000: Lever Setting Interface 1002: Available margin displayed 1004: Lever Type Selector 1008: Leverage Ratio 1010: Set lever roller 1100: Delegation Interface 1102: Request Details Box 1104: Restriction Setting Button 1106: Stop-loss setting button 1108: Edit Delegation Button 1110: Number of Orders 1114: Stop-loss setting box 1116: Trigger Price 1118: Triggered closing condition switch 1120: Final Price Setting Button 1122: Limitation setting box 1124: Price Restriction 1126: Only Order Condition Switch 1128: Only reduce position condition switch 1130: Sell or buy rollers 1132: Warning 1134: Submit button 1200: Closing Positions Interface 1202: Notification Box 1204: Added a price limit button 1206: Roller 1208: Limitation Setting Box 1212: Column 1214: Removed the price limit button 1300: Commission Return Display 1302: Request for authorization has been submitted. 1304: Second Execution Notice; Execution Notice 1306: First Execution Notice; Execution Notice 1308: Notification of Complete Transaction 1400: Portfolio View Page 1402: Tool Details Box 1404: Portfolio Details View Page 1406: Additional details box 1408: Margin Composition Indicators 1410: Close out positions button 1500: Long Position Interface 1502: Current Price Depth Chart 1504: Switch between buying and selling 1506: Currency Pair Indicator 1508: Lever Setting Button 1510: Delegation Type Display 1512: Mark Price Indicator 1514: Quantity Selection Button 1516: Quantity Input Box 1600: Short Position Interface 1700: Dynamic Margin Position Indicator 1702: Background Bar 1704: Zero open positions 1706: Current holdings 1708: Arrow 1710: New Holding Bar 1712: Bullish Direction 1714: Short Position 2000: Quantity Input Interface 2002: Interface Type Switching 2004: Percentage Scale 2100: Start Program 2102: Determine the operation mode based on the login information. 2104,2410: Anonymous mode program 2106: Authentication Setup Procedure 2108: Receive authentication materials; Receive the authentication materials 2110: Trading Interface Program 2200: Current Price View Page Program 2202,2406: Initial Appearance 2204, 2804: Current Price View Page 2206: Connection 2208: List of Cryptocurrencies 2210: List of Deactivated Cryptocurrencies 2212: Account and Setting Segments 2214: Go to tool selection 2216: Proceed to portfolio selection 2300: Lever Setting Page Program 2302: Initial setting lever input 2304: Setting Leverage Page 2306: Leveraged isolated position input 2308: Leveraged full position entry 2310: Lever Receiving Preview 2312,2504,2808: Tool Details Page 2314,2908: Request to modify the page 2400: Second Start Procedure 2402: Receive command 2404: Determine whether native application 110 is partially cached on user device 104. 2408: Determine login status 2412,2708: Authentication Procedure 2414: Determine if the authentication is restricted 2416,2716: Restricted Procedures 2418: Logout Incident 2420: Deep Link Inspection 2422: Current Price and Portfolio Review Procedure 2424: Create / Modify Delegation Procedure 2500: Tools Details Page Program 2502: Inspection Tool Actions 2506: Initial setting of lever action 2508: Initial buy / sell order action 2510: Heading to Portfolio Actions 2512: Receiving and interacting with price charts 2514: Receiving and Interacting with the Proxy Book 2516,2904: Initial draft buy / sell orders including large and small actions 2518,2906: Initial draft buy / sell order including price action 2600: Closing Positions Page Procedure 2602: Initial closing of positions 2604: Closing Positions Page 2606: Settle at the current price 2608: The judgment has been changed to settlement under the price restriction. 2610: Restrict price input 2612: Determine whether the price limit input is entered (i.e., a non-zero value). 2614: Confirmation of Restricted Settlement Status 2616: Confirmation of Current Price Settlement Status 2700: Third Start Program; Program 2702: Determine login status 2704: Perform a restricted authentication soft check 2710: Restricted Warning Status 2712: Preset State 2714: Conduct a hard check to determine if certification is restricted. 2718: Restricted Mode 2800: Portfolio Sliding Screen App 2802: Portfolio Sliding Screen Page 2806: Account and Settings Page 2810: Overview Page 2812: Portfolio Details Page (Tools) 2814: Inspection Tool Details 2816: Initial closing of positions 2818: Modify order or stop-loss action 2900: Request to Modify Procedure 2902: Initial draft of buy / sell order actions 2910: Size Input 2912: Price Restriction 2914: Stop-loss trigger setting 2916: Limit price input; Input 2918: Stop-loss trigger input; Input 2920: Trigger type input; Input 2922: Price limit entered 2924: Checking that the trigger price has been entered. 2926: Preview of Current Price Order Receiver 2928: Confirm buy / sell order action 2930: Directional Procedure 2932: Preview of Profit-Taking Current Price Orders 2934: Stop-loss order preview at current price 2936: Determine if only pending orders are selected. 2938: Restricting the Reception of Delegates (Preview) 2940: Profit-Limited Order Receiving Preview 2942: Stop-loss limit order reception preview 3000: Maintenance Procedure 3002: Wide Area Network 3004: Not connected 3006: Reconnection program 3008: Update 3010: Forced update status 3012: Update Actions Immediately 3014: Server maintenance status 3016: Server maintenance status 3018: Status page records actions 3020: Start user device 104's web browser 3022: Server maintenance has been completed. 3024: Check login process status 3026: Checking login status 3028: Check the previous status data of this device's APP 110 3030: Determine if the previous conversation is still useful. 3032: Enable the previous state 3100: Login Procedure 3102: Receive login action 3104: Login screen 3106: Email and Password 3108: Certification Mark 3110: Based on email and password, 3110 determines the success status of the login. Error messages 3112, 3148, 3160, 3234: 3114: Determining the Acceptance of Authentication Marks 3116: Five (5) minutes waiting status 3118: Determine the verification status of the mobile device 3120: Device Verification Subroutine 3122: Set a new password hint 3124: Re-enter the password 3126: Compare the passwords to determine if they match. 3128: Mismatch 3130: Determine if biometric authentication is available 3132: Main screen 3134: Check if Touch ID is available 3136: Biometric Authentication Procedure 3138: Prompts for Touch ID permissions to be activated. 3140: Transmit verification link for mobile device verification. 3142: Entering 30-minute waiting status 3144: Retransmit the verification link 3146: Determine whether the retransmission was successful. 3150: Verification Link 3152: Determine whether the interaction with the verification link is via mobile device 104 3154: Start mobile device 104's local APP 110 3156: Check if the verification link is faulty. 3158: Generates web browser recording actions 3162: Verify link failure message 3164: The device has been verified. 3166: Verification error message 3200: Biometric Authentication Program 3202: Biometric authentication is now enabled. 3204: Password enabled. 3206: Recycled Program 3208: Check device-specific authentication status, such as Face ID status. 3210: Check device-specific authentication status, such as Touch ID status. 3212: Check device-specific authentication status, such as fingerprint ID status. 3214: Face ID Authentication Program 3216: Touch ID Authentication Program 3218: Fingerprint Authentication Program 3220: Biometric verification status 3222: Password enabled 3224: Prompt for password; Prompt for this password 3226: Determine the status of verified password 3228: Failed attempt procedure 3230: Incrementing Failed Attempt Status Counter 3232: Forced Logout Incident 3236: Failed to transmit biometric data

Claims

1. A method for trading mobile digital currency futures, comprising: receiving an order input for one of an assets associated with a trading account through a computer-based implementation system; generating a platform command set through the computer-based implementation system based on the order input; executing one or more transactions simultaneously or sequentially on the trading platform through the computer-based implementation system based on the platform command set controlling the trading platform; determining a current open position value through the computer-based implementation system based on a current value of the asset; determining a dynamic margin position for the trading account associated with login information through the computer-based implementation system, wherein the dynamic margin position is based on the current open position value relative to the maximum open position associated with a currency pair, an available margin, and the order input; determining a maximum long position margin and a maximum short position margin through the computer-based implementation system based on the current open position value and the available margin; calculating a zero open position margin through the computer-based implementation system based on the maximum long position margin and the maximum short position margin. The computer-based system displays a dynamic margin position indicator, including the zero margin, the maximum margin for long positions, the maximum margin for short positions, and the dynamic margin position; and displays the dynamic margin position indicator relative to a current position and between the maximum margin for long positions and the maximum margin for short positions; wherein the dynamic margin position indicator is scaled accordingly based on the maximum margin for long positions and the maximum margin for short positions.

2. The mobile digital currency futures trading method of Request 1 further includes: receiving the login information through the computer-based implementation system; generating an authentication request through the computer-based implementation system based on the login information; receiving authentication information through the computer-based implementation system; and displaying a trading interface including a portfolio sliding screen through the computer-based implementation system based on the authentication information.

3. The mobile digital currency futures trading method as described in Request 1, wherein the order input includes at least one of a buy order, a sell order, an order modification, a leverage setting, or a position liquidation command.

4. The mobile digital currency futures trading method as described in claim 2, wherein the portfolio swipe screen is displayed in response to interaction with a current price view page, an account and settings page, and / or an instrument details page, and the portfolio swipe screen includes an instrument details page and an account summary page.

5. The mobile digital currency futures trading method as described in Request 1 further includes: receiving a tool selection through the computer-based implementation system; and, upon receiving the tool selection, initiating an order placement procedure through the computer-based implementation system.

6. The mobile digital currency futures trading method of Request 1 further includes: receiving a new order input through the computer-based system and via the advanced position interface, the new order input including a currency pair and a quantity; and, in response to receiving the new order input, adjusting the dynamic margin position indicator in real time through the computer-based system based on a new position value determined from the currency pair, the quantity, and the dynamic margin position.

7. A mobile digital currency futures trading system, comprising: receiving, via a processor, an order input for one of an asset associated with a trading account; generating, via the processor, a platform command set based on the order input; controlling, via the processor, to execute one or more transactions simultaneously or sequentially on the trading platform based on the platform command set controlling the trading platform; determining, via the processor, a current open position value based on a current value of the asset; determining, via the processor, a dynamic margin position for the trading account associated with login information, wherein the dynamic margin position is based on the current open position value relative to the maximum open position associated with a currency pair, an available margin, and the order input; determining, via the computer-based implementation system, a maximum long position margin and a maximum short position margin based on the current open position value and the available margin; and calculating a zero open position margin based on the maximum long position margin and the maximum short position margin. The processor displays a dynamic margin position indicator including the zero margin, the maximum margin in the long direction, and the maximum margin in the short direction; and displays the dynamic margin position indicator relative to a current position and between the maximum margin in the long direction and the maximum margin in the short direction; wherein the dynamic margin position indicator is scaled accordingly based on the maximum margin in the long direction and the maximum margin in the short direction.

8. The mobile digital currency futures trading system of claim 7 further includes: receiving the login information through the processor; generating an authentication request through the processor based on the login information; receiving authentication information through the processor; and displaying a trading interface including a portfolio sliding screen through the processor based on the authentication information.

9. The mobile digital currency futures trading system as described in Request 7, wherein the order input includes at least one of a buy order, a sell order, an order modification, a leverage setting, or a position liquidation command.

10. The mobile digital currency futures trading system as described in claim 8, wherein the portfolio slideshow is displayed in response to interaction with a current price view page, an account and settings page, and / or an instrument details page, the portfolio slideshow including an instrument details page and an account summary page.

11. The mobile digital currency futures trading system of claim 10 further includes: receiving an instrument detail selection through the processor; and initiating an order placement procedure through the processor upon receiving the instrument detail selection.

12. The mobile digital currency futures trading system of claim 7 further includes: receiving a new order input via the processor and through the advanced position interface, the new order input including a currency pair and a quantity; and, in response to receiving the new order input, adjusting the dynamic margin position indicator in real time via the processor based on a new position value determined from the currency pair, the quantity, and the dynamic margin position, the dynamic margin position indicator being displayed relative to a current position and between the maximum margin in the long direction and the maximum margin in the short direction.

13. A computer program article comprising a non-transitory tangible computer-readable storage medium having instructions stored thereon, which, upon execution by a computer-based implementation system, cause the computer-based implementation system to perform operations including: receiving an order input for an asset associated with a trading account through the computer-based implementation system; generating a platform command set through the computer-based implementation system based on the order input; executing one or more transactions simultaneously or sequentially on a trading platform through the computer-based implementation system based on the platform command set controlling the trading platform; determining a current position value through the computer-based implementation system based on a current value of the asset; and determining a dynamic margin position for the trading account associated with login information through the computer-based implementation system, wherein the dynamic margin position is based on the current position value relative to the maximum position associated with a currency pair, an available margin, and the order input. Based on the current open position and the available margin, the computer-based system determines the maximum margin for a long position and the maximum margin for a short position; based on the maximum margin for a long position and the maximum margin for a short position, the computer-based system calculates a zero open position margin; the computer-based system displays a dynamic margin position indicator including the zero open position margin, the maximum margin for a long position, the maximum margin for a short position, and the dynamic margin position; and displays the dynamic margin position indicator relative to the current open position and between the maximum margin for a long position and the maximum margin for a short position; wherein the dynamic margin position indicator is scaled accordingly based on the maximum margin for a long position and the maximum margin for a short position.

14. The computer program article of claim 13, which causes the computer-based system to perform the following operations: receiving login information through the computer-based system; generating an authentication request through the computer-based system based on the login information; receiving authentication information through the computer-based system; and displaying a trading interface including a portfolio slideshow through the computer-based system based on the authentication information.

15. The computer program as described in request item 13, wherein the order placement input includes at least one of a buy order, a sell order, an order modification, a leverage setting, or a position liquidation command.

16. The computer program article of claim 14, wherein the portfolio slideshow is displayed in response to interaction with a current price view page, an account and settings page, and / or a tool details page, the portfolio slideshow including a tool details and an account summary.

17. The computer program article of claim 16, which causes the computer-based implementation system to perform the following operations: receiving a tool list selection through the computer-based implementation system; and, upon receiving the tool list selection, initiating an order placement procedure through the computer-based implementation system.

18. The computer program article of claim 13, which causes the computer-based system to perform the following operations: receiving a new order input through the computer-based system and via the advanced position interface, the new order input including a currency pair and a quantity; and, in response to receiving the new order input, adjusting the dynamic margin position indicator in real time through the computer-based system based on a new position value determined from the currency pair, the quantity, and the dynamic margin position, the dynamic margin position indicator being displayed relative to a current position and between the maximum margin in the long direction and the maximum margin in the short direction.

19. The computer program of claim 17, wherein adjusting the dynamic margin position indicator further includes generating a new position value indicator, the new position value indicator being displayed in a background bar of the dynamic margin position indicator as the new position value relative to the current position value.

20. The computer program article of claim 17, which causes the computer-based implementation system to perform the following operations: receiving a second new order input through the computer-based implementation system, the second new order input including the currency pair and an adjustment quantity; and, in response to receiving the second new order input, adjusting the dynamic margin position indicator in real time through the computer-based implementation system based on the currency pair, the adjustment quantity, and the dynamic margin position, the dynamic margin position indicator being displayed relative to the current position and between the maximum margin in the long direction and the maximum margin in the short direction.

Images