Abstract: According to an aspect of an embodiment of the present disclosure, a method may include receiving a quick response (QR) code from a computing device, the QR code including a first entity identifier, and analyzing the QR code to determine a request to initiate a data transfer between a first entity associated with the first entity identifier and a second entity, and to determine one or more characteristics associated with the data transfer. The method may also include, based on the one or more characteristics, identifying a first QR code processing flow from multiple QR code processing flows to follow to process the data transfer, and verifying the first entity in the transaction based on the first entity identifier of the QR code and based on the first QR code processing flow. The method may also include processing the data transfer between the second entity and the first entity based on the first QR code processing flow.

Abstract: A method for using location-based services for service management is discussed. The method includes receiving, at a server, a user request from a user device at a geographical location. The method includes accessing a store search to determine a store reference based on the user request and a user location corresponding to the geographical location, the store reference indicating tenant(s) accessible to the user via a user interface (UI) of the user device. The method includes accessing location data for the user device based on the store reference and a user account associated with the user, the location data indicating a service accessible via the UI and associated with a certain tenant. The method includes providing, to the user device and based on the location data, an user experience for accessing the service via the UI.

Abstract: A system is configured to perform operations that include receiving a purchase request to use a consumer digital wallet account of a user to pay for an item sold by a merchant, the consumer digital wallet account being included as a payment method in a merchant digital wallet account provided by the merchant to the user. The operations further include generating a single-use payment token based on a non-transactable token. Additionally, the operations include transmitting, to an existing card payment network, a card transaction message that includes the single-use payment token, the single-use payment token causing the existing card payment network to route the card transaction message back to the system. The operations also include causing payment to be remitted from the user to the merchant using a payment method included in the consumer digital wallet account.

Abstract: Methods, systems, and computer program products are included for electronic provisioning and transactions. These methods, systems, and computer program products expose communicatively coupled components in an electronic payment framework to provide electronic omni-channel payments using a hierarchy of vault data stores. Various aspects of this framework include provisioning a tender and using the provisioned tender as part of a transaction. This framework may be used in the context of in-store, private label card, and e-commerce payments. An example method of performing an electronic transaction includes transmitting a client token from a merchant application to a white label platform. The white label platform determines a billing agreement identifier that corresponds to the client token. The white label platform transmits the billing agreement identifier to a consumer vault provider.

Abstract: There are provided systems and methods for software development kits for point-of-sale device and mobile device interactive frameworks. A service provider, such as a payment provider, that offers online and cloud based digital wallet services may configure flexible software frameworks for a merchant's point-of-sale device and a user's mobile device. A framework for a merchant's device may allow for user check-in with the merchant, and may utilize multiple different communication protocols to receive tenders and non-tenders from the user's mobile device. Thus, the user's mobile device may communicate with the merchant device to provide tokens that may be resolved by the merchant using the payment provider and/or a payment host to receive payment processing confirmation. Moreover, the frameworks may allow for a transaction to be synchronized to the user's mobile device so that the user may receive updates after processing of the tokens.