An offer processing system is configured to receive transaction data associated with user purchases from third party point of sales devices and/or third party payment processing systems. The offer processing system may then identify offers or savings that are applicable to the transaction data and redeem the offers on behalf of the users.

A system for generating and applying a secure token in a resource distribution network is provided. For example, a headend system generates a global token based on a time duration specified for multiple meters that are in communication with the headend system through at least a mesh network in a normal condition. The global token is associated with the time duration and is applicable to the multiple meters. The headend system causes the global token to be broadcast via a broadcast network. After receiving the global token, the meter verifies the global token and determines the time duration associated with the global token. The meter further connects premises associated with the meter to a resource distribution network for at least the time duration associated with the global token.

Systems and methods for push provisioning of a financial instrument to an electronic device from a browser are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for push provisioning of a financial instrument to an electronic device from a browser may include: (1) receiving, from a cardholder and at an issuer website accessed by the cardholder by a browser, a request to provision a financial instrument to an electronic wallet provided by an electronic wallet provider and executed by a mobile electronic device; (2) providing an interface to an electronic wallet provider website for the electronic wallet provider and associating the interface with a session id; (3) receiving an electronic device identifier for an electronic device and the session id from the electronic wallet provider; and (4) provisioning the financial instrument to the electronic wallet on the electronic device associated with the electronic device identifier.

The present disclosure provides systems and methods for an address exchange system including a controller configured to provide an API configured to receive an identifier from a user and further configured not to receive a physical address from the user, wherein the user provides an item for shipment to the physical address. In response to receiving the identifier, the controller is further adapted to request the physical address from a data storage system wherein the data storage system stores an association between the identifier and the physical address and further stores one or more permission settings defining situations in which the physical address is to be provided in response to receipt of the identifier. In response to receipt of the identifier, the data storage system tests the permission settings to determine whether or not to provide the associated physical address.

Systems and methods are describe herein for managing a transaction between two parties. A distributed ledger management service (DLMS) microservice receives an electronic document pertaining to a transaction from a user. The electronic document includes transactional data. A document type is determined by the DLMS microservice. A portion of the transactional data is extracted from the electronic document based on the document type. The portion of the transactional data is provided to a distributed ledger node for decentralized storage and further reporting to a third party.

Transaction identification is described. A payment processing platform can receive (i) transaction data associated with a transaction between a merchant and a customer and (ii) a transaction code from a payment making platform. The payment processing platform can receive an indication of an interaction between a computing device of the customer and the transaction code, wherein the indication is associated with context data associated with the interaction. Based at least partly on comparing the transaction data with the context data, determining that the customer is associated with the transaction and causing an association between the customer and the transaction, wherein the association causes at least a portion of the transaction data to be provided to a mobile payment application, associated with the payment making platform, on the computing device of the customer.

Aspects described herein may relate to a transaction exchange platform using a streaming data platform (SDP) and microservices to process transactions according to review and approval workflows. The transaction exchange platform may receive transactions from origination sources, which may be added to the SDP as transaction objects. Microservices on the transaction exchange platform may interact with the transaction objects based on configured workflows associated with the transactions. Processing on the transaction exchange platform may facilitate clearing and settlement of transactions. Some aspects may provide for dynamic and flexible reconfiguration of workflows and/or microservices. Other aspects may provide for data snapshots and workflow tracking, allowing for monitoring, quality control, and auditability of transactions on the transaction exchange platform.

Button functionalities for user interfaces, e.g., for use with a portable multifunction device, are disclosed. Exemplary button functionalities are described for an electronic device with a display, a rotatable and depressible input mechanism, and/or a button. Different device features may be accessed, depending on whether the rotatable and depressible input mechanism or the button is activated, and further depending on whether the activation represents a single press, a double press, or an extended press on the rotatable and depressible input mechanism or the button.

In one embodiment, techniques include storing indications of unique identifiers used by users of service providers that are part of a federated system. Each of the unique identifiers is associated with only one user. A computing system of a first service provider receives an intent to register a unique identifier with the first service provider. The computing system determines availability of the unique identifier based on determining whether the unique identifier is associated with another user in the data store. Based at least in part on the determination that the unique identifier is available, the computing system maps, in the data store, the unique identifier with an account of the user associated with each service provider that is part of the federated system. Subsequent to the mapping, the unique identifier is usable as a proxy in lieu of personal data associated with the user on each service provider.

The present application discloses a maintenance plant management method, maintenance plant management system and data management server, this method comprises: receiving, via a data management server, a transaction request of using a maintenance plant from a first user and calling a usage smart contract to grant a permission of usage of the maintenance plant to the first user according to the transaction request; calling the usage smart contract to send a transaction payment request to the first user according to transaction information when the first user finishes using the maintenance plant; performing a sharing according to the transaction sharing rule via the data management server when the payment transaction is finished by the first user; and receiving the transaction information submitted by the data management server and registering the transaction information in a block chain via the block chain node device.