Systems, methods, and storage media for performing network-based uncredentialed communication exchanges

Abstract

Various embodiments of the present disclosure provide techniques for facilitating credential-free exchange over a network using multiple identifier mappings and member interfaces. These techniques may include initiating presentation of a registration user interface via a user's client device and receiving selection data indicating selection of a service provider tool from the registration user interface. These techniques include generating a matching code for authenticating the user, providing the matching code to a service provider platform, and receiving the matching code from a partner platform. In response to authenticating the user based on the matching code, these techniques may include generating a UUEK for the user that can be used to replace permanent credentials.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 370280 filed on August 3, 2022, U.S. Provisional Patent Application Serial No. 63 / 370279 filed on August 3, 2022, and U.S. Patent Application Serial No. 18 / 329101 filed on June 5, 2023, each of which is incorporated herein by reference in its entirety, including any figures, tables, diagrams, and appendices. Technical Field

[0003] Embodiments of the present disclosure generally relate to voucherless value exchange between multiple entities in a value system. Background Art

[0004] In view of the limitations of existing transaction processing technologies and architectures, various embodiments of the present disclosure address the technical challenges associated with network-based value transactions. Existing processes for executing transactions on 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 to conduct a transaction, the user must accept the risk of financial loss, damaged credit score, identity theft, and other consequences. The inherent insecurity of permanent credentials is typically addressed using strict communication protocols, data management procedures, and authentication schemes, each of which introduces additional technical problems by increasing overhead and complicating network-based transactions, but does not address the fundamental technical problem of data security.

[0005] For example, a traditional service provider that manages user accounts may limit their exposure using disclaimers that prevent users from providing their credentials to certain third parties. This can cause network congestion because the limited number of permitted parties is overloaded with requests from the group. In addition, permitted parties are required to register users by obtaining sensitive permanent credentials (e.g., username, password, routing / transport credentials, etc.) from the users, and then manage a large number of permanent credentials across multiple registered users. This provides a single attack vector for malicious parties to obtain sensitive user information from the user group. To combat such attacks, traditional transaction processing entities need to adopt costly, resource-intensive, and robust data management procedures and authentication schemes, which are however imperfect and remain vulnerable to infiltration.

[0006] Other techniques for addressing data security include limiting exchange communications (such as financial transaction communications) to strict information standards (such as ISO information standards). However, these standards lack flexibility and are designed to not provide contextual data for transactions. Therefore, such communication standards improve network security at the expense of transaction functionality.

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

[0008] Various embodiments of the present disclosure disclose a secure intermediary computing platform and computing service that facilitates the execution of value-based exchanges without credentials, which utilize UUEKs (Universally Unique Ephemeral Keys) to eliminate the use of permanent credentials. To this end, the intermediary computing platform can facilitate interactions between one or more member platforms to register user tools in a value exchange system that is supported by a new, temporary data structure (referred to herein as UUEK). Unlike traditional registration systems, the intermediary computing platform does not receive or rely on permanent user or tool credentials to register a user's tools. Eliminating such credentials enables the use of new, more flexible interfaces, such as the application programming interface (API) described herein, which the intermediary computing platform utilizes to communicate with different network members to register a user's tools without exposing the user's credentials at any step in the process. Once registered, the intermediary 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 issued UUEK (without explicitly referencing the permanent credential) from the member platform to the intermediary platform, and (ii) the intermediary platform to map the issued UUEK 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. Ultimately, it achieves additional flexibility (e.g., by using new interfaces, etc.) and security (e.g., by eliminating permanent credentials, etc.), while reducing computing power requirements and significantly improving network throughput for exchange processing relative to traditional technologies.

[0009] In some embodiments, the method includes: initiating, by one or more processors and using a partner interface, presentation of a registration user interface via a user's client device, wherein the registration user interface includes a tool registration screen indicating one or more service provider tools associated with the user; receiving, by one or more processors and using the partner interface, selection data indicating selection of a service provider tool from the registration user interface; generating, by one or more processors, a matching code for authenticating the user; providing, by one or more processors and using the service provider interface, a registration request to a service provider platform corresponding to the service provider tool, wherein the registration request includes service provider registration data indicating the matching code, a user identifier of the user, and a tool identifier of the service provider tool; receiving, by one or more processors and using the partner interface, an authentication message including the matching code; and in response to authenticating the user based on the matching code, (i) generating, by the one or more processors, a UUEK for the user, wherein the UUEK corresponds to the user, the service provider tool, and the partner platform; and (ii) providing, by the one or more processors and using the partner interface, the UUEK to the partner platform.

[0010] In some embodiments, a computing system includes a memory and one or more processors communicatively coupled to the memory, the one or more processors being configured to: using a partner interface, initiate presentation of a registration user interface via a user's client device, wherein the registration user interface includes a tool registration screen indicating one or more service provider tools associated with the user; using the partner interface, receive selection data indicating selection of a service provider tool from the registration user interface; generate a matching code for authenticating the user; using the service provider interface, provide a registration request to a service provider platform corresponding to the service provider tool, wherein the registration request includes service provider registration data indicating the matching code, a user identifier of the user, and a tool identifier of the service provider tool; using the partner interface, receive an authentication message including the matching code; and in response to authenticating the user based on the matching code, (i) generate a UUEK for the user, wherein the UUEK corresponds to the user, the service provider tool, and the partner platform; and (ii) provide the UUEK to the partner platform using the partner interface.

[0011] 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: initiate presentation of a registration user interface via a user's client device using a partner interface, wherein the registration user interface includes a tool registration screen indicating one or more service provider tools associated with the user; receive selection data indicating selection of a service provider tool from the registration user interface using the partner interface; generate a matching code for authenticating the user; provide a registration request to a service provider platform corresponding to the service provider tool using the service provider interface, wherein the registration request includes service provider registration data indicating the matching code, a user identifier of the user, and a tool identifier of the service provider tool; receive an authentication message including the matching code using the partner interface; and in response to authenticating the user based on the matching code, (i) generate a UUEK for the user, wherein the UUEK corresponds to the user, the service provider tool, and the partner platform; and (ii) provide the UUEK to the partner platform using the partner interface. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0018] Figures 6A-6C A process flow for establishing cross-entity relationships according to one or more embodiments of the present disclosure is provided;

[0019] Figures 7A-7D A message flow for establishing a cross-entity relationship according to one or more embodiments of the present disclosure is provided;

[0020] Figures 8A-8FAn example interface for establishing cross-entity relationships according to one or more embodiments of the present disclosure is provided;

[0021] Figure 9 A process flow for facilitating voucherless value exchange according to one or more embodiments of the present disclosure is provided;

[0022] Figure 10 A first message flow for facilitating voucherless value exchange according to one or more embodiments of the present disclosure is provided;

[0023] Figure 11 A second message flow for facilitating voucherless value exchange according to one or more embodiments of the present disclosure is provided;

[0024] Figures 12A-12C An example interface for facilitating voucherless value exchange according to one or more embodiments of the present disclosure is provided. DETAILED DESCRIPTION

[0025] Various embodiments of the present disclosure will be described more fully below with reference to the accompanying drawings, which illustrate some, but not all, of the embodiments of the present disclosure. In fact, the present disclosure can be embodied in many different forms and should not be construed as limited to the embodiments described herein; rather, these embodiments are provided so that the present disclosure satisfies applicable legal requirements. Unless otherwise specified, the term "or" as used herein has both an alternative and a conjunction meaning. The terms "illustrative" and "example" are used as examples and do not indicate a level of quality. 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 herein in an open manner, so unless otherwise specified, they do not necessarily mean based only at least in part on or based only on the referenced element. The same figure numbers always refer to the same elements.

[0026] I.Overview and Technical Advantages

[0027] 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 occur in real time without requiring permanent credentials that could expose members to financial, legal, reputational, or other risks. Thus, 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 could be vulnerable to network-based attacks.

[0028] Embodiments of the present disclosure provide improved instrument enrollment and exchange processing techniques that utilize interfaces and data conversion and encryption technologies to improve data security while reducing the expenditure requirements for computing resources to protect sensitive data through network communications. For example, some technologies of the present disclosure 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. Once established, the data key can be mapped to sensitive credentials stored in the source platform (e.g., the service provider platform) without requiring network transmission of the sensitive credentials. To promote value-based exchanges, future communications may replace traditional permanent credentials with data keys to enable the source platform to identify the permanent credentials and / or perform one or more operations for the specific tool associated with it. In this way, the exchange platform can use keys (and / or other identifiers) that cannot themselves be traced back to the underlying sensitive information to facilitate exchanges. This in turn enables the exchange platform to comprehensively track, promote, and distribute network-based communications without exposing members to network attacks. In this way, the registration technology of the present disclosure provides improved data and network security technologies that can be practically applied to network-based exchanges to securely register tools with the exchange platform.

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

[0030] Example inventive and technically advantageous embodiments of the present disclosure include: (i) data conversion, mapping, and processing schemes for facilitating network-based credentialless user registration, (ii) exchange interfaces and network-based communication schemes for improving network security for cross-platform communications, and (iii) temporary data structures and data management techniques for distributing temporary data structures to facilitate real-time, secure, and dynamic value-based exchanges.

[0031] II. Example Definition

[0032] In some embodiments, the term "exchange platform" refers to a computing entity configured to facilitate the voucherless exchange of value among one or more members of a 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 the agnostic exchange of value systems. In some examples, the exchange platform may include, define, and / or otherwise utilize one or more application programming interfaces (APIs) to facilitate communication (e.g., requests and responses, etc.) between multiple members. As described herein, the APIs may be utilized to facilitate secure exchanges between one or more members of any value system.

[0033] In some embodiments, the term "member" refers to an entity that collaborates with an exchange platform to participate in a value exchange. As an example, a member may include (i) a partner that utilizes the exchange platform to receive value, (ii) a service provider that utilizes the exchange platform to provide value, and / or (iii) 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 can provide and receive value in a single member value exchange using the exchange platform.

[0034] In some embodiments, a member is a partner when it uses a service provided by a service provider. Partners may include any value-seeking entity in any value system. For example, in a financial value system, partners may include merchants (e.g., retailers, physical stores, etc.) that can use service providers (e.g., 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. It will be understood that the technology of the present disclosure can be applied to any value system, and partners may include any value seeker of any corresponding value system.

[0035] In some embodiments, when a member provides a service 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 can include financial institutions (e.g., banks, currency exchange platforms, credit unions, 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 can include a news agency (e.g., a wire service, a news service, etc.) that can provide a source of information for publication by a news publisher. It will be understood that the technology of the present disclosure can be applied to any value system, and a service provider can include any value source of any corresponding value system.

[0036] In some embodiments, the term "member platform" refers to a computing entity corresponding to a member. The member platform entity 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 in one value exchange and a service provider in 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 member platform's role in the value exchange (e.g., and / or one or more APIs used by the member platform in the value exchange).

[0037] 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 collectively (and / or individually) perform one or more computing tasks for requesting value in an agnostic exchange of the value system. 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-facing applications (e.g., partner applications, etc.) for interacting with one or more users.

[0038] 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 collectively (and / or individually) perform one or more computing tasks for providing value in an agnostic exchange of a value system. In some examples, the 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, the service provider platform may be configured to facilitate one or more service provider tools. In some examples, the service provider platform may be configured to host one or more user-facing applications (e.g., service provider applications, etc.) for managing one or more service provider tools.

[0039] 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, such as 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.

[0040] The exchange platform may include, define, and / or otherwise utilize one or more distinct 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. For example, 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.

[0041] 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 the exchange platform, and / or (ii) requests from the exchange platform to the partner platform. For example, the partner interface may define one or more registration messages, session messages, transaction messages, etc. that facilitate a value exchange between partners. In some embodiments, the partner interface defines one or more identifiers for securely identifying one or more parts of a value exchange.

[0042] 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 the exchange platform, and / or (ii) requests from the exchange platform to the service provider platform. For example, the service provider interface may define one or more registration messages, session messages, transaction messages, etc. for facilitating a value exchange using a service provider tool. In some embodiments, the service provider interface defines one or more identifiers for securely identifying one or more parts of a value exchange.

[0043] 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 character, 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 representing a service provider platform, a partner partition representing a partner platform, and the like.

[0044] 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 sequence of numbers, alphanumeric characters, or 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 each identify a service provider platform associated with (e.g., joined, registered, etc.) the 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) or the like to implement a service provider interface for the exchange platform.

[0045] In some embodiments, a "partner partition" refers to a unique identifier for a partner and / or a partner platform of a partner. A partner partition may include a sequence of numbers, alphanumeric characters, and / or any other characters or symbols representing a partner associated with an exchange platform. For example, an exchange platform may include multiple partner partitions that each identify a partner platform 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 the partner interface of the exchange platform.

[0046] 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 such as a member platform. For example, a user-oriented application may facilitate communication between members and users. As an example, 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., via one or more user interfaces) to receive information from a user.

