Exchange platform in a distributed assets management platform
Disclosed herein are methods and systems for a simplified process for managing the exchange of different types of assets on a digital platform for disparate users. The processes discussed with respect to the digital platform streamline the exchange of assets based on various conditions in an efficient manner. In one example, the platform initially receives an event message (via an endpoint API) that specifies the amounts and types of two different assets. The platform then aggregates the received data within the event message. Next, the platform's exchange manager continually monitors the data indicated within the event message. When the totals reach a predefined threshold or condition, such as reaching a certain amount, the platform triggers a process where a remote system automatically converts a specified amount of one asset type into another asset type.
1 . A method for asset exchange management, comprising:
receiving, by an application programming interface (API) endpoint of an exchange platform, a stream of API event messages associated with asset transfers initiated by distributed service systems, the stream of API event messages comprising an API event message having a format that comprises a first data field that identifies an entity associated with the API event message, a second data field that defines a first amount of a first type of asset, and a third data field that defines a second amount of a second type of asset;
processing, by an aggregator of the exchange platform, the data stored in the second data field and the third data field of the API event message to accumulate a total amount of the first type of asset and a total amount of the second type of asset in response to receipt of the API event message from the API event messages of the stream, and the aggregator is one of a plurality of aggregators of the exchange platform that is selected based on the entity identified in the first data field;
detecting, by an exchange manager of the exchange platform, an exchange event message generation trigger when at least one of the total amount of the first type of asset and the total amount of the second type of asset accumulated by the aggregator satisfies a condition defining when a second amount of the first type of asset is to be converted to the second type of asset;
in response to detecting the exchange event message generation trigger, generating, by the exchange manager of the exchange platform, an exchange event message that comprises a fourth data field that defines a source account, a fifth data field that defines a destination account, and a sixth data field that defines the second amount of the first type of asset that is to be converted to the second type of asset; and
transmitting, by the exchange manager to an exchange executor, the generated exchange event message causing the exchange executor to process an exchange based on the fourth data field, the fifth data field, and the sixth data field a trade using a remote system that converts the second amount of the first type of asset to the second type of asset.
2 . The method of claim 1 , wherein the first type of asset is stored in a first geographic location, the second type of asset is stored in a second geographic location, and a conversion of the second amount of the first type of asset to the second type of asset comprises:
reducing the total amount of the first type of asset stored in the first geographic location by the second amount of the first type of asset;
converting the second amount of the first type of asset to a converted amount of the second type of asset using the remote system; and
increasing the total amount of the second type of asset stored in the second geographic location by the converted amount of the second type of asset.
3 . The method of claim 1 , wherein the processing of the API event message by the aggregator is performed on a first periodic basis to process a plurality of new API exchange event messages that are received by the API endpoint of the exchange platform.
4 . The method of claim 3 , wherein the exchange manager detects the condition on a second periodic basis, and wherein a period of the first periodic basis is less than a period of the second periodic basis.
5 . The method of claim 1 , further comprises:
storing, in a data store, a record of a completion of a process that converted the second amount of the first type of asset to the second type of asset; and
in response to a user request, generating a graphical user interface to display data indicative of the conversion.
6 . The method of claim 1 , further comprising:
generating a graphical user interface with a current configuration of the condition;
receiving, via the graphical user interface, a new configuration of the condition that is different from the current configuration of the condition; and
performing the detection of at least one of the total amount of the first type of asset and the total amount of the second type of asset satisfying the condition based on the new configuration of the condition.
7 . The method of claim 1 , wherein the condition comprises an amount threshold indicative of a maximum total amount of the first type of asset and/or a maximum total amount of the second type of asset.
8 . The method of claim 1 , wherein the condition comprises a volatility threshold value indicative of fluctuation indicative of a conversion parameter of a conversion to be processed using the remote system.
9 . The method of claim 1 , wherein the condition comprises an anomaly threshold that defines a maximum total amount based on a historical total amount of the first type of asset and/or a historical total amount of the second type of asset.
10 . The method of claim 1 , further comprising:
generating, by the exchange manager, a liquidity event message based on the conversion of the second amount of the first type of asset to the second type of asset; and
transmitting, from the exchange platform, the liquidity event message to a liquidity engine for a periodic movement of assets between accounts.
11 . A non-transitory machine readable medium may have instructions stored thereon, which when executed by a processing system, causes the processing system to perform operations for asset exchange management, the operations comprising:
receiving, by an application programming interface (API) endpoint of an exchange platform, a stream of API event messages associated with asset transfers initiated by distributed service systems, the stream of API event messages comprising an API event message having a format that comprises a first data field that identifies an entity associated with the API event message, a second data field that defines a first amount of a first type of asset, and a third data field that defines a second amount of a second type of asset;
processing, by an aggregator of the exchange platform, the data stored in the second data field and the third data field of the API event message to accumulate a total amount of the first type of asset and a total amount of the second type of asset in response to receipt of the API event message from the API event messages of the stream, and the aggregator is one of a plurality of aggregators of the exchange platform that is selected based on the entity identified in the first data field;
detecting, by an exchange manager of the exchange platform, an exchange event message generation trigger when at least one of the total amount of the first type of asset and the total amount of the second type of asset accumulated by the aggregator satisfies a condition defining when a second amount of the first type of asset is to be converted to the second type of asset;
in response to detecting the exchange event message generation trigger, generating, by the exchange manager of the exchange platform, an exchange event message that comprises a fourth data field that defines a source account, a fifth data field that defines a destination account, and a sixth data field that defines the second amount of the first type of asset that is to be converted to the second type of asset; and
transmitting, by the exchange manager to an exchange executor, the generated exchange event message causing the exchange executor to process an exchange based on the fourth data field, the fifth data field, and the sixth data field a trade using a remote system that converts the second amount of the first type of asset to the second type of asset.
12 . The non-transitory machine readable medium of claim 11 , wherein the first type of asset is stored in a first geographic location, the second type of asset is stored in a second geographic location, and a conversion of the second amount of the first type of asset to the second type of asset comprises:
reducing the total amount of the first type of asset stored in the first geographic location by the second amount of the first type of asset;
converting the second amount of the first type of asset to a converted amount of the second type of asset using the remote system; and
increasing the total amount of the second type of asset stored in the second geographic location by the converted amount of the second type of asset.
13 . The non-transitory machine readable medium of claim 11 , wherein the processing of the API event message by the aggregator is performed on a first periodic basis to process a plurality of new API exchange event messages that are received by the API endpoint of the exchange platform.
14 . The non-transitory machine readable medium of claim 13 , wherein the exchange manager detects the condition on a second periodic basis, and wherein a period of the first periodic basis is less than a period of the second periodic basis.
15 . The non-transitory machine readable medium of claim 11 , the operations further comprising:
storing, in a data store, a record of a completion of a process that converted the second amount of the first type of asset to the second type of asset; and
in response to a user request, generating a graphical user interface to display data indicative of the conversion.
16 . A system, comprising:
a non-transitory memory storing instructions; and
a processing system coupled with the memory and configured to execute the instructions causing the system to perform operations, the operations comprising:
receiving, by an application programming interface (API) endpoint of an exchange platform, a stream of API event messages associated with asset transfers initiated by distributed service systems, the stream of API event messages comprising an API event message having a format that comprises a first data field that identifies an entity associated with the API event message, a second data field that defines a first amount of a first type of asset, and a third data field that defines a second amount of a second type of asset;
processing, by an aggregator of the exchange platform, the data stored in the second data field and the third data field of the API event message to accumulate a total amount of the first type of asset and a total amount of the second type of asset in response to receipt of the API event message from the API event messages of the stream, and the aggregator is one of a plurality of aggregators of the exchange platform that is selected based on the entity identified in the first data field;
detecting, by an exchange manager of the exchange platform, an exchange event message generation trigger when at least one of the total amount of the first type of asset and the total amount of the second type of asset accumulated by the aggregator satisfies a condition defining when a second amount of the first type of asset is to be converted to the second type of asset;
in response to detecting the exchange event message generation trigger, generating, by the exchange manager of the exchange platform, an exchange event message that comprises a fourth data field that defines a source account, a fifth data field that defines a destination account, and a sixth data field that defines the second amount of the first type of asset that is to be converted to the second type of asset; and
transmitting, by the exchange manager to an exchange executor, the generated exchange event message causing the exchange executor to process an exchange based on the fourth data field, the fifth data field, and the sixth data field a trade using a remote system that converts the second amount of the first type of asset to the second type of asset.
17 . The system of claim 16 , wherein the first type of asset is stored in a first geographic location, the second type of asset is stored in a second geographic location, and a conversion of the second amount of the first type of asset to the second type of asset comprises:
reducing the total amount of the first type of asset stored in the first geographic location by the second amount of the first type of asset;
converting the second amount of the first type of asset to a converted amount of the second type of asset using the remote system; and
increasing the total amount of the second type of asset stored in the second geographic location by the converted amount of the second type of asset.
18 . The system of claim 16 , wherein the processing of the API event message by the aggregator is performed on a first periodic basis to process a plurality of new API exchange event messages that are received by the API endpoint of the exchange platform.
19 . The system of claim 18 , wherein the exchange manager detects the condition on a second periodic basis, and wherein a period of the first periodic basis is less than a period of the second periodic basis.
20 . The system of claim 16 , the operations further comprising:
storing, in a data store, a record of a completion of a process that converted the second amount of the first type of asset to the second type of asset; and
in response to a user request, generating a graphical user interface to display data indicative of the conversion.