MOBILE WALLET EXPERIENCE FOR RESOLVING CONFLICTS BETWEEN DIFFERENT FINANCIAL INSTITUTIONS AND PAYMENT VEHICLES

• US 20120197787A1
• Filed: 01/31/2011
• Published: 08/02/2012
• Est. Priority Date: 01/31/2011
• Status: Abandoned Application

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Grigg, David M., Keller, Marc B.
• Application Number:
  US13/017,980
• Publication Number:
  US 20120197787A1
• Time in Patent Office: Days
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/363 with the personal data of a user

Abstract

In general, apparatuses, methods and computer program products for making contactless financial transactions utilizing a mobile wallet are disclosed. Particularly, a mobile wallet experience is disclosed. The experience aids to resolve conflicts between numerous payment vehicles and, particularly, financial institution-specific programs or sub-experiences on a mobile device. The mobile wallet experience permits a user to freely navigate various payment vehicles and, importantly, navigate efficiently through a plurality of financial institution sub-experiences.

Claims

1. A mobile device for making a financial transaction comprising:

a memory device;

a user interface configured to present information to a user;

a communication device;

a processing device operatively coupled to the memory device and the communication device; and

a mobile wallet experience configured to;

display, via the user interface, a menu, the menu comprising options selectable to the user, the options comprising at least one financial institution sub-experience;

receive a menu selection request from the user to execute the at least one financial institution sub-experience;

generate a secure connection between the processing device and a secure module, the secure module being associated with the selected financial institution sub-experience;

display, via the user interface, the at least one financial institution sub-experience;

receive instructions from the user accessing the at least one financial institution sub-experience to transmit payment vehicle data to an external apparatus; and

transmit the payment vehicle data wirelessly to the external apparatus.

2. The mobile device of claim 1, wherein the apparatus is a mobile phone.

3. The mobile device of claim 1, wherein the secure module is integrated into a chip in the mobile device.

4. The mobile device of claim 3, wherein the secure module is stored in a memory in the chip.

5. The mobile device of claim 1, wherein the external apparatus is a terminal configured to perform contactless transactions.

6. The mobile device of claim 1, wherein the mobile device is configured to be capable of near field communication (NFC).

7. The mobile device of claim 1, wherein the external apparatus is a contactless payment terminal.

8. The mobile device of claim 1, wherein the external apparatus is an automated teller machine (ATM).

9. The mobile device of claim 1, wherein the options selectable to the user comprise more than one financial institution sub-experience.

10. The mobile device of claim 9, wherein the mobile device is configured such that processing device may generate a secure connection to a unique secure module for each financial institution sub-experience, each financial institution sub-experience and/or the associated secure module comprising data associated with at least one payment vehicle, the payment vehicle being authorized by the financial institution associated with the sub-experience.

11. The mobile device of claim 10, wherein a plurality of secure modules are present on the same chip.

12. The mobile device of claim 10, wherein a plurality of secure modules are distributed on more than one chip.

13. The mobile device of claim 9, wherein each financial institution sub-experience is configured to be compatible with the mobile wallet experience.

14. The mobile device of claim 13, wherein the mobile wallet experience is further configured to:

receive instructions from the user to change menu selection from one financial institution sub-experience to a second financial institution sub-experience;

sever the secure connection between the processing device and the secure module; and

generate a second secure connection between the processing device and a second secure module, the second secure module being associated with the second financial institution sub-experience.

15. The mobile device of claim 1, wherein the mobile wallet experience is further configured to display, via the user interface, more than one financial institution sub-experience and payment vehicle data for payment vehicles not associated with any of the financial institution sub-experiences.

16. The mobile device of claim 1, wherein the mobile wallet experience is further configured to require security authorization from the user prior to displaying the menu, wherein no further security authorization is required to access the at least one financial institution sub-experience.

17. A method for making a financial transaction comprising:

executing, on a mobile device comprising a memory device, a user interface, a communication device, and a processing device, a mobile wallet experience, the mobile wallet experience comprising a menu of options selectable to a user, the options comprising at least one financial institution sub-experience;