[0047] 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 with (e.g., browsing, purchasing, viewing, etc.) 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., via one or more user interfaces) to receive information from the user.

[0048] In some embodiments, the user-facing application is a service provider application hosted by a service provider platform (e.g., a member platform acting as a service provider for 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 to interact with one or more service provider tools provided by the service provider (e.g., to view, manage, audit, register, etc.). For example, in a financial value system, the service provider application may be able to access bank accounts, brokerage accounts, credit lines, etc. to manage funds, assets, etc. handled by the corresponding accounts. In some examples, the service provider application may be configured to receive user input (e.g., via one or more user interfaces) to receive information, authorization, etc. from the user.

[0049] In some embodiments, the term "service provider tool" refers to the 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 the service provider platform.

[0050] 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 on the type of the tool data object. For example, 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 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.

[0051] In some embodiments, a member instrument data object is an internal representation of a service provider instrument within a member platform. The 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, the 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 contextual attributes. In some examples, the contextual attributes may depend on the value system. For example, in a financial value system, one or more contextual attributes may indicate (i) the currency associated with the service provider instrument, (ii) the asset availability of the service provider instrument (e.g., balance, coverage, etc.), (iii) one or more previous transactions with the service provider instrument, etc.

[0052] In some embodiments, a system instrument data object is an external representation of a service provider instrument within an exchange platform. The system instrument data object may include one or more instrument identifiers, such as an instrument reference for a member platform, a system instrument identifier, and / or a user identifier. For example, the 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 the currency associated with the service provider instrument.

[0053] 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.

[0054] 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, the member tool identifier may include a sequence of numbers, alphanumeric characters, and / or any other characters or symbols that represent a service provider tool of a service provider platform.

[0055] 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 the member tool identifier.

[0056] In some embodiments, the term "system tool identifier" refers to a unique identifier used to identify a service provider tool within an exchange platform. For example, the system tool identifier may include a sequence of numbers, alphanumeric characters, and / or any other characters or symbols that identifies the service provider tool to the exchange platform. In some examples, the system tool identifier may include a UUID.

[0057] In some embodiments, the term "instrument key" refers to a unique identifier used to reference a system instrument identifier. For example, during the process of registering an instrument with an exchange platform, the exchange platform may generate and / or provide an instrument key. In some examples, the instrument key may include an encapsulated system instrument identifier. For example, the instrument 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, for example, fifty characters or more. In some examples, the characters may be case sensitive. The first portion of the characters (for example, the first six characters) may be reserved as a partition for identifying the entity associated with the key. For an instrument key, the partition may include a service provider partition. The second portion of the characters may identify the system instrument identifier. The key format described herein may include one or more different parts, each of which may be arranged in any order.

[0058] 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 sequence of numbers, alphanumeric characters, and / or any other characters or symbols that visually represents the service provider. 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 (e.g., one or more numbers, alphanumeric characters, etc.) such as a subscription account. For example, a tool representation may include a derivative of the permanent credential that may only allow entities with prior knowledge of the permanent credential to identify the permanent credential using the tool representation. As another example, a tool representation may include a tool nickname that is assigned and subsequently recognized by the user.

[0059] 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 can include entities (e.g., individuals, organizations, groups, etc.) that participate in value exchanges managed by the exchange platform. In some examples, a user can indirectly engage with the exchange platform by creating a user account with a registered service provider, registering (and / or allowing registration) for a service provider tool, etc. In some examples, the exchange platform can act on behalf of the user without the user having to interact directly with the exchange platform. For example, the exchange platform can act as a hidden intermediary between user-facing applications and the user's service provider tools.

[0060] In some embodiments, a 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 on the type of the user data object. For example, 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. For example, a member platform may register multiple users with an exchange platform. During registration, the member platform may provide one or more user identifiers and / or user attributes, and in some examples, the exchange platform may return another identifier.

[0061] In some embodiments, a member user data object is an internal representation of a user within a member platform. A member tool data object may include one or more user identifiers, such as a member user identifier, a user key from an exchange platform, and the like. Additionally or alternatively, a 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 of a user. For example, a user attribute may indicate a user's first name, last name, email, physical address (e.g., one or more of a street, location, 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 an encrypted, hashed, and / or other secure representation of a user's identifiable features. For example, a user attribute may include one or more hashed identifiers of a user, etc.

[0062] In some embodiments, a system user data object is an external representation of a member user within an exchange platform. A system user data object may include one or more user identifiers, such as a member platform user reference, a system user identifier, and the like. Additionally or alternatively, as described herein, a system user data object may include one or more user attributes. For example, a 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 for the user. In some examples, the user attributes may include a hashed and / or encrypted identifier for the user.

[0063] 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 sequence of numbers, alphanumeric characters, and / or any other characters or symbols representing 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 identifier, and the like.

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

[0065] In some embodiments, the term "member user identifier" refers to a unique identifier that represents a user within the member platform. For example, the member user identifier may include a sequence of numbers, alphanumeric characters, and / or any other characters or symbols that represent the user to the service provider platform.

[0066] 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.

[0067] 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 user registration 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 as a partition for identifying the 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 characters can identify the system user identifier.

[0068] In some embodiments, the term "exchange data object" refers to a data entity that represents 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, the one or more identifiers and / or one or more exchange attributes may be based on the type of the exchange data object. For example, 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. 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. For example, using some techniques of the present disclosure, an exchange platform may issue one or more unique identifiers to a member platform that may be used to authorize a value exchange.

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

[0070] For example, the system exchange data object may include a service provider-specific exchange data object corresponding to the 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.), etc.

[0071] 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.), etc. 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 the exchange platform, etc.

[0072] In some embodiments, the term "exchange identifier" refers to a unique identifier used to exchange value using an exchange platform. The exchange identifier may include a sequence of numbers, alphanumeric characters, 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 universally unique identifier (UUID), which may be mapped (e.g., via a series of identifiers, etc.) to a user, service provider tool, and / or member registered with 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, etc.). Therefore, while the exchange identifier may be used by the exchange platform and / or member platform for one or more functions, the same exchange identifier may be useless to external parties if there is no prior association between the exchange identifier and one or more other identifiers. In some examples, the exchange identifier may be externally represented by a UUEK.

[0073] 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 do so, the exchange platform can generate and issue a UUEK to the external entity. Each UUEK can include multiple values ​​(e.g., up to fifty characters and / or more characters, potentially case sensitive) representing one or more aspects of the transaction. For example, the 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. For example, 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, while a service provider-specific UUEK can be associated with a service provider-specific exchange data object.

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

[0075] 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, the second portion of characters may identify the exchange identifier (e.g., the group of twenty-two characters following the eighth character). The third portion of characters may be reserved (e.g., the group of twenty characters following the first portion of characters). An example representation is provided below:

[0076] ppppppFiGGGGGGGGGGGGGGGGGGGGGGrrrrrrrrrrrrrr

[0077] Where 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.8×1084 unique permutations, which is more than the number of atoms in the known observable universe. This enables the generation and distribution of new UUEKs 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.

[0078] In some embodiments, the term "session identifier" refers to a unique identifier used to identify a series of related message exchanges between an exchange platform and an external platform.

[0079] In some embodiments, the term "matching code" refers to a session-unique identifier used to authorize a registration session between one or more entities. For example, a match code may include a sequence of numeric, alphanumeric, and / or similar characters that may be provided to multiple entities to ensure that each of the multiple entities is involved in the same communication sequence. For example, a match code may include an eight-character sequence that may be generated by an exchange platform, provided to a service provider platform, and then received from a partner platform to ensure that the exchange platform, the service provider platform, and the partner platform are each interacting with the same end-user (e.g., by comparing a received match code to a generated match code as described herein).

[0080] III. Computer Program Products, Methods, and Computing Entities

[0081] Embodiments of the present disclosure may be implemented in various ways, including as a computer program product comprising an article of manufacture. Such a computer program product may include one or more software components, including, for example, software objects, methods, data structures, etc. The software components may be encoded in any of a variety of programming languages. The declarative 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 comprising assembly language instructions may need to be converted by an assembler into executable machine code before being executed by the hardware architecture and / or platform. Another example programming language may be a high-level programming language that is portable across multiple architectures. Software components comprising high-level programming language instructions may need to be converted by an interpreter or compiler into an intermediate representation before being executed.

[0082] 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 of one of the above-mentioned programming language examples can be executed directly 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 related functions can be stored together, for example, 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).

[0083] A computer program product may include a non-transitory computer-readable storage medium (also referred to herein as executable instructions, execution instructions, computer program product, program code, and / or similar terms used interchangeably herein) that stores an application, program, program module, script, source code, program code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, etc. Such non-transitory computer-readable storage medium includes all computer-readable media (including volatile and non-volatile media).

[0084] In one embodiment, the non-volatile computer-readable storage medium may include a floppy disk, a flexible 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 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 pattern of holes or other optically identifiable markings), a compact disc read-only memory (CD-ROM), a rewritable compact disc (CD-RW), a digital versatile disc (DVD), a Blu-ray disc (BD), any other non-transitory optical medium, etc. Such non-volatile computer-readable storage medium 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, non-volatile computer-readable storage media 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.

[0085] 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-out 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 where embodiments are described as using computer-readable storage media, other types of computer-readable storage media may be substituted or used in addition to the computer-readable storage media described above.

[0086] It should be understood that various embodiments of the present disclosure may also be implemented as methods, apparatuses, systems, computing devices, computing entities, etc. Thus, embodiments of the present disclosure may take the form of data structures, apparatuses, systems, computing devices, computing entities, etc., which execute instructions stored on a computer-readable storage medium to perform certain steps or operations. Thus, embodiments of the present disclosure may also take the form of entirely hardware embodiments, entirely computer program product embodiments, and / or embodiments comprising a combination of computer program products and hardware that perform certain steps or operations.

