HANDS-FREE OFFLINE COMMUNICATIONS

• US 20160012430A1
• Filed: 07/10/2015
• Published: 01/14/2016
• Est. Priority Date: 07/11/2014
• Status: Active Application

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Chandrasekaran, Sashikanth, Duong, Thai Ngoc, Ho, Denise, Setchell, William Hartley, Smetters, Diana K., Walfish, Sheldon I., Xu, Zhihong
• Application Number:
  US14/797,029
• Publication Number:
  US 20160012430A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• 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/0457 the tickets being sent electronically
• CPC Class Codes: G06Q 20/16 Payments settled via telecommunication systems
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules

Abstract

A payment processing system receives a token from a user device. Based on the first token, the payment processing system establishes a second token that remains valid longer than the first token. The payment processing system then associates the second token with a user account identifier and establishes a rescue code for use in an offline user transactions. The payment processing system then communicates the second token and the rescue code to the user device. When the user engages in an offline transaction, the payment processing system receives the rescue code and the user account identifier from the merchant computing device. Based on the user account identifier received from the merchant computing devices, the payment processing system identifies the second token and verifies that the received rescue code matches the rescue code associated with the user account identifier. Based on the verification, the payment processing system authorizes the sales transaction.

Claims

1. A computer-implemented method to complete offline exchanges of information between two computing devices, wherein the exchange requires authentication by a third computing device, comprising:

receiving, by one or more computing devices, a first token associated with a user account from a user computing device, wherein the user computing device is distinct from the one or more computing devices;

in response to receiving the first token, generating, by the one or more computing devices, a second token associated with the user account, wherein the second token remains valid longer than the first token;

associating, by the one or more computing devices, the second token with a user account identifier;

generating, by the one or more computing devices, a code for use in an offline exchange between the user computing device and a merchant computing device;

associating, by the one or more computing devices, the code with the user account identifier;

communicating, by the one or more computing devices, the code and the user account identifier to the user computing device;

receiving, by the one or more computing devices and from the merchant computing device, the code and the user account identifier after the user computing device communicated the code and the user account identifier to the merchant computing device while the user computing device was in an offline state with respect to the one or more computing devices, wherein the merchant computing device is distinct from both the one or more computing devices and the user computing device;

identifying, by the one or more computing devices and based on the user account identifier received from the one or more merchant computing devices, the second token associated with the user account identifier;

verifying, by the one or more computing devices, that the code received from the merchant computing device matches the code associated with the user account identifier; and

in response to verifying that the code received from the merchant computing device matches the code associated with the user account identifier, authenticating the communication between the user computing device and the merchant computing device while the user computing device was in an offline state with respect to the one or more computing devices.

2. The computer-implemented method of claim 1, wherein authenticating the communication comprises authorizing, by the one or more computing devices and using the second token, a sales transaction involving the user account.

3. The computer-implemented method of claim 1, wherein receiving the code and the user account identifier from the one or more merchant computing devices comprises:

receiving, by the one or more merchant computing devices, the code and the user account identifier from the user computing device;

communicating, by the one or more merchant computing devices, the code and the user account identifier to the one or more computing systems.

4. The computer-implemented method of claim 3, wherein receiving the code and the user account identifier from the user computing device comprises scanning a bar code or a Quick Response Code comprising the code, the user account identifier, or both the code and the user account identifier.

5. The computer-implemented method of claim 1, wherein the code comprises a shared random counter.

6. The computer-implemented method of claim 1, wherein the second token remains valid for two weeks.

7. The computer-implemented method of claim 1, wherein the user computing device periodically communicates a first token to the one or more computing systems.

8. The computer-implemented method of claim 7, wherein the user computing device communicates the first token to the one or more computing devices every three days.

9. The computer-implemented method of claim 1, wherein verification of the rescue code further comprises recalculating a shared secret rescue code computation.

10. A computer program product, comprising:

a non-transitory computer-readable medium having computer-executable program instructions embodied therein that when executed by a computer cause the computer to complete offline transactions, the computer-executable program instructions comprising;

computer-executable program instructions to receive a first token from a user computing device, wherein the user computing device is associated with a user financial account of a user;

computer-executable program instructions to generate, in response to receiving the first token, a second token, wherein the second token remains valid longer than the first token;

computer-executable program instructions to associate the second token with a user account identifier;

computer-executable program instructions to generate a code for use in an offline sales transaction of the user, wherein the code is associated with the user account identifier;

computer-executable program instructions to communicate the code and the user account identifier to the user computing device;

computer-executable program instructions to receive, from one or more merchant computing devices, the code and the user account identifier after the user computing device communicated the code and the user account identifier to the merchant computing device while the user computing device was in an offline state with respect to the one or more computing devices, wherein the merchant computing device is distinct from the user computing device;

computer-executable program instructions to identify, based on the user account identifier received from the one or more merchant computing devices, the second token associated with the user account identifier;

computer-executable program instructions to verify that the code received from the merchant computing device matches the code associated with the user account identifier; and

computer-executable program instructions to authenticate, in response to verifying that the code received from the merchant computing system matches the code associated with the user account identifier and using the second token, the communication between the user computing device and the merchant computing device while the user computing device was in an offline state with respect to the one or more computing devices.

11. The computer program product of claim 10, wherein receiving the code and the user account identifier from the one or more merchant computing devices comprises:

receiving, by the one or more merchant computing devices, the code and the user account identifier from the user computing device, wherein receiving the code and the user account identifier from the user computing device comprises scanning a bar code or Quick Response Code comprising the code, the user account identifier, or both the code and the user account identifier; and

communicating, by the one or more merchant computing devices, the code and the user account identifier to the one or more computing systems.

12. The computer program product of claim 10, wherein the code comprises a shared random counter.

13. The computer program product of claim 10, wherein the second token remains valid for about two weeks, about three weeks, or about four weeks.

14. The computer program product of claim 10, wherein verification of the code further comprises recalculating the code.

15. A system to complete offline transactions, comprising:

a storage device; and

a processor communicatively coupled to the storage device, wherein the processor executes application code instructions that are stored in the storage device to cause the system to;

receive a first token from a user computing device, wherein the user computing device is associated with a user financial account of a user;

generate, in response to receiving the first token, a second token, wherein the second token remains valid longer than the first token;

associate the second token with a user account identifier;

generate a key code for use in an offline sales transaction of the user, wherein the key code is associated with the user account identifier;

communicate the key code and the user account identifier to the user computing device;

receive, from one or more merchant computing devices, the key code and the user account identifier after the user computing device communicated the key code and the user account identifier to the merchant computing device while the user computing device was in an offline state with respect to the one or more computing devices, wherein the merchant computing device is separate from the user computing device;

identify, based on the user account identifier received from the one or more merchant computing devices, the second token associated with the user account identifier;

verify that the key code received from the merchant computing system matches the code associated with the user account identifier; and

in response to verifying that key code received from the merchant computing system matches the key code associated with the user account identifier and using the second token, authenticate the transaction while the user computing device was in an offline state with respect to the one or more computing devices.

16. The system of claim 15, wherein receiving the key code and the user account identifier from the one or more merchant computing devices comprises:

receiving, by the one or more merchant computing devices, the key code and the user account identifier from the user computing device; and

communicating, by the one or more merchant computing devices, the key code and the user account identifier to the processor.

17. The system of claim 16, wherein receiving the key code and the user account identifier from the user computing device comprises scanning a bar code or Quick Response Code comprising the key code, the user account identifier, or both the key code and the user account identifier.

18. The system of claim 15, wherein the key code comprises a shared random counter.