SYSTEMS, METHODS, AND COMPUTER PROGRAM PRODUCTS FOR INTEGRATING THIRD PARTY SERVICES WITH A MOBILE WALLET

• US 20140012751A1
• Filed: 07/02/2013
• Published: 01/09/2014
• Est. Priority Date: 07/09/2012
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: JVL Ventures LLC (Alphabet Inc.)
• Inventors: Johnson, Kai P., Kuhn, Stephen, Lipton, Daniel L., Watkins, Ryan
• Granted Patent: US 9,563,891 B2
• Time in Patent Office: Days
• US Class Current: 705/41
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• 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 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

Systems, methods, and computer program products are provided for providing a third party service via a wallet client. Service provider information is received from a service provider and stored in a wallet client database. Based on the service provider information, a wallet client is authenticated with a service provider system, a communication session is established, and a servicing environment is invoked.

Claims

1. A system for providing a third party service via a wallet client, the method comprising steps of:

a wallet client database operable to receive service provider information from a service provider and store the service provider information; and

a wallet client communicatively coupled to the wallet client database and including at least one processor operable to, based on the service provider information;

authenticate a wallet client with a service provider system,

establish a communication session, and

invoke a servicing environment.

2. The system of claim 1, wherein the service provider information includes at least one of:

a service provider name, a service provider listing, a payment product name, customer care contact information, a uniform resource locator (URL) to a payment product registration webpage, a URL to a payment product activation service, a URL to a service provider website, a URL to a service provider mobile application, a logo corresponding to payment product, payment product identifying digits, a payment product expiration date, a payment product current balance, a payment product amount of available credit, or an activation state of the payment product.

3. The system of claim 1, the wallet client database being further operable to store database entries that include, in association with a service provider and an operating system, a base URL, an authentication procedure, and a URL signature, and

the at least one processor being further operable to authenticate the wallet client by:

validating the URL signature,

creating an authentication request based on the base URL,

adding parameters to the authentication request based on the authentication procedure, thereby generating an augmented authentication request, and

transmitting the augmented authentication request to the service provider system.

4. The system of claim 1, the at least one processor being further operable to establish the communication session by:

generating a first nonce and a second nonce;

transmitting a session establishment request to a wallet server, the session establishment request including at least one of;

the first nonce and the second nonce, a cryptographic ticket scheme, a wallet identifier associated with the wallet client, or a mobile device identifier associated with the wallet client;

generating a signing key based on the first nonce;

generating an encryption key based on the second nonce signing at least one message using the signing key; and

encrypting the at least one message using the encryption key.

5. The system of claim 4, the at least one processor being further operable to invoke the servicing environment by:

retrieving a URL from the service provider information in the wallet client database;

signing the URL using the signing key and encrypting the URL using the encryption key, thereby generating a signed encrypted URL; and

transmitting, to the service provider system, an invocation message including a wallet identifier and the signed encrypted URL.

6. The system of claim 5, wherein the URL corresponds to at least one of a service provider website, a service provider web application, a service provider mobile device application, or a mobile device application store application.

7. The system of claim 5, wherein the at least one processor is further operable to launch, if the URL corresponds to a service provider mobile device application that is unavailable, a mobile device application store application and downloads the service provider mobile device application.

8. The system according to claim 1, the at least one processor is further operable to, after the invoking of the service environment, perform at least one of:

adding a payment product to the wallet client, activating a payment product, presenting payment product details, upgrading a payment product, or adding funds to a payment product.

9. A method for providing a third party service via a wallet client, the method comprising steps of:

receiving service provider information from a service provider and storing the service provider information in a wallet client database; and

,

based on the service provider information;

authenticating a wallet client with a service provider system,

establishing a communication session, and

invoking a servicing environment.

10. The method of claim 9, wherein the service provider information includes at least one of:

a service provider name, a service provider listing, a payment product name, customer care contact information, a uniform resource locator (URL) to a payment product registration webpage, a URL to a payment product activation service, a URL to a service provider website, a URL to a service provider mobile application, a logo corresponding to payment product, payment product identifying digits, a payment product expiration date, a payment product current balance, a payment product amount of available credit, or an activation state of the payment product.

11. The method of claim 9, further comprising a step of storing, in the wallet client database, database entries that include, in association with a service provider and an operating system, a base URL, an authentication procedure, and a URL signature, and

wherein the authenticating the wallet client further includes:

validating the URL signature,

creating an authentication request based on the base URL,

