Ensuring secure access by a service provider to one of a plurality of mobile electronic wallets

• US 10,510,055 B2
• Filed: 07/02/2015
• Issued: 12/17/2019
• Est. Priority Date: 10/31/2007
• Status: Active Grant

• Current Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Original Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Inventors: Desai, Mehul, Maniar, Nehal
• Primary Examiner(s): Wong, Eric T
• Assistant Examiner(s): Poe, Kevin T
• Application Number:
  US14/790,403
• Publication Number:
  US 20150332254A1
• Time in Patent Office: 1,629 Days
• Field of Search: 705 41
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in 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/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/363 with the personal data of a user
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/3829 involving key management
• 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: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/4015 using location information
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Facilitating exclusive access to a workflow of a service provider via a mobile wallet interface involves, within a client runtime environment, activating through the interface a service provider-specific application so that the service provider-specific application has exclusive access to a secure electronic transaction workflow of the service provider associated with at least one of the service provider-specific application and the wallet, while being denied access by the client runtime environment to any other service provider services or resources.

Claims

1. A method comprising:

disposing a plurality of distinct wallets in a memory of a personal mobile device;

disposing at least one service provider-specific application in the memory;

executing at least one of the plurality of distinct wallets in a client runtime environment on the personal mobile device; and

facilitating access to service provider services through an interface of the at least one of the plurality of distinct wallets by activating, through the interface, the at least one service provider-specific application to execute in the client runtime environment, whereby the activated service provider-specific application is granted exclusive access for a period to a secure electronic transaction workflow of a service provider for accessing the service provider services;

wherein execution of at least one of the distinct wallets is suspended during the period of granting of exclusive access and wherein facilitating access to service provider services is accomplished by interfacing with an API layer of one or more device-specific APIs.

2. The method of claim 1, wherein the interface of the at least one of the plurality of distinct wallets comprises a secure entry point for one of the at least one of the plurality of service provider-specific applications, the secure entry point managed by the client runtime environment.

3. The method of claim 2, wherein the client runtime environment comprises a runtime environment provided by a wallet container executing on the personal mobile device.

4. The method of claim 1, wherein facilitating access comprises presenting a menu of service provider services in a user interface of the at least one of the plurality of distinct wallets.

5. The method of claim 4, wherein activating the at least one service provider-specific application is in response to an indication of a user selection of a service provider service in the menu of service provider services.

6. The method of claim 1, wherein the service provider-specific application is issued by the service provider through which the service provider services are accessed.

7. The method of claim 1, wherein the at least one service provider-specific application provides a user of the personal mobile device access via one of the plurality of wallets to at least one business-specific service of a service provider that issued the service provider-specific application.

8. The method of claim 1, wherein the client runtime environment is provided by a wallet container executing on the personal mobile device.

9. The method of claim 8, wherein the at least one service provider-specific application comprises a widget operating within a runtime environment provided by the wallet container.

10. The method of claim 8, wherein the interface of the at least one of the plurality of distinct wallets is provided by the wallet container to the at least one of the plurality of service provider-specific applications.

11. The method of claim 1, wherein the client runtime environment is adapted to deny access by the service provider-specific application to at least one other of the plurality of distinct wallets.

12. The method of claim 1, wherein the client runtime environment is adapted to deny access by the service provider-specific application to at least one other service provider'"'"'s secure electronic transaction workflow.

13. The method of claim 12, wherein the client runtime environment is a mobile device operating system.

14. The method of claim 12, wherein the client runtime environment is by a wallet container executing on the personal mobile device.

15. The method of claim 1, wherein a portion of the plurality of distinct wallets are provided to a wallet container of the mobile device over a network by a service provider.

16. A method comprising:

disposing a plurality of distinct wallets in a memory of a personal mobile device;

disposing at least one service provider-specific application in the memory;

executing on the personal mobile device at least two of the plurality of distinct wallets in a client runtime environment adapted to ensure isolated access to personal mobile device resources including the memory; and

facilitating access to service provider services through an interface of one of the executing distinct wallets by activating, through the interface, the at least one service provider-specific application to execute in the client runtime environment, whereby the activated service provider-specific application is granted exclusive access to a secure electronic transaction workflow of a service provider for accessing the service provider services.

17. The method of claim 16, wherein execution of the at least one of the plurality of distinct wallets is suspended during a period of granting the exclusive access.

18. A method comprising:

disposing a plurality of distinct wallets in a memory of a personal mobile device;

disposing at least one service provider-specific application in the memory;

executing at least one of the plurality of distinct wallets in a client runtime environment on the personal mobile device;

facilitating access to service provider services through an interface of the at least one of the plurality of distinct wallets by activating, through the interface, the at least one service provider-specific application to execute in the client runtime environment, whereby the activated service provider-specific application is denied access to the wallet based on the client runtime environment receiving an indication of a wallet access trigger occurrence.

19. The method of claim 18, wherein execution of the at least one of the plurality of distinct wallets is suspended during a period of granting exclusive access.