# US 11,909,733 B1 · Systems, methods, and computing platforms for executing credential-less network-based communication exchanges > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,909,733 B1 - Document ID: US11909733B1 - Status: Granted - Kind: B1 - Application number: 18/491,191 - Filed: 2023-10-20 - Published: 2024-02-15 - Granted: 2024-02-20 - Earliest claimed: 2022-08-03 - Assignees: 1080 Network, Inc. - Applicants: 1080 Network, Inc. - Inventors: Christopher Michael Petersen; Tim Kuchlein - Web page: https://patentgrep.com/patent/US11909733B1 ## CPC - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - G06Q 20/385: {using an alias or single-use codes} - G06Q 20/401: {Transaction verification} - H04L 9/0819: {Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062)} - H04L 9/321: {involving a third party or a trusted authority} - H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Various embodiments of the present disclosure provide techniques for facilitating a credential-less exchange over a network using a plurality of identifier mapping and member interfaces. The techniques may include initiating the presentation of an enrollment user interface via a client device of a user and receiving selection data indicative of a selection of a service provider instrument from the enrollment user interface. The 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 an authentication of the user based on the matching code, the techniques may include generating an UUEK for the user that may be used to replace persistent credentials. ## Claims ### Claim 1 A computer-implemented method comprising: receiving, by one or more processors and using a partner interface, an exchange request for executing a value-based exchange, wherein the exchange request is indicative of a universally unique ephemeral key (UUEK) and one or more transaction attributes; identifying, by the one or more processors, an exchange identifier based at least in part on the UUEK, wherein the exchange identifier corresponds to an exchange data object that comprises an instrument identifier for a service provider instrument of a member platform; providing, by the one or more processors and using a service provider interface, an exchange authorization request to the member platform, wherein the exchange authorization request is indicative of the one or more transaction attributes and the instrument identifier; receiving, by the one or more processors and using the service provider interface, an exchange authorization response that is indicative of at least one of a transaction approval or a transaction denial; and providing, by the one or more processors and using the partner interface, an exchange response based at least in part on the exchange authorization response, wherein the exchange response is indicative of the transaction approval or the transaction denial. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the UUEK comprises a partner partition that identifies a partner platform, the instrument identifier comprises an instrument key for the member platform, and the computer-implemented method further comprises: identifying a system instrument data object based at least in part on the instrument key; and generating the exchange authorization request based at least in part on the system instrument data object. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein the UUEK comprises a service provider partition that identifies a service provider platform and the computer-implemented method comprises: identifying the member platform based at least in part on the service provider partition; identifying a system instrument data object based at least in part on the member platform and the exchange identifier; and generating the exchange authorization request based at least in part on the system instrument data object. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, wherein the exchange data object comprises one or more exchange attributes that are indicative of an expiration status, and the computer-implemented method further comprises: validating the UUEK based at least in part on the expiration status. ### Claim 5 (depends on 4) The computer-implemented method of claim 4 further comprising: modifying the expiration status to invalidate the UUEK. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, wherein the exchange authorization request is indicative of a user identifier corresponding to the exchange data object. ### Claim 7 (depends on 6) The computer-implemented method of claim 6, wherein the user identifier comprises a user key corresponding to a system user identifier and the instrument identifier comprises an instrument key corresponding to a system instrument identifier. ### Claim 8 (depends on 6) The computer-implemented method of claim 6 further comprising: generating a transaction record for the value-based exchange; and storing the transaction record in a platform data vault in association with the instrument identifier and the user identifier. ### Claim 9 (depends on 8) The computer-implemented method of claim 8, wherein the transaction record is indicative of a transaction identifier, the one or more transaction attributes, and the exchange authorization response. ### Claim 10 (depends on 1) The computer-implemented method of claim 1, wherein the one or more transaction attributes comprise at least one transaction attribute that is indicative of a transaction value, and wherein the exchange authorization response is based at least in part on a comparison between the transaction value and an asset availability of the service provider instrument. ### Claim 11 (depends on 1) The computer-implemented method of claim 1 further comprising: generating a replacement UUEK for the service provider instrument, wherein the exchange response is indicative of the replacement UUEK. ### Claim 12 (depends on 11) The computer-implemented method of claim 11, wherein the exchange response is provided to a partner platform, and wherein the partner platform is configured to replace the UUEK with the replacement UUEK. ### Claim 13 (depends on 12) The computer-implemented method of claim 12, wherein the UUEK comprises a universally unique identifier and the replacement UUEK comprises a different universally unique identifier. ### Claim 14 A computing system comprising memory and one or more processors communicatively coupled to the memory, the one or more processors configured to: receive, using a partner interface, an exchange request for executing a value-based exchange, wherein the exchange request is indicative of a universally unique ephemeral key (UUEK) and one or more transaction attributes; identify an exchange identifier based at least in part on the UUEK, wherein the exchange identifier corresponds to an exchange data object that comprises an instrument identifier for a service provider instrument of a member platform; provide, using a service provider interface, an exchange authorization request to the member platform, wherein the exchange authorization request is indicative of the one or more transaction attributes and the instrument identifier; receive, using the service provider interface, an exchange authorization response that is indicative of at least one of a transaction approval or a transaction denial; and provide, using the partner interface, an exchange response based at least in part on the exchange authorization response, wherein the exchange response is indicative of the transaction approval or the transaction denial. ### Claim 15 (depends on 14) The computing system of claim 14, wherein the UUEK comprises a partner partition that identifies a partner platform, the instrument identifier comprises an instrument key for the member platform, and the one or more processors are further configured to: identify a system instrument data object based at least in part on the instrument key; and generate the exchange authorization request based at least in part on the system instrument data object. ### Claim 16 (depends on 14) The computing system of claim 14, wherein the UUEK comprises a service provider partition that identifies a service provider platform and the one or more processors are further configured to: identify the member platform based at least in part on the service provider partition; identify a system instrument data object based at least in part on the member platform and the exchange identifier; and generate the exchange authorization request based at least in part on the system instrument data object. ### Claim 17 (depends on 14) The computing system of claim 14, wherein the exchange data object comprises one or more exchange attributes that are indicative of an expiration status, and the one or more processors are further configured to: validate the UUEK based at least in part on the expiration status. ### Claim 18 (depends on 17) The computing system of claim 17 wherein the one or more processors are further configured to modify the expiration status to invalidate the UUEK. ### Claim 19 One or more non-transitory computer-readable storage media including instructions that, when executed by one or more processors, cause the one or more processors to: receive, using a partner interface, an exchange request for executing a value-based exchange, wherein the exchange request is indicative of a universally unique ephemeral key (UUEK) and one or more transaction attributes; identify an exchange identifier based at least in part on the UUEK, wherein the exchange identifier corresponds to an exchange data object that comprises an instrument identifier for a service provider instrument of a member platform; provide, using a service provider interface, an exchange authorization request to the member platform, wherein the exchange authorization request is indicative of the one or more transaction attributes and the instrument identifier; receive, using the service provider interface, an exchange authorization response that is indicative of at least one of a transaction approval or a transaction denial; and provide, using the partner interface, an exchange response based at least in part on the exchange authorization response, wherein the exchange response is indicative of the transaction approval or the transaction denial. ### Claim 20 (depends on 19) The one or more non-transitory computer-readable storage media of claim 19, wherein the exchange authorization request is indicative of a user identifier corresponding to the exchange data object.