adding parameters to the authentication request based on the authentication procedure, thereby generating an augmented authentication request, and

transmitting the augmented authentication request to the service provider system.

12. The method of claim 9, wherein the establishing of the communication session includes:

generating a first nonce and a second nonce;

transmitting a session establishment request to a wallet server, the session establishment request including at least one of;

the first nonce and the second nonce, a cryptographic ticket scheme, a wallet identifier associated with the wallet client, or a mobile device identifier associated with the wallet client;

generating a signing key based on the first nonce;

generating an encryption key based on the second nonce signing at least one message using the signing key; and

encrypting the at least one message using the encryption key.

13. The method of claim 12, wherein the invoking of the servicing environment includes:

retrieving a URL from the service provider information in the wallet client database;

signing the URL using the signing key and encrypting the URL using the encryption key, thereby generating a signed encrypted URL; and

transmitting, to the service provider system, an invocation message including a wallet identifier and the signed encrypted URL.

14. The method of claim 13, wherein the URL corresponds to at least one of a service provider website, a service provider web application, a service provider mobile device application, or a mobile device application store application.

15. The method of claim 13, wherein, if the URL corresponds to a service provider mobile device application that is unavailable, the wallet client launches a mobile device application store application and downloads the service provider mobile device application.

16. The method according to claim 9, further comprising, after the invoking of the service environment, at least one of:

adding a payment product to the wallet client, activating a payment product, presenting payment product details, upgrading a payment product, or adding funds to a payment product.

17. A non-transitory computer-readable medium for providing a third party service via a wallet client, the method comprising steps of:

receiving service provider information from a service provider and storing the service provider information in a wallet client database; and

,

based on the service provider information;

authenticating a wallet client with a service provider system,

establishing a communication session, and

invoking a servicing environment.

18. The non-transitory computer-readable medium of claim 17, wherein the service provider information includes at least one of:

a service provider name, a service provider listing, a payment product name, customer care contact information, a uniform resource locator (URL) to a payment product registration webpage, a URL to a payment product activation service, a URL to a service provider website, a URL to a service provider mobile application, a logo corresponding to payment product, payment product identifying digits, a payment product expiration date, a payment product current balance, a payment product amount of available credit, or an activation state of the payment product.

19. The non-transitory computer-readable medium of claim 17, when executed by the computer processor, the sequences of instructions further cause the computer processor to store, in the wallet client database, database entries that include, in association with a service provider and an operating system, a base URL, an authentication procedure, and a URL signature, and

wherein the authenticating the wallet client further includes:

validating the URL signature,

creating an authentication request based on the base URL,

adding parameters to the authentication request based on the authentication procedure, thereby generating an augmented authentication request, and

transmitting the augmented authentication request to the service provider system.

20. The non-transitory computer-readable medium of claim 17, wherein, when executed by the computer processor, the sequences of instructions further cause the computer processor to establish the communication session by:

generating a first nonce and a second nonce;

transmitting a session establishment request to a wallet server, the session establishment request including at least one of;

the first nonce and the second nonce, a cryptographic ticket scheme, a wallet identifier associated with the wallet client, or a mobile device identifier associated with the wallet client;

generating a signing key based on the first nonce;

generating an encryption key based on the second nonce signing at least one message using the signing key; and

encrypting the at least one message using the encryption key.

21. The non-transitory computer-readable medium of claim 20, wherein, when executed by the computer processor, the sequences of instructions further cause the computer processor to invoke the servicing environment by:

retrieving a URL from the service provider information in the wallet client database;

signing the URL using the signing key and encrypting the URL using the encryption key, thereby generating a signed encrypted URL; and

transmitting, to the service provider system, an invocation message including a wallet identifier and the signed encrypted URL.

22. The non-transitory computer-readable medium of claim 21, wherein the URL corresponds to at least one of a service provider website, a service provider web application, a service provider mobile device application, or a mobile device application store application.

23. The non-transitory computer-readable medium of claim 21, wherein, when executed by the computer processor, the sequences of instructions further cause the computer processor to launch, if the URL corresponds to a service provider mobile device application that is unavailable, a mobile device application store application and downloads the service provider mobile device application.

24. The non-transitory computer-readable medium according to claim 17, wherein, when executed by the computer processor, the sequences of instructions further cause the computer processor to, after the invoking of the service environment, perform at least one of:

adding a payment product to the wallet client, activating a payment product, presenting payment product details, upgrading a payment product, or adding funds to a payment product.