Systems, methods, and computing platforms for managing network-enabled security codes

Abstract

Various embodiments of the present disclosure provide techniques for facilitating credential-free exchange across networks using multiple identifier mappings, member interfaces, and secure symbol groups customized for temporary keys. These techniques may include receiving a secure interaction request, and issuing or enabling a previously issued generic unique temporary key (UUEK) in response to the secure interaction request. These techniques may include authenticating a user, a tool, or the UUEK, in response, storing a security event for the user, the tool, or the UUEK, and providing a secure interaction response indicative of the security event. These techniques may include subsequently receiving an exchange request for performing a value-based exchange using the UUEK, and facilitating the exchange request based at least in part on the security event.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 370,278 filed on August 3, 2022 and U.S. Patent Application Serial No. 18 / 363,796 filed on August 2, 2023, the entire contents of both applications (including any figures, tables, drawings, and appendices) are incorporated herein by reference. Technical Field

[0003] Embodiments of the present disclosure generally relate to network-enabled security codes. Background Art

[0004] In view of the limitations of existing exchange processing technologies and architectures, various embodiments of the present disclosure address technical challenges associated with network-based exchanges. Existing processes for performing exchanges over computing networks rely on the use of permanent credentials such as payment credentials (e.g., card numbers, usernames, passwords, bank routing numbers, account numbers, etc.) and their proxies, which expose recipients of the credentials to fraud, regulatory and compliance costs, and reputational risks. In addition, due to the static nature of traditional credentials, each time a user provides their credentials for an exchange, the user must accept the risk of financial loss, damaged credit scores, identity theft, and other consequences. Rigorous communication protocols, data management procedures, and authentication schemes are typically used to address the inherent deficiencies in the security of permanent credentials, each of which introduces additional technical issues by increasing overhead and complicating network-based transactions without addressing the fundamental technical issues of data security.

[0005] For example, one technique includes using a vendor-managed personal identification number (PIN) and / or other security code that can be set by a user or vendor and subsequently used to authenticate exchanges using a particular account. These codes can be encoded within the physical media and automatically authenticated each time an exchange is authorized using the physical media. Alternatively, the code can be provided to the vendor along with the exchange request to authorize each individual exchange.

[0006] Traditional codes lack flexibility and are insecure in many different ways. First, traditional codes are deployed in four-digit numbers, which provides an attack vector for malicious parties because they can be subject to brute force attacks given the limited number of available combinations. Furthermore, in order to work effectively, traditional codes must be provided at the same time as the exchange is requested. This results in increased network traffic and increases the cost of the exchange even if the exchange is rejected. In addition, such codes are traditionally applied to all exchanges, cannot be configured for specific characteristics of the request (e.g., exchange value, time, etc.), are cumbersome to change, and increase liability for users (e.g., in cases where the code is encoded into physical media) or vendors. These and other technical challenges limit the effectiveness of traditional security codes, which in turn creates security challenges for performing network-based exchanges.

[0007] Various embodiments of the present disclosure make important contributions to various existing network-based value exchange processing technologies by addressing each of these technical challenges. Summary of the invention

[0008] Various embodiments of the present disclosure disclose a secure intermediate computing platform and computing service that facilitates the credential-free execution of value-based exchanges that utilize UUEK (Universally Unique Temporary Key) to eliminate the use of permanent credentials. To this end, the intermediate computing platform can facilitate interactions between one or more member platforms to register users and / or user tools in a value exchange system that is supported by a new, temporary data structure referred to herein as UUEK. Unlike traditional exchange systems, the intermediate computing platform does not receive or rely on permanent user or tool credentials to register users and / or users' tools. Eliminating such credentials enables the use of new, more flexible interfaces, such as the application programming interface (API) described herein, which the intermediate computing platform fully utilizes to communicate with different network members to register users, users' tools, tool policies, and different security codes without exposing user credentials at any step in the process. Once registered, the intermediate computing platform can issue a UUEK to the member platform, which can replace traditional permanent credentials. The issued UUEK does not reflect permanent credentials or any other sensitive user or tool information. The interface between the member platform and the intermediary platform can allow (i) the user to present the UUEK issued by the member platform (without explicitly referencing the permanent credential) to the intermediary platform, and (ii) the intermediary platform to map the issued UUAK to the instrument key of the same or another member platform and provide the instrument key to the member platform to authorize the value-based exchange. In this way, network-based transactions can be authorized in a seamless process without exposing sensitive user or instrument information that may be vulnerable to network attacks.

[0009] Some technologies of the present disclosure further enhance the security of network-based exchanges by taking full advantage of flexible interfaces (such as APIs) between entities of value-based exchanges to establish security codes for UUEKs. Security codes can be used to enable and disable UUEKs for authorized exchanges. In this way, the execution of value-based exchanges can be predicted based at least in part on the decision of the security code for the UUEK. Importantly, the security code is network-managed and enables n-character codes of varying complexity. As described herein, this allows tool-specific security measures to be enforced by an intermediary platform before the exchange authorization is provided to a service provider (such as a financial institution) without the risk of exposing sensitive user or financial information. Ultimately, the technology of the present disclosure achieves additional flexibility (e.g., by using new interfaces, etc.) and security (e.g., by eliminating permanent credentials, introducing new security codes, etc.), while reducing computing power requirements and significantly improving network throughput for exchange processing compared to traditional technologies.

[0010] In some embodiments, a computer-implemented method includes receiving, by one or more processors, a security interaction request indicating a security code input and a user identifier; identifying, by the one or more processors, a security code element group for the security code input based on the user identifier; verifying, by the one or more processors, the security code input based at least in part on a comparison between the security code input and a security code reference of the security code element group; in response to verifying the security code input, (i) storing, by the one or more processors, a security event for a user, and (ii) providing, by the one or more processors, a security interaction response indicating the security event, wherein the security interaction response indicates at least one of (a) a universally unique temporary key (UUEK) or (b) a security event for the UUEK; receiving, by the one or more processors, an exchange request for performing a value-based exchange using the UUEK; providing, by the one or more processors, an exchange authorization request to the member platform, wherein the exchange authorization request indicates the tool identifier and the security event; and receiving, by the one or more processors, an exchange authorization response indicating at least one of an exchange approval or an exchange denial, wherein the exchange authorization response is based at least in part on the security event.

[0011] In some embodiments, a computing system includes a memory and one or more processors communicatively coupled to the memory, the one or more processors configured to receive a security interaction request indicating a security code input and a user identifier; identify a security code element group for the security code input based on the user identifier; verify the security code input based at least in part on a comparison between the security code input and a security code reference of the security code element group; in response to verifying the security code input, (i) store a security event for the user, and (ii) provide a security interaction response indicating the security event, wherein the security interaction response indicates at least one of (a) a universally unique temporary key (UUEK) or (b) a security event for the UUEK; receive an exchange request for performing a value-based exchange using the UUEK; provide an exchange authorization request to a member platform, wherein the exchange authorization request indicates a tool identifier and the security event; and receive an exchange authorization response indicating at least one of an exchange approval or an exchange rejection, wherein the exchange authorization response is based at least in part on the security event.

[0012] In some embodiments, one or more non-transitory computer-readable storage media include instructions that, when executed by one or more processors, cause the one or more processors to receive a security interaction request indicating a security code input and a user identifier; identify a security code element group for the security code input based on the user identifier; verify the security code input based at least in part on a comparison between the security code input and a security code reference for the security code element group; in response to verifying the security code input, (i) store a security event for a user, and (ii) provide a security interaction response indicating the security event, wherein the security interaction response indicates at least one of (a) a universally unique temporary key (UUEK) or (b) a security event for the UUEK; receive an exchange request for performing a value-based exchange using the UUEK; provide an exchange authorization request to a member platform, wherein the exchange authorization request indicates a tool identifier and the security event; and receive an exchange authorization response indicating at least one of an exchange approval or an exchange rejection, wherein the exchange authorization response is based at least in part on the security event. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Having generally described the present disclosure, reference will now be made to the accompanying drawings (which are not necessarily drawn to scale), and wherein:

[0014] Figure 1 is an example diagram of a computing ecosystem according to one or more embodiments of the present disclosure;

[0015] Figure 2 is an example schematic diagram of a computing platform according to one or more embodiments of the present disclosure;

[0016] Figure 3 is an example schematic diagram of a client device according to one or more embodiments of the present disclosure;

[0017] Figure 4 is an example block diagram of an example voucherless value exchange system according to one or more embodiments of the present disclosure;

[0018] Figure 5 is an example data graph for facilitating voucherless value exchange according to one or more embodiments of the present disclosure;

[0019] Figure 6 A process flow for facilitating network management security codes for users according to one or more embodiments of the present disclosure is provided;

[0020] Fig. 7A -C provides a process flow for establishing a secure cross-entity relationship according to one or more embodiments of the present disclosure;

[0021] Fig. 8A -B provides a process flow for facilitating secure credential-free interaction according to one or more embodiments of the present disclosure;

[0022] Fig. 9A -C provides an example interface for facilitating voucherless value exchange according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION

[0023] Various embodiments of the present disclosure will be described more fully below with reference to the accompanying drawings, in which some but not all of the embodiments of the present disclosure are shown. In fact, the present disclosure can be embodied in many different forms and should not be construed as being limited to the embodiments described herein; on the contrary, these embodiments are provided to enable the present disclosure to meet applicable legal requirements. Unless otherwise specified, the term "or" used herein has both alternative and conjunction meanings. The terms "illustrative" and "example" are used as examples and do not indicate the quality level. Words such as "calculate", "determine", "generate" and / or similar words are used interchangeably herein to refer to the creation, modification or identification of data. In addition, "based at least in part on", "based at least on", "based on" and / or similar words are used interchangeably in an open manner herein, so unless otherwise specified, they do not necessarily mean that they are based only at least in part on or only on the referenced element. The same figure mark always refers to the same element.

[0024] I.Overview and Technical Advantages

[0025] Various embodiments of the present disclosure provide technical solutions for managing network-based exchanges. In various embodiments, an exchange platform can be configured to facilitate credential-free value exchanges between one or more member platforms. These exchanges can be conducted in real time without the need for permanent credentials that may expose members to financial, legal, reputational or other risks. Therefore, in various embodiments, client devices can buy, sell and / or perform value-based exchanges in real time over any network without exposing sensitive information that is susceptible to network-based attacks.

[0026] Embodiments of the present disclosure provide improved tool-level authentication and enablement techniques that utilize new interfaces, security code management, and policy matching techniques to increase data security and communication flexibility while reducing the expenditure requirements for computing resources to protect sensitive data over network communications.

[0027] Some technologies of the present disclosure, for example, retrieve data objects and convert them into unique data keys that can only be recognized by authorized entities. Data keys can be provided and / or established by utilizing the exchange interface between the exchange platform and other member platforms in the exchange network. Once established, the data key can be mapped to sensitive credentials stored in the source platform (e.g., the service provider platform) without the need for network transmission of sensitive credentials. In order to facilitate value-based exchanges, future communications can replace traditional permanent credentials with data keys to enable the source platform to identify the permanent credentials and / or perform one or more actions on specific tools associated with them. In this way, the exchange platform can facilitate exchanges using keys (and / or other identifiers) that cannot themselves be traced back to the underlying sensitive information. This in turn allows the exchange platform to fully track, facilitate and distribute network-based communications without exposing members to cyber attacks.

[0028] Some embodiments of the present disclosure propose network-based exchange processing techniques for facilitating credential-free exchange. To this end, some of the technologies of the present disclosure utilize a new data structure UUEK, which can replace the permanent credentials traditionally used to authorize value-based exchange. Using the technology of the present disclosure, UUEK can be securely issued across member platforms to allow users to perform value-based exchange using identifiers that can be recognized by a single party and an exchange platform. UUEK can be mapped to a unique identifier, which can refer to sensitive information without directly identifying (and thus exposing) sensitive information. For example, a unique identifier can refer to a mapping that can only be interpreted by a source platform, so that a malicious party unrelated to the exchange platform cannot use the identifier. In this way, the exchange platform can distribute, track and promote exchanges without exposing member platforms to data security risks. In addition, the exchange platform can continuously update, modify and / or redistribute UUEK to member platforms to continuously adapt UUEK in real time. In this way, the exchange platform can provide technical improvements for data and network security while reducing computing resource requirements (e.g., for securely encrypting permanent credentials) to promote value-based exchanges.

[0029] Some technologies of the present disclosure can utilize the credentialless exchange of the present disclosure to implement the use of flexible exchange interfaces between members of an exchange network. Unlike traditional exchange interfaces, credentialless exchange allows the use of interfaces with n-character security codes that facilitate complex network management, which are tailored for UUEK. In this way, the intermediate computing platform can receive the information required to establish a security code customized for UUEK. The security code can be used to verify the UUEK before the exchange is initiated. In this way, exchanges are actively filtered based at least in part on the accuracy of temporary data structures. In this way, in turn, network traffic is limited to exchanges that are most likely to be authorized, thereby improving network performance of a powerful network-based exchange ecosystem. In addition, network management of security codes may increase the achievable complexity of actual codes, for example, by enabling n-character codes of different complexities. Even a simple n-character code may have more than 14,776,336 possible combinations, which is much safer than the 1,679,616 combinations of traditional 4-character alphanumeric codes.

[0030] Embodiments of example inventive and technical advantages of the present disclosure include (i) data conversion, mapping, and processing schemes for facilitating network-based credentialless exchange, (ii) exchange interfaces and network-based communication schemes for improving network security for cross-platform communications, (iii) temporary data structures and data management techniques for distributing temporary data structures to facilitate real-time, secure, and dynamic value-based exchanges, and (iv) UUEK verification techniques for enabling and / or disabling UUEKs for exchange.

[0031] II. Example Definition

[0032] In some embodiments, the term "exchange platform" refers to a computing entity configured to facilitate voucherless value exchange among one or more members in an exchange network. The exchange platform may include one or more processing devices, storage devices, etc., which are physically and / or wirelessly coupled and configured to collectively (and / or individually) perform one or more computing tasks that facilitate value system-independent exchanges. In some examples, the exchange platform may include, define, and / or otherwise utilize one or more APIs to facilitate communications (e.g., requests and responses, etc.) between multiple members. As described herein, an API may be utilized to facilitate secure exchanges between one or more members in any value system.

[0033] In some embodiments, the term "member" refers to an entity that cooperates with an exchange platform to participate in a value exchange. For example, a member may include (i) a partner that receives value using an exchange platform, (ii) a service provider that provides value using an exchange platform, and / or (iii) both a partner and a service provider. As used herein, a member may be referred to as a partner when a member receives value through a value exchange; and / or a member may be referred to as a service provider when a member provides value through a value exchange. Therefore, depending on the member's role in the value exchange, the same member may be a partner or a service provider. For example, a member may be a partner that receives value through a value exchange. The same member may be a service provider that provides value in another value exchange. In some examples, the same member may be both a partner and a service provider in the same value exchange, so that the member may provide and subsequently receive value in a single member value exchange using an exchange platform.

[0034] In one embodiment, when a member uses a service provided by a service provider, the member is a partner. Partners can include any value-seeking entity in any value system. For example, in a financial value system, partners can include merchants (such as retailers, physical stores, etc.) that can use service providers (such as financial institutions) to access funds for financial transactions. Additionally or alternatively, in an information value system, partners can include news publishers (e.g., newspapers, media organizations, etc.) that can use service providers such as news agencies (e.g., wire services, news services, etc.) to access information for information transactions. It should be understood that the technology of the present disclosure can be applied to any value system, and partners can include any value seeker for any corresponding value system.

[0035] In some embodiments, when a member provides services to a partner, the member is a service provider. A service provider can include a value source in any value system. For example, in a financial value system, a service provider may include a financial institution (e.g., a bank, a currency exchange platform, a credit union, etc.) that can provide a location for funds for financial transactions between one or more entities. Additionally or alternatively, in an information value system, a service provider may include a news agency (e.g., a wire service, a news service, etc.) that can provide a source of information for a news publisher's release. It should be understood that the technology of the present disclosure can be applied to any value system, and a service provider may include any value source for any corresponding value system.

[0036] In some embodiments, the term "service provider tool" refers to a mechanism used by a service provider to provide value on behalf of a particular user. The service provider tool may depend on the value system and / or the service provider. In some examples, the service provider tool may include an account at the service provider. For example, in a financial value system, the service provider tool may include a bank account (e.g., checking, savings, etc.), a brokerage account, a line of credit, etc. In an information value system, the service provider tool may include a subscriber account, etc. In some examples, the service provider tool may include a virtual tool hosted by a service provider platform.

[0037] In some embodiments, the services provided by the service provider are subject to one or more policies and / or security codes. For example, the service provider and / or service provider tool may be associated with a security code for verifying the use of the service provider tool. Additionally or alternatively, the service provider may be associated with one or more member policies for authenticating the security code.

[0038] In some embodiments, the term "security code" refers to a data entity that defines a sequence of characters used to verify a user in an interaction (e.g., a physical exchange, a virtual exchange, a registration, and / or the like). The security code may include a sequence of one or more different characters (e.g., six characters, eight characters, etc.) of dynamic length, which may be set and / or provided to the user in advance by the user. The security code may be provided later by the user to verify the user's presence for the interaction (e.g., as described herein, by comparing the security code input with a security code reference). The one or more different characters may include any number of alphanumeric characters, emoticons, Chinese characters, winged fonts, and / or the like.

[0039] In some embodiments, the security code is a network-managed n-character PIN. As described herein, the security code can be managed as a service by a client device to (i) securely retrieve the UUEK, (ii) register the tool with the member platform, and / or (iii) enable or disable the use of the UUEK (and / or any other exchange credentials) prior to an exchange request. In this way, security codes can be deployed for any type of service provider tool by retrieving, registering, and / or enabling or disabling the corresponding UUEK. By managing security codes at the network level, members can benefit from faster exchanges because the possibility of invalid PINs being denied authorization is eliminated. For example, the UUEK can be disabled until a security code is received for enabling the UUEK. The exchange platform can prevent users from initiating exchanges before enabling the UUEK, thereby ensuring that all exchange authorization requests provided to the service provider have been pre-verified based on the security code. This effectively reduces network traffic between members in the exchange network, thereby reducing network congestion in traditional high-traffic communication systems.

[0040] In some embodiments, the security code corresponds to the user. For example, the security code can be pre-set and / or provided to the user by the user through interaction with the exchange platform. For example, the security code can be set by the user through interaction with the exchange network widget embedded in the member software application. This allows the security code to be set without directly interacting with the corresponding member platform or sharing the security code. In some examples, the security code can be tool-specific or member-specific. For example, the corresponding security code can be configured to retrieve and / or enable the UUEK of the service provider tool and / or the specific member platform on the specific member platform. Additionally or alternatively, the corresponding security code can be configured to register the account of the member platform with the exchange network. Exemplarily, the exchange platform can manage the use of the security code to use multiple security code tuples to implement one or more security actions, and each security code tuple associates the security code with the corresponding user, member platform and / or service provider tool.

[0041] In some embodiments, the term "security code element group" refers to a data entity that defines an association between a security code, a user, and one or more of a member platform and / or a service provider tool. A security code element group may include a data object, a record, and / or any other data structure (e.g., a link node, etc.) that is configured to represent an association between a security code and a user, and in some embodiments, represents an association with a member platform, a service provider tool, or both. For example, a security code element group may include a security code reference, a user identifier, one or more member identifiers, one or more tool identifiers, and / or context pairing data. The context pairing data may include one or more pairing attributes, such as one or more timing attributes. For example, a timing attribute may indicate a configuration time (e.g., indicating a time to set a security code element group, etc.), an expiration time (e.g., a time when a security code must be reset, etc.), and / or the like. As described herein, an exchange platform may utilize a security code element group to identify a security code reference for a user to perform a security action (e.g., allowing the use of a UUEK for exchange) on behalf of the user based at least in part on a comparison between a security code reference and a security code input provided by the user.

[0042] In some embodiments, the term "security code reference" refers to a data entity that defines a security code for a record. A security code reference may include an internal representation of a security code for a user (eg, for an exchange platform, etc.).

[0043] In some embodiments, the term "security code input" refers to a data entity that defines a sequence of characters provided for performing a security action. As described herein, the security code input may include user input provided by a user. In some examples, if the security code input matches a security code reference, the security action may be performed on the user. As an example, in the event that the security code input matches a security code reference for a user (e.g., as defined by a security code tuple), the corresponding UUEK assigned to the user may be enabled.

[0044] In some embodiments, the term "security code request" refers to a data entity defined as a request for a user to set, reset and / or remove a security code. A security code request may be provided to an exchange platform from a member of an exchange network. A security code request may indicate a member user reference of a user, and in some examples, indicate a member tool reference for a user. Exemplarily, a security code request that includes only a member user reference may default to all service provider tools associated with a user, and may, for example, initiate a setting, reset and / or removal operation of a security code applicable to all service provider tools maintained by a corresponding member platform for a user. Additionally or alternatively, a security code request that includes a member user reference and a member tool reference may initiate a setting, reset and / or removal operation of a security code applicable to a specific service provider tool maintained by a corresponding member platform for a user. In addition to the reference, a security code request may include a code action attribute (indicating a desired setting, reset and / or removal operation) and a security code input (indicating a new, modified or existing n-character PIN).

[0045] In some embodiments, the term "secure interaction request" refers to a data entity that defines a request to perform secure interaction using a security code input. A secure interaction request can be provided to an exchange platform from a member of an exchange network. A secure interaction request can indicate (i) a user, a member platform, and / or a service provider tool, and (ii) a security code input for a user. Additionally or alternatively, a secure interaction request can indicate one or more contextual security attributes. The one or more contextual security attributes can include one or more timing attributes. For example, the one or more timing attributes can indicate a provision time (e.g., indicating a time to send a secure interaction request, etc.), a request time (e.g., a request time for performing a secure interaction, etc.), and / or the like.

[0046] A secure interaction request may be received from a member platform. For example, a user may initiate a secure interaction request through a member application hosted by a member platform representing a member of an exchange network. In some examples, a secure interaction request may be generated and / or provided in response to a selection input indicating a service provider tool, a UUEK for a service provider tool, and / or the like. As an example, a user may select a tool representation, a UUEK representation, and / or the like (e.g., through a partner application associated with a partner platform, a service provider application associated with a service provider platform, etc.) to authorize a value-based exchange. In some examples, a secure interaction request may be automatically initiated when a user and / or selected tool, UUEK, and / or the like is associated with a security code. For example, in response to a selection, a member platform (e.g., through a corresponding member application) may prompt a user to enter a security code. A user may type a security code input to provide a secure interaction request.

