A method for managing an anonymous e-cash transaction includes receiving a request to withdraw a payment coin, generating a combination of random attributes for the payment coin, creating the payment coin based on the combination of attributes, and issuing the payment coin in exchange for a first asset. Each attribute of the combination of attributes may represent a different portion of a total value of the payment coin. A partially spent value of the payment coin may be based on a revealed subset of the combination of attributes. The method further includes creating a refund coin based on the combination of attributes and spending the refund coin to issue a refund having a value corresponding to an unspent portion of the payment coin. Each attribute of the combination of attributes of the refund coin may represent a different portion of a total value of the refund coin.

A product exchange system manages an exchange of information related to a transaction executed through an ecommerce platform provided by a third-party business between a user and the third-party business. The product exchange system comprises a controller; a database that includes user information and login credentials associated with the user, wherein the database is in communication with the third-party business and the user; and a memory coupled to the controller. The controller is configured to: receive a user request to log into the product exchange system from the user through the ecommerce platform provided by the third-party business, wherein the user request includes the login credentials; receiving sharing preferences from the user, the sharing preferences indicating a subset of user information that is to be shared to the third-party business; and send at least the subset of the user information from the database to the third-party business.

A system and method for anonymously funding a temporary cash account is described. The system includes a personal mobile device, a cash account, a Point-of-Sale (POS) device and a network component. A device identifier is received by the personal mobile device. A unique session identification is generated by the network component and communicated to the personal mobile device and to the POS device. The POS device and personal mobile device displays the device identifier. The POS device then proceeds to receive a cash amount. The POS receives an instruction to associate the cash amount with the personal mobile device. The personal mobile device communicates the cash amount to the network component. The network component receives the device identifier, the unique session identification and the cash amount. The network component funds the cash account with the cash amount. The personal mobile device accesses the cash account to fund an activity.

Concepts and technologies disclosed herein are directed to enhancing data privacy and owner capture of data value. According to one aspect disclosed herein, an obfuscation and orchestration proxy system can receive a request for a service. The request can originate from a user. The user can be associated with user data. The obfuscation and orchestration proxy system can determine a business flow to be used to provide the service. The business flow can identify a disaggregated provider component to provide, at least in part, the service. The obfuscation and orchestration proxy system can provide a portion of the user data to the disaggregated provider component. The obfuscation and orchestration proxy system can reveal a further portion of the user data to the disaggregated provider component. The obfuscation and orchestration proxy system can obfuscate the portion of the user data for data passthrough to one or more other disaggregate provider components.

A payment processing method involves a server receiving a payee identifier, and linking the payee identifier to a device identifier identifying a payee device. The server receives from a payor device a payment initiation request identifying a specified payment amount and a payor identifier, links a unique token to the specified payment amount and to the payor identifier, and provides the payor device with the token. The token excludes the payor identifier and particulars of the associated payor. The server receives a payment completion request including the payee identifier and the token, and excluding the payment amount, the payor identifier and payor particulars. The server uses the payee identifier to confirm that the payment completion request was signed with the device identifier, uses the payee identifier to locate a payee account, and uses the token to determine the specified payment amount and a payor account associated with the payor identifier.

A secure payment agent assist (“SPAA”) feature provides assistance to a contact center agent during a transaction involving sensitive information, where the sensitive information provided by the remote party is maintained in secure manner, so that the agent is not exposed to it. The agent is assisted by being provided with a pop-up window that allows the agent to invoke a “recollect” and “cancel” function during the transaction. The pop-up window also provides information to the agent making the agent aware of the progress of the transaction as the remote party interacts with an interactive voice response (“IVR”) unit. In other embodiments, a configuration parameter allows the prompts for the payment information to be provided by the agent or the IVR.

A method of communicating a payment request from a first payment platform to a second payment platform is disclosed. The method may receive a payment request from a sending user on the first payment platform to a receiving user on the second payment platform where the payment request from the sending user is translated into a protected payment request. In response to the sending user being known, the protected payment request may be communicated to the second payment platform. An acceptance of the protected payment request from the second payment platform may be received. A transaction settlement request may be communicated to the first payment platform and the second payment platform.

A method and a DL node for processing a transaction in a distributed ledger (DL) network based on policies are described. A request for a transaction including data is received at a DL node from a user device. A first set of one or more DL nodes of the DL network that have characteristics that satisfy one or more policies associated with the data of the transaction are determined. In response to determining that the DL node is one of the set of DL nodes, the transaction is executed at the DL node, and the transaction is inserted as a private transaction in a digital ledger of the DL network causing a second set of one or more DL nodes of the DL network that is different from the first set of DL nodes to access only an identifier of the transaction and not a payload of the transaction.

Systems and methods for transferring between accounts in the absence of sensitive information needed to perform a direct transfer between accounts are described herein. In an embodiment, an intermediary system receives a request to perform a digital electronic transfer of an item from a first online account to a second online account through the intermediary system, wherein the intermediary system does not have access to the sensitive information for either the first online account or the second online account. Without requesting the sensitive information for either the first online account or the second online account, the intermediary system responds to the request by: performing a first digital electronic transfer of the item from the first online account to a system account, storing data assigning the item to an intermediary account for which the intermediary system has the sensitive information, and performing a second digital electronic transfer of the item from the system account to the second online account.

A method for generating, by an artificial intelligence engine, a treatment plan and a billing sequence associated with the treatment plan is disclosed. The method includes receiving information pertaining to a patient. The information includes a medical diagnosis code of the patient. The method includes generating, based on the information, the treatment plan for the patient. The treatment plan includes instructions for the patient to follow. The method includes receiving a set of billing procedures associated with the instructions. The set of billing procedures includes rules pertaining to billing codes, timing, constraints, or some combination thereof. The method includes generating, based on the set of billing procedures, the billing sequence for at least a portion of the instructions. The billing sequence is tailored according to a certain parameter. The method includes transmitting the treatment plan and the billing sequence to a computing device.