[0087] The 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 diagrams, flow charts, etc. can be embodied as 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 that can be used interchangeably (for example, executable instructions, instructions for execution, program code, 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 example 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.

[0088] IV. Example System Architecture

[0089] 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, and the like. The member platform network 110 may include a first member platform 112a, a second member platform 112b, a third member platform 112c, and the like associated with the exchange platform 102 (e.g., registered, etc.). For example, as described herein, the member platform network 110 may include partner platforms and / or service provider platforms. In some examples, the partner platform may include the first member platform 112a, and the service provider platform may include a second member platform 112b that is different from the first member platform 112a. In some examples, the partner platform and / or the service provider platform may include a single member platform (e.g., the third member platform 112c). In some examples, the member platform network 110 may be configured for one or more different services.

[0090] For example, each component in the computing ecosystem 100 can electronically communicate 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), etc. For example, the networks 120 can include any network connections, including any type of network and / or spanning any geographic boundaries (e.g., connections between countries involving one or more sovereign entities, etc.). In addition, although Figure 1Certain systems are shown as separate stand-alone entities, but the various embodiments are not limited to this particular architecture.

[0091] 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 member platforms 112a-c may each comprise the same computing platform.

[0092] a. Example computing platform

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

[0094] For example, processing element 202 may be embodied 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. Furthermore, processing element 202 may be embodied as one or more other processing devices or circuits. The term "circuit" may refer to a fully hardware embodiment or a combination of hardware and a computer program product. Thus, 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 the like.

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

[0096] 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, a hard disk, 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, and the like.

[0097] 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., a hierarchical database model, a network model, a relational model, an entity-relationship model, an object model, a document model, a semantic model, a graph model, etc.).

[0098] In some embodiments, computing platform 200 includes or communicates with volatile memory 206 (also referred to as volatile memory, medium, memory, memory circuit, and / or similar terms used interchangeably herein). In some examples, volatile memory 206 can 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.

[0099] It will 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.

[0100] 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 (e.g., Figure 1 The system may communicate with one or more components of a network, 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.

[0101] 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.

[0102] As described above, computing platform 200 may be Figure 1 Examples of one or more components in , such as, exchange platform 102 and / or member platforms 112a - c .

[0103] b. Example client device

[0104] Figure 3 is an example schematic diagram of a client device 104 according to one or more embodiments of the present disclosure. Client device 104 can be operated by various entities, and an example computing ecosystem can include one or more client devices 104. For example, client device 104 can be associated with, owned by, operated by, or the like, one or more end users. In various embodiments, end users of client device 104 may wish to participate in value exchanges between partners and service providers. As described herein, the user can do so by interacting with one or more functionalities, which are provided through user input from client device 104.

[0105] For example, the client device 104 may be a personal computing device, a smartphone, a tablet computer, a laptop computer, a personal digital assistant, etc. In various embodiments, the computing platform 200 may communicate with 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), a receiver 306 (e.g., a radio), 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.

[0106] The signals provided to transmitter 304 and the signals received from receiver 306, respectively, may include signaling information / data in accordance with the air interface standard of the applicable wireless system. In this regard, client device 104 may be capable of operating using one or more air interface standards, communication protocols, modulation types, and access types. More specifically, client device 104 may operate in accordance with any of a variety of wireless communication standards and protocols, such as those described above with respect to computing platform 200. In certain embodiments, client device 104 may operate in accordance with a variety 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, and the like. Similarly, client device 104 may operate in accordance with a variety of wired communication standards and protocols, such as those described above with respect to computing platform 200 via network interface 320.

[0107] 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 a 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.

[0108] In some embodiments, the client device 104 includes location determination aspects, devices, modules, functionality, and / or similar terms used interchangeably herein. For example, the client device 104 may include outdoor location determination aspects, such as a location module adapted to obtain information such as latitude, longitude, altitude, geocode, route, direction, heading, speed, Universal Time (UTC), date, and / or various other information / data. In one embodiment, the location module may 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 the Global Positioning System (GPS)). The satellites may be a variety of different satellites, including low earth orbit (LEO) satellite systems, Department of Defense (DOD) satellite systems, the European Union's Galileo positioning system, China's BeiDou navigation system, India's regional navigation satellite system, and the like. This data may be collected using various coordinate systems, such as decimal degrees (DD); degrees, minutes, seconds (DMS); Universal Transverse Mercator (UTM); Universal Polar Stereographic (UPS) coordinate systems, and the like. Alternatively, 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, geocode, 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 a person or thing to within inches or centimeters.

[0109] In some embodiments, the client device 104 may include a user interface 316 (e.g., a display screen, a speaker, a tactile mechanism, etc. coupled to the processing element 308) 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 to, for example, activate or deactivate certain functions, such as a screen saver and / or sleep mode.

[0110] 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 are accessible via a browser or other user interface to communicate with the computing platform 200.

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

[0112] In various embodiments, the client device 104 may be embodied as an artificial intelligence (AI) computing entity, such as Amazon Echo, Amazon Echo Dot, Amazon Show, Google Home, etc. Accordingly, the client device 104 may be configured to provide and / or receive information / data to an end user via an input / output mechanism (e.g., a display, a camera, a speaker, a voice-activated input, etc.). 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 upon the occurrence of a predefined trigger event.

[0113] c. Example network

[0114] In some embodiments, Figure 1 Any two or more of the illustrative components of computing ecosystem 100 can be configured to communicate with each other via respective communication couplings of one or more networks 120. Networks 120 can include, but are not limited to, any one or a combination of different types of suitable communication networks, such as, for example, 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. Furthermore, networks 120 can have any suitable communication range associated therewith and can include, for example, a global network (e.g., the Internet), a MAN, a WAN, a LAN, or a PAN. Furthermore, networks 120 can 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 terrestrial transceivers, radio frequency communication medium, satellite communication medium, or any combination thereof, as well as various network devices and computing platforms provided by a network provider or other entity.

[0115] d. Example Value Exchange System

[0116] Figure 4is an exemplary 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 computing platform that provides an end-to-end value exchange solution to replace traditional exchange processing systems. As described herein, the network-based exchange system 400 can be value system agnostic 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, etc. In any value system, the network-based exchange system 400 can utilize intermediary entities and one or more defined communication interfaces to facilitate network-based exchanges between value-seeking entities (e.g., partners) and value-providing entities (e.g., service providers), which entities can be associated with one or more member platforms of the network-based exchange system 400.

[0117] As shown, the network-based exchange system 400 may include the 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.

[0118] In some embodiments, exchange platform 102 is a computing entity configured to facilitate the voucherless exchange of value between one or more members of a network. Exchange platform 102 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 the agnostic exchange of value systems. In some examples, exchange platform 102 may include, define, and / or otherwise utilize one or more exchange interfaces to facilitate communication (e.g., requests, responses, etc.) between multiple members. As described herein, interfaces may be utilized to facilitate secure exchanges between one or more members of any value system.

[0119] In some embodiments, a member is an entity that collaborates with the exchange platform 102 to participate in a value exchange. As an example, a member may include (i) a partner that utilizes the exchange platform 102 to receive value, (ii) a service provider that utilizes the exchange platform 102 to provide value, 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. Thus, 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, such that the member may use the exchange platform 102 to provide and subsequently receive value in a single member value exchange.

