Secure ecosystem infrastructure enabling multiple types of electronic wallets in an ecosystem of issuers, service providers, and acquires of instruments

• US 10,176,476 B2
• Filed: 06/04/2013
• Issued: 01/08/2019
• Est. Priority Date: 10/06/2005
• Status: Active Grant

• Current Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Original Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Inventors: Desai, Mehul, Pitroda, Satyan G., Maniar, Nehal
• Primary Examiner(s): Wong, Eric T
• Assistant Examiner(s): Poe, Kevin T
• Application Number:
  US13/909,262
• Publication Number:
  US 20130268437A1
• Time in Patent Office: 2,044 Days
• Field of Search: 705 41
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06Q 20/08 Payment architectures
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• 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 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0641 Shopping interfaces

Abstract

A platform for performing secure personalized transactions in a multi-domain ecosystem includes a personalization tier that enables service provider personalization for one or more ecosystem elements stored on a mobile device. Further, the platform includes an enabling tier for facilitating interoperation between the personalization tier and a client device. The platform further includes a service tier that may be operating independently of the enabling tier and may enable service delivery for a plurality of services.

Claims

1. A system comprising:

a platform for service-provider development and personalization of multiple service-types of electronic wallets in a multi-tier mobile transaction processing platform for secure personalized transactions in a multi-domain ecosystem comprising at least one processor and non-transient memory storage device, the platform comprising;

a software development kit executing on the at least one processor for developing a plurality of different types of provider specific electronic wallets, wherein the software development kit comprises a first part for wallet development and a second part for widget development of provider specific widgets that are deployable on a plurality of client device types without requiring mobile-device specific programming, the software development kit is executable at least in part by a service provider-specific networked workstation;

a plurality of reference service implementations for electronic wallets in the ecosystem and stored on the memory storage device, the reference implementations accessible through the software development kit, wherein the plurality of reference service implementations for electronic wallets comprises a reference implementation of a wallet for each of a plurality of provider types including an instrument issuer, a service provider, and an instrument acquirer;

a mobile application deployment capability executing on the at least one processor that facilitates deployment of service provider specific wallets developed through the software development kit for at least one of the instrument issuer, the service provider, and the instrument acquirer service provider types, the mobile application deployment capability further providing at least two types of mobile application deployment models selected from the list of application deployment models consisting of independent native application model, hybrid ecosystem application model, and cross-platform ecosystem application model; and

a runtime container stored on the memory storage device that is configurable via the software development kit to be operable on a client device and for receiving different types of provider specific wallets, wherein the runtime container facilitates the distinct operation of each type of provider specific wallet, and wherein the distinct operation of each type of provider specific wallet enables secure transactions involving a provider that developed the provider specific wallet.

2. The system of claim 1, wherein the runtime container facilitates operation of a provider specific widget.

3. The system of claim 1, wherein the software development kit facilitates maintaining client-device operable wallets, widgets, companion applets and containers.

4. The system of claim 1, wherein the software development kit facilitates configuration of parameters for customizing client-side user experience.

5. The system of claim 1, wherein the software development kit includes a configuration module that facilitates customizing enabling tier and service tier parameters.

6. The system of claim 1, wherein the software development kit includes an interface module that facilitates integrating peripheral customer care and user portal systems.

7. The system of claim 1, wherein the software development kit facilitates enabling support for multiple types of client devices, security, authentication, and NFC-based secure proximity transactions.

8. The system of claim 1, wherein the software development kit facilitates development of a client-operable widget based on service provider specific requirements.

9. A method of enabling multiple types of electronic wallets in an ecosystem, comprising:

developing a plurality of different types of provider specific wallets with a software development kit, wherein the software development kit is executable at least in part by a networked workstation;

accessing a plurality of reference wallets through the software development kit, wherein the plurality of reference wallets comprises a reference wallet for each of a plurality of provider types including an instrument issuer, a service provider, and an instrument acquirer; and

communicating over a network with a runtime container operable on a client device to facilitate deployment of different types of provider specific wallets, wherein the runtime container facilitates the distinct operation of each type of provider specific wallet, and wherein the distinct operation of each type of provider specific wallet enables secure transactions involving a provider that developed the provider specific wallet.