Systems, methods, and computer program products for integrating third party services with a mobile wallet

• US 10,387,873 B2
• Filed: 01/12/2017
• Issued: 08/20/2019
• Est. Priority Date: 07/09/2012
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Kuhn, Stephen, Lipton, Daniel L., Johnson, Kai P., Watkins, Ryan
• Primary Examiner(s): Robinson, Kito R
• Application Number:
  US15/404,439
• Publication Number:
  US 20170124559A1
• Time in Patent Office: 950 Days
• Field of Search: 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
• 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 to communicate user service requests to service provider systems and to provide response data associated with user service requests via a wallet client of a mobile device, the system comprising:

at least one storage device; and

at least one processor communicatively coupled to the at least one storage device, wherein the at least one processor executes instructions that are stored in the at least one storage device to cause the system to;

receive, in a wallet client database, service provider system information from a service provider system;

receive, in the wallet client database, database entries that include, in association with the service provider system and an operating system, a base URL, an authentication procedure, and a URL signature; and

receive, in a wallet client, an indication of a selection of a particular user service request;

receive, in the wallet client, an indication of a selection of a particular user service request;

authenticate the wallet client with the service provider system based on the service provider information, 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;

upon authentication, establish a communication session with the service provider system;

transmit, to the service provider system, an invocation message including a wallet identifier and a request URL associated with the particular user service request;

receive, from the service provider system, data in response to the request URL; and

present, via a user interface, at least a portion of the data received from the service provider system.

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

a service provider system name, a service provider system 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 system 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 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.

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

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

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

wherein the request URL transmitted to the service provider system comprises the signed encrypted request URL.

5. The system of claim 4, wherein the request URL corresponds to at least one of a service provider system website, a service provider system web application, a service provider system mobile device, or a mobile device application store application, and wherein establishing a communication session further comprises launching the corresponding website or application on the system to communicate with the service provider system via the corresponding website or application.

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

7. 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 the payment product, presenting payment product details, upgrading the payment product, or adding funds to the payment product.

8. A method to communicate user service requests to service provider systems and to provide response data associated with user service requests via a wallet client of a mobile device, comprising:

receiving, by a wallet client database and on a mobile device, service provider system information from a service provider system comprising instructions to generate request uniform resource locators (URLs) associated with one or more user service requests;

receive database entries that include, in association with the service provider system and an operating system, a base URL, an authentication procedure, and a URL signature;

receive, in a wallet client on the mobile device, an indication of a selection of a particular user service request; and

,

authenticate a wallet client with the service provider system based on the service provider information, 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;

upon authentication, establish a communication session with the service provider system;

transmit, to the service provider system, an invocation message including a wallet identifier and a request URL associated with the particular user service request;

receive, from the service provider system, data in response to the request URL; and

present, via a user interface of the mobile device, at least a portion of the data received from the service provider system.

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

a service provider system name, a service provider system listing, a payment product name, customer care contact information, a request URL to a payment product registration webpage, a request URL to a payment product activation service, a request URL to a service provider website, a request 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.

10. The method of claim 8, 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.

11. The method of claim 10, wherein the invoking of the servicing environment includes:

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

wherein the request URL in the invocation message comprises the signed encrypted URL.

12. The method of claim 11, wherein the request URL corresponds to a service provider system website.

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

14. The method according to claim 8, further comprising, after the invoking of the service environment, one or more of:

activating, by the service provider system, a payment product, wherein the request URL corresponds to a user service request to activate the payment product and wherein the response data received from the service provider system indicates that the payment product was successfully activated,

upgrading, by the service provider system, the payment product, wherein the base URL corresponds to a user service request to upgrade the payment product and wherein the response data received from the service provider system comprises an indication that the payment product was upgraded, and

adding, by the service provider system, funds to the payment product, wherein the base URL corresponds to a user service request to add the funds to the payment product and wherein the response data received from the service provider system comprises an indication that the funds were added to the payment product.

15. A non-transitory computer-readable medium having computer-executable program instructions embodied thereon that when executed by a computer cause the computer to communicate user service requests to service providers and to provide response data associated with user service requests via a wallet client of a mobile device, the computer-executable program instructions comprising:

computer-executable program instructions to receive service provider system information from a service provider system;

computer-executable program instructions to receive database entries that include, in association with the service provider system and an operating system, a base URL, an authentication procedure, and a URL signature;

computer-executable program instructions to receive, in a wallet client on a mobile device, an indication of a selection of a particular user service request;

computer-executable program instructions to receive, in a wallet client on the mobile device, an indication of a selection of a particular user service request to authenticate, based on the service provider system information,

computer-executable program instructions to authenticate the wallet client with a service provider system based on the service provider information, 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;

upon authentication, computer-executable program instructions to establish a communication session with the service provider system;

computer-executable program instructions to transmit, to the service provider system, an invocation message including a wallet identifier and a request URL associated with the particular user service request;

computer-executable program instructions to receive, from the service provider system, data in response to the request URL; and

computer-executable program instructions to present, via a user interface of the mobile device, at least a portion of the data received from the service provider system.

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

a service provider system name, a service provider system 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 system 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.

17. The non-transitory computer-readable medium of claim 15, 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.

18. 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 invoke the servicing environment by:

retrieving a URL from the service provider system 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.

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

20. The non-transitory computer-readable medium of claim 18, 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 system mobile device application that is unavailable, a mobile device store application and downloads the service provider system mobile device application.

21. The non-transitory computer-readable medium of claim 15, 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 the payment product, presenting payment product details, upgrading the payment product, or adding funds to the payment product.