[0047] In some embodiments, the term "verification event" refers to a data entity that defines the verification of the security code input for the user. The verification event may include a security event, which may indicate that the verification between the security code input and the security code reference has passed. Additionally or alternatively, the verification event may include an unsafe event, which may indicate a failed verification between the security code input and the security code reference. For example, a security event may indicate a determination that the security code input matches the corresponding security code reference. In some examples, an unsafe event may indicate a determination that the security code input does not match the corresponding security code reference. In some examples, in response to a determination that the security code input matches the corresponding security code reference, the exchange platform may generate a security event. Additionally or alternatively, in response to a determination that the security code input does not match the corresponding security code reference, the exchange platform may generate an unsafe event. In some examples, a security event may be associated with a security time period, and the exchange platform may generate an unsafe event in response to determining that the security time period has expired.

[0048] In some embodiments, the verification event is stored in association with a secure data entity (such as a UUEK, a service provider tool, and / or a user). For example, the verification event may be stored in an exchange data object corresponding to the UUEK, a system tool data object corresponding to the service provider tool, a system user data object corresponding to the user, and / or the like. Additionally or alternatively, the verification event may be stored in association with a secure code element group. For example, a secure event may be stored in response to a verification user passing, and an unsafe event may be stored in response to a verification user failing.

[0049] In some embodiments, the verification event includes contextual verification data. For example, the contextual verification data may indicate verification timing. The verification timing may include a timestamp corresponding to the sending, receiving, creating, and / or judging of the verification request. For example, the contextual verification data may include a verification timestamp indicating the time when the exchange platform determines that the security code input and the security code reference match or do not match. In some examples, the contextual verification data may indicate a security time period. In response to the security event, the security time period may indicate a subsequent timestamp, duration, and / or the like of the security of the UUEK, service provider tools, and / or the like.

[0050] In some embodiments, the term "secure interaction response" refers to a data entity that defines a response to a secure interaction request. In some embodiments, the secure interaction response is provided from the exchange platform to the member that provided the secure interaction request. The secure interaction response may indicate a verification event.

[0051] In some embodiments, the term "member policy" refers to a data entity that defines one or more verification requirements for a service provider tool. A member policy may correspond to a member and / or a member's service provider tool. For example, a member policy may define one or more verification requirements for using a service provider tool based at least in part on one or more member-specific criteria. Additionally or alternatively, a member policy may define one or more verification requirements for using a service provider tool based at least in part on one or more tool-specific criteria. Member-specific criteria may apply to multiple service provider tools associated with a member, and tool-specific criteria may apply to at least one of multiple service provider tools associated with a member.

[0052] The verification requirement may indicate one or more attributes of a value-based exchange that require a secure interaction. For example, a previously issued UUEK may be used without a security code to authorize a value-based exchange that does not include one or more attributes that require a secure interaction. In the event that the value-based exchange includes at least one attribute that requires a secure interaction, the UUEK may be prevented from authorizing the value-based exchange unless a verified security code is provided.

[0053] In some examples, the policy attributes may include an object identifier, one or more object attributes, and / or one or more value exchange attributes that identify an object and / or one or more authorized / unauthorized amounts of an object. For example, a member policy may include multiple object identifiers. The multiple object identifiers may indicate multiple objects that are authorized / unauthorized to obtain (e.g., purchase, etc.) without a security code.

[0054] In some examples, the object identifier may be a global object identifier. For example, the global object identifier may be a stock keeping unit (SKU) code. Additionally or alternatively, the global object identifier may be a manufacturer part number (MPN), a global trade item number (GTIN), a product or service name, an international standard book number (ISBN), a universal product code (UPC), an international article number (EIN), and / or the like. In some examples, the object identifier may include a system object identifier. For example, the system object identifier may include an identifier (e.g., a table identifier, etc.) corresponding to a record data object representing an object within a switching platform. In some embodiments, the system object identifier and the global object identifier are the same.

[0055] In some embodiments, the policy attributes include value exchange attributes corresponding to a particular value-based exchange and / or an object included in the value-based exchange. For example, the value exchange attributes may include a threshold exchange value without a security code. For example, one or more exchange attributes may indicate an exchange value, and one or more verification requirements may define an exchange value threshold where a corresponding security event is required for the service provider tool.

[0056] In some embodiments, the term "record data object" refers to a data object that represents an object that can participate in a value-based exchange. In some examples, a record data object can be an internal representation of an object for an exchange platform. For example, an object can include different units of a value-based exchange for which value is being transferred. A record data object for an object can include a data object that records one or more aspects of the object (e.g., an object identifier, object attributes, etc.).

[0057] For example, a record data object may include an object identifier and / or one or more object attributes for a particular object associated with a value system. The object may be based at least in part on a value system. For example, in a financial value system, an object may be a tangible or intangible item, product, and / or the like that can be purchased in exchange for a unit of currency. In a healthcare value system, an object may be a healthcare procedure covered by a healthcare policy, and / or the like.

[0058] In some examples, the exchange platform can maintain and / or access an object data store including a plurality of record data objects. As described herein, the object data store can include a plurality of record data objects from at least in part one or more members of the exchange network.

[0059] In some embodiments, the term "object attribute" refers to a data entity that describes a characteristic of an object. Object attributes may include object-based attributes and / or exchange-based attributes.

[0060] For example, object-based attributes may include spatial attributes, count attributes, value attributes, source attributes, composite attributes, classification attributes, and / or any other attributes that describe object characteristics. For example, spatial attributes may indicate one or more dimensions of an object (e.g., height, width, weight, etc.), value attributes may indicate the value of the object (e.g., price, etc.), ingredient attributes may indicate one or more ingredients, components, etc. of an object, classification attributes may indicate one or more categories (e.g., restricted substances, etc.), and / or the like. Exemplarily, one or more classification attributes may indicate whether an object is associated with (i) one or more general store categories, such as vegetables, fruits, dairy products, meats, grains, seeds, alcohol, tobacco, in-store consumables, hot foods, pharmacies, pet food, and non-food products, (ii) one or more medical categories, such as dental, ophthalmology, general health, etc., (iii) one or more information categories, such as international sources, domestic sources, etc., and / or the like. In one example, the ingredient attribute may indicate one or more ingredients of the object, such as the volume percentage of alcohol within the object, one or more ingredients such as meat, dairy derivatives, peanut derivatives, tree nut derivatives, soy derivatives, and / or the like.

[0061] In some examples, object-based attributes may be based at least in part on a value system. For example, in at least one financial-based value system, object-based attributes may include one or more line item attributes, one or more line item adjustments, and / or the like. Line item attributes may include a sequence, a line item group, a product code, an item name, an item source (e.g., a supplier, a manufacturer, etc.), a description, a quantity, a mass (e.g., grams, kilograms, etc.), one or more spatial dimensions (e.g., length, width, height, volume, etc.), a unit amount, a unit tax amount, a line amount (e.g., an amount of a line item), a line tax amount, and / or the like. Line item adjustments may include an adjustment type (e.g., a manufacturer discount, a store discount, a return, a cash payment, a gift card payment, a payment other, and / or the like), an item, a product or service code, an item description, an item quantity, a unit item, an item mass (e.g., grams, kilograms, etc.), a unit amount, a unit tax amount, a line amount (e.g., an amount of a line item), a line tax amount, and / or the like.

[0062] In some embodiments, the term "exchange request" refers to a data entity that defines a request to perform a value exchange. The exchange request may be provided to the exchange platform from a member of the exchange network. The exchange request may include one or more request attributes. The one or more request attributes may include one or more object identifiers, object attributes, and / or the like.

[0063] For example, the one or more request attributes may include a plurality of object identifiers corresponding to a plurality of objects associated with the value-based exchange. Additionally or alternatively, the one or more request attributes may include one or more object attributes for a plurality of objects. For example, the one or more object attributes may include one or more object-based attributes (e.g., one or more line item attributes), one or more exchange-based attributes (e.g., number of objects, location of objects), and / or the like. For example, an exchange request may indicate an exchange location from which to obtain an object.

[0064] In some embodiments, the term "exchange authorization request" refers to a data entity that defines a request to perform a value-based exchange on a member. In some embodiments, the exchange authorization request is provided from an exchange platform to a member of an exchange network. For example, in response to an exchange request from a partner of the exchange network, the exchange authorization request may be provided to a service provider of the exchange network. In some examples, the exchange authorization request may indicate a verification event associated with a UUEK. For example, the exchange authorization request may indicate a disabled and / or enabled state of a UUEK for initiating a value exchange.

[0065] In some embodiments, the term "exchange authorization response" refers to a data entity that defines a response to an exchange authorization request. In some embodiments, the exchange authorization response is provided to the exchange platform from a member of the exchange network. For example, in response to the exchange authorization request, the exchange authorization response may be provided by a service provider of the exchange network.

[0066] In some embodiments, the exchange authorization response indicates at least one of an exchange approval or an exchange rejection. The exchange authorization response may be based at least in part on a comparison between an exchange value, asset availability of a service provider tool, and / or a verification event. For example, in response to receiving an exchange authorization request, a member may be configured to compare the exchange value with the asset availability of the identified service provider tool. If the asset availability exceeds the exchange value, a value-based exchange may be authorized (e.g., resulting in an exchange approval, etc.), otherwise a value-based exchange may be rejected (e.g., causing an exchange rejection). In some examples, if the exchange value is within an exchange value threshold, a value-based exchange may be authorized (e.g., resulting in an exchange approval, etc.), otherwise a value-based exchange may be rejected unless the exchange authorization response indicates that an enabled UUEK is used to initiate a value exchange.

[0067] In some embodiments, the exchange authorization response indicates one or more contextual response attributes. For example, one or more contextual response attributes may indicate one or more influencing factors for the exchange authorization response. For example, influencing factors may include bad actor risk and / or fraud check, error, full approval, tool closed, tool-based risk and / or fraud check, insufficient value, invalid UUEK, limit exceeded (e.g., exceeded UUEK or tool usage limit), missing line items (e.g., does not include a value exchange for a verified object), tool not found, account not found, password required, partial approval, member unavailable, transaction risk and / or fraud check, unsupported operation, user contact member (e.g., the user may need to contact a member (such as a service provider) to resolve the issue), user risk and / or fraud check, and combinations thereof.

[0068] In some embodiments, the term "exchange response" refers to a data entity that defines a response to an exchange request. In some embodiments, the exchange response is provided from the exchange platform to the member that provided the exchange request. The exchange response may indicate an exchange grant and / or an exchange rejection. Additionally or alternatively, the exchange response may indicate a verified data object, an invalid data object, and / or a context response attribute. Exemplarily, the exchange response may indicate one or more verified objects and / or one or more invalid objects of the exchange request.

[0069] In some embodiments, the term "exchange record" refers to a data entity that provides context information for an exchange request. The context information may indicate one or more aspects of an exchange request, an exchange response, an exchange authorization request, and / or an exchange authorization request. For example, an exchange record may indicate one or more verified objects, invalid objects, the object status of each verified and / or invalid object, and / or any other information associated with a value-based exchange.

[0070] In some embodiments, the term "member platform" refers to a computing entity corresponding to a member. A member platform may include a partner computing platform representing a partner, a service provider computing platform representing a service provider, and / or both. In some examples, a member platform may be both a partner platform and a service provider platform. For example, the same member platform may be configured to operate on behalf of a partner of one value exchange and a service provider of another value exchange. In some examples, the same member platform may be configured to operate on behalf of both a partner and a service provider in a single value exchange. It should be noted that the term member platform may refer to a partner platform, a service provider platform, or both, and in some examples, may depend on the role of the member platform in the value exchange (e.g., and / or one or more APIs used by the member platform in the value exchange).

[0071] In some embodiments, the partner platform is a computing entity configured to perform one or more operations on behalf of the partner. For example, the partner platform may include one or more processing devices, storage devices, etc., which are physically and / or wirelessly coupled and configured to jointly (and / or individually) perform one or more computing tasks for requesting value in a value system-independent exchange. In some examples, the partner platform may include, define and / or otherwise utilize one or more APIs to facilitate communication with the exchange platform (e.g., requests and responses, etc.). In some examples, the partner platform may be configured to host one or more user-oriented applications (e.g., partner applications, etc.) for interacting with one or more users.

[0072] In some embodiments, a service provider platform is a computing entity configured to perform one or more operations on behalf of a service provider. For example, a service provider platform may include one or more processing devices, storage devices, etc., which are physically and / or wirelessly coupled and configured to jointly (and / or individually) perform one or more computing tasks for providing value in an exchange that is independent of the value system. In some examples, a service provider platform may include, define and / or otherwise utilize one or more APIs to facilitate communication (e.g., requests and responses, etc.) with an exchange platform. In some examples, a service provider platform may be configured to facilitate one or more service provider tools. In some examples, a service provider platform may be configured to host one or more user-oriented applications (e.g., service provider applications, etc.) for managing one or more service provider tools.

[0073] In some embodiments, the term "exchange interface" refers to a set of instructions for facilitating communication between an exchange platform and one or more member platforms and / or internal services. The exchange interface may include an API, a file-based interface, a message queue-based interface, and the like. For example, the exchange interface may include an API, for example, the API includes one or more Simple Object Access Protocol (SOAP) APIs, one or more Remote Procedure Call (RPC) APIs, one or more websocket APIs, one or more Representational State Transfer (REST) ​​APIs, and the like. In some embodiments, the exchange interface may include one or more RPC APIs, such as one or more gRPC APIs.

[0074] The exchange platform may include, define and / or otherwise utilize one or more different exchange interfaces to facilitate communication with one or more external platforms, such as one or more member platforms (e.g., partner platforms, service provider platforms, etc.). Each API may include a plurality of communication instructions, message definitions, etc., for exchanging requests and / or responses between the exchange platform and entities participating in the value exchange. Exemplarily, the exchange interface may include a partner API for facilitating communication with a partner platform and / or a service provider API for facilitating communication with a service provider platform.

[0075] In some embodiments, the term "partner interface" refers to an exchange interface for facilitating one or more communications between a partner platform and an exchange platform. The partner interface may define one or more communication instructions, message definitions, etc., for facilitating one or more request messages and / or response messages between the partner platform and the exchange platform. For example, the partner interface may include an API that defines (i) requests from a computing entity acting as a partner platform to an exchange platform, and / or (ii) requests from an exchange platform to a partner platform. For example, the partner interface may define one or more registration messages, session messages, transaction messages, etc. that facilitate value exchange for partners. In some embodiments, the partner interface defines one or more identifiers for securely identifying one or more parts of a value exchange.

[0076] In some embodiments, the term "service provider interface" refers to an exchange interface for facilitating one or more communications between a service provider platform and an exchange platform. The service provider interface may define one or more communication instructions, message definitions, etc., for facilitating one or more request messages and / or response messages between the service provider platform and the exchange platform. For example, the service provider interface may include an API that defines (i) requests from a computing entity acting as a service provider platform to an exchange platform, and / or (ii) requests from an exchange platform to a service provider platform. For example, the service provider interface may define one or more registration messages, session messages, transaction messages, etc. that facilitate the use of a service provider tool to facilitate a value exchange. In some embodiments, the service provider interface defines one or more identifiers for securely identifying one or more parts of a value exchange.

[0077] In some embodiments, the term "entity partition" refers to a unique identifier for a computing entity. An entity partition may include a unique number, alphanumeric number, etc. representing a specific computing entity. For example, an entity partition may include a member partition representing a member platform, a service provider partition representing a service provider platform, a partner partition representing a partner platform, etc.

[0078] In some embodiments, the term "service provider partition" refers to a unique identifier for a service provider and / or a service provider platform of a service provider. A service provider partition may include a number, an alphanumeric number, any character or symbol, and / or a sequence of any other characters or symbols representing a service provider associated with (e.g., joined, registered, etc.) an exchange platform. For example, an exchange platform may include multiple service provider partitions that respectively identify service provider platforms associated with (e.g., joined, registered, etc.) an exchange platform. Each service provider partition may represent a service provider platform that has been configured with one or more exchange platform software development kits (SDKs), etc., to implement a service provider interface for the exchange platform.

[0079] In some embodiments, the term "partner partition" refers to a unique identifier of a partner and / or a partner platform of a partner. A partner partition may include a number, an alphanumeric number, any character or symbol, and / or a sequence of any other characters or symbols representing a partner associated with an exchange platform. For example, an exchange platform may include multiple partner partitions that respectively identify partner platforms associated with (e.g., joined, registered, etc.) the exchange platform. Each partner partition may represent a partner platform that has been configured with one or more exchange SDKs, etc., for implementing a partner interface of the exchange platform.

[0080] In some embodiments, the term "user-oriented application" refers to a computer program hosted by a computing entity for facilitating one or more user interactions. A user-oriented application may include software (e.g., computer-readable instructions, etc.) that is designed to perform one or more computing tasks for a computing entity (e.g., a member platform). For example, a user-oriented application may facilitate communication between members and users. Exemplarily, a user-oriented application may be configured to present one or more user interfaces to interact with users on behalf of members. In some examples, a user-oriented application may be configured to receive user input (e.g., through one or more user interfaces) to receive information from a user.

[0081] In some embodiments, the user-facing application is a partner application hosted by a partner platform (e.g., a member platform that acts as a partner for a particular exchange, etc.) to facilitate the functionality of the partner. The partner application may include software (e.g., computer-readable instructions, etc.) that is designed to: perform one or more computing tasks for the partner. For example, the partner application may be configured to present one or more user interfaces for interacting (e.g., browsing, purchasing, viewing, etc.) with one or more products provided by a retail-based partner, one or more information units provided by an information-based partner, etc. In some examples, the partner application may be configured to receive user input (e.g., through one or more user interfaces) to receive information from a user.

[0082] In some embodiments, the user-facing application is a service provider application hosted by a service provider platform (e.g., a member platform of a service provider acting as a particular exchange, etc.) to facilitate the functionality of the service provider. The service provider application may include software (e.g., computer-readable instructions, etc.) designed to perform one or more computing tasks for the service provider. For example, the service provider application may be configured to present one or more user interfaces for interacting with one or more service provider tools provided by the service provider (e.g., viewing, managing, auditing, registering, etc.). Exemplarily, in a financial value system, the service provider application may enable access to bank accounts, brokerage accounts, credit lines, etc. to manage funds, property, etc. handled by the corresponding accounts. In some examples, the service provider application may be configured to receive user input (e.g., through one or more user interfaces) to receive information, authorization, etc. from the user.

[0083] In some embodiments, the term "tool data object" refers to a data entity representing a service provider tool. A tool data object may include one or more tool identifiers and / or one or more tool attributes. In some examples, the one or more tool identifiers and / or one or more tool attributes may be based at least in part on the type of the tool data object. Exemplarily, a service provider tool may be represented in a member platform as a member tool data object. Additionally or alternatively, a service provider tool may be independently represented by a system tool data object in an exchange platform. In some examples, a member tool data object and a system tool data object may include one or more of the same one or more tool identifiers and / or one or more tool attributes. For example, a member platform may register multiple service provider tools with an exchange platform. During registration, the member platform may provide one or more tool identifiers and / or tool attributes, and in some examples, the exchange platform may return another identifier.

[0084] In some embodiments, a member instrument data object is an internal representation of a service provider instrument within a member platform. A member instrument data object may include one or more instrument identifiers, such as a member instrument identifier, an instrument key from an exchange platform, and / or a user identifier. For example, a user identifier may include a member user identifier. Additionally or alternatively, a member instrument data object may include one or more instrument attributes, such as an instrument type (e.g., a credit-based instrument, a debit-based instrument, an information-based instrument, etc.), an instrument representation, and / or one or more context attributes. In some examples, the context attributes may depend on a value system. For example, in a financial value system, one or more context attributes may indicate (i) a currency associated with a service provider instrument, (ii) asset availability of a service provider instrument (e.g., balance, coverage, etc.), (iii) one or more previous transactions with a service provider instrument, etc.

[0085] In some embodiments, the system instrument data object is an external representation of a service provider instrument within the exchange platform. The system instrument data object may include one or more instrument identifiers, such as an instrument reference of a member platform, a system instrument identifier, and / or a user identifier. For example, a user identifier may include a system user identifier. Additionally or alternatively, the system instrument data object may include one or more instrument attributes, such as an instrument type (e.g., a credit-based instrument, a debit-based instrument, an information-based instrument, etc.), an instrument representation, and / or one or more context attributes. In some examples, the context attributes may depend on the value system. For example, in a financial value system, one or more context attributes may indicate a currency associated with a service provider instrument.

[0086] In some embodiments, the term "tool identifier" refers to any representation of a service provider tool. As described herein, a tool identifier may include a tool identifier, a tool reference, a tool key, and the like.

[0087] In some embodiments, the term "member tool identifier" refers to a unique identifier used to represent a service provider tool within a member platform. For example, a member tool identifier may include a number, an alphanumeric number, any character or symbol, or a sequence of any other characters or symbols that represents a service provider tool of a service provider platform.

[0088] In some embodiments, the term "tool reference" refers to a unique identifier used to reference a member tool identifier. For example, a tool reference may be generated by a member platform and / or provided to an exchange platform to allow the exchange platform to reference tools maintained on the member platform. In some examples, the tool reference is the same value as the member tool identifier. In some examples, the tool reference is a different value that maps to a member tool identifier.

[0089] In some embodiments, the term "system tool identifier" refers to a unique identifier used to represent a service provider tool within an exchange platform. For example, the system tool identifier may include a number, an alphanumeric number, any character or symbol, or any other sequence of characters or symbols that represents the service provider tool to the exchange platform. In some examples, the system tool identifier may include a UUID.

[0090] In some embodiments, the term "tool key" refers to a unique identifier used to reference a system tool identifier. For example, in the process of registering a tool with an exchange platform, the exchange platform may generate and / or provide a tool key. In some examples, the tool key may include an encapsulated system tool identifier. For example, the tool key may include an alphanumeric string formatted according to a key format established by the exchange platform (and / or one or more of its APIs). The key format may include any number of characters, such as fifty characters or more. In some examples, the characters may be case sensitive. The first portion of the characters (e.g., the first six characters) may be reserved for identifying a partition of an entity associated with the key. For a tool key, a partition may include a service provider partition. The second portion of the characters may identify a system tool identifier. The key format described herein may include one or more different parts, each of which may be arranged in any order.

[0091] In some embodiments, the term "tool representation" refers to a unique identifier used to represent a service provider tool to a user. For example, a tool representation may include a number, an alphanumeric number, any character or symbol / or a sequence of any other characters or symbols that visually represents a service provider tool. The format and / or value of the tool representation may be based at least in part on the type of service provider and / or service provider tool. For example, in a financial value system, a tool reference may include a portion of a permanent credential (e.g., the last four digits, etc.), such as an account number (e.g., a debit account, a credit account, etc.), a financial account name, etc. As another example, in an information value system, a tool reference may include a portion of a permanent credential such as a subscription account (e.g., one or more numbers, alphanumeric characters, etc.). For example, a tool representation may include a derivative of a permanent credential that may only allow entities with prior knowledge of the permanent credential to use the tool representation to identify the permanent credential. As another example, a tool representation may include a tool nickname assigned by a user and subsequently recognized by the user.

