Mobile payment application architecture

• US 10,454,693 B2
• Filed: 09/28/2010
• Issued: 10/22/2019
• Est. Priority Date: 09/30/2009
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Pirzadeh, Kiushan, Kekicheff, Marc B.
• Primary Examiner(s): Kanervo, Virpi H
• Application Number:
  US12/892,328
• Publication Number:
  US 20110078081A1
• Time in Patent Office: 3,311 Days
• CPC Class Codes: G06F 21/78 to assure secure storage of data address-based protection against unauthorised use of memory G06F12/14; record carriers for use with machines and with at least a part designed to carry digital markings G06K19/00
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/3226 Use of secure elements separate from M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3229 Use of the SIM of a M-device as secure element
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3263 characterised by activation or deactivation of payment capabilities
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1467 involving prepayment

Abstract

A system, apparatus, and method for conducting payment transactions using a mobile device. Embodiments of the invention are directed to an architecture or system design for the functional elements residing in a mobile device that may be used to conduct a payment transaction. The inventive architecture may be implemented as a set of functional modules resident in a secure element that is embedded or otherwise incorporated into the mobile device.

Claims

1. An apparatus for conducting a payment transaction, comprising:

a mobile device;

an electronic processor configured to execute a set of instructions, wherein the electronic processor is incorporated into the mobile device;

a mobile payment application user interface on the mobile device;

a secure element incorporated into the mobile device, wherein the secure element is secure at least with respect to a user of the mobile device;

a user interface application installed on the mobile device, wherein the user interface application is external to the secure element, and wherein the user interface application includes instructions which, when executed by the electronic processor, generate a user interface enabling the user of the mobile device to interact with a mobile payment module; and

a plurality of functional modules installed in the secure element, wherein the plurality of modules includes;

the mobile payment module, the mobile payment module interacting with the mobile payment application user interface which is outside of the secure element, including instructions which, when executed by the electronic processor, enable the user of the mobile device to conduct a payment transaction;

a mobile gateway authentication module, the mobile gateway authentication module including instructions which, when executed by the electronic processor, mutually authenticate a mobile gateway and the mobile payment module;

an over the air communication and data transfer module, the over the air communication and data transfer module including instructions which, when executed by the electronic processor, transfer data and commands to conduct the payment transaction between a cellular network and the mobile device;

a process message module, the process message module including instructions which, when executed by the electronic processor, convert messages received from the mobile gateway into commands that are executable by other of the plurality of functional modules and to convert responses from the other of the plurality of functional modules into messages that are understood by the mobile gateway; and

a multi-access module, the multi-access module including instructions which, when executed by the electronic processor, maintain a plurality of multi-access instances at the mobile device, wherein each of the plurality of multi-access instances represents a unique financial account of a plurality of financial accounts of the user of the mobile device, wherein each of the multi-access instances includes unique data, wherein the multi-access module maintains non-unique shared data such that each of the plurality of multi-access instances including unique data shares the non-unique shared data with the other multi-access instances whereby a storage requirement for the plurality of instances of the multi-access module is reduced, and wherein the non-unique shared data includes a counter that is updated when the payment transaction is conducted using any of the plurality of financial accounts represented by the plurality of multi-access instances.

2. The apparatus of claim 1, wherein the non-unique shared data further comprises one or more of:

cryptographic keys, data used for a consumer verification, account related data, and payment transaction data.

3. The apparatus of claim 1, further comprising a cryptography function module, wherein the cryptography function module includes instructions which, when executed by the electronic processor, encrypt or decrypt data or messages.

4. The apparatus of claim 1, wherein a first instance of the plurality of multi-access instances corresponds to a domestic account of the user of the mobile device and a second instance of the plurality of multi-access instances corresponds to an international account of the user of the mobile device.

5. The apparatus of claim 1, wherein the secure element is secured at least in part by requiring that external access to the secure element is performed with a defined set of access commands.

6. The apparatus of claim 5, wherein the defined set of access commands is in accordance with at least one of the ISO 7816 series of standards.

7. The apparatus of claim 5, wherein the defined set of access commands comprises a select command that selects a particular financial account of the plurality of financial accounts stored on the secure element.

8. The apparatus of claim 7, wherein select command response data includes file control information.

9. The apparatus of claim 8, wherein the unique data of each of the multi-access instances maintained by the multi-access module comprises interchange profile data.

10. The apparatus of claim 5, wherein the defined set of access commands comprises a get processing options command that obtains options with respect to accessing the secure element, and wherein get processing options command response data contains at least one of:

file location data with respect to a selected financial account, and interchange profile data with respect to processing capabilities of the secure element.

11. The apparatus of claim 1, wherein fraud control with respect to the plurality of financial accounts of the user of the mobile device is based at least in part on the counter.

