Abstract: There are provided systems and methods for authenticating a mobile device for use in a secure transaction. A user having a master device authenticated for use in a secure transaction system, such as an electronic payment system, identifies a secondary device to be enabled for use in processing a secure transaction. The secondary device connects to a companion device and shares information associated with the secondary device and companion device with a transaction processing server, which returns authentication information associated with both devices. When the user initiates a secure transaction, the secondary device identifies whether the third device is in proximity. The secure transaction is processed only if the second and third devices are in communication and authenticated during the transaction. If the secondary device is lost or stolen, the device may be disabled until reauthenticated through the master device.

Abstract: In an embodiment, a system includes a processor coupled with a data store, the at least one processor configured to: receive a client product version number from a client device; identify a differential bundle based on a difference between the client product version number and a current product version number, wherein the differential bundle comprises a set of bytewise differences between an executable client product binary file associated with the client product version number and a executable current product binary file associated with the current product version number; determine whether the differential bundle is available in the data store; retrieve the differential bundle from the data store in response to determining that the differential bundle is available in the data store; produce the differential bundle in response to determining that the differential bundle is not available in the data store; and send the differential bundle to the client device.

Abstract: There are provided systems and methods for display of locally broadcasted uniform resource locators for checkout and payment. A user may utilize a computing device, such as a mobile phone, to receive a plurality of local broadcasts. The broadcasts may be limited in range to a defined region through short range communications or geo-locations of users or entities. Thus, the computing device may display the broadcasts for nearby users and entities. The broadcast may contain a URL that unique identifiers the user or entity and the checkout and payment process for the payment requested by the user or entity. The URL may cause a device receiving the URL to load a webpage or application interface having the checkout and payment process. The user may then use the process in the broadcast to provide a payment to another user or entity.

Abstract: An approach is proposed to support version control for integrating updated web-based components with a native application of a mobile device. A new version of a mini app is received at an application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features in JavaScript to be integrated with the native application. Version compatibility checks are performed to confirm that the new version of the mini app only contains native dependencies that match with a version of the native application the version of the mini app depends on. The new version of the mini app is integrated with the native application into the target mobile application if the version compatibility checks pass. Finally, the target mobile application is uploaded to an app store to make the target mobile application available to an end user.

Abstract: An approach is proposed to support version control for integrating updated web-based components with a native application of a mobile device. A new version of a mini app is received at an application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features in JavaScript to be integrated with the native application. Version compatibility checks are performed to confirm that the new version of the mini app only contains native dependencies that match with a version of the native application the version of the mini app depends on. The new version of the mini app is integrated with the native application into the target mobile application if the version compatibility checks pass. Finally, the target mobile application is uploaded to an app store to make the target mobile application available to an end user.

Abstract: There are provided systems and methods for generation of locally broadcasted uniform resource locators for checkout and payment. A user or entity controlling a device may wish to establish a checkout and payment processes that allows payments to the user or device entity. The user or entity may cause generation of a broadcast that may contain information to retrieve the checkout and payment process. For example, the broadcast may contain a URL that unique identifiers the user or entity and the checkout and payment process for the payment requested by the user or entity. The broadcast may further include information, such as a description, amount, and a type of checkout and payment process. The URL may cause a device receiving the URL to load the checkout and payment process. The broadcast may be limited in range to a defined region through short range communications or geo-locations.

Abstract: There are provided systems and methods for display of locally broadcasted uniform resource locators for checkout and payment. A user may utilize a computing device, such as a mobile phone, to receive a plurality of local broadcasts. The broadcasts may be limited in range to a defined region through short range communications or geo-locations of users or entities. Thus, the computing device may display the broadcasts for nearby users and entities. The broadcast may contain a URL that unique identifiers the user or entity and the checkout and payment process for the payment requested by the user or entity. The URL may cause a device receiving the URL to load a webpage or application interface having the checkout and payment process. The user may then use the process in the broadcast to provide a payment to another user or entity.

Abstract: An approach is proposed to support cross-platform information exchange mechanism for integration of web-based components with a native application. First, mini apps are imported to a platform of a mobile device, wherein the mini apps are web-based features assembled and packaged together in JavaScript to be deployed to and integrated with the application native to the platform. A bridge enables bi-directional communication between the mini apps in JavaScript and the native to the platform by marshalling native code of the native application into a JavaScript project to be integrated with the imported mini apps and un-marshalling the mini apps in JavaScript to the native code of the native application. The mini apps are then integrated with the native application on the mobile device over the bridge to create a target mobile application, which is uploaded to an app store to make the target mobile application available to an end user.

Abstract: An approach is proposed to support automatic API generation for integration of web-based components with a native application. First, mini apps are included in a container, wherein the mini apps are web-based features assembled together as a bundle of JavaScript assets to be integrated with the native application on a mobile device. A set of APIs to the mini apps are then automatically generated based on pre-defined schemas in native code specific to the platform of the mobile device and merged with the mini apps into the container. The container is published to a repository at a central, team shared, location and imported to the mobile device for integration with the native application. Finally, a target mobile application is created by integrating the mini apps with the native application on the mobile device via the APIs, wherein the target mobile application is uploaded and made available to an end user.

Abstract: There are provided systems and methods for display of locally broadcasted uniform resource locators for checkout and payment. A user may utilize a computing device, such as a mobile phone, to receive a plurality of local broadcasts. The broadcasts may be limited in range to a defined region through short range communications or geo-locations of users or entities. Thus, the computing device may display the broadcasts for nearby users and entities. The broadcast may contain a URL that unique identifiers the user or entity and the checkout and payment process for the payment requested by the user or entity. The URL may cause a device receiving the URL to load a webpage or application interface having the checkout and payment process. The user may then use the process in the broadcast to provide a payment to another user or entity.

Abstract: There are provided systems and methods for generation of locally broadcasted uniform resource locators for checkout and payment. A user or entity controlling a device may wish to establish a checkout and payment processes that allows payments to the user or device entity. The user or entity may cause generation of a broadcast that may contain information to retrieve the checkout and payment process. For example, the broadcast may contain a URL that unique identifiers the user or entity and the checkout and payment process for the payment requested by the user or entity. The broadcast may further include information, such as a description, amount, and a type of checkout and payment process. The URL may cause a device receiving the URL to load the checkout and payment process. The broadcast may be limited in range to a defined region through short range communications or geo-locations.

Abstract: A system or a method is provided that detects or establishes a connected network of personal or wearable devices of a user whereby the number and type of devices connected to that network are used to determine a security or confidence level for a particular transaction being attempted. The personal or wearable devices may include one or more of a smart watch, a mobile phone, a car, a smart belt buckle, smart key fob, or any other personal or wearable devices. Information indicating the number and composition on the various connected devices may be communicated from a user device requesting a payment transaction to a merchant or a payment service provider. The information indicating the number and composition of connected devices may be used for risk assessment to determine the confidence level or security level for the transaction requested by the user.

Abstract: There are provided systems and methods for authenticating a mobile device for use in a secure transaction. A user having a master device authenticated for use in a secure transaction system, such as an electronic payment system, identifies a secondary device to be enabled for use in processing a secure transaction. The secondary device connects to a companion device and shares information associated with the secondary device and companion device with a transaction processing server, which returns authentication information associated with both devices. When the user initiates a secure transaction, the secondary device identifies whether the third device is in proximity. The secure transaction is processed only if the second and third devices are in communication and authenticated during the transaction. If the secondary device is lost or stolen, the device may be disabled until reauthenticated through the master device.