[0120] In some embodiments, a member is a partner when it uses a service provided by a service provider. Partners may include any value-seeking entity in any value system. For example, in a financial value system, partners may include merchants (e.g., retailers, physical stores, etc.) that can use service providers (e.g., 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. It will be understood that the technology of the present disclosure can be applied to any value system, and partners may include any value seeker of any corresponding value system.

[0121] In some embodiments, when a member provides a service 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 can include financial institutions (e.g., banks, currency exchange platforms, credit unions, 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 can include a news agency (e.g., a wire service, a news service, etc.) that can provide a source of information for publication by a news publisher. It will be understood that the technology of the present disclosure can be applied to any value system, and a service provider can include any value source of any corresponding value system.

[0122] The service provider and the partner can communicate through one or more member platforms associated with each 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.

[0123] In some embodiments, a member platform is a computing entity corresponding to a member associated with exchange platform 102. A member platform can include a partner platform 420 representing a partner, a service provider platform 440 representing a service provider, and / or both. In some examples, a member platform can be both a partner platform 420 and a service provider platform 440. For example, the same member platform can be configured to operate on behalf of a partner in one value exchange and a service provider in another value exchange. In some examples, the same member platform can 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 can refer to partner platform 420, service provider platform 440, or both, and in some examples, can depend on the member platform's role in the value exchange (e.g., and / or one or more interfaces used by the member platform in the value exchange).

[0124] 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, etc., which are physically and / or wirelessly coupled and configured to collectively (and / or individually) perform one or more computing tasks for requesting value in an agnostic exchange of value systems. 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.

[0125] For example, in a financial value system, partner platform 420 may host an online marketplace for a partner that allows users to interact with one or more products or services offered by the partner (e.g., search, browse, purchase, return, etc.). In the case of purchasing products, partner platform 420 may work with one or more service providers to access funds for the purchase. Traditionally, users are required to use card numbers, account numbers, and / or other financial credentials to access funds from service providers, but this may expose users to malicious attackers. To address cybersecurity and data privacy issues of traditional financial systems (and / or other value-based systems), partner platform 420 may register with exchange platform 102 by configuring one or more software development kits (SDKs), APIs, and / or the like to facilitate communication with exchange platform 102. For example, 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 exchange platform 102.

[0126] 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, 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 agnostic exchange of the value system. In some examples, the service provider platform 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-facing applications (e.g., service provider applications, etc.) for managing one or more service provider tools.

[0127] In some examples, such as in a financial value system, 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 fund a transaction to purchase a product from a partner. If a product purchase occurs, service provider platform 440 may collaborate with partner platform 420 to authorize the transaction and / or otherwise provide access to the purchase funds. Traditionally, access to funds at a service provider is facilitated by providing a card number, account number, and / or other financial credential to service provider platform 440, which may expose the user, service provider, or partner to malicious parties, particularly when provided over an unsecured network (e.g., a public network, etc.). To address cybersecurity and data privacy issues of traditional financial systems (and / or other value-based systems), service provider platform 440 may register with exchange platform 102 by configuring one or more software development kits (SDKs), APIs, and / or the like to facilitate communication with 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 .

[0128] As described herein, the service provider interface 404 can enable the exchange platform 102 to identify and request the use of service provider tools to facilitate transactions. For example, the service provider platform 440 can be configured to facilitate one or more service provider tools.

[0129] In some embodiments, a service provider tool is a mechanism used by a service provider to provide value (e.g., on behalf of a specific user, organization, etc.). 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, a benefit value system, etc., the service provider tool may include a member account, etc. In some examples, the 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 multiple member tool data objects that indicate multiple service provider tools for multiple affiliated entities.

[0130] 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, the one or more tool identifiers and / or one or more tool attributes may be based on the type of the tool data object. For example, 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 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 with exchange platform 102 (e.g., using service provider interface 404). 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, exchange platform 102 may return another identifier.

[0131] In some embodiments, a member instrument data object is an internal representation of a service provider instrument within a member platform (e.g., service provider platform 440). The member instrument data object may include one or more instrument identifiers, such as a member instrument identifier, an instrument key from exchange platform 102, and / or a user identifier. As described above, for example, the user identifier may include a member user identifier. Additionally or alternatively, the 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 contextual attributes. In some examples, the contextual attributes may depend on the value system. For example, in a financial value system, one or more contextual attributes may indicate (i) the currency associated with the service provider instrument, (ii) the asset availability of the service provider instrument (e.g., balance, coverage, etc.), (iii) one or more previous transactions with the service provider instrument, etc.

[0132] In some embodiments, a system instrument data object is an external representation of a service provider instrument within the exchange platform 102. The system instrument data object may include one or more instrument identifiers, such as an instrument reference for a member platform, a system instrument identifier, and / or a user identifier. For example, as described herein, the 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 the currency associated with the service provider instrument.

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

[0134] In some embodiments, the user-oriented application is a computer program hosted by a computing entity for facilitating one or more user interactions. The 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 such as a member platform. For example, the user-oriented application can facilitate communication between members and users. As an example, the user-oriented application can be configured to present one or more user interfaces 406 (e.g., through client devices 104) that interact with users on behalf of the member. In some examples, the user-oriented application can be configured to receive user input (e.g., via one or more user interfaces 406) to receive information from the user.

[0135] In some embodiments, the user-facing application is a partner application 416 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. 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 information units provided by an information-based partner, etc. In some examples, the partner application 418 may be configured to receive user input (e.g., via one or more user interfaces 406) to receive information from the user.

[0136] 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-facing application may be a service provider application 418 hosted by the service provider platform 440 (e.g., a member platform acting as a service provider for a particular exchange, etc.) to facilitate the functionality of 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 provided by the service provider (e.g., viewing, managing, auditing, registering, etc.). For example, in a financial value system, the service provider application 418 may be able to access bank accounts, brokerage accounts, lines of credit, etc. to manage the funds, assets, etc. 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.

[0137] In some embodiments, the exchange platform 102 facilitates communication between the partner platform 420 and the service provider platform 440 using one or more exchange interfaces.

[0138] 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 the like. For example, the exchange interface may include an API, such as 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.

[0139] 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, etc., for exchanging requests and / or responses between the exchange platform 102 and entities participating in a value exchange. For example, the exchange interfaces 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.

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

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

[0142] 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, and so on. In some examples, the exchange platform 102 can implement 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.

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

[0144] In some embodiments, partner services 410 and / or service provider services 412 interact with each other and / or with 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 a connection service 408 configured to establish, maintain, and authenticate secure network sessions with member platforms (e.g., partner platform 420). In some examples, connection services 408 and / or partner services 410 may operate in conjunction to register a user (and / or a user's service provider tool) with exchange platform 102. Additionally or alternatively, partner services 410 and / or service provider services 412 may operate in conjunction to register a user (and / or a user's service provider tool) and / or facilitate value exchange between partner platform 420 and service provider platform 440. In some examples, connection services 408 may be part of partner services 410.

[0145] 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 users, service provider tools, and / or one or more aspects of the value exchange. At least some of these identifiers can include universally unique identifiers, such as UUEKs, which can be used to provide credential-free value exchange. Each identifier can be at least temporarily stored in platform database 414. Platform database 414 can include any type of memory device as described herein. In some examples, each service and / or one or more groups of services can be associated with a separate portion of platform database 414.

[0146] 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 also be made to Figure 5 Describe examples of non-traditional identifiers.

[0147] e. Example data structure

[0148] Figure 51 is an example data graph 500 for facilitating credentialless value exchange, according to one or more embodiments of the present disclosure. Data graph 500 illustrates 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 enables communication between exchange platform 102 and service provider platform 440 that references service provider tools 518 without exposing permanent credentials 514 (e.g., username, password, card number, etc.) associated with service provider tools 518, which are susceptible to fraud, abuse, and exploitation by malicious parties. As shown, using some techniques of the present disclosure, permanent credentials 514 may never need to be transmitted outside of service provider platform 440. Data graph 500 illustrates only some of the multiple identifiers that can be generated, stored, and / or utilized by various embodiments of the present disclosure. It should be understood that the illustrated identifiers 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.

[0149] 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 that can be mapped to a member user identifier 522 of a service provider platform 440, (ii) one or more service provider partitions 504 corresponding to a joined service provider platform network (e.g., service provider platform 440), (iii) one or more partner partitions 506 corresponding 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 that can be mapped to the system identifier 512 and / or the key 516, and / or (vii) one or more UUEKs 524 that 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.

[0150] In some examples, the service provider platform 440 can store one or more identifiers that can 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.

[0151] For example, 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 provisioned during a registration process between the service provider platform 440 and / or the exchange platform 102.

[0152] 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 the member tool identifier 508 and / or the member user identifier 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.

[0153] 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 character, 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 the like.

[0154] In some embodiments, a service provider partition 504 is a unique identifier for a service provider and / or a service provider's service provider platform 440. A service provider partition 504 may include a sequence of numbers, alphanumeric characters, and / or any other characters or symbols representing 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 each 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 for the exchange platform 102.

[0155] In some embodiments, the partner partition 506 is a unique identifier for a partner and / or a partner platform of the partner. The partner partition 506 may include a sequence of numbers, alphanumeric characters, and / or 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 each identify a partner platform 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.

[0156] 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 register one or more service provider tools with the exchange platform 102 using one or more exchange interfaces. The service provider tool 518 registers with the exchange platform 102 by exchanging one or more tool identifiers with the exchange platform 102.

[0157] In some embodiments, the tool identifier comprises 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 the like.

[0158] In some embodiments, the member tool identifier 508 is a unique identifier used to represent the service provider tool 518 within a member platform (e.g., the service provider platform 440). For example, the member tool identifier 508 may include a sequence of numbers, alphanumeric characters, and / or any other 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.

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

[0160] In some embodiments, the system tool identifier is a unique identifier used to represent the service provider tool 518 within the exchange platform 102. For example, the system tool identifier can include a sequence of numbers, alphanumeric characters, and / or 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.

[0161] In some embodiments, a tool key is a unique identifier used to reference a system tool identifier. For example, during the registration process of a 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 of its APIs). The key format may include any number of characters, for example, fifty or more. In some examples, the characters may be case-sensitive. The first portion of the characters (for example, the first six characters) may be reserved as a partition for identifying the entity associated with the key. For example, for a 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.

[0162] 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 with the exchange platform 102 by exchanging one or more user identifiers with the exchange platform 102. For example, the user identifiers may be utilized to generate, maintain, and / or update one or more user data objects reflecting the users of the member platform and / or the exchange platform 102.

[0163] In some embodiments, user data objects are data entities representing users interacting with the membership platform and / or exchange platform 102. For example, users can include entities (e.g., individuals, organizations, groups, etc.) that participate in value exchanges managed by exchange platform 102. In some examples, users can indirectly engage with exchange platform 102 by creating a user account with a registration service provider, registering with (and / or granting registration permissions to) a service provider tool 518, and so on. In some examples, exchange platform 102 can act on behalf of a user without the user having to interact directly with exchange platform 102. For example, exchange platform 102 can act as a hidden intermediary between user-facing applications and the user's service provider tool 518.

[0164] In some embodiments, a 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 on the type of the user data object. For example, 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. For example, a member platform may register multiple users with exchange platform 102. During registration, the member platform may provide one or more user identifiers and / or user attributes, and in some examples, exchange platform 102 may return another identifier.

[0165] In some embodiments, a member user data object is an internal representation of a user within a member platform (e.g., a service provider platform 440). A 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, or the like. Additionally or alternatively, a member user data object may include one or more user attributes. One or more user attributes may indicate one or more contextual features of a user. In some examples, a user attribute may indicate one or more identifiable features of a user. For example, a user attribute may indicate a user's first name, last name, email address, physical address (e.g., one or more of a street, location, 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 an encrypted, hashed, and / or otherwise secure representation of a user's identifiable features. For example, a user attribute may include one or more hashed identifiers of a user, etc.

[0166] In some embodiments, a system user data object is an external representation of a member user within exchange platform 102. A system user data object may include one or more user identifiers, such as a member platform user reference 502, a system user identifier, and the like. Additionally or alternatively, a system user data object may include one or more user attributes, such as those described herein. For example, a member platform may register a user with 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 of the user.

[0167] 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 sequence of numbers, alphanumeric characters, and / or any other characters or symbols representing a user of the exchange platform 102 and / or the member platform. In some examples, the user identifier may comprise a user reference 502, a user key, a system user identifier, a member user identifier, and the like.

[0168] 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 can include a sequence of numbers, alphanumeric characters, and / or any other characters or symbols that represent the user to exchange platform 102. In some examples, the system user identifier can include a UUID that is specific to a particular user. In some examples, the system user identifier can include at least one of system identifiers 512.

[0169] 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 sequence of numbers, alphanumeric characters, and / or any other characters or symbols that represent the user to the service provider platform 440.

[0170] 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 is mapped to member user identifier 522.

[0171] In some embodiments, the user key is a unique identifier for referencing a system user identifier. The user key can, for example, be generated and / or provided by the exchange platform 102 during the user's registration process with the exchange platform 102. 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 retained 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.

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

[0173] 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, etc., 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 permanent credentials 514 to the user. Traditionally, the user then uses the permanent credentials 514 to initiate a value exchange through the service provider tool. As a result, 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 scheme of the present disclosure overcomes these technical deficiencies.

[0174] In some examples, each of the identifiers is interpretable to the computing platform (e.g., exchange platform 102 and / or service provider platform 440), but not to the user. To enable the user to select the service provider tool 518 while maintaining the enhanced security features of the present disclosure, in some examples, the tool representation can be further enhanced. Figure 5 Identifier of .

[0175] In some embodiments, the tool representation ( Figure 5 The tool representation (not shown) is a unique identifier used to represent the service provider tool 518 to the user without exposing the permanent credential 514 of the service provider tool 518. For example, the tool representation may include a sequence of numbers, alphanumeric characters, and / or any other characters or symbols that extrinsically represent 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, etc. 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 number, etc. For example, the tool representation may include a derivative of the permanent credential 514 that may only allow 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.

[0176] 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 way, 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 was 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.

[0177] In some embodiments, the identifier mapping scheme is supplemented by unique, temporary keys issued to member platforms 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 exchange identifiers 510 that represent various aspects of a value-based exchange. Some examples of exchange identifiers 510 may include service provider-specific exchange identifiers and / or partner-specific exchange identifiers. A service provider-specific exchange identifier may include a temporary, unique exchange identifier that temporarily represents both a service provider tool 518 and a service provider platform 440. For example, a service provider-specific exchange identifier may be mapped to a system identifier 512 for a service provider tool 518. A partner-specific exchange identifier may include a temporary, unique exchange identifier that temporarily represents both a service provider tool 518 and a partner platform. For example, a partner-specific exchange identifier may be mapped to a key 516 for a 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.

[0178] In some embodiments, an exchange data object is a data entity representing an authorized value exchange between one or more members associated with exchange platform 102. In some examples, an exchange data object may include one or more identifiers and / or one or more exchange attributes. For example, the one or more identifiers and / or one or more exchange attributes may be based on the type of the exchange data object. For example, 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 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. For example, using some techniques of the present disclosure, exchange platform 102 may issue one or more unique identifiers to a member platform, which may be used to authorize a value exchange.

[0179] In some embodiments, a system exchange data object is an internal representation of a value exchange mediated 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 its role in the value-based exchange.

[0180] 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, 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.), etc.

[0181] 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), a UUEK 524, a member tool reference (e.g., a partner-specific tool reference, etc.), etc. 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, etc.

[0182] In some embodiments, a member exchange data object is an external representation of a value exchange mediated using the exchange platform 102. The 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 the exchange platform 102, and the like.

[0183] In some embodiments, exchange identifier 510 is a unique identifier for value exchanges using exchange platform 102. Exchange identifier 510 may include a sequence of numbers, alphanumeric characters, and / or any other characters or symbols that represents at least a user and / or service provider tool 518. In some examples, exchange identifier 510 may include a universally unique identifier (UUID), which may be mapped (e.g., via a series of identifiers, etc.) to a user, service provider tool 518, and / or member registered with exchange platform 102. In some examples, exchange identifier 510 may be generated using one or more UUID generators. For example, exchange identifier 510 may include sixteen bytes of information generated according to one or more UUID formatting standards (e.g., UUID v4, etc.). Thus, while exchange identifier 510 may be used by exchange platform 102 and / or member platforms for one or more functions, the same exchange identifier 510 may be useless to external parties if there is no prior association between exchange identifier 510 and one or more other identifiers. In addition to prior identifier associations, exchange identifier 510 may also be associated with 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. Furthermore, before the exchange identifier 510 can be used detrimentally, the counterparty needs to update the settlement account to an account owned by the counterparty, as well as perform a number of other tasks. Each of these tasks increases the workload required to overcome the enhanced security layer added by the exchange identifier 510. When paired with the exchange identifier 510 on a temporary basis, these tasks can become prohibitively expensive.