[0092] In some embodiments, the term "user data object" refers to a data entity representing a user interacting with a member platform and / or an exchange platform. For example, a user may include an entity (e.g., an individual, an organization, a group, etc.) that participates in the exchange of value managed by the exchange platform. In some examples, a user may cooperate with the exchange platform indirectly by creating a user account with a registered service provider, registering (and / or allowing registration) a service provider tool, etc. In some examples, the exchange platform may act on behalf of the user without the user having to interact directly with the exchange platform. For example, the exchange platform may act as a hidden intermediary between a user-oriented application and a user's service provider tool.

[0093] In some embodiments, the user data object includes one or more user identifiers and / or one or more user attributes. In some examples, the one or more user identifiers and / or one or more user attributes may be based at least in part on the type of the user data object. Exemplarily, a user may be represented as a member user data object in a member platform. Additionally or alternatively, a user may be independently represented by a system user data object in an exchange platform. In some examples, a member user data object and a system user data object may include one or more of the same one or more user identifiers and / or user attributes. Exemplarily, a member platform may register multiple users with an exchange platform. During registration, the member platform may provide one or more of a user identifier and / or user attributes, and in some examples, the exchange platform may return another identifier.

[0094] In some embodiments, the member user data object is an internal representation of a user within the member platform. The member user data object may include one or more user identifiers, such as a member user identifier, a user key from an exchange platform, etc. Additionally or alternatively, the member user data object may include one or more user attributes. One or more user attributes may indicate one or more contextual features for a user. In some examples, a user attribute may indicate one or more identifiable features for a user. Exemplarily, a user attribute may indicate a user's first name, last name, email, physical address (e.g., one or more of a street, region, zip code, country, etc.), birthday (e.g., date of birth, age group, etc.), phone number, etc. In some examples, a user attribute may include encryption, hashing, and / or other secure representations of identifiable features for a user. For example, a user attribute may include one or more hash identifiers for a user, etc.

[0095] In some embodiments, the system user data object is an external representation of a user of a member within the exchange platform. The system user data object may include one or more user identifiers, such as a user reference for the member platform, a system user identifier, etc. Additionally or alternatively, the system user data object may include one or more user attributes (such as those described herein). Exemplarily, the member platform may register a user with the exchange platform. During registration, the member platform may provide a user reference and / or one or more user attributes of the user. In some examples, the user attributes may include a hashed and / or encrypted identifier for the user.

[0096] In some embodiments, the term "user identifier" refers to a unique identifier for a user involved in a value-based exchange. A user identifier may include a number, an alphanumeric number, any character or symbol, and / or a sequence of any other characters or symbols that represents a user of an exchange platform and / or a member platform. In some examples, a user identifier may include a user reference, a user key, a system user identifier, a member user identification, and / or the like.

[0097] In some embodiments, the term "system user identifier" refers to a unique identifier used to represent a user within an exchange platform. For example, a system user identifier may include a number, an alphanumeric number, any character or symbol, and / or a sequence of any other characters or symbols that represents a user to the exchange platform. In some examples, a system user identifier may include a UUID that is specific to a particular user.

[0098] In some embodiments, the term "member user identifier" refers to a unique identifier used to represent a user within a member platform. For example, a member user identifier may include a number, an alphanumeric number, any character or symbol, or a sequence of any other characters or symbols that represents the user to the service provider platform.

[0099] In some embodiments, the term "user reference" refers to a unique identifier used to reference a member user identifier. For example, a user reference may be generated by a member platform and / or provided to an exchange platform to allow the exchange platform to reference a user associated with the member platform. In some examples, the user reference is the same value as the member user identifier. In some examples, the user reference is a different value that is mapped to the member user identifier.

[0100] In some embodiments, the term "user key" refers to a unique identifier used to reference a system user identifier. The user key can be generated and / or provided by the exchange platform, for example, during the process of a user registering with the exchange platform. In some examples, the user key can include an encapsulated system user identifier. For example, the user key can include an alphanumeric string formatted according to a key format established by the exchange platform (and / or one or more of its APIs). For example, the key format can include a first portion of characters (e.g., the first six characters), which can be reserved for a partition used to identify an entity associated with the key (e.g., a member, etc.). For example, for a user key, the partition can include a service provider partition and / or a partner partition. The second portion of the characters can identify the system user identifier.

[0101] In some embodiments, the term "exchange data object" refers to a data entity representing an authorized value exchange between one or more members associated with an exchange platform. In some examples, an exchange data object may include one or more identifiers and / or one or more exchange attributes. For example, one or more identifiers and / or one or more exchange attributes may be based at least in part on the type of the exchange data object. Exemplarily, an exchange may be represented in a member platform as a member exchange data object. Additionally or alternatively, an exchange may be independently represented by a system exchange data object in an exchange platform. In some examples, a member exchange data object and a system exchange data object may include one or more of the same one or more identifiers and / or one or more exchange attributes. Exemplarily, using some techniques of the present disclosure, an exchange platform may issue one or more unique identifiers to a member platform, which may be used to authorize a value exchange.

[0102] In some embodiments, the system exchange data object is an internal representation of a value exchange intermediated using an exchange platform. In some examples, the system exchange data object may include one or more different identifiers and / or exchange attributes, depending on the role of the system exchange data object in the value-based exchange.

[0103] For example, the system exchange data object may include a service provider specific exchange data object corresponding to a service provider platform. The service provider specific exchange data object may include one or more identifiers, such as an exchange identifier, a system user identifier, a system tool identifier, a UUEK, etc. Additionally or alternatively, the service provider specific exchange data object may include one or more exchange attributes, such as an expiration date, a currency (e.g., for a financial value system, etc.), and / or the like.

[0104] Additionally or alternatively, the system exchange data object may include a partner-specific exchange data object corresponding to the partner platform. The partner-specific exchange data object may include one or more identifiers, such as an exchange identifier, an instrument key, a UUEK, a member instrument reference (e.g., a partner-specific instrument reference, etc.), and / or the like. Additionally or alternatively, the partner-specific exchange data object may include one or more exchange attributes, such as an expiration date, a currency (e.g., for a financial value system, etc.), an instrument type, a previous UUEK identifier, etc. In some embodiments, a member exchange data object is an external representation of a value exchange using an exchange platform as an intermediary. The member exchange data object may include one or more identifiers, such as a member exchange identifier, a member instrument identifier, a UUEK from an exchange platform, etc.

[0105] In some embodiments, the term "exchange identifier" refers to a unique identifier for value exchange using an exchange platform. The exchange identifier may include a sequence of numbers, alphanumerics, and / or any other characters or symbols representing at least a user and / or service provider tool. In some examples, the unique exchange identifier may include a universal unique identifier (UUID), which may be mapped (e.g., through a series of identifiers, etc.) to a user, a service provider tool, and / or a member registered at the exchange platform. In some examples, the exchange identifier may be randomly generated using one or more UUID generators. For example, the exchange identifier may include random sixteen bytes of information generated according to one or more UUID formatting standards (e.g., UUID v4 and / or the like). Therefore, although the exchange identifier may be used by the exchange platform and / or member platform for one or more functions, if there is no prior association between the exchange identifier and one or more other identifiers, the same exchange identifier will be useless for external parties. In some examples, the exchange identifier may be represented externally by the UUEK.

[0106] In some embodiments, a "universally unique temporary key" or "UUEK" refers to an external representation of an exchange identifier that can be issued to an external entity (e.g., a user, partner, and / or service provider) (e.g., in place of a service provider exchange identifier and / or a partner exchange identifier) ​​to initiate a transaction using an exchange platform. To this end, a UUEK can be generated by the exchange platform and issued to an external entity. Each UUEK can include multiple values ​​(e.g., up to fifty characters and / or more, which can be case sensitive) representing one or more aspects of a transaction. For example, multiple values ​​can indicate an exchange identifier, a partition (e.g., identifying a recipient of the UUEK, etc.), an identifier type, and / or one or more flags. Exemplarily, a UUEK can include a partner-specific UUEK and / or a service provider-specific UUEK. As described herein, a partner-specific UUEK can be associated with a partner-specific exchange data object, and a service provider-specific UUEK can be associated with a service provider-specific exchange data object.

[0107] Exemplarily, the UUEK may be generated according to a key format. The key format may include a plurality of characters, including, for example, fifty or more characters (which may be case sensitive). The first portion of the characters (e.g., the first six characters) may be reserved for identifying a partition of the recipient of the UUEK. For example, the partition may include a partner partition, a service provider partition, and / or any other member partition. For example, the UUEK may be issued in response to a request from an authorized member (e.g., associated with a partner and / or a service provider).

[0108] Additionally or alternatively, at least one character of the key format (e.g., the seventh character) may identify the format of the UUEK. At least another character (e.g., the eighth character) may identify the type of the UUEK. In some examples, a second portion of characters may identify an exchange identifier (e.g., a group of twenty-two characters following the eighth character). A third portion of characters may be reserved (e.g., a group of twenty characters following the first portion of characters). An example representation is provided below:

[0109] ppppppFiGGGGGGGGGGGGGGGGGGGGGGGrrrrrrrrrrrrrrrrrrrrwhere p represents the partition character, F represents the format character, i represents the identifier type character, G represents the exchange identifier, and r represents a reserved character. The key format allows 9.8x1084 unique permutations, which is more than the number of atoms in the known observable universe. This enables new UUEKs to be generated and distributed on demand without compromising the security of the underlying data to which the UUEKs may be mapped, such as identifiers of users, tools, and / or any other potentially sensitive information. The key format described herein may include one or more distinct parts, each of which may be arranged in any order.

[0110] In some embodiments, a "UUEK representation" refers to a visual representation of a UUEK. The UUEK representation may include a digital representation of the UUEK that is visible to a user. For example, the UUEK representation may be represented in one or more different forms, such as a machine-readable optical image (e.g., a barcode, a quick response code, etc.), a keyword, a virtual widget, and / or the like. In some examples, the UUEK representation may include a scannable representation of the UUEK (e.g., a barcode, a QR code, a non-fungible token, a near field communication sequence, etc.). The scannable representation may be saved to a member account of a member platform to enable a user to physically perform a value-based exchange using a service provider tool without having to reference a permanent credential of the service provider tool. For example, the UUEK representation may be scanned by a barcode scanner and / or the like to read the UUEK and initiate a value-based exchange with the UUEK.

[0111] In some embodiments, an "enabled UUEK representation" refers to a UUEK representation for a UUEK that was enabled by a previous security event. The enabled UUEK representation may include a status indicator indicating the enabled state of the UUEK and / or one or more other indicators. In some examples, the enabled UUEK representation may include a readable UUEK representation.

[0112] In some embodiments, a "disabled UUEK representation" refers to a UUEK representation for a UUEK that is not enabled by a previous security event. The disabled UUEK representation may include a status indicator indicating the disabled state of the UUEK and / or one or more other indicators. In some examples, the disabled UUEK representation may include an unreadable UUEK representation. For example, the unreadable UUEK representation may include a gray, obscured, partially covered, and / or similar, scannable representation that prevents the scannable representation from being read. III. Computer Program Products, Methods, and Computing Entities

[0113] Embodiments of the present disclosure may be implemented in various ways, including as a computer program product including a manufactured article. Such a computer program product may include one or more software components, including, for example, software objects, methods, data structures and / or the like. The software components may be encoded in any of a variety of programming languages. The illustrative programming language may be a low-level programming language, such as an assembly language associated with a specific hardware architecture and / or operating system platform. Software components containing assembly language instructions may need to be converted by an assembler into executable machine code before the hardware architecture and / or platform is executed. Another example programming language may be a high-level programming language that can be ported across multiple architectures. Software components containing high-level programming language instructions may need to be converted by an interpreter or compiler into an intermediate representation before execution.

[0114] Other examples of programming languages ​​include, but are not limited to, macro languages, shell or command languages, job control languages, scripting languages, database query or search languages, and / or report writing languages. In one or more example embodiments, a software component comprising instructions in one of the above programming language examples can be directly executed by an operating system or other software component without first being converted to another form. Software components can be stored as files or other data storage structures. Software components of similar type or functionally related can be stored together, such as in a particular directory, folder, or library. Software components can be static (e.g., pre-established or fixed) or dynamic (e.g., created or modified at execution time).

[0115] A computer program product may include a non-transitory computer-readable storage medium (also referred to herein as executable instructions, execution instructions, computer program products, program codes, and / or similar terms used interchangeably herein) storing applications, programs, program modules, scripts, source code, program code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, etc. Such non-transitory computer-readable storage media include all computer-readable media (including volatile and non-volatile media).

[0116] In one embodiment, the non-volatile computer-readable storage medium may include a floppy disk, a floppy disk, a hard disk, a solid-state storage (SSS) (e.g., a solid-state drive (SSD), a solid-state card (SSC), a solid-state module (SSM), an enterprise-class flash drive, a magnetic tape, or any other non-transitory magnetic medium, etc. The non-volatile computer-readable storage medium may also include a punched card, a paper tape, an optical marker sheet (or any other physical medium with a hole pattern or other optically identifiable markings), a compact disk read-only memory (CD-ROM), a rewritable compact disk (CD-RW), a digital versatile disk (DVD), a Blu-ray disc (BD), any other non-transitory optical medium, etc. Such non-volatile computer-readable storage media may also include a read-only memory (ROM), a programmable read-only memory (PROM), Erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory (e.g., serial, NAND, NOR, etc.), multimedia memory card (MMC), secure digital (SD) memory card, smart media card, compact flash (CF) card, memory stick, etc. In addition, the non-volatile computer-readable storage medium may also include conductive bridging random access memory (CBRAM), phase change random access memory (PRAM), ferroelectric random access memory (FeRAM), non-volatile random access memory (NVRAM), magnetoresistive random access memory (MRAM), resistive random access memory (RRAM), silicon-oxide-nitride-oxide-silicon memory (SONOS), floating junction gate random access memory (FJG RAM), millipede memory, racetrack memory, etc.

[0117] In one embodiment, the volatile computer-readable storage medium may include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), fast page mode dynamic random access memory (FPM DRAM), extended data output dynamic random access memory (EDO DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), double data rate type two synchronous dynamic random access memory (DDR2 SDRAM), double data rate type three synchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), two-transistor RAM (TTRAM), thyristor RAM (T-RAM), zero capacitor (Z-RAM), Rambus in-line memory module (RIMM), dual in-line memory module (DIMM), single in-line memory module (SIMM), video random access memory (VRAM), cache memory (including various levels), flash memory, register memory, etc. It should be understood that in the case of describing embodiments using computer-readable storage media, other types of computer-readable storage media in addition to the above-mentioned computer-readable storage media may be used instead of or in use.

[0118] It should be understood that various embodiments of the present disclosure may also be implemented as methods, apparatuses, systems, computing devices, computing entities, etc. Therefore, embodiments of the present disclosure may take the form of data structures, apparatuses, systems, computing devices, computing entities, etc., executing instructions stored on a computer-readable storage medium to perform certain steps or operations. Therefore, embodiments of the present disclosure may also take the form of a complete hardware embodiment, a complete computer program product embodiment, and / or an embodiment including a combination of a computer program product and hardware that performs certain steps or operations.

[0119] Embodiments of the present disclosure are described below with reference to block diagrams, flow charts, message passing flows, and other representations of data, operations, and message passing schemes. It should be understood that each box, arrow, etc. in the diagram, flow chart, etc. can be embodied in the form of a computer program product, a complete hardware embodiment, a combination of hardware and computer program products, and / or a device, system, computing device, computing entity, etc. that executes instructions, operations, steps, and similar words (e.g., executable instructions, instructions for execution, program codes, etc.) on a computer-readable storage medium. For example, the retrieval, loading, and execution of the code can be performed sequentially so that an instruction is retrieved once, loaded, and executed. In some embodiments, retrieval, loading, and / or execution can be run in parallel so that multiple instructions can be retrieved, loaded, or run together. Therefore, such an embodiment can produce a machine that performs a specific configuration of the steps or operations specified in the representation of the present disclosure. Therefore, the representation of the present disclosure supports various combinations of embodiments for executing specified instructions, operations, or steps.

[0120] IV. Example System Architecture

[0121] Figure 1 An illustration of a computing ecosystem 100 that can be used in conjunction with various embodiments of the present disclosure is provided. Figure 1 As shown, the architecture may include an exchange platform 102, one or more client devices 104, a member platform network 110, one or more networks 120, etc. The member platform network 110 may include a first member platform 112a, a second member platform 112b, a third member platform 112c, etc. that are related to the exchange platform 102 (e.g., registered, etc.). For example, as described herein, the member platform network 110 may include a partner platform and / or a service provider platform. In some examples, the partner platform may include a first member platform 112a, and the service provider platform may include a second member platform 112b that is different from the first member platform 112. In some examples, the partner platform and / or the service provider platform may include a single member platform (e.g., a third member platform 112c). In some examples, the member platform network 110 may be configured for one or more different services.

[0122] For example, each component of computing ecosystem 100 may be in electronic communication with each other via the same or different wireless or wired networks 120, including, for example, wired or wireless personal area networks (PANs), local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), and / or the like. For example, network 120 may include any network connection, including any type of network and / or across any geographic boundaries (e.g., inter-country connections involving one or more sovereign entities, etc.). In addition, although Figure 1Certain systems are illustrated as separate stand-alone entities, but the various embodiments are not limited to this particular architecture.

[0123] Although not explicitly illustrated, exchange platform 102 may be client device 104 and / or may be part of member platform network 110. Additionally or alternatively, member platforms 112a-c may be part of client device 104 and / or exchange platform 102. In some embodiments, exchange platform 102 and / or each of member platforms 112a-c may include the same computing platform.

[0124] a. Example computing platform

[0125] Figure 2 is an example schematic diagram of a computing platform 200 according to one or more embodiments of the present disclosure. The computing platform 200, for example Figure 1 The exchange platform 102, member platforms 112a-c, and / or the like may include or communicate with one or more processing elements 202 (also referred to as processors, processing circuits, and / or similar terms used interchangeably herein), for example, the one or more processing elements 202 communicate with other elements within the computing platform 200 via a bus. It will be appreciated that the processing element 202 may be implemented in many different ways.

[0126] For example, processing element 202 may be implemented as one or more complex programmable logic devices (CPLDs), microprocessors, multi-core processors, co-processing entities, application specific instruction set processors (ASIPs), microcontrollers, and / or controllers. In addition, processing element 202 may be implemented as one or more other processing devices or circuits. The term circuit may refer to a complete hardware embodiment or a combination of hardware and a computer program product. Therefore, processing element 202 may be implemented as an integrated circuit, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic array (PLA), a hardware accelerator, other circuits, and / or the like.

[0127] Therefore, it can be understood that the processing element 202 can be configured for a specific purpose, or configured to execute instructions stored in a volatile or non-volatile medium, or instructions that are otherwise accessible to the processing element 202. Therefore, whether configured by hardware or a computer program product, or by a combination thereof, when the processing element 202 is configured accordingly, the processing element 202 can perform the steps or operations according to the embodiments of the present disclosure.

[0128] In some embodiments, computing platform 200 includes or communicates with non-volatile memory 204 (also referred to as non-volatile memory, medium, memory, memory circuit, and / or similar terms used interchangeably herein). In some examples, non-volatile memory 204 may include one or more non-volatile memories or storage media, including, but not limited to, hard disks, ROMs, PROMs, EPROMs, EEPROMs, flash memory, MMCs, SD memory cards, memory sticks, CBRAMs, PRAMs, FeRAMs, NVRAMs, MRAMs, RRAMs, SONOSs, FJG RAMs, Millipede memories, racetrack memories, and the like.

[0129] It should be appreciated that the non-volatile memory 204 may store data, databases, database instances, database management systems, files, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, etc. The terms database, database instance, database management system, and / or similar terms used interchangeably herein may refer to a collection of records or data stored in a computer-readable storage medium using one or more database models (e.g., hierarchical database model, network model, relational model, entity-relationship model, object model, document model, semantic model, graph model, etc.).

[0130] In some embodiments, computing platform 200 includes or is in communication with volatile memory 206 (also referred to as volatile memory, media, memory, memory circuit, and / or similar terms used interchangeably herein). In some examples, volatile memory 206 may include one or more volatile memories or storage media including, but not limited to, RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, and the like.

[0131] It should be appreciated that volatile memory 206 may be used to store at least a portion of a database, database instance, database management system, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, etc., that is executed by, for example, processing element 202. Thus, databases, database instances, database management systems, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, etc. may be used to control certain aspects of the steps / operations of computing platform 200 with the assistance of processing element 202 and an operating system.

[0132] As described above, in one embodiment, the computing platform 200 may also include one or more network interfaces 208 for communicating with various computing entities (eg, Figure 1 One or more components of a wireless communication network may communicate with each other, for example, by sending data, content, information, and / or similar terms used interchangeably herein, which may be transmitted, received, manipulated, processed, displayed, stored, etc. Such communication may be performed using a wired data transmission protocol, such as Fiber Distributed Data Interface (FDDI), Digital Subscriber Line (DSL), Ethernet, Asynchronous Transfer Mode (ATM), Frame Relay, Data Over Cable Service Interface Specification (DOCSIS), or any other wired transmission protocol. Similarly, the computing platform 200 can be configured to communicate via a wireless external communication network using any of a variety of protocols, such as General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), CDMA2000 1X (1xRTT), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Evolution Data Optimized (EVDO), High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi), Wi-Fi Direct, 802.16 (WiMAX), Ultra Wideband (UWB), Infrared (IR) protocol, Near Field Communication (NFC) protocol, Wibree, Bluetooth protocol, wireless Universal Serial Bus (USB) protocol and / or any other wireless protocol.

[0133] Although not shown, the computing platform 200 may include or be in communication with one or more input elements, such as keyboard input, mouse input, touch screen / display input, motion input, movement input, audio input, pointing device input, joystick input, keypad input, etc. The computing platform 200 may also include or be in communication with one or more output elements (not shown), such as audio output, video output, screen / display output, motion output, movement output, etc.

[0134] As described above, computing platform 200 may be Figure 1 Examples of one or more components in the example embodiment include, for example, the exchange platform 102 and / or the member platforms 112a-c.

[0135] b. Example Client Device

[0136] Figure 3 1 is an example schematic diagram of a client device 104 according to one or more embodiments of the present disclosure. The client device 104 can be operated by various entities, and the example computing ecosystem can include one or more client devices 104. For example, the client device 104 can be associated with, owned by, operated by, and / or the like by one or more end users. In various embodiments, the end user of the client device 104 may wish to participate in a value exchange between a partner and a service provider. As described herein, the user can achieve the above operations by utilizing one or more functional interactions, which are provided by user input of the client device 104.

