PROCESSING A TRANSACTION USING MULTIPLE APPLICATION IDENTIFIERS

• US 20150186864A1
• Filed: 12/29/2014
• Published: 07/02/2015
• Est. Priority Date: 12/27/2013
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Jones, Christopher, Aabye, Christian, Makhotin, Oleg
• Granted Patent: US 10,445,718 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/3572 Multiple accounts on card
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules

Abstract

Embodiments of the present invention are directed to methods, systems, apparatuses, and computer-readable mediums for selecting multiple payment applications and preparing multiple transaction payloads for a transaction during interaction between a mobile device and an access device. Accordingly, by preparing multiple transaction payloads for a single transaction, the merchant may initiate transactions using each of the prepared transaction payloads in order of preference. If a transaction initiated using payment credentials associated with a preferred application is unsuccessful for any reason, a transaction may be initiated using payment credentials associated with an alternate application automatically, and without additional interaction by the mobile device and/or access device.

Claims

1. A method for processing a transaction initiated by a mobile device communicating with an access device, the method comprising:

receiving, by the access device, a plurality of application identifiers from the mobile device, wherein the plurality of application identifiers are associated with one or more payment credentials provisioned on the mobile device;

determining, by the access device, a first application identifier and a second application identifier from the plurality of application identifiers for the transaction;

preparing, by the access device, a first transaction payload including first payment credentials associated with the first application identifier and a second transaction payload including second payment credentials associated with the second application identifier;

initiating, by the access device, a first transaction using the first transaction payload;

storing, by the access device, the second transaction payload in a temporary memory;

determining, by the access device, that the first transaction should not or cannot be completed; and

initiating, by the access device, a second transaction using the stored second transaction payload from the temporary memory.

2. The method of claim 1, wherein preparing the first transaction payload and the second transaction payload comprises:

sending, by the access device, a first application selection message to the mobile device, the first application selection message including the first application identifier;

receiving, by the access device, payment information associated with the first application identifier from the mobile device, the payment information including the first payment credentials associated with the first application identifier;

sending, by the access device, a second application selection message to the mobile device, the second application selection message including the second application identifier;

receiving, by the access device, payment information associated with the second application identifier from the mobile device, the payment information including the second payment credentials associated with the second application identifier; and

preparing, by the access device, the first transaction payload using the first payment credentials and the second transaction payload using the second payment credentials.

3. The method of claim 2, wherein the access device communicates with the mobile device over a short range communication channel.

4. The method of claim 1, wherein initiating the first transaction using the first application identifier further comprises:

determining, by the access device, a cardholder verification method associated with the first payment credentials; and

requesting, by the access device, the determined cardholder verification method from the user.

5. The method of claim 1, wherein initiating the second transaction using the second application identifier further comprises:

determining, by the access device, a cardholder verification method associated with the second payment credentials, wherein the cardholder verification method does not require a user input;

submitting, by the access device, an authorization request message including the transaction payload to a payment network.

6. The method of claim 1, wherein the first application identifier is associated with network-generic payment information and wherein the second application identifier is associated with network-specific payment information.

7. The method of claim 1, wherein the first application identifier and the second application identifier are associated with the same payment credentials and wherein the first application identifier and the second application identifier are associated with different cardholder verification methods.

8. The method of claim 1, wherein determining the first application identifier and the second application identifier from the plurality of application identifiers for the transaction comprises:

determining, by the access device, supported application identifiers from the plurality of application identifiers,

determining, by the access device, a first priority application identifier and a second priority application identifier from the supported application identifiers; and

selecting the first priority application identifier as the first application identifier and the second priority application identifier as the second application identifier.

9. The method of claim 1, wherein determining that the first transaction should not or cannot be completed includes determining that a cardholder verification method input is not received by the access device in a predetermined period of time.

10. The method of claim 1, wherein determining that the first transaction should not or cannot be completed includes receiving an input from a consumer indicating a preference for initiating the second transaction.

11. An access device comprising:

a processor;

a computer-readable medium coupled to the processor, the computer-readable medium comprising code, executable by the processor, for performing a method of processing a transaction initiated by a mobile device, the method comprising;

receiving a plurality of application identifiers from the mobile device, wherein the plurality of application identifiers are associated with one or more payment credentials provisioned on the mobile device;

determining a first application identifier and a second application identifier from the plurality of application identifiers for the transaction;

preparing a first transaction payload including first payment credentials associated with the first application identifier and a second transaction payload including second payment credentials associated with the second application identifier;

initiating a first transaction using the first transaction payload;

storing the second transaction payload in a temporary memory;

determining that the first transaction should not or cannot be completed; and

initiating a second transaction using the stored second transaction payload from the temporary memory.

12. The access device of claim 11, wherein preparing the first transaction payload and the second transaction payload comprises:

sending, by the access device, a first application selection message to the mobile device, the first application selection message including the first application identifier;

receiving, by the access device, payment information associated with the first application identifier from the mobile device, the payment information including the first payment credentials associated with the first application identifier;

sending, by the access device, a second application selection message to the mobile device, the second application selection message including the second application identifier;

receiving, by the access device, payment information associated with the second application identifier from the mobile device, the payment information including the second payment credentials associated with the second application identifier; and

preparing, by the access device, the first transaction payload using the first payment credentials and the second transaction payload using the second payment credentials.

13. The access device of claim 12, wherein the access device communicates with the mobile device over a short range communication channel.

14. The access device of claim 11, wherein initiating the first transaction using the first application identifier further comprises:

determining, by the access device, a cardholder verification method associated with the first payment credentials; and

requesting, by the access device, the determined cardholder verification method from the user.

15. The access device of claim 11, wherein initiating the second transaction using the second application identifier further comprises:

determining, by the access device, a cardholder verification method associated with the second payment credentials, wherein the cardholder verification method does not require a user input;

submitting, by the access device, an authorization request message including the transaction payload to a payment network.

16. The access device of claim 11, wherein the first application identifier is associated with network-generic payment information and wherein the second application identifier is associated with network-specific payment information.

17. The access device of claim 11, wherein the first application identifier and the second application identifier are associated with the same payment credentials and wherein the first application identifier and the second application identifier are associated with different cardholder verification methods.

18. The access device of claim 11, wherein determining the first application identifier and the second application identifier from the plurality of application identifiers for the transaction comprises:

determining, by the access device, supported application identifiers from the plurality of application identifiers,

determining, by the access device, a first priority application identifier and a second priority application identifier from the supported application identifiers; and

selecting the first priority application identifier as the first application identifier and the second priority application identifier as the second application identifier.

19. The access device of claim 11, wherein determining that the first transaction should not or cannot be completed includes determining that a cardholder verification method input is not received by the access device in a predetermined period of time.

20. The access device of claim 11, wherein determining that the first transaction should not or cannot be completed includes receiving an input from a consumer indicating a preference for initiating the second transaction.

21. A system for processing payment transactions initiated by a mobile device communicating with an access device, the system comprising:

the mobile device configured to;

send a plurality of application identifiers to the access device, the plurality of application identifiers being associated with two or more payment credentials stored on the mobile device; and

the access device configured to;

receive the plurality of application identifiers from the mobile device;

determine a first and a second application identifier for the transaction;

prepare a first transaction payload including payment credentials associated with the first application identifier and a second transaction payload including payment credentials associated with the second application identifier;

initiate a first transaction using the first transaction payload;

determine that the first transaction should not or cannot be completed; and

initiate the second transaction using the second transaction payload.