BACKGROUND

Systems and methods for processing transactions between user devices and access devices are known. For example, in the case of a payment transaction, a consumer may use a user device (e.g., payment card or digital wallet application on a smartphone device) to execute a contactless (or contact) data exchange with an access device (e.g., a Point-of-Sale (POS) terminal). In another example, a user device may be used to execute data exchange with an access device (e.g., smartcard reader) to allow a user to access to a building and/or event. In these examples, data is communicated or exchanged between the user device and the access device.

A number of problems, however, exist with existing systems and methods for processing transactions. For example, in the case where a user device is a smartphone, the user device may indiscriminately prompt the user to enter their credentials whenever the user device is used to conduct any type of transaction (e.g., payment or non-payment). However, for some transaction types, additional processing such as user prompts may not be necessary or may even degrade the transaction experience. For example, in a transit transaction, a user may tap his or her phone against a terminal with a turnstile to gain access to a secure area in a transit station. Each patron of the transit station needs to move past the turnstile quickly. In this environment, it is cumbersome and in many cases unnecessary for the user to enter their credentials into their user device before allowing the user to enter the restricted area.

Another problem exists when a user may maintain multiple applications on their user device. In this situation, each application is capable of executing a different type of transaction. When the user device is proximate to an access device, an application (e.g., a digital wallet application) on the user device may transmit to the access device a list of the applications associated with a digital wallet on the user device. However, the user may want to use a specific application when encountering a specific access device type (e.g., using a specific credit card for payment at a particular retailer where the user has a loyalty account, or using a specific mass transit application corresponding to a prepaid card to pass through a train terminal gate, instead of always using a default credit card). The user may want to be able to do this without physically interacting with their user device to select the appropriate application at the time of the transaction.

Embodiments of the disclosure address these and other problems, individually and collectively.

SUMMARY

One embodiment includes a method comprising: receiving, by a user device from an access device, an available applications request message, wherein the available applications request message comprises an access device type identifier; determining, by the user device, whether an association exists between the access device type identifier and one or more application identifiers of a plurality of application identifiers stored on the user device, wherein the plurality of application identifiers respectively correspond to different applications on the user device; and transmitting, by the user device to the access device, based in part on whether the association exists, an available applications response, the available applications response comprising the one or more application identifiers of the plurality of application identifiers associated with the access device type identifier.

Another embodiment includes a communication device comprising: a processor; and a computer readable medium, coupled to the processor. The computer readable medium comprises code, executable by the processor, for implementing a method. The method comprises: receiving from an access device, an available applications request message, wherein the available applications request message comprises an access device type identifier; determining whether an association exists between the access device type identifier and one or more application identifiers of a plurality of application identifiers stored on the user device, wherein the plurality of application identifiers respectively correspond to different applications on the user device; and transmitting to the access device, based in part on whether the association exists, an available applications response, the available applications response comprising the one or more application identifiers of the plurality of application identifiers associated with the access device type identifier.

Another embodiment includes a method comprising: generating, by an access device, an available applications request message, wherein the available applications request message comprises an access device type identifier; transmitting, by the access device, the available applications request message to a user device; and receiving, by the access device from the user device, an available applications response, the available applications response comprising one or more application identifiers associated with the access device type identifier.

Another embodiment includes a method comprising: receiving, by a user device from an access device, an available applications request message, wherein the available applications request message comprises an access device type identifier; and determining, by the user device, based in part on the access device type identifier, whether user interaction on the user device is necessary.

Further details regarding embodiments of the disclosure are described in the Detailed Description and the Figures.

