Techniques for managing an application token may include providing, by a first service provider application on a communication device to a first service provider computer, a first request for a first application token, receiving, by an account management application on the communication device from a token service computer in communication with the first service provider computer, the first application token, and storing the first application token in a token container in the account management application.

A system for generating and applying a secure token in a resource distribution network is provided. For example, a headend system generates a time-based token based on a time duration specified for a meter. The time-based token indicates the time duration for the meter. The time-based token is further generated based on an identifier of the meter. The headend system transmits the time-based token to the meter via at least a mesh network. After receiving the time-based token, the meter validates the time-based token to determine that the time-based token is generated for the meter based on information related to the identifier of the meter. If the meter determines that the time-based token is valid, the meter connects premises associated with the meter to a resource distribution network for at least the time duration specified in the time-based token.

A system for generating and applying a secure token in a resource distribution network is provided. For example, a headend system generates a payment-based token based on a payment made for a meter. The payment-based token indicates a credit value to be applied to the meter. The credit value can range from a negative credit value limit and a positive credit value limit. The payment-based token is further generated based on a meter identifier. The headend system transmits the payment-based token to the meter via at least a mesh network. After receiving the payment-based token, the meter validates the payment-based token to determine that the payment-based token is generated for the meter. The meter further determines the balance associated with the meter based on the credit value specified in the payment-based token. Based on the balance, the meter connects or disconnects premises associated with the meter from a resource supply.

A method and system capable of generating a relying party risk-adjusted indicator associated with and used by users and parties entering into one or more transactions with a relying party.

Various embodiments are generally directed to NFC-based mobile currency transfers. A mobile payment may be programmatically initialized when at least two mobile devices come into NFC communications range. A payment card associated with an account used to fund the currency transfer may be tapped to one or more of the devices to allow a server to validate the currency transfer.

Aspects of the present disclosure involve systems, methods, devices, and the like for communicating with a unified messaging center using multi-channel messaging with block-based datastore. In one embodiment, a system is introduced that can provide a unified experience and capability for messaging with one or more entities across platforms. The messaging capability includes the ability to provide user interaction using a single architecture with data store in a centralized form. In one embodiment, the data store includes the use of blockchain technology wherein each interaction with the user and across platforms is recorded and stored on a cryptographed block.

An information processing system for receiving a service using an electronic device, the information processing system includes an acquisition section configured to acquire a license key for using the service issued by a server system and a processing section. The license key includes setting information to be used when the electronic device uses the service. The processing section acquires the setting information included in the acquired license key and performs setting processing of the electronic device based on the acquired setting information.

Pursuant to some embodiments, systems, methods and computer program code are provided for receiving a transaction request message, the transaction request message specifying transaction attributes for a proposed payment transaction involving a user of a mobile device and a merchant, comparing the transaction attributes with a permitted transaction rule, the permitted transaction rule having been stored in the mobile device prior to receiving the transaction request message, approving the proposed transaction upon determining that the transaction attributes satisfy the permitted transaction rule, the approving including generating a transaction cryptogram, and transmitting the transaction cryptogram to the merchant for use in completing the proposed payment transaction.

A high security communication channel between the back-end application and the customer's mobile device is disclosed. An application programming interface that integrates into a service provider's back end application and a software development kit that integrates into a mobile application on the customer's mobile device establish a two-way communication channel between the back-end application and the mobile device. When a customer is ready to complete a transaction in one of the service provider's sales channels, such as online, by phone, in-person, by mobile device, or at a kiosk, the transaction moves to the mobile device for completion. A push message on the mobile device launches the service provider's mobile application and the customer completes the transaction quickly and securely using the advanced automation functions, such as biometrics, GPS, wallet, camera or near field communication, available on the mobile device.

A method for enabling anonymous shipment of a package containing goods purchased by a customer from a vendor for delivery to a customer and an address unknown to the vendor is provided. The method includes, storing personal information associated with the customer in a shipping intermediary's secure database including the actual name and associated intended delivery address, and generating a tokenized customer name representing the actual name along with a preferred intermediary address associated with the shipping intermediary. The tokenized customer name and the preferred intermediary address do not include the actual name and any of the intended delivery address information for the package. The method further includes providing to the vender the tokenized customer name and the preferred intermediary address in place of the actual name and the intended delivery address.