Abstract: An embodiment of the invention may include a method, computer program product and system for transaction authentication. The embodiment may include receiving, by a mobile device from a network server via a wireless access point using a medium-range wireless communication protocol, an indication corresponding to a transaction to execute. The embodiment may include displaying a graphical interface element having an indication of approval to initiate the transaction to execute from a user based on receiving the indication. The embodiment may include authorizing the transaction to execute for a period of time based on receiving the indication of approval to initiate the transaction to execute. The embodiment may include detecting within the period of time, from a point of sale device using a short-range wireless communication protocol, a mobile payment method associated with the transaction to execute. The embodiment may include initiating the transaction based on detecting the mobile payment method.

Abstract: Embodiments of the present invention utilize a data hash and an associated geotag for authentication of geolocation policies for data object storage in a cloud system. The geotag may be an alphanumeric identifier such as a city name, postal (ZIP) code, and/or latitude-longitude pair. Embodiments include a post-authenticate process, in which, after a data object is retrieved from a BMS, the geographic location of the source is confirmed to ensure the location policies have not been violated. Additionally, embodiments include a pre-authenticate process, in which, prior to storing a data object in a BMS, the geographic location of the BMS that is to receive the data object is confirmed to ensure the location policies will not be violated. Embodiments may use pre-authenticate, post-authenticate, or both pre-authenticate and post-authenticate, in order to implement and verify the location policies.

Abstract: Embodiments of the present invention utilize a data hash and an associated geotag for authentication of geolocation policies for data object storage in a cloud system. The geotag may be an alphanumeric identifier such as a city name, postal (ZIP) code, and/or latitude-longitude pair. Embodiments include a post-authenticate process, in which, after a data object is retrieved from a BMS, the geographic location of the source is confirmed to ensure the location policies have not been violated. Additionally, embodiments include a pre-authenticate process, in which, prior to storing a data object in a BMS, the geographic location of the BMS that is to receive the data object is confirmed to ensure the location policies will not be violated. Embodiments may use pre-authenticate, post-authenticate, or both pre-authenticate and post-authenticate, in order to implement and verify the location policies.