Automatic approval

• US 9,576,288 B1
• Filed: 07/21/2014
• Issued: 02/21/2017
• Est. Priority Date: 06/30/2008
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Jesensky, James, Oates, Isaac, Agarwal, Amit D., Vaidya, Vinay P.
• Primary Examiner(s): Chuang, Jung-Mu
• Application Number:
  US14/336,258
• Time in Patent Office: 946 Days
• US Class Current: 1/1
• 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 30/06 Buying, selling or leasing transactions

Abstract

Techniques for automatically approving transactions are described herein. These techniques may include determining whether a user who requested to conduct a transaction is the same user as a user that approves the transaction. If so, then the transaction may be approved. If not, then the approving user may be asked to provide authentication information in order to finish the approval process.

Claims

1. A method comprising:

receiving a first request to conduct a transaction initiated by a user, the first request including a payment identifier;

transmitting a message to a computing device associated with a controlling user associated with the payment identifier, the message including a second request for approval of the transaction;

receiving a response to the message approving the transaction responded to by the controlling user using the computing device and a cookie from the computing device;

performing a hash of the cookie;

determining a hash value of the cookie matches a stored hash value of a previous cookie that was received from the computing device;

mapping the hash value of the cookie and the payment identifier to the controlling user associated with the payment identifier based at least in part on determining that the hash value of the cookie matches the stored hash value of the previous cookie;

determining a setting is elected to automatically approve the transaction without requesting authentication information from the controlling user; and

automatically approving the transaction and refraining from sending, to the computing device, a third request to get the authentication information from the controlling user.

2. A method as recited in claim 1, wherein the payment identifier comprises a transaction phrase token entered into a text box as a payment instrument to conduct the transaction.

3. A method as recited in claim 1, wherein the cookie is associated with a browser stored on the computing device.

4. A method as recited in claim 1, wherein the previous cookie is associated with a browser stored on the computing device.

5. An apparatus comprising:

a memory comprising instructions for executing by one or more processors;

the one or more processors coupled to the memory, and the one or more processors being operable when executing the instructions to;

receive a first request to conduct a transaction initiated by a user using a payment identifier;

responsive to the receiving of the first request, transmit a message to a computing device associated with a controlling user associated with the payment identifier, the message requesting approval of the transaction;

receive a response to the message approving the transaction responded to by the controlling user using the computing device, the response including a cookie from the computing device;

perform a hash of the cookie;

determine a hash value of the cookie matches a stored hash value of a previous cookie that was received from the computing device;

map the hash value of the cookie and the payment identifier to the controlling user associated with the payment identifier based at least in part on determining that the hash value of the cookie matches the stored hash value of the previous cookie;

determine a setting is elected to automatically approve the transaction without requesting authentication information from the controlling user; and

automatically approve the transaction while refraining from sending a second request to the computing device to get the authentication information from the controlling user.

6. An apparatus as recited in claim 5, wherein automatically approving the transaction comprises approving the transaction without authenticating the controlling user associated with the payment identifier.

7. An apparatus as recited in claim 6, wherein authenticating comprises the controlling user associated with the payment identifier signing into an account using a user name or password.

8. An apparatus as recited in claim 5, wherein the payment identifier comprises a transaction phrase token comprising words selected by the controlling user as a way to perform transactions.

9. An apparatus as recited in claim 8, wherein the transaction phrase token is entered into a text box to conduct the transaction.

10. An apparatus as recited in claim 5, wherein the message comprises an email message.

11. An apparatus as recited in claim 5, wherein the message comprises an instant message.

12. An apparatus as recited in claim 5, further comprising providing the message in a web interface.

13. An apparatus as recited in claim 5, wherein the transmitting of the message to the controlling user associated with the payment identifier is on a channel different from a channel the first request to conduct the transaction is received on.

14. An apparatus as recited in claim 5, wherein the cookie is associated with a browser stored on the computing device.

15. A non-transitory storage device storing computer-executable instructions that, when executed on one or more processors, perform acts comprising:

receiving a first request to conduct a transaction initiated by a user, the first request including a payment identifier;

transmitting a message to a computing device associated with a controlling user associated with the payment identifier, the message including a second request for approval of the transaction;

receiving a response to the message approving the transaction responded to by the controlling user using the computing device and a cookie from the computing device;

performing a hash of the cookie;

determining a hash value of the cookie matches a stored hash value of a previous cookie that was received from the computing device;

mapping the hash value of the cookie and the payment identifier to the controlling user associated with the payment identifier based at least in part on determining that the hash value of the cookie matches the stored hash value of the previous cookie;

determining a setting is elected to automatically approve the transaction without requesting authentication information from the controlling user; and

automatically approving the transaction and refraining from sending, to the computing device, a third request to get the authentication information from the controlling user.

16. A non-transitory storage device as recited in claim 15, wherein the payment identifier comprises a transaction phrase token entered into a text box as a payment instrument to conduct the transaction.

17. A non-transitory storage device as recited in claim 15, wherein authentication information comprises a user name or password.

18. A non-transitory storage device as recited in claim 15, wherein the cookie is associated with a browser stored on the computing device.

19. A non-transitory storage device as recited in claim 15, wherein the previous cookie is associated with a browser stored on the computing device.