# US 8,740,067 B1 · Secondary verification

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,740,067 B1
- Document ID: US8740067B1
- Status: Granted
- Kind: B1
- Application number: 13/407,904
- Filed: 2012-02-29
- Granted: 2014-06-03
- Earliest claimed: 2012-02-29
- Assignees: Amazon Technologies, Inc.
- Applicants: Ammar Chinoy; Michael Donikian; Ashish Agrawal; Amit Bhosle
- Inventors: Ammar Chinoy; Michael Donikian; Ashish Agrawal; Amit Bhosle
- Web page: https://patentgrep.com/patent/US8740067B1

## CPC

- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q 20/2295: {Parent-child type, e.g. where parent has control on child rights}
- G06Q 20/4014: {Identity check for transactions}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Disclosed are various embodiments for implementing secondary verification of user accounts through the use of near field communication devices. A first account code and first verification code are stored in a memory accessible to a computing device, wherein the first account code is associated with a payment instrument. A second account code is received in a charge request from a transaction client. A second verification code is further obtained from a client device. A determination is made as to whether to approve charging of an account based at least on whether the second verification code received in the computing device matches the first verification code.

## Claims

### Claim 1

A non-transitory computer-readable medium embodying a program executable in a computing device, the program comprising:
code that maintains an account in at least one memory accessible to the computing device, the at least one memory having stored thereon a first account code and a first verification code, wherein both the first account code and the first verification code are associated with the account; and
code that, in response to receiving a charge request containing a second account code and a second verification code, determines whether to approve the charge request based at least in part on whether the second account code matches the first account code, the second verification code matches the first verification code, and the second verification code is received within a predefined amount of time, wherein the account is associated with a payment instrument, the payment instrument comprising a first near field communication device that embodies the second account code that is read by a transaction client, the second verification code originating from a second near field communication device that is read by the transaction client.

### Claim 2 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the second account code and the second verification code are obtained at a single transaction client.

### Claim 3 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the second near field communication device is embedded in a mobile device.

### Claim 4

A system, comprising:
at least one computing device;
at least one memory accessible by the at least one computing device, the at least one memory having stored thereon a first account code, a first verification code, and a verification application; and
the verification application executable in the at least one computing device, the verification application comprising:
logic that obtains a second account code from a charge request received from a transaction client, wherein the second account code is obtained by reading a first near field communication device that embodies the second account code at the transaction client, the second account code being associated with a payment instrument that includes the first near field communication device;
logic that obtains a second verification code, wherein the second verification code is associated with a second near field communication device; and
logic that determines whether to approve charging an account associated with the charge request received from the transaction client based at least upon whether the first account code matches the second account code, and the first verification code matches the second verification code.

### Claim 5 (depends on 4)

The system of claim 4, wherein the second account code and the second verification code are obtained in a single location.

### Claim 6 (depends on 4)

The system of claim 4, wherein the second near field communication device is implanted in a user associated with the payment instrument.

### Claim 7 (depends on 4)

The system of claim 4, wherein the second near field communication device is embedded in a mobile device.

### Claim 8 (depends on 4)

The system of claim 4, wherein the logic that determines whether to approve charging the account further comprises logic that determines whether the second verification code is received within a predefined amount of time.

### Claim 9 (depends on 4)

The system of claim 4, wherein the second account code and the second verification code are obtained while the transaction client and the second near field communication device are within a predefined distance from each other.

### Claim 10 (depends on 4)

The system of claim 4, wherein the second account code and the second verification code are obtained through the transaction client contemporaneously with respect to each other.

### Claim 11 (depends on 4)

The system of claim 4, wherein the logic that determines whether to approve charging the account further comprises logic that sends an electronic message to a client, and wherein the electronic message comprises a query for the second verification code.

### Claim 12 (depends on 11)

The system of claim 11, wherein the logic that determines whether to approve charging the account further comprises logic that determines whether to approve charging the account based on whether the second verification code received from the client matches the first verification code.

### Claim 13 (depends on 11)

The system of claim 11, wherein the electronic message further comprises a short message service text message.

### Claim 14 (depends on 11)

The system of claim 11, wherein the electronic message further comprises an email message.

### Claim 15 (depends on 4)

The system of claim 4, wherein the verification application further comprises logic that generates a dynamic pin code for display in at least one user interface on a client.

### Claim 16 (depends on 15)

The system of claim 15, wherein the logic that determines whether to approve charging the account further comprises logic that determines whether to approve charging the account based on receipt of the dynamic pin code received from the client.

### Claim 17

A method, comprising:
storing, using at least one of one or more computing devices, a first account code and a first verification code in at least one memory;
obtaining, using at least one of the one or more computing devices, a second account code from a charge request received from a transaction client, wherein the second account code is obtained by reading a first near field communication device that embodies the second account code at the transaction client, the second account code being associated with a payment instrument that includes the first near field communication device;
obtaining, using at least one of the one or more computing devices, a second verification code, wherein the second verification code is associated with a second near field communication device; and
determining, using at least one of the one or more computing devices, whether to approve charging an account associated with the charge request received from the transaction client based at least in part upon whether the first account code matches the second account code, and the first verification code matches the second verification code.

### Claim 18 (depends on 17)

The method of claim 17, wherein the second near field communication device is embedded in a card, a ring, or an accessory associated with a user of the payment instrument.

### Claim 19 (depends on 17)

The method of claim 17, further comprising transmitting an electronic message to a client, wherein the electronic message comprises a query for the second verification code.

### Claim 20 (depends on 17)

The method of claim 17, wherein the second account code and the second verification code are obtained in a single location.