[0184] In some examples, the exchange identifier 510 can be represented externally by a UUEK 524. For example, 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 via previously mapped data entities.

[0185] 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, such as a user, a partner platform, and / or a service provider platform, to initiate a value-based exchange using the exchange platform 102. To this end, the exchange platform 102 can generate and issue the UUEK 524 to the external entity. Each UUEK 524 can include multiple values ​​(e.g., up to fifty characters and / or more characters, which may or may not be case-sensitive) that represent 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 the recipient of the UUEK 524, etc.), an identifier type, and / or one or more flags. For example, 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 .

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

[0187] 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, the second portion of characters may identify the exchange identifier 510 (e.g., the group of twenty-two characters following the eighth character). The third portion of characters may be reserved (e.g., the group of twenty characters following the first portion of characters). An example representation is provided below:

[0188] ppppppFiGGGGGGGGGGGGGGGGGGGGGGrrrrrrrrrrrrrr

[0189] 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.8×1084 unique permutations, which is greater 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 UUEKs 524 may be mapped, such as identifiers of users, tools, and / or any other potentially sensitive information.

[0190] As described herein, unique sequences of identifiers and mapping schemes between identifiers can facilitate a credential-free value exchange system for registered and / or unregistered entities. In some examples, one or more identifiers can be generated by a registration or enrollment process configured to establish a cross-entity relationship between a user, a partner, and a service provider entity. Reference will now also be made to Figure 6A -C Describes a sample procedure for establishing cross-entity relationships.

[0191] V. Example System Operation

[0192] Figure 6A -C provides a process flow for establishing a 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 600 for registering a user and / or service provider tool with an exchange platform to facilitate a credential-free value exchange between a partner platform and a service provider platform. For purposes of explanation, Figure 6A FIG6-C shows an example process 600. Although example process 600 describes a particular order of steps / operations, this order may be changed without departing from the scope of this 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 process 600. In other examples, different components of an example device or system implementing process 600 may perform the functionality substantially simultaneously or in a particular order.

[0193] Various embodiments of process 600 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 registration mechanisms that require 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 a partner platform for storage and subsequent processing. By doing so, user credentials are transmitted and exposed to multiple different entities during the traditional registration process, ultimately increasing the risk of exposure to malicious parties during and after network communications. Various embodiments of process 600 provide improved network communication, data encryption, and data management technologies to enable credential-free exchange registration capabilities, thereby reducing the data security risks posed by traditional processes.

[0194] One or more embodiments of process 600 may be implemented by one or more computing devices, entities, and / or systems described herein. For example, through the various steps / operations of process 600, exchange platform 102 may utilize credentialless registration techniques to overcome various limitations of traditional registration mechanisms by registering a service provider tool with a partner platform without access to the service provider tool's permanent credentials. In this manner, sensitive information behind the service provider tool participating 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, exchange platform 102 never receives a user's identifiable or actionable account information, and the service provider managing the account participates in the registration process rather than being disintermediated by a potentially insecure registration service. This, in turn, eliminates the need to enforce resource data governance standards on every device involved in the registration process, ultimately improving computing resource utilization while enhancing network and data security.

[0195] Figure 6A 6 is a flow chart illustrating an example of the first stage of a registration process 600 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 their reliance on sensitive and permanent credentials. The communication technique may be implemented by one or more computing devices, entities, and / or systems described herein (e.g., an exchange platform establishing a secure communication session with a user via a partner application).

[0196] In some embodiments, process 600 includes establishing a registration session for the user and the partner platform at step / operation 602. For example, the registration process 600 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 with the exchange platform on the partner application in order to access service provider tools. The partner platform may enable user registration by initiating a registration session with the exchange platform.

[0197] For example, as described herein, a user may access a partner application via a client device through a portal (e.g., a browser, a web application, etc.). The user's browser, web application, mobile application, etc., may retrieve 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 by the partner interface to initiate a registration widget to establish a registration session for the user.

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

[0199] In some embodiments, an 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 of the user. Additionally or alternatively, the registration initialization request may include one or more user attributes of the user. In some examples, the user attributes may be encrypted and / or hashed, as described herein.

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

[0201] In some embodiments, process 600 includes generating a session identifier for the registration session at step / operation 606. For example, the exchange platform (e.g., its connection service, partner service, etc.) may generate a session identifier for the communication session between the partner platform and the exchange platform to track communications exchanged during the registration session. For example, the session identifier may include a unique number, string, etc., used to authenticate information exchanged during the registration session. The exchange platform may utilize the connection service and / or the partner service to establish the registration session. For example, in response to a registration initialization request, the partner service may call another service, such as the connection service, to establish a communication session that can be used by the client-side widget to provide an interface between the user and the 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 initialize the client-side widget through an instance of the partner application on the client device. Once the partner application receives the session identifier, the partner application may launch (e.g., execute, initialize, etc.) the client-side widget. The user may then interact with the widget to complete the registration process 600.

[0202] In some embodiments, process 600 includes determining and providing a member list for the user at step / operation 608. 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 the user's list of service providers from a network of service providers associated with the exchange platform (e.g., registered with it, etc.). In some examples, the list of service providers can include every service provider platform associated with the exchange platform. Additionally or alternatively, the list of service providers can include a subset of related service provider platforms tailored for the user.

[0203] For example, the exchange platform may determine one or more service provider platforms based at least in part on user attributes of a registration session and customize a service provider list for the one or more service provider platforms. For example, the exchange platform may include multiple system user data objects and / or system tool data objects, as described herein. 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 manner, the exchange platform may determine one or more service providers associated with the user based on one or more system user data objects.

[0204] Additionally or alternatively, the exchange platform (e.g., one or more of its service provider services) may provide a presence request for user presence data from each service provider platform in the member platform network (e.g., via a service provider interface). The user presence request may include one or more user attributes of the user (e.g., encrypted attributes, hashed attributes, etc.), which the service provider platform may utilize to determine whether the user possesses 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 data from one or more of the service provider platforms indicating the presence of the tool on each service provider platform. The exchange platform (e.g., its partner service) may determine one or more service providers based, at least in part, on the presence data.

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

[0206] Next, the registration process 600 may continue to the second stage, in which, as shown in FIG. Figure 6B As described in further detail, a tool identifier corresponding to a user is identified through interaction between the exchange platform, the user, and the service provider platform.

[0207] Now refer to Figure 6B , Figure 6BThis flowchart illustrates an example of the second stage of a registration process 600 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 flowchart describes communication techniques that overcome various limitations of traditional registration systems by circumventing their reliance on user-provided permanent credentials (e.g., card numbers, etc.). These communication techniques can be implemented by one or more computing devices, entities, and / or systems described herein (e.g., an exchange platform) to establish a connection between the user, the partner platform, and the service provider tool.

[0208] In some embodiments, process 600 includes determining and providing a service provider tool list for the user at step / operation 610. The service provider tool list can be determined based at least in part on the selection of 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 selection of a particular service provider 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 the partner interface). The tool registration request can include a session identifier and / or a service provider identifier indicating the selected service provider.

[0209] 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 provided by the selected service provider platform for the user. 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 of the tool data objects may include a system user identifier corresponding to the user.

[0210] 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 the exchange platform with service provider-tool data indicating the one or more tool references and / or one or more corresponding tool representations.

[0211] 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 using a partner interface and via a registration user interface, based at least in part on the service provider-tool data. The tool registration screen may be internally defined by the 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 the selected service provider. For example, 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.

[0212] In some embodiments, process 600 includes receiving selection data at step / operation 612. For example, the selection data may indicate a selection of a service provider tool from a registration user interface. For example, the selection data may identify a service provider tool from a list of service provider tools associated with the user. Additionally or alternatively, the selection data may indicate confirmation of a single service provider tool associated with the user.

[0213] For example, the exchange platform may use the partner interface to receive a registration tool with an account request from a client-side widget. The request may include selection data and / or a session identifier. The selection data may indicate a selection of a service provider tool from the registration user interface. For example, the selection data may indicate an instrument representation (e.g., the last four digits of an account, an account nickname, etc.) of the selected service provider tool. In some examples, the selection data may include at least one of an instrument type, a currency type (e.g., in a financial value system), and / or an instrument identifier (e.g., an instrument representation, etc.) corresponding to the selection.

[0214] In some embodiments, the client-side widget can be configured to authenticate the user before initiating a registration tool with an account request. For example, the client-side widget can be configured to generate a user verification prompt based at least in part on the user data. The user verification prompt indicates a request for confirmation of at least a portion of the user data. In some examples, the widget can be configured to present the user verification prompt to the user. In some embodiments, the exchange platform can initiate presentation of the user verification prompt using a partner interface. In response to user input indicating confirmation of at least a portion of the user data (e.g., one or more user attributes, etc.), the widget can provide the registration tool with the account request to the exchange platform.

[0215] In some embodiments, process 600 includes generating a match code at step / operation 614. In some examples, the exchange platform (e.g., its connection service, partner service, etc.) can generate the match code. In some examples, the match code can be generated in response to user input indicating confirmation of at least a portion of the user data and / or a registration tool with an account request indicating such confirmation. The exchange platform (e.g., its connection service, partner service, etc.) can generate the match code for authenticating the user.

[0216] In some embodiments, a match code is a session unique identifier for authorizing a registration session between one or more entities. For example, a match code may include a sequence of numbers, alphanumerics, and / or similar characters that may be provided to multiple entities to ensure that each of the multiple entities is involved in the same communication sequence. For example, a match code may include a sequence of one or more different characters of dynamic length (e.g., six, eight characters, etc.) that may be generated by an exchange platform, provided to a service provider platform, and then received from a partner platform to ensure that the exchange platform, the service provider platform, and the partner platform are each interacting with the same end user (e.g., by comparing the received match code to the generated match code described herein). The one or more different characters may include one or more alphanumerics, emoticons, Chinese characters, wingdings, etc.

[0217] In some embodiments, process 600 includes providing a registration request with a matching code to a service provider platform corresponding to the service provider tool at step / operation 616. 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 service provider tool using a service provider interface. The registration request may include service provider registration data indicating the matching code, one or more user identifiers of the user, and / or one or more tool identifiers of the service provider tool. In response to the registration request, the service provider platform may use the one or more identifiers to authenticate the service provider tool.

[0218] For example, the service provider registration data may include one or more identifiers for referencing the service provider tool in communications between the exchange platform, the service provider platform, and / or the partner platform, without using the service provider tool's permanent credentials (e.g., card number, 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 tool through one or more redundancy 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.

[0219] The service provider registration data may include any combination of references, keys, and / or identifiers 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 changeable based on the communication scheme. In this way, the specific combination of identifiers provided in the registration request may be used as an additional validation check to ensure that the registration request is received from the relevant platform (e.g., an exchange platform).

[0220] The service provider can compare the identifier from the registration request with one or more member data objects (e.g., member tool data object, member user data object, etc.) to identify the service provider tool corresponding to the registration request without exposing the permanent credentials of the service provider tool.

[0221] In some embodiments, process 600 includes receiving a match code from a partner platform at step / operation 618. For example, the exchange platform may use a partner API to receive an authentication message including a match code and / or a session identifier. The authentication message may be received from the partner platform in response to user input to a registration user interface.