[0137] For example, the client device 104 may be a personal computing device, a smartphone, a tablet computer, a laptop computer, a personal digital assistant, and / or the like. In various embodiments, the computing platform 200 may communicate with one or more client devices 104 and manage value exchanges for one or more client devices 104. Figure 3 As shown, the client device 104 may include an antenna 312, a transmitter 304 (e.g., a radio transmitter), a receiver 306 (e.g., a radio receiver), and a processing element 308 (e.g., a CPLD, a microprocessor, a multi-core processor, a co-processing entity, an ASIP, a microcontroller, and / or a controller) that provides signals to and receives signals from the transmitter 304 and the receiver 306, respectively.

[0138] The signals provided to the transmitter 304 and the receiver 306, respectively, and the signals received from the receiver 306 may include signaling information / data according to the air interface standard of the applicable wireless system. In this regard, the client device 104 may be capable of operating using one or more air interface standards, communication protocols, modulation types, and access types. More specifically, the client device 104 may operate according to any of a plurality of wireless communication standards and protocols, such as those described above with respect to the computing platform 200. In a particular embodiment, the client device 104 may operate according to a plurality of wireless communication standards and protocols, such as UMTS, CDMA2000, 1xRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth, USB, etc. Similarly, the client device 104 may operate via a plurality of wired communication standards and protocols, such as those described above with respect to the computing platform 200 via the network interface 320.

[0139] Through these communication standards and protocols, the client device 104 can communicate with the computing platform 200 using concepts such as Unstructured Supplementary Service Data (USSD), Short Message Service (SMS), Multimedia Messaging Service (MMS), Dual Tone Multi-Frequency Signaling (DTMF), and / or Subscriber Identity Module Dialer (SIM Dialer). The client device 104 can also download, for example, changes, add-ons, and updates to its firmware, software (e.g., including executable instructions, applications, program modules), and operating system.

[0140] In some embodiments, the client device 104 includes location determination aspects, devices, modules, functions, and / or similar terms used interchangeably herein. For example, the client device 104 may include outdoor positioning aspects, such as a location module suitable for obtaining information such as latitude, longitude, altitude, geocoding, route, direction, heading, speed, universal time (UTC), date, and / or various other information / data. In one embodiment, the location module can obtain data, sometimes referred to as ephemeris data, by identifying the number of satellites in view and the relative positions of these satellites (e.g., using a global positioning system (GPS)). The satellite can be a variety of different satellites, including a low earth orbit (LEO) satellite system, a Department of Defense (DOD) satellite system, the European Union Galileo positioning system, the Chinese Beidou navigation system, the Indian regional navigation satellite system, etc. The data can be collected using various coordinate systems, such as decimal degrees (DD); degrees, minutes, seconds (DMS); universal transverse Mercator (UTM); Universal Polar Stereographic (UPS) coordinate system, etc. Alternatively, the location information / data may be determined by triangulating the location of the client device 104 in conjunction with various other systems, including cellular towers, Wi-Fi access points, and the like. Similarly, the client device 104 may include indoor positioning aspects, such as a location module adapted to obtain information such as latitude, longitude, altitude, geocoding, route, direction, heading, speed, time, date, and / or various other information / data. Some indoor systems may use various location or positioning technologies, including RFID tags, indoor beacons or transmitters, Wi-Fi access points, cellular towers, nearby computing devices (e.g., smartphones, laptops), and the like. For example, these technologies may include iBeacons, gimbaled proximity beacons, Bluetooth Low Energy (BLE) transmitters, NFC transmitters, and the like. These indoor positioning aspects may be used in a variety of settings to determine the location of someone or something to within inches or centimeters.

[0141] In some embodiments, the client device 104 may include a user interface 316 (e.g., a display screen coupled to the processing element 308, a speaker, tactile mechanization, etc.) and / or a user input interface 318 (e.g., a touch screen, a microphone, etc. connected to the processing element 308). For example, the user interface 316 may be one or more application screens presented by one or more computing platforms described herein. The user input interface 318 may include any of a plurality of devices or interfaces that allow the client device 104 to receive data, such as a keyboard (hard or soft), a touch display, a voice / speech or motion interface, or other input devices. In an example including a keyboard, the keyboard may include (or cause to be displayed) traditional numbers (0-9) and related keys (#, *), as well as other keys for operating the client device 104, and may include a full set of alphabetic keys or a set of keys that may be activated to provide a full set of alphanumeric keys. In addition to providing input, the user input interface may also be used, for example, to activate or deactivate certain functions, such as a screen saver and / or a sleep mode.

[0142] The client device 104 may also include volatile memory 322 and / or non-volatile memory 324, which may be embedded and / or removable. For example, the non-volatile memory 324 may be ROM, PROM, EPROM, EEPROM, flash memory, MMC, SD memory card, memory stick, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory, racetrack memory, etc. The volatile memory 322 may be RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, etc. The volatile and non-volatile storage or memory may store databases, database instances, database management systems, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and the like to implement the functionality of the client device 104. As indicated, this may include partner applications, service provider applications, and the like that reside on the client device 104 and / or that may be accessed via a browser or other user interface to communicate with the computing platform 200.

[0143] In some embodiments, client device 104 may include one or more components or functions that are the same or similar to components or functions of computing platform 200, as described in more detail above. As will be appreciated, these architectures and descriptions are provided for example purposes only and are not limiting of the various embodiments.

[0144] In various embodiments, the client device 104 can be implemented as an artificial intelligence (AI) computing entity, such as Amazon Echo, Amazon Echo Dot, Amazon Show, Google Home, and / or the like. Therefore, the client device 104 can be configured to provide and / or receive information / data from an end user via an input / output mechanism (e.g., a display, a camera, a speaker, a voice-activated input, and / or the like). In certain embodiments, the AI ​​computing entity may include one or more predefined and executable program algorithms stored in an onboard memory storage module and / or accessible via a network. In various embodiments, the AI ​​computing entity may be configured to retrieve and / or execute one or more predefined program algorithms when a predefined trigger event occurs.

[0145] c. Example network

[0146] In some embodiments, Figure 1 Any two or more of the illustrative components of computing ecosystem 100 may be configured to communicate with each other through respective communication couplings with one or more networks 120. Networks 120 may include, but are not limited to, any one or combination of different types of suitable communication networks, such as a wired network, a public network (e.g., the Internet), a private network (e.g., a frame relay network), a wireless network, a cellular network, a telephone network (e.g., a public switched telephone network), or any other suitable private and / or public network. In addition, network 120 may have any suitable communication range associated therewith, and may include, for example, a global network (e.g., the Internet), a MAN, a WAN, a LAN, or a PAN. In addition, network 120 may include any type of medium that can carry network traffic, including, but not limited to, coaxial cable, twisted pair, optical fiber, hybrid fiber coaxial (HFC) medium, microwave ground transceiver, radio frequency communication medium, satellite communication medium, or any combination thereof, as well as various network devices and computing platforms provided by network providers or other entities.

[0147] d. Example value exchange system

[0148] Figure 44 is an example block diagram of an exemplary network-based exchange system 400 according to one or more embodiments of the present disclosure. The network-based exchange system 400 includes a new computing ecosystem and a computing platform that provide an end-to-end value exchange solution to replace the traditional exchange processing system. As described herein, the network-based exchange system 400 can be value system-independent and can be applied to any value-based exchange, including, for example, information-based exchange, financial-based exchange, reputation-based exchange, healthcare-based exchange, interest-based exchange, and / or the like. In any value system, the network-based exchange system 400 can utilize an intermediate entity and one or more defined communication interfaces to facilitate a network-based exchange between a value-seeking entity (e.g., a partner) and a value-providing entity (e.g., a service provider), which can be associated with one or more member platforms of the network-based transaction system 400.

[0149] As shown, the network-based exchange system 400 may include an exchange platform 102, a partner platform 420, and / or a service provider platform 440, which may be configured to communicate via one or more exchange interfaces. The partner platform 420 and / or the service provider platform 440 may include one or more member platforms 112a-c from the member platform network 110. For example, the partner platform 420 and the service provider platform 440 may include a single member platform (e.g., member platform 112c). Additionally or alternatively, the partner platform 420 and the service provider platform 440 may include one or more different member platforms (e.g., member platforms 112a and 112b). In some examples, a user may interact with one or more platforms via a client device 104.

[0150] In some embodiments, the exchange platform 102 is a computing entity that is configured to facilitate the voucherless exchange of value for one or more members in the network. The exchange platform 102 may include one or more processing devices, storage devices, and / or the like that are physically and / or wirelessly coupled and configured to collectively (and / or individually) perform one or more computing tasks that facilitate value system-independent exchanges. In some examples, the exchange platform 102 may include, define, and / or otherwise utilize one or more exchange interfaces to facilitate communications (e.g., requests, responses, etc.) between multiple members. As described herein, interfaces may be utilized to facilitate secure exchanges between one or more members in any value system.

[0151] In some embodiments, a member is an entity that cooperates with the exchange platform 102 to participate in a value exchange. For example, a member may include (i) a partner that receives value using the exchange platform 102, (ii) a service provider that provides value using the exchange platform 102, and / or (iii) both a partner and a service provider. As used herein, when a member receives value through a value exchange, the member may be referred to as a partner; and / or when a member provides value through a value exchange, the member may be referred to as a service provider. Therefore, depending on the member's role in the value exchange, the same member may be a partner or a service provider. For example, a member may be a partner that receives value through a value exchange. The same member may be a service provider that provides value in another value exchange. In some examples, the same member may be both a partner and a service provider in the same value exchange, so that the member may use the exchange platform 102 to provide and subsequently receive value in a single member value exchange.

[0152] In one embodiment, when a member uses a service provided by a service provider, the member is a partner. Partners may include any value seeking entity in any value system. For example, in a financial value system, partners may include merchants (such as retailers, physical stores, etc.) that can use service providers (such as financial institutions) to access funds for financial transactions. Additionally or alternatively, in an information value system, partners may include news publishers (e.g., newspapers, media organizations, etc.) that can use service providers such as news agencies (e.g., wire services, news services, etc.) to access information for information transactions. In a healthcare value system, partners may include healthcare providers that can access healthcare benefit administrators to access medical benefits to provide funding for medical operations. It should be understood that the technology of the present disclosure can be applied to any value system, and partners may include any value seeker for any corresponding value system.

[0153] In some embodiments, when a member provides services to a partner, the member is a service provider. A service provider can include a value source in any value system. For example, in a financial value system, a service provider may include a financial institution (e.g., a bank, a currency exchange platform, a credit union, etc.) that can provide access to funds for financial transactions between one or more entities. Additionally or alternatively, in an information value system, a service provider may include a news agency (e.g., a wire service, a news service, etc.) that can provide a source of information for a news publisher's release. In a healthcare value system, a service provider may include a healthcare benefits administrator that can provide healthcare providers with access to healthcare benefits. It should be understood that the technology of the present disclosure can be applied to any value system, and a service provider may include any value source for any corresponding value system.

[0154] In some embodiments, a service provider tool is a mechanism utilized by a service provider to provide value on behalf of a particular user. The service provider tool may depend on the value system and / or the service provider. In some examples, the service provider tool may include an account with the service provider. For example, in a financial value system, the service provider tool may include a bank account (e.g., checking, savings, etc.), a brokerage account, a line of credit, and / or the like. In an information value system, the service provider tool may include a subscriber account and / or the like. In a healthcare value system, the service provider tool may include a healthcare benefit account and / or the like.

[0155] In some embodiments, the services provided by the service provider are subject to one or more policies and / or security codes. For example, the service provider and / or service provider tool may be associated with a security code for verifying the use of the service provider tool. Additionally or alternatively, the service provider may be associated with one or more member policies for authenticating the security code.

[0156] In some embodiments, the security code is a data entity that defines a sequence of characters used to verify a user in an exchange. The security code may include a sequence of one or more dynamic lengths of different characters (e.g., six characters, eight characters, etc.) that may be set and / or provided to the user in advance by the user. The security code may be provided later by the user to verify the presence status of the user for the exchange (e.g., as described herein, by comparing the security code input with a security code reference). The one or more different characters may include any number of alphanumeric characters, emojis, Chinese characters, winged fonts, and / or the like.

[0157] In some embodiments, the security code is a network-managed n-character PIN. As described herein, the security code can be managed by a client device as a microservice to enable and / or disable the UUEK (and / or any other exchange credential) prior to an exchange request. In this way, security codes can be deployed for any type of service provider tool by enabling and / or disabling the corresponding UUEK. By managing security codes at the network level, members can benefit from faster exchanges because the possibility of authorization being denied for an invalid PIN is eliminated. For example, the UUEK can be disabled until a security code is received to enable the UUEK. The exchange platform 102 can prevent a user from initiating an exchange before the UUEK is enabled, thereby ensuring that all exchange authorization requests provided to the service provider have been pre-verified based on the security code.

[0158] In some embodiments, the security code corresponds to a user. For example, the security code may be pre-set by the user and / or provided to the user for a UUEK accessible to the user. In some examples, each security code may be UUEK specific. For example, each corresponding security code may be configured to enable a single UUEK. Exemplarily, the exchange platform 102 may be configured to enable a UUEK using a plurality of security code element groups 424, each security code element group associating a security code with a corresponding UUEK.

[0159] In some embodiments, the security code element group 424 is a data entity that defines the correlation between the UUEK and the security code. The security code element group 424 may include a data object, a record, and / or any other data structure (e.g., a link node, etc.) that is configured to represent the association between the security code and the UUEK. The security code element group 424 may include, for example, a security code reference, a UUEK, one or more derivative identifiers of the UUEK (as described herein), and / or contextual pairing data. The contextual pairing data may include one or more pairing attributes, such as one or more timing attributes. For example, the timing attribute may indicate a configuration time (e.g., indicating the time to set the security code element group, etc.), an expiration time (e.g., the time when the security code must be reset, etc.), and / or the like. As described herein, the exchange platform 102 may utilize the security code element group 424 to identify the security code reference of the UUEK and enable (and / or disable) the UUEK based at least in part on a comparison between the security code reference and the security code input provided by the user.

[0160] In some embodiments, a security code reference is a data entity that defines a record security code. The security code reference may include an internal representation of a security code for a UUEK (eg, for exchange platform 102, etc.).

[0161] In some embodiments, member policy 422 defines one or more verification requirements for a service provider tool. Member policy 422 may correspond to a member and / or a member's service provider tool. For example, member policy 422 may define one or more verification requirements for using a service provider tool based at least in part on one or more member-specific criteria. Additionally or alternatively, member policy 422 may define one or more verification requirements for using a service provider tool based at least in part on one or more tool-specific criteria. Member-specific criteria may apply to multiple service provider tools associated with a member, while tool-specific criteria may apply to at least one of multiple service provider tools associated with a member.

[0162] The verification requirement may indicate one or more policy attributes of a value-based exchange that requires an enabled UUEK. For example, a disabled UUEK may be used to authorize a value-based exchange that does not include one or more attributes of the required enabled UUEK. In the event that the value-based exchange includes at least one attribute of the required enabled UUEK, the disabled UUEK may be prevented from authorizing the value-based exchange.

[0163] In some examples, the policy attributes may include an object identifier, one or more object attributes, and / or one or more value exchange attributes that identify an object and / or one or more authorized / unauthorized amounts of an object. For example, member policy 422 may include multiple object identifiers. The multiple object identifiers may indicate multiple objects that are authorized / unauthorized to obtain (e.g., purchase, etc.) with a disabled UUEK.

[0164] In some examples, the object identifier may be a global object identifier. For example, the global object identifier may be a stock keeping unit (SKU) code. In addition or alternatively, the global object identifier may be a manufacturer part number (MPN), a global trade item number (GTIN), a product or service name, an international standard book number (ISBN), a universal product code (UPC), an international article number (EIN), and / or the like. In some examples, the object identifier may include a system object identifier. For example, the system object identifier may include an identifier (e.g., a table identifier, etc.) corresponding to a record data object representing an object within the exchange platform 102. In some embodiments, the system object identifier and the global object identifier are the same.

[0165] In some embodiments, the policy attributes include value exchange attributes corresponding to a particular value-based exchange and / or an object included in the value-based exchange. For example, the value exchange attributes may include a threshold exchange value for a disabled UUEK. For example, one or more exchange attributes may indicate an exchange value, and one or more verification requirements may define an exchange value threshold at which a corresponding security event is required for the service provider tool.

[0166] The service provider and the partner can communicate through one or more corresponding member platforms respectively associated with the entity. As an example, the service provider can be associated with the service provider platform 440, and the partner can be associated with the partner platform 420.

[0167] In some embodiments, the member platform is a computing entity corresponding to a member associated with the exchange platform 102. The member platform may include a partner platform 420 representing a partner, a service provider platform 440 representing a service provider, and / or both. In some examples, the member platform may be both a partner platform 420 and a service provider platform 440. For example, the same member platform may be configured to operate on behalf of a partner of one value exchange and a service provider of another value exchange. In some examples, the same member platform may be configured to operate on behalf of both a partner and a service provider in a single value exchange. It should be noted that the term member platform may refer to a partner platform 420, a service provider platform 440, or both, which may depend on the role of the member platform in the value exchange (e.g., and / or one or more interfaces used by the member platform in the value exchange).

[0168] In some embodiments, partner platform 420 is a computing entity configured to perform one or more operations on behalf of a partner. For example, partner platform 420 may include one or more processing devices, storage devices, and / or the like that are physically and / or wirelessly coupled and configured to jointly (and / or individually) perform one or more computing tasks for requesting value in a value system-independent exchange. In some examples, partner platform 420 may include, define, and / or otherwise utilize one or more exchange interfaces to facilitate communication (e.g., requests, responses, etc.) with exchange platform 102. In some examples, partner platform 420 may be configured to host one or more user-facing applications (e.g., partner applications, etc.) for interacting with one or more users.

[0169] For example, in a financial value system, the partner platform 420 may host an online marketplace for a partner that allows users to interact with one or more products or services provided by the partner (e.g., search, browse, purchase, return, etc.). In the case of purchasing a product, the partner platform 420 may work with one or more service providers to access the purchase funds. Traditionally, users need to use a card number, account number, and / or other financial credentials to access funds from a service provider, but this may expose the user to malicious parties. In order to address the cybersecurity and data privacy issues of traditional financial systems (and / or other value-based systems), the partner platform 420 may register with the exchange platform 102 by configuring one or more software development kits (SDKs), APIs, and / or the like to facilitate communication with the exchange platform 102. For example, the partner platform 420 may include, define, and / or otherwise utilize one or more partner interfaces 402 to facilitate communication (e.g., requests, responses, etc.) with the exchange platform 102.

[0170] In some embodiments, the service provider platform 440 is a computing entity configured to perform one or more operations on behalf of the service provider. For example, the service provider platform 440 may include one or more processing devices, storage devices, and / or the like, which are physically and / or wirelessly coupled and configured to jointly (and / or individually) perform one or more computing tasks for providing value in an exchange that is independent of the value system. In some examples, the service provider 440 may include, implement, and / or otherwise utilize one or more interfaces to facilitate communication (e.g., requests, responses, etc.) with the exchange platform 102. In some examples, the service provider platform 440 may be configured to facilitate one or more service provider tools. In some examples, the service provider platform 440 may be configured to host one or more user-oriented applications (e.g., service provider applications, etc.) for managing one or more service provider tools.

[0171] In some examples, for example, in a financial value system, the service provider platform 440 may maintain one or more financial assets (e.g., a line of credit, a bank account, etc.) to allow a user to provide funds in exchange for purchasing a product from a partner. In the case of purchasing a product, the service provider platform 440 may work with the partner platform 420 to authorize the exchange and / or otherwise provide access to the purchase funds. Traditionally, access to funds at a service provider is facilitated by presenting a card number, an account number, and / or another financial credential to the service provider platform 440, which may expose the user, service provider, or partner to malicious parties, especially when provided over an unsecured network (e.g., a public network, etc.). In order to address the cybersecurity and data privacy issues of traditional financial systems (and / or other value-based systems), the service provider platform 440 may register with the exchange platform 102 by configuring one or more software development kits (SDKs), APIs, and / or the like to facilitate communication with the exchange platform 102. For example, the service provider platform 440 can include, implement, and / or otherwise utilize one or more service provider interfaces 404 to facilitate communications (eg, requests, responses, etc.) with the exchange platform 102 .

[0172] As described herein, the service provider interface 404 may enable the exchange platform 102 to identify and request the use of a service provider tool to facilitate a transaction. For example, the service provider platform 440 may be configured to facilitate one or more service provider tools. In some examples, a service provider tool may include a virtual tool (e.g., a virtual account, a line of credit, etc.) hosted by the service provider platform 440. For example, the service provider platform 440 may be configured to maintain a plurality of tool data objects indicating a plurality of service provider tools for a plurality of affiliated entities.

[0173] In some embodiments, a tool data object is a data entity representing a service provider tool. A tool data object may include one or more tool identifiers and / or one or more tool attributes. In some examples, one or more tool identifiers and / or one or more tool attributes may be based at least in part on the type of the tool data object. Exemplarily, a service provider tool may be represented as a member tool data object in a member platform (e.g., service provider platform 440). Additionally or alternatively, a service provider tool may be independently represented by a system tool data object in an exchange platform 102. In some examples, a member tool data object and a system tool data object may include one or more of the same one or more tool identifiers and / or one or more tool attributes. For example, a member platform may register multiple service provider tools (e.g., using a service provider interface 404) with an exchange platform 102. During registration, a member platform (e.g., service provider platform 440) may provide one or more tool identifiers and / or tool attributes, and in some examples, an exchange platform 102 may return another identifier.

[0174] In some embodiments, a member instrument data object is an internal representation of a service provider instrument within a member platform (e.g., a service provider platform 440). A member instrument data object may include one or more instrument identifiers, such as a member instrument identifier, an instrument key from an exchange platform 102, and / or a user identifier. As described herein, for example, a user identifier may include a member user identifier. Additionally or alternatively, a member instrument data object may include one or more instrument attributes, such as an instrument type (e.g., a credit-based instrument, a debit-based instrument, an information-based instrument, etc.), an instrument representation, and / or one or more context attributes. In some examples, the context attributes may depend on a value system. For example, in a financial value system, one or more context attributes may indicate (i) a currency associated with a service provider instrument, (ii) asset availability of a service provider instrument (e.g., balance, coverage, etc.), (iii) one or more previous transactions with a service provider instrument, etc.

[0175] In some embodiments, the system tool data object is an external representation of a service provider tool within the exchange platform 102. The system tool data object may include one or more tool identifiers, such as a tool reference for a member platform, a system tool identifier, and / or a user identifier. As described herein, for example, a user identifier may include a system user identifier. Additionally or alternatively, the system tool data object may include one or more tool attributes, such as a tool type (e.g., a credit-based tool, a debit-based tool, an information-based tool, etc.), a tool representation, and / or one or more context attributes. In some examples, the context attributes may depend on the value system. For example, in a financial value system, one or more context attributes may indicate a currency associated with a service provider tool.

[0176] As described herein, a service provider tool may be associated with one or more usage restrictions, such as a security code and / or a member policy 422. In some examples, the exchange platform 102 may include a verification service 408 configured to adjudicate secure interaction requests and / or exchange requests based at least in part on a valid security code input and / or a member policy 422. To this end, the exchange platform 102 (and / or its verification service 408) may access a security code element set 424 and / or a member policy 422 for a service provider tool. For example, a member platform may register a security code with the exchange platform 102 (e.g., using a service provider interface 404 and / or a partner interface 402). Upon registration, the security code may be stored as a security code reference of a security code element set 424 that associates the security code reference with a user, member, service provider tool, and / or a UUEK associated therewith. Additionally or alternatively, the member platform may register a member policy 422 with the exchange platform 102 (e.g., using a service provider interface 404). During registration, a member platform (e.g., service provider platform 440) may provide one or more policy attributes, attribute updates, and / or the like for validating secure interactions and / or exchange requests that reference one or more service provider tools and / or the like maintained by the member platform. In some examples, the member platform may continuously update member policy 422 when one or more policy attributes are modified, added, and / or removed.

[0177] As described herein, the exchange platform 102 (e.g., the authentication service 408, etc.) can authenticate the user, service provider tool, UUEK, and / or exchange request using the security code and / or member policy 422. In some examples, the authentication of the exchange request can be based at least in part on the recorded data object.]