12. A method of conducting a payment transaction, comprising:

maintaining, by a multi-access module installed in a secure element of a mobile device, a plurality of multi-access instances, wherein each of the plurality of multi-access instances represents a unique financial account of a plurality of financial accounts of a user of the mobile device, wherein each of the plurality of the multi-access instances includes unique data and non-unique shared data, and wherein the multi-access module maintains the non-unique shared data such that each of the plurality of multi-access instances including unique data shares the non-unique shared data with the other multi-access instances whereby a storage requirement for the plurality of multi-access instances of the multi-access module in the secure element is reduced;

maintaining, by the multi-access module installed in the secure element of the mobile device, a counter as part of the non-unique shared data of the multi-access module;

performing, by a mobile payment module installed in the secure element of the mobile device via a mobile payment application user interface which is outside of a mobile payment application, a first payment transaction with respect to a first financial account of the plurality of financial accounts of the user of the mobile device, the first financial account corresponding to a first multi-access instance of the plurality of multi-access instances;

updating, by the first multi-access instance installed in the mobile device, the counter based at least in part on the first payment transaction;

performing, by the mobile payment module installed in the secure element of the mobile device via the mobile payment application user interface which is outside of the mobile payment application, a second payment transaction with respect to a second financial account of the plurality of financial accounts of the user of the mobile device, the second financial account corresponding to a second multi-access instance of the plurality of multi-access instances;

updating, by the second multi-access instance installed in the mobile device, the counter based at least in part on the second payment transaction; and

providing, by the multi-access module installed in the secure element of the mobile device, a value of the counter to enable multi-account functionality.

13. The method of claim 12, wherein the first multi-access instance of the plurality of multi-access instances corresponds to a domestic financial account of the user of the mobile device and the second multi-access instance of the plurality of multi-access instances corresponds to an international financial account of the user of the mobile device.

14. The method of claim 12, wherein the counter indicates a total number of transactions conducted using any of the plurality of financial accounts of the user of the mobile device.

15. The method of claim 12, wherein the counter indicates a total value of transactions conducted using any of the plurality of financial accounts of the user of the mobile device.

16. The method of claim 12, wherein the counter counts a total number of transactions across the plurality of financial accounts of the user of the mobile device.

17. The method of claim 12, wherein the counter counts a total value of transactions across the plurality of financial accounts of the user of the mobile device.

18. The method of claim 12, wherein the counter counts a total number of transactions in a particular transaction category of a plurality of transaction categories across the plurality of financial accounts of the user of the mobile device.

19. The method of claim 12, wherein providing the value of the counter enables multi-account functionality including multi-account fraud control.

20. The method of claim 12, wherein providing the value of the counter enables multi-account functionality including multi-account marketing.

21. The method of claim 12, further comprising:

receiving, with a toolkit module installed in the secure element of the mobile device, a scripting request from a source external to the secure element of the mobile device; and

responsive to receiving the scripting request, refreshing the counter maintained by the multi-access module.

22. One or more non-transitory computer readable media collectively storing instructions for conducting a payment transaction, which when executed by one or more processors of a computer system, collectively cause the computer system to perform operations comprising:

maintaining, by a multi-access module installed in a secure element of a mobile device, a plurality of multi-access instances, wherein each of the plurality of multi-access instances represents a unique financial account of a plurality of financial accounts of a user of the mobile device, wherein each of the plurality of the multi-access instances includes unique data and non-unique shared data, and wherein the multi-access module maintains the non-unique shared data such that each of the plurality of multi-access instances including unique data shares the non-unique shared data with the other multi-access instances whereby a storage requirement for the plurality of multi-access instances of the multi-access module in the secure element is reduced;

maintaining, by the multi-access module installed in the secure element of the mobile device, a counter as part of the non-unique shared data of the multi-access module;

performing, by a mobile payment module installed in the secure element of the mobile device via a mobile payment application user interface which is outside of a mobile payment application, a first payment transaction with respect to a first financial account of the plurality of financial accounts of the user of the mobile device, the first financial account corresponding to a first multi-access instance of the plurality of multi-access instances;

updating, by the first multi-access instance installed in the mobile device, the counter based at least in part on the first payment transaction;

performing, by the mobile payment module installed in the secure element of the mobile device via the mobile payment application user interface which is outside of the mobile payment application, a second payment transaction with respect to a second financial account of the plurality of financial accounts of the user of the mobile device, the second financial account corresponding to a second multi-access instance of the plurality of multi-access instances;

updating, by the second multi-access instance installed in the mobile device, the counter based at least in part on the second payment transaction; and

providing, by the multi-access module installed in the secure element of the mobile device, a value of the counter to enable multi-account functionality.