[0222] The exchange platform can compare the matching code with a previously generated matching code to authenticate the user. For example, the service provider platform can be configured to provide the matching code to the user via one or more pre-existing communication protocols between the service provider platform and the user (e.g., via a service provider application, a registered phone number, an email address, etc.). When the exchange platform receives the matching code from the partner platform, the exchange platform can authenticate that the user interacting with the partner platform is an authorized user of the service provider.

[0223] In some examples, the exchange platform can use the partner interface to initiate presentation of an authentication user screen through a registration user interface. Substantially simultaneously, the service provider platform can provide a matching code to the user (e.g., via a client device and / or other preconfigured means). The user can enter the matching code (e.g., received from the service provider platform) through the authentication user screen, and the partner platform can forward the matching code to the exchange platform. The exchange platform can use the partner interface to receive an authentication message based at least in part on the user input to the authentication user screen.

[0224] In some embodiments, the exchange platform authenticates the registration session in response to authenticating the user based at least in part on the matching code. Figure 6C As further described in detail, upon successful registration, control is passed back to the partner application running on the client device, which requests the UUEK.

[0225] Now refer to Figure 6C , Figure 6C is a flowchart illustrating an example of the third stage of a registration process 600 for issuing a UUEK to facilitate credential-free value exchange. The flowchart describes a communication technique that overcomes various limitations of traditional registration systems by circumventing their reliance on user-provided instrument references (e.g., card numbers, etc.). The communication technique can be implemented by one or more computing devices, entities, and / or systems described herein (e.g., an exchange platform) to establish a user instrument record for registering a user with the exchange platform.

[0226] In some embodiments, process 600 includes, at step / operation 620, verifying the registration session based at least in part on the session identifier. For example, the exchange platform may receive, via a partner interface, a session exchange request to exchange the session identifier for a UUEK. The session exchange request may include the session identifier and a member tool reference to a service provider tool. The member tool reference may include a partner-specific reference to the service provider tool. The exchange platform (e.g., its partner service) may receive the session exchange request, verify (e.g., via its connection service, partner service, etc.) the session identifier by comparing it to a previously generated session identifier, and verify the registration session in response to a match.

[0227] In some embodiments, process 600 includes generating a UUEK at step / operation 622. For example, the exchange platform can generate the UUEK in response to verification of the registration session. For example, the exchange platform can generate UUEKs corresponding to the user, the service provider tool, and the partner platform. As described herein, the exchange platform can store the UUEK in a partner-specific exchange data object that associates the UUEK with the exchange identifier, the tool key, and the partner-specific tool reference.

[0228] In some embodiments, process 600 includes providing the UUEK to the partner platform at step / operation 624. 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.). For example, 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, etc.

[0229] Figure 7A -D provides instructions and Figure 6A -C related message flow diagram of the steps / operations for establishing cross-entity relationships. It should be recognized that these steps / operations can be as follows Figure 6A -C to execute the corresponding steps / operations. Usually, Figure 7A -B shows the steps / operations of establishing a secure communication session with a user through a partner application that may be applicable to Figure 6A steps / operations and / or Figure 6A For example, Figure 7A The steps / operations shown in -B may correspond to and / or be related to certain operations of the first phase of the registration process 600 for registering a service provider tool with a partner platform without exposing permanent credentials associated with the user and / or the service provider tool.

[0230] At step / operation 702, partner application 416 retrieves a widget (e.g., a set of instructions such as a JavaScript widget) from connection service 408. At step / operation 704, connection service 408 returns the widget and creates a session. In various embodiments, step / operation 704 is performed in response to step / operation 702.

[0231] At step / operation 706, partner application 416 initializes the widget using partner platform 420 (e.g., a host, etc.). At step / operation 708, partner platform 420 initializes the widget by calling a widget initialization function of partner service 410 using a partner interface (e.g., an initialize widget call, etc.). In some examples, the widget initialization call may include user data (e.g., one or more user attributes). At step / operation 710, partner service 410 retrieves and initializes the widget using a partner interface (e.g., an initialize widget call, etc.) by calling connection service 408. In various embodiments, step / operation 710 is performed in response to step / operation 708.

[0232] At step / operation 712, connection service 408 stores the partner identifier corresponding to partner platform 420. At step / operation 714, connection service 408 stores the user's user data. At step / operation 716, connection service 408 generates a session identifier to identify the communication session between the partner and the exchange platform. At step / operation 718, connection service 408 provides the session identifier to partner service 410. At step / operation 720, partner service 410 returns the session identifier to partner platform 420. Furthermore, at step / operation 722, partner platform 420 returns the session identifier to partner application 416. In various embodiments, when step / operation 722 is performed, the communication session may be initialized.

[0233] Go to Figure 7B At step / operation 728, partner application 416 executes widget 724 and transfers control to widget 724 to continue the registration process. Widget 724 is provided with a session identifier and user data. At step / operation 730, widget 724 sets the session identifier. At step / operation 732, widget 724 sets the user data. At step / operation 734, widget 724 uses the partner interface to request a public key from connection service 408. At step / operation 736, connection service 408 returns the public key to widget 724. At step / operation 738, widget 724 uses the partner interface to request a list of service providers from connection service 408. And, at step / operation 740, connection service 408 returns the list of service providers. In some examples, at step / operation 742, widget 724 returns the list of service providers to partner application 416 for presentation to the user (e.g., via a client device).

[0234] Go to Figure 7C After establishing a secure communication session with the partner application, the registration process can continue to Figure 7C The steps / operations shown in the second stage. Generally, Figure 7CThe steps / operations shown in the Figure 6B For example, Figure 7C The steps / operations shown in may be equivalent to and / or related to certain operations of the second phase of the registration process 600 for registering a service provider tool with a partner platform without exposing permanent credentials associated with the user and / or the service provider tool.

[0235] At step / operation 744, partner application 416 receives input from a service provider indicating a list of service providers and sends the service provider identifier to widget 724. At step / operation 746, widget 724 uses a partner interface (e.g., a widget registration tool initiation call, etc.) to send a request to connectivity service 408 to initiate registration of a service provider tool with the service provider platform. This request may include a service provider identifier (e.g., a service provider partition, etc.). At step / operation 748, connectivity service 408 uses a partner interface (e.g., a widget registration tool initiation call, etc.) to request a list of tools corresponding to the user and the service provider. At step / operation 750, service provider service 412 returns the tool list to connectivity service 408. At step / step 752, connectivity service 408 returns the tool list to widget 724, which may provide the user with a pre-registration screen indicating the tool list (e.g., one or more tool representations thereof).

[0236] At step / operation 754, widget 724 receives input indicating a service provider tool (e.g., a tool representation, etc.). At step / operation 756, widget 724 confirms the user data with the user (e.g., through one or more user verification screens, etc.). At step / operation 758, widget 724 provides a request to register the service provider tool with connection service 408 using a partner interface (e.g., a widget registration tool with an account call, etc.). In various embodiments, step / operation 758 is performed in response to confirmation of the user data at step / operation 756.

[0237] At step / operation 760, the connection service 408 generates a match code. At step / operation 762, the connection service 408 provides a request to register the service provider tool to the service provider service 412 using a partner interface (e.g., a widget registration tool with an account call, etc.). This request may include the match code and session identifier. At step / operation 764, the service provider service 412 provides a request to register the service provider tool to the service provider platform 440 using a service provider interface (e.g., a register user tool call, etc.). This request may include a tool reference, user reference, user key, tool key, and / or match code. The service provider platform 440 may register the service provider tool and, at step / operation 766, provide a registration success response to the service provider service 412 using the service provider interface. At step / operation 768, the service provider service 412 provides data indicating the registration success response to the connection service 408. At step / operation 770, the connection service 408 provides data indicating the registration success response to the widget 724.

[0238] Meanwhile, the service provider platform 440 provides the user with a pairing code using one or more pre-existing communication channels at step 772. The user can access the pairing code and, at step 774, enter the pairing code into a verification interface presented by the widget 724.

[0239] At step / operation 776, widget 724 provides a registration complete response to connection service 408 using the partner interface. In various embodiments, step / operation 776 is performed in response to confirmation of the matching code provided at step / operation 774.

[0240] At step / operation 778, the connection service 408 provides a response indicating successful registration to the widget 724. At step / operation 780, the widget 724 provides data indicative of the response to the partner application 416.

[0241] Go to Figure 7D After authorizing the user based at least in part on confirmation of the matching code as described above, the registration process may continue as follows: Figure 7D The steps / operations shown are the third stage. Generally speaking, Figure 7D The steps / operations shown in the Figure 6C For example, Figure 7D The steps / operations shown in may correspond to and / or be related to certain operations of the third phase of the registration process 600 for registering a service provider tool with a partner platform without exposing permanent credentials associated with the user and / or the service provider tool.

[0242] At step / operation 782, partner application 416 provides data indicating successful registration to partner platform 420. At step / operation 784, partner platform 420 provides a key request to partner service 410 using the partner interface. At step / operation 786, partner service 410 verifies the communication session by providing a session identifier to connection service 408. Connection service 408 compares the session identifier with the identifier issued to initiate the communication session and, if the identifiers match, provides data indicating the verified session to partner service 410 at step / operation 788.

[0243] At step / operation 790, partner service 410 generates a UUEK for the partner and exchanges the UUEK for a session identifier. At step / operation 792, partner service 410 uses the partner interface to provide the UUEK to partner platform 420. At step / operation 794, partner platform 420 may provide an indication of successful registration to partner application 416. In some examples, the indication of successful registration may include a representation of the UUEK, such as a barcode, QR code, and / or the like, for representing the UUEK to the user.

[0244] Thus, having described various operations, processes, methods, functionality, etc., for registering a user for credential-free exchange, various user interface screens for controlling, initiating, executing, and / or the like steps / operations are provided and described. In various embodiments, the user interface screens provided and described herein are configured to be provided via a user interface of a client device 104.

[0245] Figure 8A -F provides an example user interface flow configured for the client device 104. The user interface flow may include multiple user interface screens that may be configured to guide the user through a credential-free registration process to facilitate credential-free exchanges between a partner platform and a service provider platform. In some examples, these transactions may be managed through a user account on the partner platform. For example, Figure 8A The user interface screen 802 includes an account setup screen for entering user attributes 804 for a user account. The user interface screen 802 may include a selectable account creation icon 806 for initiating the account creation process. Additionally or alternatively, a user may register with a partner platform via an exchange screen. For example, Figure 8B The user interface screen 808 includes a registration setting screen for inputting one or more user attributes 804 through a widget executed by a partner application. Figure 8B The user interface screen 808 may include an optional registration navigation 810 for proceeding to the next step in the registration process.

[0246] Steps of the registration process may include selecting a service provider, with the user having a service provider tool that can register with the partner platform. Figure 8C User interface screen 812 can facilitate selection of a service provider by providing a list of service providers 814 with selectable icons. In some examples, the list of service providers 814 can be automatically matched to the user's available user attributes (e.g., provided via one or more previous user interface screens). For example, the list of service providers 814 can be customized for the user and, in some examples, can be proactively limited to service providers associated with the user. As shown in user interface screen 812, service providers can include financial institutions (e.g., banks, etc.) that provide value exchange services. This is provided as an example only. As described herein, the techniques of this disclosure can be applied to any value exchange system.