[0178] In some embodiments, a recorded data object is a data object that represents an object that can participate in a value-based exchange. In some examples, a recorded data object can be an internal representation of an object for exchange platform 102. For example, an object can include different units of a value-based exchange for which value is being transferred. A recorded data object for an object can include a data object that records one or more aspects of an object (e.g., an object identifier, an object attribute, etc.).

[0179] For example, the recorded data object may include an object identifier and / or one or more object attributes for a particular object associated with a value system. The object may be based at least in part on a value system. For example, in a financial value system, an object may be a tangible or intangible item, product, and / or the like that can be purchased in exchange for a monetary unit. In a healthcare value system, an object may be a healthcare procedure covered by a healthcare policy, and / or the like.

[0180] In some examples, exchange platform 102 can maintain and / or access an object data store including a plurality of recorded data objects. As described herein, the object data store can include a plurality of recorded data objects from at least in part one or more members of an exchange network.

[0181] In some embodiments, an object attribute is a data entity that describes a characteristic of an object. Object attributes may include object-based attributes and / or exchange-based attributes.

[0182] For example, object-based attributes may include spatial attributes, count attributes, value attributes, source attributes, combination attributes, classification attributes, and / or any other attributes that describe object characteristics. For example, spatial attributes may indicate one or more dimensions of an object (e.g., height, width, weight, etc.), value attributes may indicate the value of the object (e.g., price, etc.), ingredient attributes may indicate one or more ingredients, components, etc. of an object, classification attributes may indicate one or more categories (e.g., restricted substances, etc.), and / or the like. Exemplarily, one or more classification attributes may indicate whether an object is associated with (i) one or more general store categories, such as vegetables, fruits, dairy products, meats, grains, seeds, alcohol, tobacco, in-store consumables, hot food, pharmacy, pet food, and non-food, (ii) one or more medical categories, such as dental, ophthalmology, general health, etc., (iii) one or more information categories, such as international sources, domestic sources, etc., and / or the like. In one example, the ingredient attribute may indicate one or more ingredients of the object, such as the volume percentage of alcohol within the object, one or more ingredients such as meat, dairy derivatives, peanut derivatives, tree nut derivatives, soy derivatives, and / or the like.

[0183] In some examples, object-based attributes may be based at least in part on a value system. For example, in at least one financial-based value system, object-based attributes may include one or more line item attributes, one or more line item adjustments, and / or the like. Line item attributes may include a sequence, a line item group, a product code, an item name, an item source (e.g., a supplier, a manufacturer, etc.), a description, a quantity, a mass (e.g., grams, kilograms, etc.), one or more spatial dimensions (e.g., length, width, height, volume, etc.), a unit amount, a unit tax amount, a line amount (e.g., an amount of a line item), a line tax amount, and / or the like. Line item adjustments may include an adjustment type (e.g., a manufacturer discount, a store discount, a return, a cash payment, a gift card payment, a payment other, and / or the like), an item, a product or service code, an item description, an item quantity, a unit item, an item mass (e.g., grams, kilograms, etc.), a unit amount, a unit tax amount, a line amount (e.g., an amount of a line item), a line tax amount, and / or the like.

[0184] In some examples, a member platform, such as partner platform 420 and / or service provider platform 440 , may be associated with a user-facing application to facilitate one or more interactions with the user and / or other affiliated entities (eg, via client device 104 ).

[0185] In some embodiments, user-oriented applications are computer programs hosted by computing entities for facilitating one or more user interactions. User-oriented applications may include software (e.g., computer-readable instructions, etc.) that is designed to perform one or more computing tasks for computing entities (e.g., member platforms). For example, user-oriented applications may facilitate communication between members and users. Exemplary, user-oriented applications may be configured to present one or more user interfaces 406 (e.g., through client devices 104) for interacting with users on behalf of members. In some examples, user-oriented applications may be configured to receive user input (e.g., through one or more user interfaces 406) to receive information from users. For example, user input may include a security code input for ensuring user interaction security.

[0186] In some embodiments, the user-oriented application is a partner application 416 hosted by a partner platform 420 (e.g., a member platform that acts as a partner for a specific exchange, etc.) to facilitate functionality for the partner. The partner application 416 may include software (e.g., computer-readable instructions, etc.) that is designed to perform one or more computing tasks for the partner. In some examples, the partner application 416 may be configured with one or more devices (e.g., point-of-sale terminals, etc.) from an independent partner institution (e.g., a physical bank, etc.). For example, the partner application 416 may be configured to present one or more user interfaces 406 for interacting (e.g., browsing, purchasing, viewing, etc.) with one or more products provided by a retail-based partner, one or more units of information provided by an information-based partner, and / or the like. In some examples, the partner application 416 may be configured to receive user input (e.g., through one or more user interfaces 406) to receive information from a user.

[0187] In some embodiments, the service provider platform 440 is configured to host one or more service provider applications 418 for managing one or more service provider tools. For example, a user-oriented application may be a service provider application 418 hosted by the service provider platform 440 (e.g., acting as a member platform for a service provider for a particular exchange, etc.) to facilitate functionality for the service provider. In some examples, the service provider application 418 may be configured with one or more devices from an independent service provider institution (e.g., a physical bank, etc.). The service provider application 418 may include software (e.g., computer-readable instructions, etc.) designed to perform one or more computing tasks for the service provider. For example, the service provider application 418 may be configured to present one or more user interfaces for interacting with one or more service provider tools facilitated by the service provider (e.g., viewing, managing, auditing, registering, etc.). Exemplarily, in a financial value system, the service provider application 418 may enable access to bank accounts, brokerage accounts, credit lines, and / or the like to manage funds, assets, and / or the like handled by each account. In some examples, service provider application 418 may be configured to receive user input (eg, via one or more user interfaces 406 ) to receive information, authorization, etc. from a user.

[0188] In some embodiments, the partner application 416 and / or the service provider application 418 are configured to maintain, update and / or register member policies 422 for users, service provider tools and / or security codes corresponding to the UUEK. For example, the partner platform 420 and / or the service provider platform 440 can enable users, organizations and / or any other entities to configure security codes for initiating secure interactions. Additionally or alternatively, the service provider platform 440 can enable users, organizations and / or any other entities to configure member policies 422 for managing the use of service provider tools.

[0189] In some examples, user input may be provided and / or received via service provider application 418 and / or partner application 416. For example, the user input may include a security code input for initiating a secure interaction. For example, the security code input may be provided to exchange platform 102 via input to a user interface of service provider application 418 and / or partner application 416. In some embodiments, exchange platform 102 facilitates communication between partner platform 420 and service provider platform 440 using one or more exchange interfaces.

[0190] In some embodiments, the exchange interface is a set of instructions for facilitating communication between the exchange platform 102 and one or more member platforms and / or internal services. The exchange interface may include an API, a file-based interface, a message queue-based interface, and / or the like. For example, the exchange interface may include an API, for example, including one or more simple object access protocol (SOAP) APIs, one or more remote procedure call (RPC) APIs, one or more websocket APIs, one or more representational state transfer (REST) ​​APIs, and / or the like. In some embodiments, the exchange interface may include one or more RPC APIs, such as one or more gRPC APIs.

[0191] The exchange platform 102 may include, define, and / or otherwise utilize one or more different exchange interfaces to facilitate communication with one or more external platforms, such as one or more member platforms (e.g., partner platform 420, service provider platform 440, etc.). Each interface may include a plurality of communication instructions, message definitions, and / or the like for exchanging requests and / or responses between the exchange platform 102 and entities participating in the value exchange. Exemplarily, the exchange interface may include a partner interface 402 for facilitating communication with the partner platform 420 and / or a service provider interface 404 for facilitating communication with the service provider platform 440.

[0192] In some embodiments, the partner interface 402 is an exchange interface for facilitating one or more communications between the partner platform 420 and the exchange platform 102. The partner interface 402 may define one or more communication instructions, message definitions, and / or the like for facilitating one or more request messages and / or response messages between the partner platform 420 and the exchange platform 102. For example, the partner interface 402 may include an API that defines (i) requests from a computing entity acting as a partner platform 420 to the exchange platform 102, and / or (ii) requests from the exchange platform 102 to the partner platform 420. For example, the partner interface 402 may define one or more registration messages, session messages, transaction messages, and / or the like to facilitate the value exchange of the partner. In some embodiments, the partner interface 402 defines one or more identifiers for securely identifying one or more parts of the value exchange.

[0193] In some embodiments, the service provider 404 is an exchange interface for facilitating one or more communications between the service provider platform 440 and the exchange platform 102. The service provider interface 404 may define one or more communication instructions, message definitions, and / or the like for facilitating one or more request messages and / or response messages between the service provider platform 440 and the exchange platform 102. For example, the service provider interface 404 may include an API that defines (i) requests from a computing entity acting as the service provider platform 440 to the exchange platform 102, and / or (ii) requests from the exchange platform 102 to the service provider platform 440. For example, the service provider interface 404 may define one or more registration messages, session messages, transaction messages, and / or the like to facilitate value exchange using a service provider tool. In some embodiments, the service provider interface 404 defines one or more identifiers for securely identifying one or more parts of a value exchange.

[0194] The exchange platform 102 can facilitate communication between member platform networks. For example, a member network can include multiple entities that have joined the exchange platform 102, for example, by registering with the exchange platform 102, configuring corresponding interfaces for communicating with the exchange platform 102, etc. In some examples, the exchange platform 102 can execute one or more separate services for interacting with each joined entity. For example, each service can include one or more partner services 410 and / or service provider services 412.

[0195] In some embodiments, the exchange platform 102 instantiates a separate partner-specific service, i.e., partner service 410, for each member network. Additionally or alternatively, for example, in a multi-tenant environment, partner service 410 may be instantiated for one or more partners from a member network. Partner service 410 may be configured to perform one or more exchange operations to resolve exchange requests from partner platform 420. In some embodiments, the exchange platform 102 instantiates a separate service provider-specific service, i.e., service provider service 412, for each member network. Additionally or alternatively, for example, in a multi-tenant environment, service provider service 412 may be instantiated for one or more service providers from a member network. Service provider service 412 may be configured to perform one or more exchange operations to obtain and resolve exchange requests from partner platform 420. The exchange operations may include any of the steps and / or operations described herein.

[0196] In some embodiments, partner service 410 and / or service provider service 412 interact with each other and / or one or more other components of exchange platform 102 via one or more local communication mechanisms to perform exchange operations. For example, exchange platform 102 may include verification service 408. Verification service 408 may be configured to perform one or more verification operations of the present disclosure to verify the UUEK. In this way, exchange platform 102 may pre-process exchange requests and authorization credentials for exchange requests on behalf of member platforms to implement their member policies 422.

[0197] By performing one or more exchange operations, partner service 410 and / or service provider service 412 can generate and utilize multiple non-traditional identifiers to reference one or more aspects of a user, service provider tool, and / or value exchange. At least some of these identifiers may include a universal unique identifier, such as a UUEK, which can be used to provide a value exchange without credentials. Each identifier may be at least temporarily stored in a platform database 414. Platform database 414 may include any type of memory device described herein. In some examples, each service and / or one or more groups of services may be associated with a single portion of platform database 414.

[0198] As described herein, one or more identifiers may be stored in association with one another to form an identifier mapping that the exchange platform 102 (and / or one or more of its services) may utilize to reference users, service provider tools, and / or any other aspects of a value exchange from communications between partner platforms 420, service provider platforms 440, and / or any other member platforms, without including user credentials. Reference will now be made to Figure 5 Examples of non-traditional identifiers are further described.

[0199] e. Example data structure

[0200] Figure 5 500 is an example data graph for facilitating value exchange without credentials according to one or more embodiments of the present disclosure. The data graph 500 shows multiple related identifiers of different types. As shown, each identifier can be associated with at least one related identifier to form an identifier mapping within one or more platforms (e.g., exchange platform 102 and / or service provider platform 440). The identifier mapping authorizes communication between the exchange platform 102 and the service provider platform 440, which references the service provider tool 518 without exposing the permanent credentials 514 (e.g., username, password, card number, etc.) associated with the service provider tool 518 that are susceptible to fraud, abuse and exploitation by malicious parties. As shown, using some techniques of the present disclosure, the permanent credentials 514 may never have to be transmitted outside the service provider platform 440. The data graph 500 only shows some of the multiple identifiers that various embodiments of the present disclosure can generate, store and / or utilize. It should be understood that the identifiers shown are not an exhaustive list and may include other identifiers not shown. Each identifier may be labeled as an identifier, a reference, a key, and / or other similar terms. These terms are used interchangeably herein to refer to units of information used to identify data structures, entities and / or any other components described herein.

[0201] As shown, some of the multiple related identifiers in various embodiments of the present disclosure may include, for example, (i) one or more user references 502, which can be mapped to a member user identifier 522 of a service provider platform 440, (ii) one or more service provider partitions 504, which correspond to a network of a joined service provider platform (such as the service provider platform 440), (iii) one or more partner partitions 506, which correspond to a joined partner platform network, (iv) one or more tool references 520 that can be mapped to a member tool identifier 508 of the service provider platform 440, (v) one or more keys 516 and / or system identifiers 512 that can be associated with the user reference 502 and / or the tool reference 520, (vi) one or more exchange identifiers 510, which can be mapped to the system identifier 512 and / or the key 516, and / or (vii) one or more UUEKs 524, which can be mapped to at least one of the exchange identifier 510 and / or the partner partition 506 and / or the service provider partition 504.

[0202] In some embodiments, the service provider platform 440 may store one or more identifiers that may be mapped to one or more identifiers of the service provider tool 518 and / or the exchange platform 102 to enable the service provider platform 440 to reference the service provider tool 518 based at least in part on the identifiers, which identifiers themselves do not indicate any aspect of the service provider tool 518, including its permanent credentials 514.

[0203] Exemplarily, the service provider platform 440 can store, maintain, and / or otherwise access one or more keys 516 that are mapped to (e.g., are copies, derivatives, etc. of) one or more system identifiers 512 of the exchange platform 102. For example, the keys 516 can include the system identifier 512 as part of the keys 516. The keys 516 can be mapped to the member tool identifier 508 and / or the member user identifier 522, which can internally reference a user of the service provider platform and / or the service provider tool 518. For example, the keys 516 can be provided during a registration process between the service provider platform 440 and / or the exchange platform 102.

[0204] As another example, the exchange platform 102 can store, maintain, and / or otherwise access one or more references, such as tool references 520 and / or user references 502, that are mapped to (e.g., are copies, derivatives, etc. of) one or more member identifiers, such as member tool identifiers 508 and / or member user identifiers 522 of the service provider platform 440. For example, the references can be provided during a registration process between the service provider platform 440 and / or the exchange platform 102.

[0205] In some embodiments, the exchange platform 102 uses one or more entity partitions to reference each member platform of the member platform network. In some embodiments, an entity partition is a unique identifier for a computing entity. An entity partition may include a unique number, alphanumeric number, and / or the like representing a particular computing entity. For example, an entity partition may include a member partition representing a member platform, a service provider partition 504 representing a service provider platform 440, a partner partition 506 representing a partner platform 420, and / or the like.

[0206] In some embodiments, the service provider partition 504 is a unique identifier of a service provider and / or a service provider platform 440 of the service provider. The service provider partition 504 may include a number, an alphanumeric number, any character or symbol, and / or any other sequence of characters or symbols that represents a service provider associated with (e.g., joined, registered, etc.) the exchange platform 102. For example, the exchange platform 102 may include multiple service provider partitions that respectively identify a service provider platform 440 associated with (e.g., joined, registered, etc.) the exchange platform 102. Each service provider partition 504 may represent a service provider platform 440 that has been configured with one or more exchange platform software development kits (SDKs) or the like to implement a service provider interface of the exchange platform 102.

[0207] In some embodiments, the partner partition 506 is a unique identifier for a partner and / or a partner platform of a partner. The partner partition 506 may include a number, an alphanumeric number, any character or symbol, and / or a sequence of any other characters or symbols representing a partner associated with the exchange platform 102. For example, the exchange platform 102 may include multiple partner partitions that respectively identify partner platforms associated with (e.g., joined, registered, etc.) the exchange platform 102. Each partner partition 506 may represent a partner platform that has been configured with one or more exchange SDKs, etc., for implementing a partner interface of the exchange platform 102.

[0208] In some embodiments, when a member platform joins the exchange platform 102, an entity partition is generated to identify the member. In some examples, after joining the exchange platform, the member platform can utilize one or more exchange interfaces to register one or more service provider tools with the exchange platform 102. The service provider tool 518 registers with the exchange platform 102 by exchanging one or more tool identifiers with the exchange platform 102.

[0209] In some embodiments, the tool identifier includes any representation of the service provider tool 518 that identifies the service provider tool without exposing the permanent credentials 514 of the service provider tool 518. As described herein, the tool identifier may include a member tool identifier 508, a system tool identifier, a tool reference 520, a tool key, and / or the like.

[0210] In some embodiments, the member tool identifier 508 is a unique identifier used to represent a service provider tool 518 within a member platform, such as the service provider platform 440. For example, the member tool identifier 508 may include a number, an alphanumeric number, any character or symbol, or any other sequence of characters or symbols used to represent the service provider tool 518 to the service provider platform 440. In some examples, the member tool identifier 508 may include a table identifier for a member tool data object.

[0211] In some embodiments, the tool reference 520 is a unique identifier used to reference the member tool identifier 508. For example, the tool reference 520 can be generated by the member platform and / or provided to the exchange platform 102 to allow the exchange platform 102 to reference the service provider tool 518 maintained on the member platform. In some examples, the tool reference 520 is the same value as the member tool identifier 508. In some examples, the tool reference 520 is a different value that is mapped to the member tool identifier 508.

[0212] In some embodiments, the system tool identifier is a unique identifier used to represent a service provider tool 518 within the exchange platform 102. For example, the system tool identifier can include a number, an alphanumeric number, any character or symbol, or a sequence of any other characters or symbols that represents the service provider tool 518 to the exchange platform 102 without exposing the permanent credentials 514 of the service provider tool 518. In some examples, the system tool identifier can include a UUID. In some examples, the system tool identifier can include at least one of the system identifiers 512.

[0213] In some embodiments, the tool key is a unique identifier for referencing a system tool identifier. For example, during the registration of the service provider tool 518 with the exchange platform 102, the exchange platform 102 may generate and / or provide a tool key. In some examples, the tool key may include an encapsulated system tool identifier. For example, the tool key may include an alphanumeric string formatted according to a key format established by the exchange platform 102 (and / or one or more APIs thereof). The key format may include any number of characters, such as fifty characters or more. In some examples, the characters may be case sensitive. The first portion of the characters (e.g., the first six characters) may be reserved as a partition for identifying an entity associated with the key. For example, for the tool key, the partition may include the service provider partition 504. The second portion of the characters may identify the system tool identifier. In some examples, the tool key may include at least one of the keys 516. The key format described herein may include one or more different parts, each of which may be arranged in any order.

[0214] In some embodiments, after joining the exchange platform 102, the member platform may utilize one or more exchange interfaces to register one or more users with the exchange platform 102. The user may register on the exchange platform 102 by exchanging one or more user identifiers with the exchange platform 102. For example, the user identifier may be utilized to generate, maintain, and / or update one or more user data objects reflecting the user of the member platform and / or the exchange platform 102.

[0215] In some embodiments, a user data object is a data entity that represents a user interacting with a member platform and / or exchange platform 102. For example, a user can include an entity (e.g., an individual, an organization, a group, etc.) that participates in a value exchange managed by exchange platform 102. In some examples, a user can indirectly engage with exchange platform 102 by creating a user account with a registration service provider, registering (and / or granting registration permission) to a service provider tool 518, and / or the like. In some examples, exchange platform 102 can act on behalf of a user without the user directly interacting with exchange platform 102. For example, exchange platform 102 can act as a hidden intermediary between a user-facing application and a user's service provider tool 518.

[0216] In some embodiments, the user data object includes one or more user identifiers and / or one or more user attributes. In some examples, the one or more user identifiers and / or one or more user attributes may be based at least in part on the type of the user data object. Exemplarily, a user may be represented as a member user data object in a member platform. Additionally or alternatively, a user may be independently represented by a system user data object in an exchange platform. In some examples, a member user data object and a system user data object may include one or more of the same one or more user identifiers and / or one or more user attributes. Exemplarily, a member platform may register multiple users with an exchange platform 102. During registration, the member platform may provide one or more user identifiers and / or user attributes, and in some examples, the exchange platform 102 may return another identifier.

[0217] In some embodiments, the member user data object is an internal representation of a user within a member platform (e.g., a service provider platform 440). The member tool data object may include one or more user identifiers, such as a member user identifier 522, a user key from an exchange platform 102, and / or the like. Additionally or alternatively, the member user data object may include one or more user attributes. One or more user attributes may indicate one or more contextual features for a user. In some examples, a user attribute may indicate one or more identifiable features for a user. Exemplarily, a user attribute may indicate a user's first name, last name, email, physical address (e.g., one or more of a street, region, zip code, country, etc.), birthday (e.g., date of birth, age group, etc.), phone number, and / or the like. In some examples, a user attribute may include encryption, hashing, and / or otherwise secure representation of identifiable features for a user. For example, a user attribute may include one or more hash identifiers and / or the like for a user.

