AUTOMATIC PAYMENT CODE DISPLAY SYSTEM

• US 20150379506A1
• Filed: 06/27/2014
• Published: 12/31/2015
• Est. Priority Date: 06/27/2014
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Griffin, Kent
• Granted Patent: US 9,589,263 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/3226 Use of secure elements separate from M-devices
• 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

Automatic payment code display systems and methods include a user device detecting a beacon system at a physical merchant location. The user device establishes a background communication process with the beacon system that occurs without user intervention subsequent to detecting the beacon system. The user device then provides the user account authentication token to the beacon system as part of the background communication process. The user device then receives a payment code from the beacon system as part of the background communication process. The user device then causes the payment code to be displayed, and the displayed payment code is configured to be utilized by a payment processing device at the physical merchant location in a payment transaction. The payment code may be caused to be displayed on a lock screen in a background display process that occurs without user intervention.

Claims

1. An automatic payment code display system, comprising:

a non-transitory memory storing a user account authentication token;

one or more hardware processors coupled to the memory and configured to read instructions from the memory to perform the steps of;

detecting a beacon system at a physical merchant location;

establishing a background communication process with the beacon system, wherein the background communication process occurs without user intervention subsequent to detecting the beacon system;

providing the user account authentication token to the beacon system as part of the background communication process;

receiving a payment code from the beacon system as part of the background communication process; and

causing the payment code to be displayed, wherein the payment code is configured to be utilized by a payment processing device at the physical merchant location in a payment transaction.

2. The system of claim 1, wherein the causing the payment code to be displayed includes causing the payment code to be displayed on a lock screen in a background display process that occurs without user intervention.

3. The system of claim 1, and wherein the one or more hardware processors are further operable to read instructions from the memory to perform the steps of:

causing a payment code notification to be displayed on a lock screen in a background display process that occurs without user intervention; and

detecting a user input that was instructed by the payment code notification and, in response, causing the payment code to be displayed.

4. The system of claim 1, wherein the payment code is configured to scanned by a scanning device that is coupled to the payment processing device.

5. The system of claim 1, wherein the one or more hardware processors are further operable to read instructions from the memory to perform the steps of:

receiving the user account authentication token over a network from a payment service provider device; and

storing the user account authentication token in the non-transitory memory.

6. The system of claim 1, wherein the payment code encodes a user payment account identifier for a user payment account and a merchant payment account identifier for a merchant payment account.

7. A method for automatically displaying a payment code, comprising:

detecting, by a user device, a beacon system at a physical merchant location;

establishing, by the user device, a background communication process with the beacon system, wherein the background communication process occurs without user intervention subsequent to detecting the beacon system;

providing, by the user device, a user account authentication token that is stored in a database to the beacon system as part of the background communication process;

receiving, by the user device, a payment code from the beacon system as part of the background communication process; and

causing, by the user device, the payment code to be displayed, wherein the payment code is configured to be utilized by a payment processing device at the physical merchant location in a payment transaction.

8. The method of claim 7, wherein the causing the payment code to be displayed includes causing the payment code to be displayed on a lock screen in a background display process that occurs without user intervention.

9. The method of claim 7, further comprising:

causing, by the user device, a payment code notification to be displayed on a lock screen in a background display process that occurs without user intervention; and

detecting, by the user device, a user input that was instructed by the payment code notification and, in response, causing the payment code to be displayed.

10. The method of claim 7, further comprising:

forwarding, by the beacon system, the user account authentication token to a payment service provider device over a network; and

receiving, by the beacon system, the payment code from the payment service provider device over the network.

11. The method of claim 7, further comprising:

receiving, by a payment service provider device, payment information associated with the payment code over the network from the payment processing device; and

transferring, by the payment service provider device, funds from a user account of a user associated with the user device to a merchant account of a merchant associated with the merchant physical location.

12. The method of claim 7, further comprising:

receiving, by the user device, the user account authentication token over a network from a payment service provider device; and

storing, by the user device, the user account authentication token in the database.

13. The method of claim 7, wherein the payment code is a one-time use code that is restricted in use to the physical merchant location.

14. A non-transitory machine-readable medium comprising a plurality of machine-readable instructions which, when executed by one or more processors, are adapted to cause the one or more processors to perform a method comprising:

detecting a beacon system at a physical merchant location;

establishing a background communication process with the beacon system, wherein the background communication process occurs without user intervention subsequent to detecting the beacon system;

providing at least one of a plurality of user account authentication tokens that are stored in a database to the beacon system as part of the background communication process;

receiving a payment code from the beacon system as part of the background communication process; and

causing the payment code to be displayed, wherein the payment code is configured to be utilized by a payment processing device at the physical merchant location in a payment transaction.

15. The non-transitory machine-readable medium of claim 14, wherein the causing the payment code to be displayed includes causing the payment code to be displayed on a lock screen in a background display process that occurs without user intervention.

16. The non-transitory machine-readable medium of claim 14, wherein the method further comprises:

causing a payment code notification to be displayed on a lock screen in a background display process that occurs without user intervention; and

detecting a user input that was instructed by the payment code notification and, in response, causing the payment code to be displayed.

17. The non-transitory machine-readable medium of claim 14, wherein the payment code is a Quick Response (QR) code that is configured to provide user payment account information to a QR code reader device that is coupled to the payment processing device.

18. The non-transitory machine-readable medium of claim 14, wherein the method further comprises:

receiving a first set of the plurality of user account authentication tokens over a network from a payment service provider device;

storing the first set of the plurality of user account authentication tokens in the non-transitory memory;

receiving a second set of the plurality of user account authentication tokens over a network from a payment service provider device; and

storing the second set of the plurality of user account authentication tokens in the non-transitory memory.

19. The non-transitory machine-readable medium of claim 18, wherein the payment code encodes a user payment account identifier for a user payment account, user authentication credentials for the user payment account, and a merchant identifier for a merchant associated with the merchant physical location.

20. The non-transitory machine-readable medium of claim 14, wherein the payment code is a one-time use code that is restricted in use to a predetermined time period.