[0247] After selecting a service provider, the user may be directed to another user interface screen (not shown) for selecting a service provider's service provider tool. Once selected, the exchange platform may perform a registration process to register the service provider tool with the partner platform. During the registration process, the user may be switched to Figure 8D The user interface screen 816 may include a verification prompt 818 for entering a matching code. Figure 8E As shown in the user interface screen 820 of FIG, the matching code is automatically provided to the user via information 822 from the service provider platform. The user can answer the verification prompt 818 by entering the matching code and select the submit icon 824 to complete the registration process. The next screen, Figure 8F A user interface screen 826 of the UUEK may be displayed to the user for displaying a UUEK representation 828 of the UUEK. For example, the UUEK representation 828 may include a scannable representation of the UUEK (e.g., a barcode, a QR code, a non-replaceable token, a near field communication sequence, etc.). The scannable representation may be saved to a partner account on the partner platform to enable the user to perform value-based transactions using the service provider tool without having to reference the permanent credentials of the service provider tool.

[0248] Figure 9A process flow for facilitating credential-free value exchange according to one or more embodiments of the present disclosure is provided. The process flow describes a communication and data encryption process 900 for securely authorizing exchanges in a value-agnostic exchange using a UUEK. As described herein, process 900 can be utilized to overcome various limitations of traditional exchange systems that expose sensitive and permanent credentials to multiple third parties. Process 900 can be implemented by one or more computing devices, entities, and / or systems described herein. For example, through the various steps / operations of process 900, an exchange platform can utilize communication and data encryption techniques to overcome various limitations of traditional exchange mechanisms by eliminating the reliance on static, sensitive credentials.

[0249] Figure 9 An example process 900 is shown for explanation purposes. Although example process 900 depicts a particular order of steps / operations, this 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 process 900. In other examples, different components of an example device or system implementing process 900 may perform functions substantially simultaneously or in a particular order.

[0250] In some examples, process 900 Figure 6A -C begins after the registration process 600, where the user and / or partner platform can receive a UUEK to facilitate a credential-free value exchange. However, process 900 can also be performed before the registration process 600. For example, the user can obtain a UUEK directly from the service provider platform without completing the partner platform registration process. If the registration process 600 is completed, the partner platform can use the partner interface and the UUEK specific to the partner platform to facilitate the value-based exchange, otherwise the partner platform can use the UUEK specific to and provided by the service provider platform to facilitate the value-based exchange.

[0251] For example, when a user wishes to engage in a value-based exchange with a partner with whom the user has a registered partner account, the partner platform may look up the registered partner account and identify the user's issued UUEK from the partner account for use in authorizing the value-based exchange. If the user wishes to engage in a value-based exchange with a partner without a registered partner account, the user may present a previously issued UUEK (e.g., issued to a service provider platform, etc.) to the partner platform (e.g., via a partner application, etc.), and the partner platform may use the UUEK to authorize the value-based exchange.

[0252] The partner platform can generate an exchange request data object for executing a value-based exchange based at least in part on a UUEK for a specific use case (e.g., a partner UUEK when the user has a registered account, a service provider UUEK when the user does not have a registered account, etc.). The exchange request data object can include request data identifying the UUEK of the requested value-based exchange and transaction attributes. Process 900 can begin when the partner platform issues an exchange request based on the exchange request data object.

[0253] In some embodiments, process 900 includes receiving an exchange request with a UUEK at step / operation 902. For example, an exchange platform (e.g., its partner service, etc.) may use a partner interface to receive an exchange request for performing a value-based exchange. The exchange request may indicate the UUEK and / or one or more transaction attributes.

[0254] The transaction attributes may indicate one or more characteristics of the requested exchange. For example, the one or more transaction attributes may include at least one transaction attribute indicating the transaction value (e.g., a shopping cart amount, etc.). For example, the transaction value may include the sum of one or more line items in a financial transaction, including one or more modifiers (e.g., taxes, discounts, etc.). Taking a financial-based value system as an example, in some examples, the transaction attributes may include (i) an order number, (ii) one or more line item attributes, including sequence, line item group, product code, description, quantity, unit-item, grams, kilograms, etc., unit amount, unit tax amount, line amount (e.g., the amount of the line item), line tax amount, etc., and / or (iii) one or more line item adjustments, including sequence, adjustment type (e.g., manufacturer discount, store discount, return, cash payment, gift card payment, other payment, etc.), product code, description, quantity, unit-item, grams, kilograms, etc., unit amount, unit tax amount, line amount (e.g., the amount of the line item), line tax amount, etc.

[0255] Additionally or alternatively, transaction attributes may include request permission type (e.g., full or partial), partner transaction reference (e.g., transaction reference of the partner platform), channel (e.g., currency exchange type of financial value system, such as push or pull value transfer, real-time payment, etc.), currency (e.g., for the financial value system, etc.), organization key (e.g., platform identifier of the partner organization), organization category (e.g., airline, apparel, etc.), institution key (e.g., platform identifier of a retail location, etc.), employee identifier and / or any other traceable information of the value-based exchange.

[0256] In some embodiments, process 900 includes validating the UUEK at step / operation 904. For example, the exchange platform (e.g., its partner service) can look up the UUEK to identify a matching identifier from the platform database 414. For example, the UUEK can include an exchange identifier corresponding to an exchange data object. The exchange platform can identify the exchange identifier based at least in part on the UUEK and use the exchange identifier to identify the corresponding exchange data object.

[0257] As described herein, a UUEK may correspond to a partner platform and / or a service provider platform. For example, where the UUEK is issued to a partner platform, the UUEK may include a partner partition that identifies the partner platform. In this case, the UUEK includes an exchange identifier that corresponds to a partner exchange data object. As another example, where the UUEK is issued to a service provider platform, the UUEK may include a service provider partition that identifies the service provider platform. In this case, the UUEK includes an exchange identifier that corresponds to a service provider exchange data object. In some examples, the exchange platform may process the UUEK based on entity partitioning.

[0258] In some embodiments, the exchange platform (e.g., its partner service, etc.) receives a UUEK that includes a partner partition that identifies the partner platform. The exchange platform can use the exchange identifier to identify the partner-specific exchange data object. The partner-specific exchange data object may include a tool key for a service provider tool corresponding to a member platform. The exchange platform can identify a system tool data object based on the tool key. For example, the exchange platform can identify a member platform based on the entity partition of the tool key and provide the tool key to a service corresponding to the member platform (e.g., a service provider service, etc.). The service can identify the system tool data object based on the tool key. The system tool data object can then be used to identify one or more identifiers (e.g., a user identifier, a tool identifier, etc.) to process the exchange request.

[0259] In some embodiments, an exchange platform (e.g., its partner service, etc.) receives a UUEK that includes a service provider partition that identifies a service provider platform. The exchange platform (e.g., its partner service, etc.) may determine that a partner-specific exchange data object is unavailable. In response to this determination, the exchange platform may identify a member platform based on the service provider partition and provide the UUEK to a service corresponding to the member platform (e.g., a service provider service, etc.). The service may identify the service provider-specific exchange data object based at least in part on the exchange identifier of the UUEK. Based on the member platform and the exchange identifier, the service provider-specific exchange data object may be utilized to identify a system tool data object. The system tool data object may then be utilized to identify one or more identifiers (e.g., a user identifier, a tool identifier, etc.) to process the exchange request.

[0260] In some examples, the exchange platform may perform one or more validation actions on the UUEK. For example, the exchange data object may include one or more exchange attributes indicating an expiration status. In some examples, the expiration status may indicate (i) whether the UUEK has been previously used to authorize a value-based exchange and / or (ii) a validity period for which the UUEK may be valid. The validation actions may include identifying an expiration status corresponding to the UUEK and validating the UUEK based at least in part on the expiration status. For example, the exchange platform may validate the UUEK if the expiration status indicates that (i) the UUEK has not been previously used to authorize a value-based exchange and / or (ii) the UUEK has been presented within the validity period.

[0261] In some examples, the verification action may include verifying whether the sender of the UUEK is related to the original entity to which the UUEK was issued. In some examples, the UUEK may include an entity partition that indicates the original entity to which the UUEK was issued (e.g., a member platform such as a partner or service provider platform). The exchange platform may use the entity partition of the UUEK to determine the entity corresponding to the UUEK (e.g., the original entity). In some examples, the verification action may include verifying whether the sender of the exchange request matches and / or is related to the original entity of the UUEK. In response to determining that the sender is the original entity, the exchange platform may verify the UUEK.

[0262] In the event that the UUEK is verified, process 900 may continue to step / operation 906. Otherwise, process 900 may continue to step / operation 914, where the exchange platform provides an error response to the partner platform using the partner interface.

[0263] In some embodiments, process 900 includes requesting exchange authorization from the member platform at step / operation 906. For example, the exchange platform (e.g., its service provider service) can request exchange authorization from the service provider platform of the service provider tool associated with the UUEK. In some examples, the exchange platform (e.g., its partner service) can identify the member platform based at least in part on the UUEK (e.g., its entity partition). Additionally or alternatively, the exchange platform (e.g., its service provider service) can identify the service provider tool based at least in part on the UUEK (e.g., the exchange identifier).

[0264] The exchange platform (e.g., its service provider service) can provide an exchange authorization request to the member platform using the service provider interface. The exchange authorization request can indicate at least one of one or more transaction attributes and / or an instrument identifier of a service provider instrument. For example, the exchange platform can generate the exchange authorization request based on a system instrument data object identified from one or more aspects of the UUEK. The exchange authorization request can include an instrument key and / or an instrument reference from the system instrument data object.

[0265] 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 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 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 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.

[0266] Additionally or alternatively, the transaction authorization request may indicate an exchange identifier. For example, the exchange platform may generate a transaction identifier representing a value-based exchange and provide the transaction identifier to the member platform.

[0267] In some embodiments, process 900 includes receiving an exchange authorization response at step / operation 908. For example, the exchange platform (e.g., its service provider service) may receive the exchange authorization response using a service provider interface, the 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., causing the transaction to be approved, etc.), otherwise the exchange may be rejected (e.g., causing the transaction to be rejected).

[0268] In some examples, the exchange authorization response may indicate one or more response attributes. The response attributes may include one or more error codes, etc., for characterizing the exchange authorization response.

[0269] The exchange platform may generate a transaction record for the value-based exchange based at least in part on the exchange authorization request and / or the exchange authorization response. In some examples, the transaction record may include a transaction identifier, one or more transaction attributes, one or more response attributes, the 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 transaction record in a platform database in association with the one or more instrument and / or user identifiers.

[0270] In some embodiments, process 900 includes optionally generating a replacement UUEK at step / operation 910. For example, the exchange platform may automatically generate a replacement UUEK to replace the received UUEK.

[0271] In some examples, this may include (i) invalidating the received UUEK for future authorization requests and / or (ii) generating a replacement UUEK. For example, the exchange platform may modify the expiration status of the UUEK, rendering the UUEK invalid for subsequent value exchanges. Additionally or alternatively, the exchange platform may move, delete, and / or otherwise modify the exchange data object corresponding to the UUEK to invalidate the UUEK. The replacement UUEK may include a new unique exchange identifier (e.g., a different universally unique identifier) ​​corresponding to the service provider tool to replace the invalidated exchange identifier. In this way, the UUEK can be continuously modified and changed as users complete exchanges on different platforms, thereby limiting the exposure of users and platforms to malicious parties.

[0272] In some embodiments, process 900 includes providing an exchange response to the member platform at step / operation 912. For example, the exchange platform (e.g., its partner service) may provide an exchange response to the member platform (e.g., partner platform, etc.) using a partner interface. 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 transaction 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 the replacement UUEK.

[0273] Figure 10 and 11 One or more embodiments of the present disclosure are provided, illustrating Figure 9 Message flow diagram of the steps / operations involved in facilitating a credential-free value exchange. It will be appreciated that these can be Figure 9 For example, Figure 10 A first message flow is shown for facilitating a credential-free exchange through a registered partner account, and Figure 11 A second message flow is shown that facilitates a credential-less exchange without a registered partner account.