[0218] In some embodiments, the system user data object is an external representation of a member user within the exchange platform 102. The system user data object may include one or more user identifiers, such as a user reference 502 for the member platform, a system user identifier, and / or the like. Additionally or alternatively, the system user data object may include one or more user attributes (such as those described herein). Exemplarily, the member platform may register a user with the exchange platform 102. During registration, the member platform may provide the user with a user reference 502 and / or one or more user attributes. In some examples, the user attributes may include a hashed and / or encrypted identifier for the user.

[0219] In some embodiments, the user identifier comprises a unique identifier for a user participating in a value-based exchange. The user identifier may comprise a number, an alphanumeric number, any character or symbol, or a sequence of any other characters or symbols representing a user of the exchange platform 102 and / or a member platform. In some examples, the user identifier may comprise a user reference 502, a user key, a system user identifier, a member user identification, and / or the like.

[0220] In some embodiments, the system user identifier is a unique identifier used to represent a user within exchange platform 102. For example, the system user identifier may include a number, an alphanumeric number, any character or symbol, and / or any other character or symbol that represents the user to exchange platform 102. In some examples, the system user identifier may include a UUID that is specific to a particular user. In some examples, the system user identifier may include at least one of system identifiers 512.

[0221] In some embodiments, the member user identifier 522 is a unique identifier for representing a user within the member platform. For example, the member user identifier may include a number, alphanumeric, any character or symbol / or any other sequence of characters or symbols that represents the user to the service provider platform 440.

[0222] In some embodiments, user reference 502 can be a unique identifier used to reference member user identifier 522. For example, user reference 502 can be generated by a member platform and / or provided to exchange platform 102 to allow exchange platform 102 to reference a user associated with the member platform. In some examples, user reference 502 is the same value as member user identifier 522. In some examples, user reference 502 is a different value that maps to member user identifier 522.

[0223] In some embodiments, the user key is a unique identifier for referencing a system user identifier. For example, during the registration process of a user with the exchange platform 102, the exchange platform 120 can generate and / or provide the user key. In some examples, the user key can include an encapsulated system user identifier. For example, the user key can include an alphanumeric string formatted according to a key format established by the exchange platform (and / or one or more APIs thereof). For example, the key format can include a first portion of characters (e.g., the first six characters), which can be reserved as a partition for identifying an entity (e.g., a member, etc.) associated with the key. For example, for the user key, the partition can include a service provider partition 504 and / or a partner partition. The second portion of the characters can identify the system user identifier.

[0224] like Figure 5 As shown, keys 516, such as user and tool keys described herein, can be shared between the exchange platform 102 and the service provider platform 440. In addition, in some examples, references such as tool reference 520 and user reference 502 can be shared across entities. These identifiers and the mapping schemes described herein allow the exchange platform 102 to reference the service provider tool 518 without knowing the permanent credentials 514 (e.g., card number, etc.) of the service provider tool 518. As described herein, one or more of the keys 516 and / or references can be provided to the service provider platform 440 alone or in any combination. In some examples, each of the keys 516 and references can be provided to the service provider platform 440 in a redundant process that allows the service provider platform to verify that the communication is provided by the exchange platform 102 (e.g., an entity with access to a particular set of keys and references, etc.).

[0225] In some embodiments, the permanent credentials 514 of the service provider tool 518 include sensitive user and / or tool credentials, such as card numbers, account numbers, subscription numbers, and / or the like, which may put users, members, and / or intermediary entities at risk. When a user applies for, is authorized, and / or is otherwise able to open a new service provider tool 518, the service provider platform 440 can generate, access, and / or otherwise provide the user with permanent credentials 514. Traditionally, the user then uses the permanent credentials 514 to initiate a value exchange through the service provider tool. By doing so, each time the service provider tool 518 is used, the user is forced to expose sensitive credentials that are directly bound to the service provider tool 518. The key 516, reference, and identifier mapping schemes disclosed herein overcome these technical deficiencies.

[0226] In some examples, each identifier is interpretable to a computing platform, such as exchange platform 102 and / or service provider platform 440, but not to a user. To enable a user to select service provider tools 518 while maintaining the enhanced security features of the present disclosure, in some examples, Figure 5 The identifiers can be further enhanced with tool representations.

[0227] In some embodiments, the tool represents ( Figure 5 518) is a unique identifier of a permanent credential 514 used to represent a service provider tool 518 to a user without exposing the service provider tool 518. For example, the tool representation may include a sequence of numbers, alphanumerics, and / or any other characters or symbols that extrinsically represents the service provider tool 518 only to entities with prior knowledge of the service provider tool 518. The format and / or value of the tool representation may be based at least in part on the type of service provider and / or service provider tool 518. For example, in a financial value system, the tool representation may include a portion of the permanent credential 514 (e.g., the last four digits, etc.), such as a card number (e.g., debit card, credit card, etc.), a financial account number, and / or the like. As another example, in an information value system, the tool representation may include a portion of the permanent credential 514 (e.g., one or more numbers, alphanumeric characters, etc.), such as a subscription account, and / or the like. For example, the tool representation may include a derivative of the permanent credential 514 that may allow only entities with prior knowledge of the permanent credential 514 to identify the permanent credential 514 using the tool representation. As another example, a tool representation may include a tool nickname assigned by a user and subsequently recognized by the user.

[0228] In some embodiments, a tool representation may be provided to the exchange platform 102 (e.g., during the registration process) in place of the permanent credentials 514. In this manner, the exchange platform 102 may use the tool representation to represent the service provider tool 518 without needing to know the permanent credentials 514 from which the tool representation may be derived. For example, unlike conventional network-based exchange platforms, the exchange platform 102 may not require the permanent credentials 514 corresponding to the service provider tool 518 to implement the various computing tasks of the present disclosure. This, in turn, allows the exchange platform 102 to operate more flexibly while storing previously unrecorded contextual data, not only reducing operational computing costs, but also increasing the ability of users and the platform to defend against penetration attacks by malicious computing entities.

[0229] In some embodiments, the identifier mapping scheme is supplemented by a unique temporary key issued to the member platform to facilitate secure, real-time value exchange. For example, the exchange platform 102 can facilitate an additional layer of network and data security by implementing an exchange identifier 510 for representing aspects of value-based exchange. Some examples of the exchange identifier 510 may include a service provider-specific exchange identifier and / or a partner-specific exchange identifier. The service provider-specific exchange identifier may include a temporary, unique exchange identifier that temporarily represents a service provider tool 518 and a service provider platform 440. For example, the service provider-specific exchange identifier may be mapped to a system identifier 512 of the service provider tool 518. The partner-specific exchange identifier may include a temporary, unique exchange identifier that temporarily represents a service provider tool 518 and a partner platform. For example, the partner-specific exchange identifier may be mapped to a key 516 for the service provider tool 518, which may be used to identify the service provider platform 440. In some examples, this mapping may be defined by an exchange data object.

[0230] In some embodiments, an exchange data object is a data entity representing an authorized value exchange between one or more members associated with the exchange platform 102. In some examples, the exchange data object may include one or more identifiers and / or one or more exchange attributes. For example, one or more identifiers and / or one or more exchange attributes may be based at least in part on the type of the exchange data object. Exemplarily, an exchange may be represented in a member platform as a member exchange data object. Additionally or alternatively, an exchange may be independently represented by a system exchange data object in the exchange platform 102. In some examples, a member exchange data object and a system exchange data object may include one or more of the same one or more identifiers and / or one or more exchange attributes. Exemplarily, using some techniques of the present disclosure, the exchange platform 102 may issue one or more unique identifiers to the member platform, which may be used to authorize the value exchange.

[0231] In some embodiments, a system exchange data object is an internal representation of a value exchange intermediated using the exchange platform 102. In some examples, a system exchange data object may include one or more different identifiers and / or exchange attributes, depending on the role of the system exchange data object in the value-based exchange.

[0232] For example, the system exchange data object may include a service provider specific exchange data object corresponding to the service provider platform 440. The service provider specific exchange data object may include one or more identifiers, such as an exchange identifier 510, a system identifier 512 (e.g., a system user identifier and / or a system tool identifier), a UUEK 524, and / or the like. Additionally or alternatively, the service provider specific exchange data object may include one or more exchange attributes, such as an expiration date, a currency (e.g., for a financial value system, etc.), and / or the like.

[0233] Additionally or alternatively, the system exchange data object may include a partner-specific exchange data object corresponding to the partner platform. The partner-specific exchange data object may include one or more identifiers, such as an exchange identifier 510, one or more keys 516 (e.g., tool keys), UUEK 524, member tool references (e.g., partner-specific tool references, etc.), and / or the like. Additionally or alternatively, the partner-specific exchange data object may include one or more exchange attributes, such as an expiration date, a currency (e.g., for a financial value system, etc.), an instrument type, and / or the like.

[0234] In some embodiments, a member exchange data object is an external representation of a value exchange intermediated using exchange platform 102. A member exchange data object may include one or more identifiers, such as a member exchange identifier, a member tool identifier 508, a UUEK 524 from exchange platform 102, and / or the like.

[0235] In some embodiments, the exchange identifier 510 is a unique identifier for value exchange using the exchange platform 102. The exchange identifier 510 may include a number, an alphanumeric number, any character or symbol, or a sequence of any other characters or symbols that represents at least a user and / or a service provider tool 518. In some examples, the exchange identifier 510 may include a universal unique identifier (UUID), which may be mapped (e.g., through a series of identifiers, etc.) to a user, a service provider tool 518, and / or a member registered at the exchange platform 102. In some examples, the exchange identifier 510 may be generated using one or more UUID generators. For example, the exchange identifier 510 may include sixteen bytes of information generated according to one or more UUID formatting standards (e.g., UUID v4 and / or the like). Therefore, although the exchange identifier 510 may be used by the exchange platform 102 and / or a member platform for one or more functions, if there is no prior association between the exchange identifier 510 and one or more other identifiers, the same exchange identifier 510 will be useless to external parties. In addition to the previous identifier association, the exchange identifier 510 may also be associated with the exchange platform 102. Therefore, even if the exchange identifier 510 is recognized by the counterparty, the counterparty still needs to impersonate the exchange platform 102 in order to use the exchange identifier 510. In addition, before the exchange identifier 510 can be used adversely, the counterparty needs to update the settlement account to an account owned by the counterparty, in addition to many other tasks. Each of these tasks increases the amount of work required to overcome the enhanced security layer added by the exchange identifier 510. When paired with the temporary nature of the exchange identifier 510, these tasks may become prohibitively expensive.

[0236] In some examples, the exchange identifier 510 can be represented externally by a UUEK 524. Exemplarily, to facilitate credential-free exchange, the exchange platform 102 can issue one or more UUEKs 524 to one or more member platforms. As described herein, the UUEK 524 can eliminate the reliance on traditional permanent credentials 514 by identifying aspects of the value exchange conducted through previously mapped data entities.

[0237] In some embodiments, the UUEK 524 is an external representation of the exchange identifier 510 that can be issued (e.g., in place of the exchange identifier 510) to an external entity (e.g., a user, a partner platform, and / or a service provider platform, and / or the like) to initiate a value-based exchange using the exchange platform 102. To this end, the UUEK 524 can be generated by the exchange platform and issued to the external entity. Each UUEK 524 can include multiple values ​​(e.g., up to fifty characters and / or more, which can be case-sensitive or not) representing one or more aspects of the value-based exchange. For example, the multiple values ​​can indicate the exchange identifier 510, a partition (e.g., identifying a recipient of the UUEK 524, etc.), an identifier type, and / or one or more flags. Exemplarily, the UUEK 524 can include a partner-specific UUEK and / or a service provider-specific UUEK. As described herein, a partner-specific UUEK may be associated with a partner-specific exchange data object and may include a partner partition 506 , while a service provider-specific UUEK may be associated with a service provider-specific exchange data object and may include a service provider partition 504 .

[0238] Exemplarily, the UUEK 524 may be generated according to a key format. The key format may include a plurality of characters, including, for example, fifty or more characters, which may or may not be case sensitive. The first portion of the characters (e.g., the first six characters) may be reserved for identifying a partition of the recipient of the UUEK 524. For example, the partition may include a partner partition 506, a service provider partition 504, and / or any other member partition. For example, the UUEK 524 may be issued in response to a request from an authorized member (e.g., associated with a partner and / or a service provider).

[0239] Additionally or alternatively, at least one character of the key format (e.g., the seventh character) may identify the format of the UUEK 524. At least another character (e.g., the eighth character) may identify the type of the UUEK 524. In some examples, a second portion of characters may identify the exchange identifier 510 (e.g., a group of twenty-two characters following the eighth character). A third portion of characters may be reserved (e.g., a group of twenty characters following the first portion of characters). An example representation is provided below:

[0240] ppPpppFiGGGGGGGGGGGGGGGGGGGGGGrrrrrrrrrrrrrr

[0241] Where p represents a partition character, F represents a format character, i represents an identifier type character, G represents an exchange identifier 510, and r represents a reserved character. The key format allows for 9.8x1084 unique permutations, which is more than the number of atoms in the known observable universe. This enables the generation and distribution of new UUEKs 524 on demand without compromising the security of the underlying data to which the UUEK 524 may be mapped, such as identifiers of users, tools, and / or any other potentially sensitive information.

[0242] In some embodiments, the exchange platform 102 maintains multiple security code element groups 424 for one or more users, member platforms, service provider tools, and / or the like registered with the exchange platform 102. The security code element group 424 can be a data entity that defines the correlation between the security code, the user, and one or more of the member platform and / or service provider tools. The security code element group 424 may include a data object, a record, and / or any other data structure (e.g., a link node, etc.) that is configured to represent the association between the security code and the user, and in some embodiments, represents the association between the member platform, the service provider tool, or both. The security code element group 424 may, for example, include a security code reference, one or more system identifiers 512 (e.g., a user identifier), one or more member identifiers, one or more tool identifiers, and / or the like, and / or contextual pairing data. The contextual pairing data may include one or more pairing attributes, such as one or more timing attributes. For example, the timing attribute may indicate a configuration time (e.g., indicating the time to set the security code element group, etc.), an expiration time (e.g., the time when the security code must be reset, etc.), and / or the like. As described herein, the exchange platform 102 can utilize the security code element group 424 to identify a security code reference for a user to perform a security action on behalf of the user (e.g., allowing exchange using a UUEK, etc.) based at least in part on a comparison between the security code reference and a security code input provided by the user.

[0243] In some embodiments, a security code reference is a data entity that defines a security code for a record. A security code reference may include an internal representation of a security code for a user (eg, for exchange platform 102, etc.).

[0244] In some embodiments, a security code is a data entity that defines a sequence of characters used to verify a user in an interaction (e.g., a physical exchange, a virtual exchange, a registration, and / or the like). The security code may include a sequence of one or more dynamic lengths of different characters (e.g., six characters, eight characters, etc.) that may be set and / or provided to the user in advance by the user. The security code may be provided later by the user to verify the presence status of the interactive user (e.g., as described herein, by comparing the security code input with a security code reference). The one or more different characters may include any number of alphanumeric characters, emoticons, Chinese characters, winged fonts, and / or the like.

[0245] In some embodiments, the security code is a network-managed n-character PIN. As described herein, the security code can be managed as a service by a client device to (i) securely retrieve the UUEK, (ii) register the tool with the member platform, and / or (iii) enable or disable the use of the UUEK (and / or any other exchange credentials) prior to an exchange request. In this way, security codes can be deployed for any type of service provider tool by retrieving, registering, and / or enabling or disabling the corresponding UUEK. By managing security codes at the network level, members can benefit from faster exchanges because the possibility of invalid PINs being denied authorization is eliminated. For example, the UUEK can be disabled until a security code is received for enabling the UUEK. The exchange platform can prevent users from initiating exchanges before enabling the UUEK, thereby ensuring that all exchange authorization requests provided to the service provider have been pre-verified based on the security code. This effectively reduces network traffic between members in the exchange network, thereby reducing network congestion in traditional high-traffic communication systems.

[0246] In some embodiments, the security code corresponds to the user. For example, the security code can be pre-set and / or provided to the user by the user through interaction with the exchange platform 102. For example, the security code can be set by the user through interaction with the exchange network widget embedded in the member software application. This allows the security code to be set without directly interacting with the corresponding member platform (e.g., service provider platform 440) or sharing the security code. In some examples, the security code can be tool-specific or component-specific. For example, the corresponding security code can be configured to retrieve and / or enable the UUEK of a specific member platform and / or the service provider tool on a specific member platform. Additionally or alternatively, the corresponding security code can be configured to register the account of the member platform with the exchange network. Exemplarily, the exchange platform 102 can manage the use of the security code to implement one or more security actions using multiple security code tuples, each of which associates the security code with the corresponding user, member platform, and / or service provider tool.

[0247] V. Example System Operation

[0248] Figure 6 A process flow for facilitating network management of security codes for users according to one or more embodiments of the present disclosure is provided. The process flow describes a network process 600 for establishing network management security codes for performing secure interactions between users and third parties. Process 600 can be utilized to overcome various limitations of traditional exchange systems that rely on limited PIN mechanisms that are unable to adequately protect network interactions due to the limited complexity of traditional PINs and the party managing the PINs as described herein. Process 600 can be implemented by one or more computing devices, entities, and / or systems described herein. For example, through the various steps / operations of process 600, an exchange platform can utilize various communication and authentication technologies to overcome various limitations of traditional network exchange mechanisms by improving the management of security codes used to protect network-based interactions.

[0249] Figure 6 An example process 600 is shown for explanation purposes. Although the example process 600 depicts a particular order of steps / operations, the order may be changed without departing from the scope of the present disclosure. For example, some of the steps / operations described may be performed in parallel or in a different order without materially affecting the functionality of the process 600. In other examples, different components of an example device or system implementing the process 600 may perform functions substantially simultaneously or in a particular order.

[0250] In some embodiments, process 600 includes establishing a security code session at step / operation 602. For example, an exchange platform (e.g., its partner service, service provider, etc.) can establish a security code session. In some examples, process 602 can begin on a member application, such as a partner application (e.g., a partner website, a user application, etc.) and / or a service provider application, at which point the member platform can allow a user to manage (e.g., set, reset, remove, etc.) a network-managed security code. The member platform can enable management of the network-managed security code by initiating a security code session with the exchange platform.

[0251] For example, as described herein, a user may access a member application via a client device through a portal (e.g., a browser, a web application, and / or the like). The user's browser, web application, mobile application, etc. may obtain a platform connection widget from a content delivery network (CDN) and issue a communication session request to the member platform to establish a secure code session. In response to the request, the member platform may generate (e.g., using one or more exchange interfaces, etc.) a communication session request for the exchange platform (e.g., its member service). The communication session request may include an API request provided through a partner interface to initiate a secure code management widget for establishing a secure code session for the user.

[0252] In some embodiments, process 600 includes receiving a security code request at step / operation 604. For example, the exchange platform (e.g., its partner service, service provider, etc.) can receive the security code request through a communication session established with the member platform. For example, the security code management widget can provide a user prompt for information about the security code for network management. The user can respond to the prompt through the client device to generate a security code request and provide the security code request to the exchange platform. The security code request is generated and provided by a widget running in the member application. In this way, the member application can be used as an interface between the exchange platform and the user, and the member platform can never access the security code information provided by the user.

[0253] In some embodiments, a security code request is a data entity defined as a request for a user to set, reset and / or remove a security code. A security code request may be provided to an exchange platform from a member of an exchange network. A security code request may indicate a member user reference of a user, and in some examples, indicate a member tool reference for a user. Exemplarily, a security code request including only a member user reference may default to all service provider tools associated with a user, and may, for example, initiate a security code tuple group action (e.g., one or more settings, reset and / or removal operations, etc.) applicable to all service provider tools maintained by a corresponding member platform for a user. Additionally or alternatively, a security code request including a member user reference and a member tool reference may initiate a security code tuple group action (e.g., one or more settings, reset and / or removal operations, etc.) applicable to a specific service provider tool maintained by a corresponding member platform for a user. In addition to the reference, a security code request may include a code action attribute (indicating the required setting, reset and / or removal operations) and a security code input (indicating a new, modified or existing n-character PIN) to replace, modify or remove a user's security code.

[0254] In this manner, the security code widget can be configured to interact with a user to set, reset, and / or remove a specific security code, which allows the security code to be set, reset, and / or removed without directly interacting with the member platform. This improves network security by providing an access point (the switching platform) for modifying multiple different security codes for a single user across multiple different member platforms.

[0255] In some embodiments, process 600 includes verifying the user at step / operation 606. For example, the exchange platform (e.g., its partner service, service provider, etc.) can verify the user by comparing the user reference from the security code request with a plurality of pre-registered user identifiers. In the case where the user reference corresponds to the user identifier, the user can be verified. If the user is verified, process 600 can continue to step / operation 610 to perform a security code tuple action on behalf of the identified user. Otherwise, process 600 can continue to step / operation 612 to provide a security code response indicating a failure to verify the user.

[0256] In some embodiments, process 600 includes optionally verifying the service provider tool at step / operation 608. For example, if the security code request includes a tool reference, the exchange platform (e.g., its partner service, service provider, etc.) can verify the service provider tool. In the case where the tool reference corresponds to a pre-registered tool identifier, the tool can be verified. If the tool is verified, process 600 can continue to step / operation 610 to perform a security code tuple action on behalf of the identified user. Otherwise, process 600 can continue to step / operation 612 to provide a security code response indicating a failure to verify the tool.

[0257] In some embodiments, process 600 includes performing a security code element group action at step / operation 610. For example, the exchange platform (e.g., its partner service, service provider, etc.) may perform a security code element group action by setting a new security code for the user, resetting the security code for the user, and / or removing the security code for the user. To this end, the exchange platform may (i) generate a new security code element group including a user identifier and a new security code for the user, (ii) modify an existing security code element group corresponding to the user identifier to update the security code for the user, and / or (iii) remove an existing security code element group corresponding to the user.

[0258] In some embodiments, process 600 includes providing a security code response at step / operation 612. For example, an exchange platform (e.g., its partner services, service providers, etc.) may provide a security code response indicating completion and / or failure of a security code tuple action.