select an option to engage a financial institution sub-experience;

select a payment vehicle to utilize for the financial transaction; and

transmit payment vehicle data associated with the payment vehicle wirelessly to an external apparatus.

18. The method of claim 17, wherein the mobile device is a mobile phone.

19. The method of claim 17, wherein, upon selecting to engage a financial institution sub-experience, a secure connection is formed between the processing device and a secure module.

20. The method of claim 19, wherein the secure module is integrated into a chip in the mobile device.

21. The method of claim 20, wherein the secure module is stored in a memory in the chip.

22. The method of claim 17, wherein the external apparatus is a terminal configured to perform contactless transactions.

23. The method of claim 17, wherein the mobile device is configured to be capable of near field communication (NFC).

24. The method of claim 17, wherein the external apparatus is a contactless payment terminal.

25. The method of claim 17, wherein the external apparatus is an automated teller machine (ATM).

26. The method of claim 17, wherein the options selectable to the user comprise more than one financial institution sub-experience.

27. The method of claim 26, wherein the mobile device is configured such that processing device may generate a secure connection to a unique secure module for each financial institution sub-experience, each financial institution sub-experience and/or the associated secure module comprising data associated with at least one payment vehicle, the payment vehicle being authorized by the financial institution associated with the sub-experience.

28. The method of claim 27, wherein a plurality of secure modules are present on the same chip.

29. The method of claim 27, wherein a plurality of secure modules are distributed on more than one chip.

30. The method of claim 26, wherein each financial institution sub-experience is configured to be compatible with the mobile wallet experience.

31. The method of claim 26, further comprising:

changing from engaging one financial institution sub-experience to engaging a second financial institution sub-experience.

32. The method of claim 31, wherein upon changing, a first secure connection between the processing device and a first secure module is severed, and a second secure connection between the processing device and a second secure module is formed, the second secure module being associated with the second financial institution sub-experience.

33. The method of claim 17, wherein the menu of options selectable to the user comprise more than one financial institution sub-experience and payment vehicle data for payment vehicles not associated with any of the financial institution sub-experiences.

34. The method of claim 17, wherein the mobile wallet experience requires security authorization from the user, wherein no further security authorization is required to access the at least one financial institution sub-experience.

35. A computer program product for making a financial transaction via a mobile device, the computer program product comprising a non-transitory computer-readable medium comprising computer program code instructions for:

executing, on a mobile device, a mobile wallet experience configured to be capable of presenting a menu of options selectable to a user, the options comprising more than one financial institution sub-experience, the financial institution sub-experiences being configured to be compatible with the mobile wallet experience such that a user may freely switch between financial institution sub-experiences without significant delay or conflict, the set of code configured to form a secure connection between a processing device and a secure module upon selection of a financial institution sub-experience by the user, the set of code being further configured to sever the connection between the processing device and the secure module upon instruction from the user to change from the financial institution sub-experience to a second financial institution sub-experience and generate a second secure connection to a second secure module, the second secure module being associated with the second financial institution sub-experience, the set of code being further configured to transmit payment vehicle data associated with a payment vehicle wirelessly to an external apparatus.

36. The computer program product of claim 35, wherein the mobile device is a mobile phone.

37. The computer program product of claim 35, wherein the secure modules are integrated into a chip in the mobile device.

38. The computer program product of claim 37, wherein the secure modules are stored in a memory in the chip.

39. The computer program product of claim 35, wherein the set of code is configured to transmit the payment vehicle data via near field communication (NFC).

40. The computer program product of claim 35, wherein the external apparatus is a contactless payment terminal.

41. The computer program product of claim 35, wherein the external apparatus is an automated teller machine (ATM).

42. The computer program product of claim 35, wherein the menu of options selectable to the user additionally comprise payment vehicle data for payment vehicles not associated with any of the financial institution sub-experiences.

43. The computer program product of claim 35, wherein the set of code is configured to require security authorization from the user to access the mobile wallet experience, wherein no further security authorization is required in order to access the financial institution sub-experiences.