[0274] In the first message flow, at step / operation 1004, a user initiates a transaction through a registered partner account. At step / operation 1006, partner platform 420 retrieves the user's UUEK to execute the transaction on the user's behalf. At step / operation 1008, partner platform 420 uses a partner interface to provide an exchange request to at least one of the plurality of partner services 410 corresponding to the exchange platform of partner platform 420. The exchange request may indicate the UUEK and / or one or more transaction attributes of the value-based exchange.

[0275] At step / operation 1010, partner service 410 looks up the partner-specific transaction token (e.g., in a partner-specific data store, such as a portion of a platform database, etc.) to determine the member platform corresponding to the UUEK (e.g., by mapping to a service provider partition, etc.). At step / operation 1012, partner service 410 provides data indicative of the exchange request to service provider service 412 of the exchange platform corresponding to the member platform.

[0276] At step / operation 1014, the service provider service 412 verifies the UUEK (and / or its exchange identifier). At step / operation 1016, the service provider service 412 provides an exchange authorization request to the service provider platform 440 using the service provider interface. The exchange authorization request may include one or more keys (e.g., user keys, tool keys, etc.), references (e.g., tool references, user references, etc.), and / or one or more transaction attributes.

[0277] At step / operation 1018, the service provider platform 440 approves the transaction and provides an exchange authorization response to the service provider service 412 using the service provider interface. At step / operation 1020, the service provider service 412 records the value-based exchange associated with one or more keys (e.g., user keys, tool keys, etc.), references (e.g., tool references, user references, etc.). At step / operation 1022, the service provider service 412 provides the exchange authorization response to the partner service 410. At step / operation 1024, the partner service 410 provides the exchange response to the partner platform 420 using the partner interface.

[0278] In the second message flow, at step / operation 1102, user 1002 initiates a transaction by presenting a UUEK (and / or a representation of its UUEK) to partner platform 420. At step / operation 1104, partner platform 420 uses a partner interface to provide an exchange request to partner service 410 corresponding to the exchange platform of partner platform 420. The exchange request may identify the UUEK and / or one or more transaction attributes for a value-based exchange.

[0279] At step / operation 1106, partner service 410 looks up the exchange identifier (e.g., in a partner-specific data store, such as part of a platform database, etc.) to determine if an exchange data object exists. If no exchange data object exists, partner service 410 provides the UUEK to service provider service 412 of the exchange platform corresponding to the service provider platform identified from the UUEK at step / operation 1108.

[0280] At step / operation 1110, the service provider service 412 verifies the exchange identifier of the UUEK. At step / operation 1112, the service provider service 412 provides an exchange authorization request to the service provider platform 440 using the service provider interface. The exchange authorization request may include one or more keys (e.g., user keys, tool keys, etc.), references (e.g., tool references, user references, etc.), and / or one or more exchange attributes.

[0281] At step / operation 1114, the service provider platform 440 approves the exchange and provides an exchange authorization response to the service provider service 412 using the service provider interface. At step / operation 1116, the service provider service 412 records the transaction in association with one or more keys (e.g., user keys, tool keys, etc.), references (e.g., tool references, user references, etc.). At step / operation 1118, the service provider service 412 provides an exchange authorization response indicating the response to the partner service 410. At step / operation 1120, the partner service 410 provides an exchange response to the partner platform 420 using the partner interface.

[0282] Having described various operations, processes, methods, functions, etc., for processing exchanges on behalf of a user, various user interface screens for controlling, initiating, executing, and / or similar steps / operations are provided and described above. In various embodiments, the user interface screens provided and described herein are configured to be provided via a user interface of a client device 104.

[0283] Figure 12A -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 and permanent credentials to a service provider tool used to perform the value-based exchange. Figure 12A As shown, the no-credentials exchange process can begin when the user selects a payment method from the partner application's transaction processing screen 1202. After selecting a payment method provided by the exchange platform, the user can switch to a payment method such as Figure 12B Tool selection screen 1204 is shown. Tool selection screen 1204 may include a plurality of selectable tool icons 1206, each of which may be associated with a UUEK issued by the exchange platform using the various techniques described herein. A user may perform an exchange by selecting one or more selectable tool icons 1206.

[0284] In some examples, in response to the selection, a scanning screen 1208 for an in-store transaction may be provided. The scanning screen 1208 may present a scannable UUEK representation 1210 corresponding to the UUEK. The user may scan the scannable UUEK representation 1210 to complete the value-based exchange. Additionally or alternatively, in an online setting, the user may transition to a verify user screen 1212 to provide a personal identification number (PIN) associated with the service provider tool. The user may enter the PIN to complete the transaction.

[0285] VI. Conclusion

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

Claims

1. A computer-implemented method for voucherless value exchange, comprising: initiating, by one or more processors and using a partner interface, presentation of a registration user interface via a client device of a user, wherein the registration user interface includes a tool registration screen indicative of one or more service provider tools associated with the user; receiving, by the one or more processors and using the partner interface, selection data indicating a selection of a service provider tool from the registration user interface; generating, by the one or more processors, a matching code for authenticating a user; providing, by the one or more processors and using a service provider interface, a registration request to a service provider platform corresponding to the service provider tool, wherein the registration request includes service provider registration data indicating the matching code, a user identifier of the user, and a tool identifier of the service provider tool; receiving, by the one or more processors and using the partner interface, an authentication message including the matching code; and In response to authenticating the user based on the matching code, (i) generating, by the one or more processors, a UUEK universally unique temporary key for the user, wherein the UUEK corresponds to the user, the service provider tool, and the partner platform; and (ii) providing the UUEK to the partner platform by the one or more processors and using the partner interface.

2. The computer-implemented method of claim 1 , wherein: The user identifier of the user includes a user reference of the service provider platform and a user key corresponding to the user reference.

3. The computer-implemented method of claim 1 , wherein: The tool identifier of the service provider tool includes a tool reference of the service provider platform and a tool key corresponding to the tool reference.

4. The computer-implemented method of claim 3, wherein: The selection data indicates a tool representation corresponding to the tool reference.

5. The computer-implemented method of claim 1 , wherein: Initiating presentation of the registration user interface includes: initiating presentation of a pre-registration screen via a registration user interface using a partner interface, the pre-registration screen indicating one or more service providers associated with the exchange platform; receiving, using the partner interface, pre-selection data indicating selection of a particular service provider from among the one or more service providers; receiving service provider-tool data based at least in part on the preselection data, wherein the service provider-tool data indicates one or more service provider tools for the user; and Presentation of the tool registration screen is initiated using the partner interface and via the registration user interface based at least in part on the service provider-tool data, wherein the tool registration screen indicates a respective tool representation for each of one or more service provider tools.

6. The computer-implemented method of claim 5, wherein: Initiating presentation of the pre-registration screen includes: receiving, via the partner interface, a communication session request for the user, wherein the communication session request includes one or more user attributes; generating a session identifier for a communication session between the partner platform and the exchange platform; determining the one or more service providers based at least in part on the one or more user attributes; and Presentation of a pre-registration screen is initiated based at least in part on the one or more service providers using the partner interface and via the registration user interface.

7. The computer-implemented method of claim 1 , wherein: The matching code includes a sequence of one or more different characters.

8. The computer-implemented method of claim 1 , wherein: The client device is configured to access a partner application hosted by the partner platform and present the registration user interface to the user using the partner application.

9. The computer-implemented method of claim 1 , wherein: The service provider platform is configured to provide the matching code to the user, and wherein receiving the authentication message comprises: initiating presentation of an authenticate user screen using the partner interface and via the registration user interface; and The authentication message is received based at least in part on user input to the authenticate user screen using the partner interface.

10. A computing system for voucherless value exchange, comprising a memory and one or more processors communicatively coupled to the memory, the one or more processors configured to: Using the partner interface, initiating presentation of a registration user interface via the user's client device, wherein The registration user interface includes a tool registration screen indicating one or more service provider tools associated with the user; receiving, using the partner interface, selection data indicating selection of a service provider tool from the registration user interface; Generate a matching code for authenticating the user; providing, using a service provider interface, a registration request to a service provider platform corresponding to the service provider tool, wherein the registration request includes service provider registration data indicating the matching code, a user identifier of the user, and a tool identifier of the service provider tool; Using the partner interface, receiving an authentication message including the matching code; and In response to authenticating the user based on the matching code, (i) generating a universally unique temporary key (UUEK) for the user, wherein the UUEK corresponds to the user, the service provider tool, and the partner platform; and (ii) Using the partner interface, provide the UUEK to the partner platform.

11. The computing system of claim 10, wherein: The user identifier of the user includes a user reference of the service provider platform and a user key corresponding to the user reference.

12. The computing system of claim 10, wherein: The tool identifier of the service provider tool includes a tool reference of the service provider platform and a tool key corresponding to the tool reference.

13. The computing system of claim 12, wherein: The selection data indicates a tool representation corresponding to the tool reference.

14. The computing system of claim 10, wherein: Initiating presentation of the registration user interface includes: initiating presentation of a pre-registration screen via a registration user interface using a partner interface, the pre-registration screen indicating one or more service providers associated with the exchange platform; receiving, using the partner interface, pre-selection data indicating selection of a particular service provider from among the one or more service providers; receiving service provider-tool data based at least in part on the preselection data, wherein the service provider-tool data indicates one or more service provider tools for the user; and Presentation of the tool registration screen is initiated using the partner interface and via the registration user interface based at least in part on the service provider-tool data, wherein the tool registration screen indicates a respective tool representation for each of one or more service provider tools.

15. The computing system of claim 14, wherein: Initiating presentation of the pre-registration screen includes: receiving, via the partner interface, a communication session request for the user, wherein the communication session request includes one or more user attributes; generating a session identifier for a communication session between the partner platform and the exchange platform; determining the one or more service providers based at least in part on the one or more user attributes; and Presentation of a pre-registration screen is initiated based at least in part on the one or more service providers using the partner interface and via the registration user interface.

16. The computing system of claim 10, wherein: The matching code includes a sequence of one or more different characters.

17. The computing system of claim 10, wherein: The client device is configured to access a partner application hosted by the partner platform and present the registration user interface to the user using the partner application.

18. One or more non-transitory computer-readable storage media for voucherless value exchange, comprising instructions that, when executed by one or more processors, cause the one or more processors to: Using the partner interface, initiating presentation of a registration user interface via the user's client device, wherein The registration user interface includes a tool registration screen indicating one or more service provider tools associated with the user; receiving, using the partner interface, selection data indicating selection of a service provider tool from the registration user interface; Generate a matching code for authenticating the user; providing, using a service provider interface, a registration request to a service provider platform corresponding to the service provider tool, wherein the registration request includes service provider registration data indicating the matching code, a user identifier of the user, and a tool identifier of the service provider tool; Using the partner interface, receiving an authentication message including the matching code; and In response to authenticating the user based on the matching code, (i) generating a universally unique temporary key (UUEK) for the user, wherein the UUEK corresponds to the user, the service provider tool, and the partner platform; and (ii) Using the partner interface, provide the UUEK to the partner platform.

19. The one or more non-transitory computer-readable storage media of claim 18, wherein: The client device is configured to access a partner application hosted by the partner platform and present the registration user interface to the user using the partner application.

20. The one or more non-transitory computer-readable storage media of claim 18, wherein: The service provider platform is configured to provide the matching code to the user, and wherein receiving the authentication message comprises: initiating presentation of an authenticate user screen using the partner interface and via the registration user interface; and The authentication message is received based at least in part on user input to the authenticate user screen using the partner interface.

Images