[0259] Fig. 7A -C provides a process flow for establishing a secure cross-entity relationship according to one or more embodiments of the present disclosure. The process flow illustrates one or more stages of a registration process 700 for registering a user and / or service provider tool with another member platform to facilitate a credential-free value exchange between the two member platforms. Fig. 7A700 is shown for explanation purposes. Although the example process 700 depicts a particular order of steps / operations, the order may be changed without departing from the scope of the present disclosure. For example, some of the steps / operations described may be performed in parallel or in a different order without materially affecting the functionality of the process 700. In other examples, different components of the example device or system implementing the process 700 may perform functions substantially simultaneously or in a particular order.

[0260] Various embodiments of process 700 address technical challenges associated with data security and efficiency of network-based exchanges in value exchanges between one or more computing entities. Traditional systems address these challenges using a registration mechanism that requires users to disclose sensitive and permanent credentials to a third-party registration service. These traditional registration services then verify the user's account ownership and provide the permanent credentials to the partner platform for storage and subsequent processing. By doing so, during the traditional registration process, user credentials are transmitted and exposed to multiple different entities, ultimately increasing the risk of exposure to malicious parties during and after network communications. Various embodiments of process 700 provide improved network communications, data encryption, and data management techniques to enable credential-free exchange registration capabilities, thereby reducing the data security risks posed by traditional processes.

[0261] One or more embodiments of process 700 may be implemented by one or more computing devices, entities, and / or systems described herein. For example, through the various steps / operations of process 700, by registering a service provider tool with a partner platform without accessing the permanent credentials of the service provider tool, the exchange platform 102 may utilize credential-free registration techniques to overcome various limitations of traditional registration mechanisms. By doing so, sensitive information behind the service provider tool used to participate in the value exchange is never exposed to potentially malicious parties or partner platforms that may be vulnerable to network-based attacks. For example, unlike traditional techniques, the exchange platform 102 never receives identifiable or actionable account information for the user, and the service provider who manages the account participates in the registration process rather than being disintermediated by a potentially unsafe registration service. This in turn eliminates the need to implement resource data governance standards on each device involved in the registration process, ultimately improving computing resource utilization while enhancing network and data security.

[0262] Fig. 7Ais a flow chart illustrating an example of a first stage of a registration process 700 for registering a user with an exchange platform without exposing permanent credentials associated with the user and / or service provider tools. The flow chart describes a communication technique that overcomes various limitations of traditional registration systems by circumventing the traditional system's reliance on sensitive and permanent credentials. The communication technique may be implemented by one or more computing devices, entities, and / or systems described herein, such as an exchange platform that establishes a secure communication session with a user through a partner application.

[0263] In some embodiments, process 700 includes establishing a registration session for the user and the partner platform at step / operation 702. For example, the registration process 700 may begin on a partner application (e.g., a partner website, a user application, etc.), at which point the partner platform may allow the user to register a partner account on the partner application using an exchange platform to facilitate access to service provider tools. The partner platform may enable registration of the user by initiating a registration session with the exchange platform.

[0264] For example, as described herein, a user may access a partner application through a client device through a portal (e.g., a browser, a web application, and / or the like). The user's browser, web application, mobile application, etc. may obtain a platform connection widget from a content delivery network (CDN) and issue a communication session request to the partner platform to establish a registration session. In response to the request, the partner platform may generate (e.g., using one or more exchange interfaces, etc.) a communication session request to the exchange platform (e.g., its partner service). The communication session request may include an API request provided through the partner interface to initiate a registration widget for establishing a registration session for the user.

[0265] In some embodiments, the communication session request includes one or more registration attributes, such as user data, user identifier, user hash, timestamp, device identifier, partner identifier, and / or the like. As described herein, some techniques of the present disclosure enable a computing entity to use an identifier to identify a service provider tool without including permanent credentials of the service provider tool in the communication session request. For example, the partner platform may be configured to obtain user data for a user (e.g., through user input to a user interface screen, pre-recorded data from a partner account, etc.), and provide the user data to the exchange platform to begin the registration process. In some examples, the partner platform (e.g., through one or more API calls of a partner interface, etc.) may provide the user data to the exchange platform (e.g., its partner service) along with the communication session request to initiate a widget session. In some examples, the user data may be encrypted, hashed, etc. before being transmitted to the exchange platform. In some examples, the user data may include one or more user attributes (as described herein).

[0266] In some embodiments, the exchange platform (e.g., its partner service) receives a communication session request using a partner interface to initiate a registration session on a user's client device. In some examples, the communication session request may include user data for the user. Additionally or alternatively, the registration initiation request may include one or more user attributes for the user. In some examples, the user attributes may be encrypted and / or hashed as described herein.

[0267] In some embodiments, process 700 includes setting user and partner data at step / operation 704. For example, the exchange platform (e.g., its connection service, partner service, etc.) can identify and / or generate user and / or partner data from data provided in the communication session request. In some examples, the user data can include one or more user attributes. In some examples, the user data can include one or more encrypted and / or hashed user attributes. In some examples, the partner data can include a shared identifier between the exchange platform and the partner platform (such as the partner partition described herein).

[0268] In some embodiments, process 700 includes generating a session identifier for a registration session at step / operation 706. For example, an exchange platform (e.g., its connection service, partner service, etc.) may generate a session identifier for a communication session between a partner platform and an exchange platform to track communications exchanged during a registration session. For example, a session identifier may include a unique number, string, and / or the like for authenticating messages exchanged during a registration session. The exchange platform may establish a registration session using a connection service and / or a partner service. For example, in response to a registration initiation request, a partner service may call another service, such as a connection service, to establish a communication session that a client-side widget may use to provide an interface between a user and a partner service to complete user registration. The connection service may generate a session identifier and return the session identifier to the partner service. The partner service may return the session identifier to the partner platform, which may use the session identifier to initiate a client-side widget through an instance of a partner application on a client device. Once the partner application receives the session identifier, the partner application may launch (e.g., execute, initiate, etc.) a client-side widget. The user may interact with the widget to complete the registration process 700.

[0269] In some embodiments, process 700 includes determining and providing a member list for the user at step / operation 708. The member list can be a list of service providers. For example, the exchange platform (e.g., its connection services, partner services, etc.) can determine a list of service providers for the user from a network of service providers related to the exchange platform (e.g., registered with it, etc.). In some examples, the list of service providers can include each service provider platform related to the exchange platform. Additionally or alternatively, the list of service providers can include a subset of the relevant service provider platforms tailored for the user.

[0270] For example, the exchange platform may determine one or more service provider platforms based at least in part on the user attributes of the registration session, and customize the service provider list for the one or more service provider platforms. As described herein, exemplary, the exchange platform may include multiple system user data objects and / or system tool data objects. In some examples, the exchange platform may identify one or more system user data objects corresponding to the user based on the user attributes. In some examples, each system user data object may identify a service provider platform associated with the user. In this way, the exchange platform may determine one or more service providers associated with the user based on one or more system user data objects.

[0271] Additionally or alternatively, the exchange platform (e.g., one or more of its service provider services) may provide a presence request for user presence status data from each service provider platform in the member platform network (e.g., through a service provider interface). The user presence request may include one or more user attributes for the user (e.g., encrypted attributes, hashed attributes, etc.), which the service provider platform may utilize to determine whether the user has a tool of the service provider platform. In response to the request, the exchange platform (e.g., one or more of its service provider services) may receive presence status data representing presence tools on each service provider platform from the one or more service provider platforms. The exchange platform (e.g., its partner service) may determine one or more service providers based at least in part on the presence status data.

[0272] In some examples, the exchange platform (e.g., its connection service, partner service, etc.) may use a partner interface and a registration user interface provided via a partner application to initiate presentation of a pre-registration screen based at least in part on one or more service providers. For example, a client device may be configured to access a partner application hosted by the partner platform. The registration user interface may be presented to the user on the client device via a widget within the partner application. The widget may be defined internally by the partner or provided by the exchange platform. The pre-registration screen may present a plurality of selectable icons indicating a list of service providers.

[0273] Next, as reference Figure 7B As described in further detail, the registration process 700 may proceed to a second stage, wherein a tool identifier corresponding to the user is identified through interaction between the exchange platform, the user, and the service provider platform.

[0274] Reference now Figure 7B , Figure 7B is a flow chart illustrating an example of a second stage of a registration process 700 for registering a service provider tool with a partner platform without exposing permanent credentials associated with the user and / or the service provider tool. The flow chart describes communication techniques that overcome various limitations of conventional registration systems by circumventing the conventional systems' reliance on permanent credentials (such as card numbers and / or the like) provided by the user. The communication techniques may be implemented by one or more computing devices, entities, and / or systems (e.g., an exchange platform) described herein to establish a connection between a user, a partner platform, and a service provider tool.

[0275] In some embodiments, process 700 includes determining and providing a service provider tool list for the user at step / operation 710. The service provider tool list can be determined based at least in part on selecting a service provider from a pre-registration screen. For example, in some examples, the exchange platform (e.g., its connection service, partner service, etc.) can use a partner interface to receive pre-selection data that indicates a particular service provider is selected from one or more service providers presented on the pre-registration screen. For example, a widget can receive pre-selection data from a partner application and provide a tool registration request to the exchange platform (e.g., its connection service, partner service, etc.) (e.g., via a partner interface). The tool registration request can include a session identifier and / or a service provider identifier indicating a selected service provider.

[0276] In response to the request, the exchange platform (e.g., its connection service, partner service, etc.) may receive service provider-tool data based at least in part on the pre-selected data. The service provider-tool data may indicate one or more service provider tools for the user facilitated by the selected service provider platform. For example, the service provider-tool data may include one or more system tool identifiers and / or corresponding tool representations from one or more tool data objects corresponding to the service provider and the user. For example, each tool data object may include a system user identifier corresponding to the user.

[0277] Additionally or alternatively, the exchange platform (e.g., one or more service provider services thereof) may provide a tool request for service provider-tool data from a selected service provider platform (e.g., via a service provider interface). For example, the tool request may include a user reference corresponding to a member user identifier of the service provider platform. In response to the request, the service provider platform may identify one or more member tool data objects including the member user identifier, identify one or more tool references corresponding to the one or more member tool data objects, and provide service provider-tool data indicating the one or more tool references and / or one or more corresponding tool representations to the exchange platform.

[0278] The exchange platform (e.g., its connection service, partner service, etc.) may initiate presentation of a tool registration screen via a user's client device based at least in part on the service provider-tool data using a partner interface and via a registration user interface. The tool registration screen may be defined internally by a partner and / or provided by the exchange platform. For example, the tool registration screen may indicate one or more service provider tools associated with the user and a selected service provider. Exemplarily, the tool registration screen may indicate a corresponding tool representation for each of the one or more service provider tools. In some examples, such as when the user is only associated with a single service provider tool, the tool registration screen may include a confirmation prompt to confirm the user's intent to register the service provider tool.

[0279] In some embodiments, process 700 includes receiving a secure interaction request at step / operation 712. For example, the exchange platform may receive a secure interaction request from a member platform using a member interface. In some embodiments, a secure interaction request is a data entity that defines a request to perform a secure interaction using a security code input. The secure interaction request may be provided to the exchange platform from a member of the exchange network. The secure interaction request may indicate (i) a user, a member platform, and / or a service provider tool, and (ii) a security code input for the user. In some examples, the secure interaction request may indicate a service provider tool selected by the user from a service provider tool list.

[0280] In some examples, the secure interaction request may indicate one or more contextual security attributes. The one or more contextual security attributes may include one or more timing attributes. For example, the one or more timing attributes may indicate a provision time (e.g., indicating a time to send a secure interaction request, etc.), a request time (e.g., a request time for performing a secure interaction, etc.), and / or the like.

[0281] The secure interaction request can be received from the member platform. For example, a user can initiate a secure interaction request through a member application hosted by a member platform representing a member of the exchange network. In some examples, in response to a selection input indicating a service provider tool, a UUEK for a service provider tool, and / or the like, a secure interaction request can be generated and / or provided. As an example, a user can select a tool representation, a UUEK representation, and / or the like (e.g., through a partner application associated with a partner platform, a service provider application associated with a service provider platform, etc.) for registering a service provider tool, authorizing a value-based exchange, and / or the like. In some examples, a secure interaction request can be automatically initiated when a user and / or selected tool, UUEK, and / or the like are associated with a security code. For example, in response to a selection, a member platform (e.g., through a corresponding member application) can prompt a user to enter a security code. The user can enter a security code input to provide a secure interaction request.

[0282] In some examples, the exchange platform may receive a secure interaction request from a client-side widget using a partner interface. The request may include selection data and / or a security code input. The selection data may indicate a selection of a service provider tool from a registration user interface. For example, the selection data may indicate a tool representation (e.g., an account nickname, etc.) for the selected service provider tool. In some examples, the selection data may include at least one of a tool type, a currency type (e.g., in a financial value system), and / or a tool identifier (e.g., a tool representation, etc.) corresponding to the selection.

[0283] In some embodiments, process 700 includes verifying the security code input of the security interaction request at step / operation 714. In some examples, the exchange platform (e.g., its connection service, partner service, etc.) can compare the security code input with the security code tuple corresponding to the security interaction request to verify the user's presence. The exchange platform can generate a verification event indicating that the verification of the security code input is passed and / or the verification is invalid. In the case of verification, process 700 can advance to step / operation 718, wherein the exchange platform provides a valid security interaction response. In the case of invalid verification, the exchange platform can advance to step / operation 716, wherein the exchange platform provides an invalid security interaction response, and then returns to step / operation 712 to receive another security interaction request.

[0284] In some embodiments, a verification event is a data entity that defines a verification of a security code input for a user. The verification event may include a security event that may indicate that the verification between the security code input and the security code reference has passed. Additionally or alternatively, the verification event may include an unsafe event that may indicate a failed verification between the security code input and the security code reference. For example, a security event may indicate a determination that the security code input matches the corresponding security code reference. In some examples, an unsafe event may indicate a determination that the security code input does not match the corresponding security code reference. In some examples, in response to a determination that the security code input matches the corresponding security code reference, the exchange platform may generate a security event. Additionally or alternatively, in response to a determination that the security code input does not match the corresponding security code reference, the exchange platform may generate an unsafe event. In some examples, a security event may be associated with a security time period, and the exchange platform may generate an unsafe event in response to determining that the security time period has expired.

[0285] In some embodiments, the verification event is stored in association with a secure data entity (such as a UUEK, a service provider tool, and / or a user). For example, the verification event may be stored in an exchange data object corresponding to the UUEK, a system tool data object corresponding to the service provider tool, a system user data object corresponding to the user, and / or the like. Additionally or alternatively, the verification event may be stored in association with a secure code element group. For example, a secure event may be stored in response to a verification user passing, and an unsafe event may be stored in response to a verification user failing.

[0286] In some embodiments, the verification event includes contextual verification data. For example, the contextual verification data may indicate verification timing. The verification timing may include a timestamp corresponding to the sending, receiving, creating, and / or judging of the verification request. For example, the contextual verification data may include a verification timestamp indicating the time when the exchange platform determines that the security code input and the security code reference match or do not match. In some examples, the contextual verification data may indicate a secure time period. The secure time period may indicate a subsequent timestamp, duration, and / or the like that may be secure in response to a security event by a UUEK, a service provider tool, and / or the like.

[0287] In some embodiments, process 700 includes providing a valid secure interaction response to the partner platform at step / operation 718. For example, the exchange platform may provide a valid secure interaction response to the partner platform. The secure interaction response may define a response to the secure interaction request. In some embodiments, the secure interaction response is provided from the exchange platform to the member providing the secure interaction request. The secure interaction response may indicate a verification event. The valid secure interaction response may indicate an event of successful verification.

[0288] In some embodiments, process 700 includes providing a registration request to a service provider platform corresponding to the service provider tool in response to the network-level authentication of the user at step / operation 720. For example, an exchange platform (e.g., its service provider service, etc.) may provide a registration request to a service provider platform corresponding to the selected service provider tool using a service provider interface. The registration request may include service provider registration data indicating one or more user identifiers of the user and / or one or more tool identifiers for the service provider tool. In response to the registration request, the service provider platform may authenticate the service provider tool using the one or more identifiers.

[0289] For example, the service provider registration data may include one or more identifiers for referencing a service provider tool in communications between an exchange platform, a service provider platform, and / or a partner platform without using permanent credentials for the service provider tool (e.g., a card number, an account number, etc.). For example, the one or more identifiers may include various combinations of user identifiers and / or tool identifiers to authenticate the user and / or device through one or more redundant checks. For example, a user identifier for a user may include a user reference for the service provider platform and / or a user key from the exchange platform corresponding to the user reference. As another example, a tool identifier for a service provider tool may include a tool reference for the service provider platform and / or a tool key from the exchange platform corresponding to the tool reference.

[0290] The service provider registration data may include any combination of references, keys, and / or identifiers as described herein. In one example, the service provider registration data may include one of a tool reference, a tool key, a user reference, and / or a user key. Additionally or alternatively, the service provider registration data may include a combination of a tool reference, a tool key, a user reference, and a user key corresponding to built-in redundancy. In some examples, the combination of identifiers may be specified by an interface call. The combination may be service provider specific and / or dynamically changed according to a communication scheme. Thus, a specific combination of identifiers provided in a registration request may be used as an additional verification check to ensure that the registration request is received from a relevant platform (e.g., an exchange platform).

[0291] The service provider may compare the identifier from the registration request with one or more member data objects (eg, member tool data object, member user data object, etc.) to identify the service provider tool corresponding to the registration request without exposing the service provider tool's permanent credentials.

[0292] Reference now Figure 7C , Figure 7Cis a flow chart illustrating an example of a third stage of a registration process 700 for issuing a UUEK to facilitate credential-free value exchange. The flow chart describes communication techniques that overcome various limitations of conventional registration systems by circumventing the conventional system's reliance on a tool reference (such as a card number and / or the like) provided by a user. The communication techniques may be implemented by one or more computing devices, entities, and / or systems (e.g., an exchange platform) described herein to establish a user tool record for registering a user with an exchange platform.

[0293] In some embodiments, process 700 includes receiving a registration response from the service provider platform at step / operation 722. For example, the exchange platform may receive a registration response indicating a success or failure of the registration.

[0294] In some embodiments, process 700 includes determining whether the service provider tool is successfully registered at step / operation 724. In the event that the service provider tool is successfully registered, process 700 may proceed to step / operation 728. Otherwise, the process may proceed to step / operation 726, where the exchange platform provides a failure response.

[0295] In some embodiments, process 700 includes generating a UUEK in response to a successful registration at step / operation 728. For example, the exchange platform may generate the UUEK in response to verification of a registered user and / or tool by an exchange network (e.g., using a security code) and / or a service provider platform. Exemplarily, the exchange platform may generate a UUEK corresponding to a user, a service provider tool, and a partner platform. As described herein, the exchange platform may store the UUEK in a partner-specific exchange data object that associates the UUEK with an exchange identifier, a tool key, and a partner-specific tool reference.

[0296] In some embodiments, process 700 includes providing the UUEK to the partner platform at step / operation 730. For example, the exchange platform may provide data indicating the UUEK to the partner platform using a partner interface. In some examples, the partner platform may provide the UUEK and / or a representation thereof to the user (e.g., for storage in a virtual wallet, etc.). Exemplarily, the UUEK may be represented in one or more different forms, such as a machine-readable optical image (e.g., a barcode, a quick response code, etc.), a keyword, a virtual widget, and / or the like.

[0297] Fig. 8A-B provides a process flow for facilitating secure interactions without credentials according to one or more embodiments of the present disclosure. The process flow describes a network process 800 for establishing a network-managed UUEK to securely verify the presence of a user for value exchange. As described herein, process 800 can be utilized to overcome various limitations of traditional exchange systems that expose sensitive and permanent credentials to multiple third parties and rely on limited PIN mechanisms that fail to adequately protect value-based exchanges. Process 800 can be implemented by one or more computing devices, entities, and / or systems described herein. For example, through the various steps / operations of process 800, an exchange platform can utilize various communication and verification technologies to overcome various limitations of traditional exchange mechanisms by improving the management of security codes used to protect network-based exchanges.

[0298] Fig. 8A -B shows an example process 800 for explanation purposes. Although the example process 800 depicts a particular order of steps / operations, the order may be changed without departing from the scope of the present disclosure. For example, some of the steps / operations described may be performed in parallel or in a different order without materially affecting the functionality of the process 800. In other examples, different components of the example device or system implementing the process 800 may perform functions substantially simultaneously or in a particular order.

[0299] In some examples, process 800 begins after a registration and / or security code process (such as process 600), where a user can manage a network-managed security code to facilitate secure, credential-free interactions. For example, as described herein, one or more registration processes may be pre-performed between one or more member platforms and / or exchange platforms to register multiple service provider tools with the exchange platform. Thereafter, the exchange platform may generate a UUEK and issue it to the registered service provider platform to issue a value-based exchange using the registered service provider tool without reference to the permanent credentials of the service provider tool. Additionally or alternatively, a registration process may be performed to register the registered service provider tool maintained by the service provider platform to the partner platform. In some examples, the exchange platform may facilitate the registration process and, in response to a successful registration, generate and issue a UUEK to the partner platform to initiate future value-based exchanges. In some examples, once registered, the user may establish a network-managed security code with the exchange platform to facilitate the allocation of UUEKs and / or enable previously issued UUEKs.

[0300] Thus, using some of the communication techniques of the present disclosure, a member platform can enhance the security of a UUEK by establishing one or more security codes for a user. For example, by replacing the permanent credentials of a service provider tool with a UUEK, the communication techniques of the present disclosure can enforce standards on behalf of members by issuing new UUEKs and / or enabling or disabling previously issued UUEKs, thereby managing access to service provider tools. In some examples, this includes enforcing the use of security codes to verify the user's presence for secure interactions. For example, using some of the techniques of the present disclosure, an exchange platform can act as a ruling engine to verify the user's presence before issuing a UUEK and / or verify a previously issued UUEK on behalf of a member platform. According to the steps / operations of process 800, an exchange platform can enforce security codes for users, service provider tools, and / or their UUEKs, which can be used to enforce member policies on behalf of member platforms without the continued involvement of member platforms. In this way, network-managed security codes can be established that extend the security provided by UUEKs in credential-free exchanges.

[0301] refer to Fig. 8A In some embodiments, process 800 includes receiving a secure interaction request at step / operation 802. For example, an exchange platform (e.g., its partner service, service provider, etc.) may receive a secure interaction request from a member platform. As described herein, the secure interaction request may include a security code input, a user identifier, and / or a tool identifier.

[0302] In some embodiments, process 800 includes identifying a security symbol set at step / operation 804. For example, the exchange platform (e.g., its authentication service, etc.) can identify a security symbol set corresponding to the user identifier and / or the tool identifier.

