Systems and methods for streamlined checkout

• US 10,657,531 B1
• Filed: 01/23/2015
• Issued: 05/19/2020
• Est. Priority Date: 01/24/2014
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Arumugam, Avin
• Primary Examiner(s): Trotter, Scott S
• Application Number:
  US14/603,479
• Time in Patent Office: 1,943 Days
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/363 with the personal data of a user
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G07G 1/0009 Details of the software in the checkout register, electronic cash register [ECR] or point of sale terminal [POS]
• CPC Class Codes: G07G 1/0036 Checkout procedures

Abstract

Embodiments of the present invention are directed to a “one-click payment” scheme for streamlining customers'"'"' online checkout experiences. According to one particular embodiment, a customer can use a computing device to be authenticated and receive a unique, one-time token to make a one-click payment during an online checkout process. The one-time token may be encrypted and directly associated with a payment account which the customer is authorized to access. The online merchant may forward a transaction request including the one-time token and purchase amount to an authorization server which would verify the token and charge the corresponding payment account.

Claims

1. A computer-implemented method for streamlined online checkout, the method comprising programming at least one processor of a personal computing device to cause it to perform the following:

storing data associated with at least one payment account on said personal computing device;

identifying, from said at least one payment account, a payment account for an online transaction with an online merchant;

authenticating a user of said personal computing device before allowing access to said stored data, wherein a form of authentication used to authenticate an identity of the user varies according to a transaction threshold of the online transaction, wherein the transaction threshold is dependent on at least one characteristic of the transaction;

implementing an application on said personal computing device that provides a user interface for access by authorized user upon successful biometric authentication or physical attribute authentication and connects to an Internet application to process the payment account for the online transaction;

generating, by said at least one processor of said personal computing device, a token that is temporarily associated with the identified payment account, wherein the token is a hash value generated from real account data including account number, expiration date, account holder name, and transaction-specific information including amount, date, and time of transaction; and

submitting the token to the online merchant as a payment for the online transaction.

2. The method according to claim 1, wherein said data associated with said at least one payment account is securely stored in connection with an electronic wallet app on said personal computing device.

3. The method according to claim 1, wherein the identity of said user is authenticated based at least in part on OS-level biometric or behavioral data.

4. The method according to claim 1, wherein the identity of said user is authenticated based at least in part on a GPS location of said personal computing device.

5. The method according to claim 1, wherein the identity of said user is authenticated based on at least one biometric characteristic or physical attribute of said user.

6. The method according to claim 1, wherein the payment account is automatically identified based on one or more pre-set rules or preferences.

7. The method according to claim 1, wherein the token is generated with an algorithm only known to the online merchant and the personal computing device.

8. The method according to claim 1, wherein the token is generated randomly and then shared with a remote server.

9. A computer-implemented method for facilitating streamlined online checkout, the method comprising programming at least one processor of a server computer to cause it to perform the following:

receiving a request for payment from a customer in an online transaction between the customer and an online merchant;

authenticating the customer upon initiation of a checkout process in the online transaction with the merchant, wherein a form of authentication used to authenticate an identity of the customer varies according to a transaction threshold of the online transaction, wherein the transaction threshold is dependent on at least one characteristic of the transaction;

identifying a customer payment account for use in the online transaction;

implementing an application on said personal computing device that provides a user interface for access by authorized user upon successful biometric authentication or physical attribute authentication and connects to an Internet application to process the customer payment account for use in the online transaction;

generating a token temporarily associated with the payment account, wherein the token is a hash value generated from real account data including account number, expiration date, account holder name, and transaction-specific information including amount, date, and time of transaction;

making the token available to the customer for submission to the merchant as a form of payment;

receiving a transaction request from the merchant, the transaction request including the token; and

verifying the received token and matching the received token to the corresponding payment account, thereby making a decision to approve or decline the transaction request.

10. The method according to claim 9, further comprising programming said at least one processor of said server computer to:

cause the token to be generated on a mobile computing device operated by the customer.

11. The method according to claim 9, wherein the token is generated with an algorithm only known to the server computer.

12. The method according to claim 9, wherein the token is generated randomly.

13. The method according to claim 9, further comprising programming said at least one processor of said server computer to:

generate the token; and

transmit the token to a personal computing device operated by the customer.

14. The method according to claim 9, further comprising programming said at least one processor of said server computer to:

configure the token to expire after a predetermined period of time beyond which its association with the payment account is no longer valid.

15. The method according to claim 9, wherein the token is limited to a transaction with one or more designated merchants.

16. The method according to claim 9, wherein the token is limited to a transaction at or near a GPS location of a mobile computing device operated by the customer.

17. The method according to claim 9, further comprising programming said at least one processor of said server computer to:

pre-generate one or more tokens by said at least one processor of said server computer; and

transmit the one or more tokens to a personal computing device operated by the customer for at least one future online transaction.

18. The method according to claim 9, wherein the identity of said user is authenticated based at least in part on OS-level biometric or behavioral data.

19. The method according to claim 9, wherein the identity of said user is authenticated based at least in part on a GPS location of said personal computing device.

20. The method according to claim 9, wherein the identity of said user is authenticated based on at least one biometric characteristic or physical attribute of said user.