A bridge service is provided to support multi-user simulated contactless cards that in response to receiving a request to provision a secure element with payment card profile information of a user, provisions a token representing the payment card profile, converts the token representing the payment card profile into a format for the payment application; and provides the payment card profile to the payment application, the payment card profile comprising a single use key. The bridge service enables simulated contactless cards to store payment card information for a user on volatile memory instead of the persistent, secure element memory.

A mobile wallet computer server receives a fund access request from a user device. The fund access request is made in connection with a payment transaction. The mobile wallet server generates a tokenized card number, transmits the tokenized card number to the user device, and receives receive the tokenized card number from a card network computer system after having been routed from the user device via a merchant computer system and via an acquirer processor computer system. The mobile wallet computer server converts the tokenized card number to the actual credit card account number of the user and transmits the actual credit card account number to the card network computer system to process the payment transaction.

Methods and systems for facilitating electronic transactions on a mobile communications device are described. Available funding sources for sending funds to a contact from a list of contacts is provided for display on a graphical user interface (GUI) of a mobile communications device. A selection of a funding source from the available funding sources is received from the mobile communications device. In response to receiving a selection of the funding source, a payment indicator is provided for display on the GUI. A touch input associated with the payment indicator is receiving via the GUI. A transaction amount is determined based on a contact point dependent measurement of the touch input. The determined transaction amount along with the payment indicator is provided for display on the GUI.

The described device allows a user to set preference and receive the preferences by simply allowing a payment device to communicate with a preference reader.

A client device comprises a first secure element and a second secure element. The first secure element comprises a first computer-readable medium having a payment application comprising instructions for causing the client device to initiate a financial transaction. The second secure element comprises a second computer-readable medium having a security key, a payment instrument, stored authentication data and instructions for generating a secure payment information message responsive to the payment application. The secure payment information message comprises the payment instrument and is encrypted in accordance with the security key.

Described are systems and methods for transferring a token between mobile computing devices. A token transfer processing computing device includes a memory device for storing data and a processor in communication with the memory device. The processor is programmed to receive a token transfer message. The token transfer message includes a current device identifier associated with a current mobile device having an original token associated therewith for initiating secure payments using the current mobile device, and a new device identifier associated with a new mobile device replacing the current mobile device. The processor is further programmed to perform a lookup in a device-to-token mapping table to identify the original token associated with the current mobile device. The processor further generates an updated token associated with the payment account and transmits a token transfer response to the new mobile device. The token transfer response includes the updated token.

An embodiment of the present invention is directed to delivering an entitlements model that scales to both mid-frequency and low-latency use cases. The innovative solution may be distributed in nature and able to operate in low priority threads alongside the main logic of the software. An embodiment of the present invention may be implemented as a software module with APIs for ease of adoption.

Systems and methods associated with providing an automated portal to migrate one or more relationships with one entity to another entity are disclosed. In one embodiment, an exemplary method may comprise: providing a portal enabling automated migration of existing relationships from existing entities to a first entity; generating a first UI configured for identifying and providing access information regarding existing relationships for potential migration; generating a second UI to display information regarding the existing relationships and provide UI elements enabling the user to receive migration offers; determining terms of replacement relationships that the first entity can offer the user; generating a third UI to (i) compare terms between the existing and new relationships, and (ii) enable the user to authorize the relationship migration; performing an automated generation process to create the new relationship(s); and performing an automated transfer process to transfer all objects to the new relationship.

Methods, systems, and machine-readable media are disclosed for registering a mobile device for use in a mobile commerce system. According to one embodiment, a method of registering a mobile device for use in a mobile commerce system can comprise receiving at a service provider system a registration request from a user of the mobile device. A determination can be made with the service provider system whether to allow registration of the mobile device. In response to determining to allow registration of the mobile device, the registration request can be sent from the service provider system to an acquirer system.

Methods, apparatus and computer software are provided for authorizing an EMV transaction between a user device and a point of sale terminal, particularly, but not exclusively, in situations where a secure element is not made available for the deployment of a payment application on the user device. The payment application is instead deployed to a processing environment that is outside of any secure element on the user device. An ICC Master Key corresponding to the payment application is held by a trusted authority, such as the issuing bank. The trusted authority is adapted generate time-limited session keys on the basis of the ICC Master Key and distribute session keys to the payment application. Receipt of a session key by the payment application enables the payment application to conduct an EMV payment transaction. The session key is used to authorize a single EMV payment transaction.