[0303] In some embodiments, process 800 includes determining whether the security code input is valid at step / operation 806. For example, the exchange platform (e.g., its verification service, etc.) can verify the security code input based at least in part on a comparison between the security code input and a corresponding security code reference. Exemplarily, the user identifier and / or tool identifier can be associated with a security code element group that includes the security code reference and the corresponding user and / or tool identifier. For example, as described herein with reference to Figure 6 As described in AC, the security code element group may be previously generated in response to a security code request from a member platform.

[0304] In some embodiments, the security code reference includes an n-character sequence of one or more different characters. The one or more different characters may include one or more alphanumeric characters and / or any other characters. The security code input may include a second n-character sequence of one or more different characters. If the security code input matches (e.g., strictly matches, partially matches, etc.) the character sequence of the security code reference, the input may be verified.

[0305] If the security code input is valid, process 800 can proceed to step / operation 808, where a security event is recorded. If the security code input is invalid (e.g., one or more characters do not match the security code reference, etc.), process 800 can proceed to step / operation 810, where an unsafe event is recorded.

[0306] In some embodiments, process 800 includes storing the authentication event at step / operation 812. For example, the exchange platform (e.g., its authentication service) may store data indicating the authentication event with reference to a user, tool, and / or security symbol set for the user and / or service provider tool.

[0307] In some embodiments, a verification event is a data entity that defines the verification of a security code input for a user. A verification event may include a security event that may indicate that the verification between the security code input and the security code reference has passed. Additionally or alternatively, the verification event may include an unsafe event that may indicate a failed verification between the security code input and the security code reference. For example, a security event may indicate a determination that the security code input matches the corresponding security code reference. In some examples, an unsafe event may indicate a determination that the security code input does not match the corresponding security code reference. In some examples, in response to a determination that the security code input matches the corresponding security code reference, a switching platform may generate a security event. Additionally or alternatively, in response to a determination that the security code input does not match the corresponding security code reference, a switching platform may generate an unsafe event. In some examples, a security event may be associated with a security time period, and the switching platform may generate an unsafe event in response to determining that the security time period has expired.

[0308] In some embodiments, the verification event is stored in association with a secure data entity (such as a UUEK, a service provider tool, and / or a user). For example, the verification event may be stored in an exchange data object corresponding to the UUEK, a system tool data object corresponding to the service provider tool, a system user data object corresponding to the user, and / or the like. Additionally or alternatively, the verification event may be stored in association with a secure code element group. For example, a secure event may be stored in response to a user verification pass, and an unsafe event may be stored in response to a user verification failure.

[0309] In some embodiments, the verification event includes contextual verification data. For example, the contextual verification data may indicate verification timing. The verification timing may include a timestamp corresponding to the sending, receiving, creating, and / or determining of the verification request. For example, the contextual verification data may include a verification timestamp indicating the time when the exchange platform determines that the security code input and the security code reference match or do not match. In some examples, the contextual verification data may indicate a security time period. The security time period may indicate a subsequent timestamp, duration, and / or the like that the UUEK, service provider tools, and / or the like may be secure in response to the security event.

[0310] In some embodiments, if the security code is valid, process 800 includes storing a security event at step / operation 808. For example, the exchange platform may store a security event for the user in response to verifying the UUEK. In some examples, the exchange platform may generate a security event in response to determining that the security code input matches the corresponding security code reference. For example, in response to verifying the security code input, the security event may be stored.

[0311] In some embodiments, in the event that the security code is invalid, process 800 includes storing an unsafe event at step / operation 810. For example, the exchange platform may store an unsafe event for the user in response to a failure to authenticate the user. In some examples, the exchange platform may generate an unsafe event in response to a determination that the security code input does not match the corresponding security code reference. For example, the unsafe event may be stored in response to a failure to authenticate the user. In some examples, the security event may be associated with a security time period, and the exchange platform may generate an unsafe event in response to a determination that the security time period has expired.

[0312] In some embodiments, process 800 includes providing a secure interaction response at step / operation 814. For example, an exchange platform (e.g., its service provider service, etc.) may provide a secure interaction response indicating a verification event to a member platform (and / or client device) associated with a secure interaction request. In some embodiments, the secure interaction response defines a response to the secure interaction request. In some embodiments, the secure interaction response is provided from the exchange platform to the member providing the secure interaction request. The secure interaction response may indicate a verification event. In some examples, the secure interaction response may include a UUEK and / or service provider tool for the user.

[0313] In some examples, the security code input may correspond to a previously established UUEK for the user. For example, as described herein, one or more registration processes may be pre-performed between one or more service provider platforms and an exchange platform to register multiple service provider tools with the exchange platform. Thereafter, the exchange platform may generate a UUEK and publish it to the registered service provider platform to initiate a value-based exchange using the registered service provider tool without reference to the permanent credentials of the service provider tool. Additionally or alternatively, a registration process may be performed to register the registered service provider tool maintained by the service provider platform to the partner platform. In some examples, the exchange platform may facilitate a security code registration process for the issued UUEK to generate a security code tuple group. In the case of generating a security code tuple group for the UUEK, the exchange platform may perform one or more steps / operations of process 800 on behalf of the member platform to enable and / or disable the UUEK. In this way, a security code for network management that actively prevents the UUEK from being used for invalid exchanges may be provided.

[0314] In some embodiments, the interaction request may include an enablement request for enabling a previously issued UUEK for the user. In this case, the secure interaction request may indicate the UUEK and a security code input for the UUEK and / or one or more contextual security attributes, such as a configuration time (e.g., indicating a time to send the secure interaction request, etc.), a request time (e.g., a request time to allow use of the UUEK, etc.), and / or the like.

[0315] In some examples, in response to a selection input indicating a disabled UUEK, a secure interaction request may be generated and / or provided. For example, a user may select a UUEK (e.g., via a partner application associated with a partner platform, a service provider application associated with a service provider platform, etc.) to authorize a value-based exchange. In some examples, a secure interaction request may be automatically initiated where the selected UUEK is a disabled UUEK. For example, in response to the selection, a member platform (e.g., via a corresponding member application) may prompt the user to enter a security code. The user may enter a security code input to provide a secure interaction request.

[0316] In some embodiments, the UUEK representation is a visual representation of the UUEK. The UUEK representation may include a digital representation of the UUEK that is visible to the user. For example, the UUEK representation may be represented in one or more different forms, such as a machine-readable optical image (e.g., a barcode, a quick response code, etc.), a keyword, a virtual widget, and / or the like. In some examples, the UUEK representation may include a scannable representation of the UUEK (e.g., a barcode, a QR code, a non-fungible token, a near field communication sequence, etc.). The scannable representation may be saved to a member account of the member platform to enable the user to perform a value-based exchange using a service provider tool without having to refer to the permanent credentials of the service provider tool. For example, the UUEK representation may be scanned by a barcode scanner and / or the like to read the UUEK and initiate a value-based exchange with the UUEK.

[0317] In some embodiments, the disabled UUEK representation is a UUEK representation for a disabled UUEK. The disabled UUEK representation may include a status indicator indicating the disabled state of the UUEK and / or one or more other indicators. In some examples, the disabled UUEK representation may include an unreadable UUEK representation. For example, the unreadable UUEK representation may include a gray, blocked, partially covered, and / or similar scannable representation that prevents the scannable representation from being read.

[0318] In some examples, the secure interaction response may initiate the activation of the UUEK. For example, the enabled UUEK may be associated with an enabled UUEK representation. The enabled UUEK representation may include a status indicator indicating the UUEK activation status and / or one or more other indicators. In some examples, the enabled UUEK representation may include a readable UUEK representation.

[0319] Go to Figure 8B In response to the security event, process 800 includes receiving an exchange request with a UUEK (e.g., issued through a secure interaction, etc.) at step / operation 816. For example, an exchange platform may receive an exchange request for performing a value-based exchange. The exchange request may indicate the UUEK and / or one or more exchange attributes. In some examples, the exchange request may be contingent upon a previous secure interaction. For example, the UUEK may be issued through a secure interaction and / or enabled through a secure interaction. In this manner, the request is filtered by the exchange platform before it is transmitted to the exchange platform, and the request is filtered again by the exchange platform before it is transmitted to another member platform. In this manner, exchange requests may be minimized to pre-verified exchanges, which may reduce network congestion between multiple parties in a high-traffic exchange network.

[0320] The exchange attributes may indicate one or more characteristics of the requested exchange. For example, the one or more exchange attributes may include at least one exchange attribute indicating an exchange value, such as a monetary value, a reward value, and / or the like.

[0321] In some embodiments, process 800 includes identifying an exchange data object indicating an exchange identifier at step / operation 818. For example, an exchange platform (e.g., its partner service, service provider service, etc.) may use some of the techniques described herein to identify an exchange identifier for a UUEK. As described herein, an exchange identifier may be associated with an exchange data object corresponding to a UUEK. An exchange data object (and / or one or more identifiers thereof) may be associated with a security code element group and / or one or more verification events for a UUEK.

[0322] In some embodiments, process 800 includes determining at step / operation 820 whether the exchange request needs verification. For example, an exchange platform (e.g., its verification service, etc.) may determine whether the exchange request needs verification. The exchange platform may determine whether verification is required based at least in part on a member policy and / or one or more exchange attributes for the exchange request. Exemplary, a member platform may be associated with a member policy that defines one or more verification requirements for a service provider tool. In some examples, an exchange request may indicate one or more exchange attributes. One or more verification requirements may correspond to one or more exchange attributes. An exchange platform (e.g., its verification service, etc.) may compare one or more exchange attributes with one or more verification requirements to determine whether the UUEK of the exchange request needs verification.

[0323] As an example, one or more exchange attributes may indicate an exchange value, and one or more verification requirements may define an exchange value threshold where a corresponding security event is required for the service provider tool. When the exchange value of the exchange request meets the exchange value threshold, in this case, the exchange request in the above case may need to be verified.

[0324] As another example, the one or more verification requirements may define one or more objects (e.g., object identifiers, object attributes, etc.) for which the service provider tool requires a corresponding security event. When the exchange request includes one or more exchange attributes that identify at least one of the one or more objects, in this case, the exchange request in the above case may need to be verified.

[0325] In some embodiments, process 800 includes determining whether the UUEK is enabled at step / operation 822. For example, the exchange platform (e.g., its partner service, service provider service, etc.) may determine that the UUEK is enabled (or disabled) based at least in part on member policies, exchange requests, and / or one or more verification events associated with the UUEK (e.g., secure events, unsecure events, etc.). Exemplarily, the exchange platform may determine whether the UUEK is enabled based at least in part on the presence status of secure events, unsecure events, and / or one or more timing attributes thereof.

[0326] In some embodiments, the exchange platform determines that the UUEK is enabled based at least in part on the latest time attribute for multiple verification events. For example, in the case where the security event is later than any unsafe event, the UUEK can be enabled. Additionally or alternatively, the exchange platform determines that the UUEK is enabled based at least in part on a comparison between a security time period and a time for the exchange request (e.g., a receipt time, a response time, a processing time, etc.). For example, in the case where a time such as a receipt time of the exchange request is within an enabling time period, the UUEK can be enabled.

[0327] In some embodiments, process 800 includes providing an exchange authorization request at step / operation 824. For example, an exchange platform (e.g., its service provider service, etc.) may provide an exchange authorization request to a member platform. In some examples, the exchange authorization request may be provided to the service provider platform using a service provider interface. The exchange authorization request may indicate a tool identifier and / or a security event. In some examples, the exchange authorization request may indicate an enabled time period for the security event and / or a time of receipt of the exchange request.

[0328] For example, an exchange platform (e.g., its service provider's service) may request exchange permission from a service provider platform of a service provider tool associated with a UUEK. In some examples, an exchange platform (e.g., its partner service) may identify a member platform based at least in part on a UUEK (e.g., its entity partition). Additionally or alternatively, an exchange platform (e.g., its service provider service) may identify a service provider tool based at least in part on a UUEK (e.g., its exchange identifier).

[0329] The exchange platform (e.g., its service provider service) may provide an exchange authorization request to the member platform using the service provider interface. The exchange authorization request may indicate at least one of one or more request attributes, a tool identifier for a service provider tool, and / or a security event. Exemplarily, the exchange platform may generate the exchange authorization request based at least in part on a system tool data object identified from one or more aspects of the UUEK. The exchange authorization request may include a tool key and / or a tool reference from the system tool data object.

[0330] In some examples, the exchange authorization request may indicate a user identifier associated with the service provider tool. For example, the exchange platform may generate the exchange authorization request based at least in part on a system user data object identified from one or more aspects of the UUEK. In some examples, the system user data object may be identified at least in part based on a user identifier of the exchange data object (e.g., a system user identifier). Additionally or alternatively, the system user data object may be identified at least in part based on a user identifier of a system tool data object (e.g., a system user identifier). In some examples, the exchange authorization request may include a user key and / or a user reference from the system user data object.

[0331] Additionally or alternatively, the exchange authorization request may indicate an exchange identifier. Exemplarily, the exchange platform may generate an exchange identifier for representing a value-based exchange and provide the exchange identifier to the member platform.

[0332] In some embodiments, process 800 includes receiving an exchange authorization response at step / operation 826. For example, an exchange platform (e.g., its partner service, service provider service, etc.) may receive an exchange authorization response indicating at least one of an exchange approval and / or an exchange rejection. In some examples, the exchange authorization response may be received from a service provider platform using a service provider interface.

[0333] In some embodiments, the exchange authorization response is based at least in part on the security event.For example, the exchange authorization response can be based at least in part on the security event, the time of receipt of the exchange request, member policies, and / or the like.

[0334] In some embodiments, the exchange platform (e.g., a service of a service provider) may use a service provider interface to receive an exchange authorization response indicating at least one of a transaction approval and / or a transaction rejection. In some embodiments, the exchange authorization response is based at least in part on a comparison between the transaction value and the asset availability of the service provider tool. For example, in response to receiving the exchange authorization request, the member platform may be configured to compare the transaction value with the asset availability of the identified service provider tool. If the asset availability exceeds the transaction value, the value-based exchange may be authorized (e.g., resulting in transaction approval, etc.), otherwise the exchange may be rejected (e.g., resulting in transaction rejection).

[0335] In some examples, the exchange authorization response may indicate one or more response attributes. The response attributes may include one or more error codes and / or the like that characterize the exchange authorization response.

[0336] The exchange platform may generate an exchange record for a value-based exchange based at least in part on the exchange authorization request and / or the exchange authorization response. In some examples, the exchange record may indicate an exchange identifier, one or more exchange attributes, one or more response attributes, an exchange authorization response, one or more instrument and / or user identifiers, and / or any other data related to the value-based exchange. In some examples, the exchange platform may store the exchange record in a platform database in association with the one or more instrument and / or user identifiers.

[0337] In some embodiments, process 800 includes providing an exchange response at step / operation 828. For example, the exchange platform (e.g., its partner service, service provider service, etc.) can provide the exchange response based at least in part on the exchange authorization response. In some examples, the exchange platform can provide the exchange response to the partner platform using a partner interface. The exchange response can indicate an exchange approval or an exchange rejection.

[0338] The exchange response may be based at least in part on the exchange authorization response. For example, the exchange response may indicate a transaction approval and / or a transaction rejection. In some examples, the exchange response may indicate a replacement UUEK (if generated), one or more exchange attributes, an exchange identifier, and / or one or more response attributes. In some examples, the member platform may be configured to replace the UUEK with a replacement UUEK. For example, the exchange response may be provided to the partner platform. The partner platform may receive the exchange response and replace the UUEK with a replacement UUEK.

[0339] Having thus described various operations, processes, methods, functions, and / or the like for processing exchanges on behalf of a user, various user interface screens for controlling, initiating, performing, and / or the like of these steps / operations are provided and described. In various embodiments, the user interface screens provided and described in this disclosure are configured to be provided via a user interface of a client device 104.

[0340] Fig. 9A -D provides an example user interface flow configured for a client device 104. The user interface can be configured to guide a user through a credential-free exchange process to facilitate a value-based exchange between one or more member platforms without exposing sensitive, permanent credentials of a service provider tool used to perform the value-based exchange. Fig. 9A As shown, the no-credentials exchange process may begin when a user selects a payment method from the exchange processing screen 902 of a partner application. Fig. 9BAs shown, after selecting a payment method provided by the exchange platform, the user can switch to a tool selection screen 904. The tool selection screen 904 may include a plurality of selectable tool icons 906, each of which may be associated with a UUEK issued by the exchange platform using the various techniques described herein. The user may perform an exchange by selecting one or more selectable tool icons 906.

[0341] In some examples, in response to the selection, a scan screen 908 may be provided for an in-store exchange. The scan screen 908 may present an enabled and / or disabled UUEK representation 910 corresponding to the UUEK. The user may scan the UUEK representation 910 to complete the value-based exchange. In the event that the UUEK is a disabled UUEK, the user may transition to a verify user screen 912 to provide a security code associated with the UUEK. The user may enter the security code to enable the UUEK and complete the exchange.

[0342] VI. Conclusion

[0343] Many modifications and other embodiments will occur to those skilled in the art having benefit of the foregoing description and the teachings presented in the associated drawings. Therefore, it should be understood that the present disclosure is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a general and descriptive sense only and not for the purpose of limitation.

Claims

1. A computer-implemented method comprising: receiving, by one or more processors, a security interaction request indicating a security code input and a user identifier; identifying, by the one or more processors, a set of security code elements for the security code input based on the user identifier; verifying, by the one or more processors, the security code input based at least in part on a comparison between the security code input and a security code reference of the set of security code elements; In response to verifying the security code input, (i) storing, by the one or more processors, security events for the user, and (ii) providing, by the one or more processors, a security interaction response indicative of the security event, wherein the security interaction response indicates at least one of (a) a universally unique temporary key (UUEK) or (b) a security event for the UUEK; receiving, by the one or more processors, an exchange request for performing a value-based exchange using the UUEK; providing, by the one or more processors, an exchange authorization request to a member platform, wherein the exchange authorization request indicates a tool identifier and the security event; and An exchange authorization response is received, by the one or more processors, indicating at least one of an exchange approval or an exchange denial, wherein the exchange authorization response is based at least in part on the security event. 2 . The computer-implemented method of claim 1 , wherein the secure interaction request is received using a partner interface corresponding to a partner platform in response to a selection input of a disabled UUEK representation corresponding to the UUEK.

3. The computer-implemented method of claim 2, wherein (i) presenting, via a user interface, a representation of the disabled UUEK, and (ii) In response to the security interaction response, modifying the exchange interface to present an enabled UUEK representation.

4. The computer-implemented method of claim 1 , wherein (i) the member platform is a service provider platform, (ii) the exchange request is received from a partner platform different from the service provider platform using a partner interface, (iii) the exchange authorization request is provided to the service provider platform using a service provider interface, (iv) the exchange authorization response is received from the service provider platform using a service provider interface, and the computer-implemented method further comprises: An exchange response is provided using the partner interface based at least in part on the exchange authorization response, wherein the exchange response indicates an exchange approval or an exchange denial.

5. The computer-implemented method of claim 1, wherein the security code reference comprises an n-character sequence of one or more different characters. The computer-implemented method of claim 5 , wherein the one or more different characters include one or more alphanumeric characters.

7. A computer-implemented method according to claim 1, wherein the security code tuple includes the security code reference and a user identifier and is previously generated in response to a security code request from the member platform.

8. The computer-implemented method of claim 1, wherein the security event is associated with a security time period and the exchange authorization response is based at least in part on a time of receipt of the security event and the exchange request.

9. The computer-implemented method of claim 1 , wherein the member platform is associated with a member policy, the member policy defining one or more authentication requirements for a service provider tool, and wherein the computer-implemented method comprises: The UUEK is determined to be enabled based at least in part on the member policy, the exchange request, and the security event.

10. The computer-implemented method of claim 9, wherein the exchange request indicates one or more exchange attributes, and the one or more authentication requirements correspond to the one or more exchange attributes.

11. The computer-implemented method of claim 10, wherein the one or more exchange attributes indicate an exchange value, and the one or more verification requirements define an exchange value threshold where a corresponding security event is required for a service provider tool.

12. A computing system comprising a memory and one or more processors communicatively coupled to the memory, the one or more processors configured to: receiving a security interaction request indicating a security code input and a user identifier; identifying a security code element group for the security code input based on the user identifier; verifying the security code input based at least in part on a comparison between the security code input and a security code reference of the set of security code elements; In response to verifying the security code input, (i) store security events for users, and (ii) providing a security interaction response indicative of the security event, wherein the security interaction response indicates at least one of (a) a universally unique temporary key (UUEK) or (b) a security event for the UUEK; receiving an exchange request for performing a value-based exchange using the UUEK; providing an exchange authorization request to a member platform, wherein the exchange authorization request indicates a tool identifier and the security event; and An exchange authorization response is received indicating at least one of an exchange approval or an exchange denial, wherein the exchange authorization response is based at least in part on the security event.

13. The computing system of claim 12, wherein the secure interaction request is received using a partner interface corresponding to a partner platform in response to a selection input of a disabled UUEK representation corresponding to the UUEK.

14. The computing system of claim 12, wherein (i) presenting, via a user interface, a representation of the disabled UUEK, and (ii) In response to the security interaction response, modifying the exchange interface to present an enabled UUEK representation.

15. The computing system of claim 12, wherein (i) the member platform is a service provider platform, (ii) the exchange request is received from a partner platform different from the service provider platform using a partner interface, (iii) the exchange authorization request is provided to the service provider platform using a service provider interface, (iv) the exchange authorization response is received from the service provider platform using a service provider interface, and the computer-implemented method further comprises: An exchange response is provided using the partner interface based at least in part on the exchange authorization response, wherein the exchange response indicates an exchange approval or an exchange denial.

16. The computing system of claim 12, wherein the security event is associated with a security time period, and the exchange authorization response is based at least in part on a time of receipt of the security event and the exchange request.

17. One or more non-transitory computer-readable storage media comprising instructions that, when executed by one or more processors, cause the one or more processors to: receiving a security interaction request indicating a security code input and a user identifier; identifying a security code element group for the security code input based on the user identifier; verifying the security code input based at least in part on a comparison between the security code input and a security code reference of the set of security code elements; In response to verifying the security code input, (i) store security events for users, and (ii) providing a security interaction response indicative of the security event, wherein the security interaction response indicates at least one of (a) a universally unique temporary key (UUEK) or (b) a security event for the UUEK; receiving an exchange request for performing a value-based exchange using the UUEK; providing an exchange authorization request to a member platform, wherein the exchange authorization request indicates a tool identifier and the security event; and An exchange authorization response is received indicating at least one of an exchange approval or an exchange denial, wherein the exchange authorization response is based at least in part on the security event.

18. The one or more non-transitory computer-readable storage media of claim 17, wherein the security code reference comprises an n-character sequence of one or more different characters, and the one or more different characters comprise one or more alphanumeric characters.

Images