APPLICANT AUTHENTICATION

• US 20090106134A1
• Filed: 10/18/2007
• Published: 04/23/2009
• Est. Priority Date: 10/18/2007
• Status: Active Grant

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: ROYYURU, VIJAY K.
• Granted Patent: US 8,255,318 B2
• Time in Patent Office: Days
• US Class Current: 705/35
• 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 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G07G 3/003 Anti-theft control theft alarms G08B13/00

Abstract

A method of authenticating an applicant. A history is obtained of transactions performed on an account held by the applicant and for which the applicant has been previously authenticated. The transaction history includes information about each transaction. The applicant is asked one or more questions relating to the information in the history. Answers to the one or more questions are received from the applicant, and a decision is made based on the received answers and the transaction history whether the applicant is authenticated. The applicant may be applying for enrollment in a service, and enrollment may be accepted or declined based on whether the applicant is authenticated. The account may relate to a payment instrument, and the authentication may be performed by an entity other than the issuer of the payment instrument.

Claims

1. A method of authenticating an applicant, the method comprising:

obtaining a transaction history of transactions performed on an account held by the applicant and for which the applicant has been previously authenticated, the transaction history comprising information about each transaction;

asking the applicant one or more questions relating to the information about one or more transactions in the history;

receiving from the applicant answers to the one or more questions; and

indicating, based at least in part on the one or more answers received and the transaction history, whether the applicant is authenticated.

2. The method of claim 1, wherein asking the applicant one or more questions comprises asking the applicant a first predetermined number of questions, the method further comprising accepting the applicant'"'"'s identity as authenticated upon receiving from the applicant, in response to the first predetermined number of questions, a second predetermined number of correct answers.

3. The method of claim 1, further comprising:

identifying one or more patterns or anomalies in the transaction history; and

framing at least one of the one or more questions so as to test the applicant'"'"'s knowledge of the one or more patterns or anomalies.

4. The method of claim 3, wherein the information indicates one or more items selected from the group consisting of locations, types, and names of merchants at which at least some transactions in the history were made, and wherein at least one pattern or anomaly relates to the one or more items.

5. The method of claim 4, wherein the information indicates types of merchants at which at least some transactions in the history were made, and wherein the merchant types are indicated by standard industrial classification codes.

6. The method of claim 3, wherein the information indicates times, dates, or both at which at least some transactions in the history were made, and wherein at least one pattern or anomaly relates to the transaction times, dates, or both.

7. The method of claim 3, wherein the information indicates amounts involved in at least some transactions in the history, and wherein at least one pattern or anomaly relates to the transaction amounts.

8. The method of claim 7, wherein the transaction amounts are automated teller machine withdrawal amounts.

9. The method of claim 3, wherein at least some of the transactions in the history are withdrawals, and wherein at least one pattern or anomaly relates to the withdrawal transactions.

10. The method of claim 3, wherein at least some of the transactions in the history are deposits, and wherein at least one pattern or anomaly relates to the deposit transactions.

11. The method of claim 3, further comprising:

analyzing transaction histories of a number of other accounts used by persons other than the applicant;

identifying in the transaction history of the applicant'"'"'s account at least one pattern or anomaly that is unusual in relation to the transaction histories of the accounts used by the other persons; and

framing at least one of the one or more questions so as to test the applicant'"'"'s knowledge of the unusual pattern or anomaly.

12. The method of claim 3, wherein at least one of the identified patterns or anomalies is selected so as to be memorable to the applicant without requiring the applicant to remember details of specific transactions in the transaction history.

13. The method of claim 3, wherein at least one of the one or more patterns or anomalies relates to a dearth or absence of a particular kind of data in the transaction history.

14. The method of claim 3, wherein at least one of the one or more patterns or anomalies relates to at least two items of transaction information in combination.

15. The method of claim 1, further comprising accepting or declining the applicant for enrollment in a service based at least in part on whether the applicant is authenticated.

16. The method of claim 15, wherein the service enables an enrollee to verify an account balance.

17. The method of claim 15, wherein the service is a payment instrument verification service.

18. The method of claim 1, wherein the account relates to a payment instrument, and wherein the verification is performed by an entity other than the issuer of the payment instrument.

19. The method of claim 18, wherein the authentication is performed by an administrator of a payments network.

20. An system for authenticating an applicant, comprising:

a host computer; and

a computer readable medium holding instructions executable by the host computer to

obtain a transaction history of transactions performed on an account held by the applicant, the transaction history comprising information about each transaction;

ask the applicant one or more questions relating to the information about one or more transactions in the history;

receive from the applicant answers to the one or more questions; and

decide, based at least in part on the one or more answers received and the transaction history, whether the applicant is authenticated.

21. The system of claim 20, the instructions further executable by the host computer to ask the one or more questions in one or more web pages served over the Internet.

22. A method of being authenticated as the rightful holder of a payment instrument account, comprising:

building a transaction history by performing one or more transactions using the payment instrument;

receiving, from an authenticating system having access to the transaction history, a first predetermined number of questions relating to one or more patterns or anomalies in the transaction history;

answering the questions; and

receiving notice of successful authentication upon answering a second predetermined number of the questions correctly.

23. A computer system, comprising:

a display screen; and

an input device;

the computer system in communication over an electronic network with a host computer system, the computer system displaying on the display screen user interface windows served by the host computer system, the user interface windows presenting to a user of the computer system questions relating to a transaction history of a payment device, the user providing answers to the questions using the input device, and the computer displaying on the display screen an indication of whether the user has been authenticated as the rightful holder of the payment instrument;

wherein the questions test the applicant'"'"'s knowledge of one or more patterns or anomalies in the transaction history.

24. A method of administering a payments network, comprising:

transmitting information about transactions from points of sale to issuers of payment instruments used in the transactions;

storing the information in transaction histories of the respective payment instruments;

asking an applicant one or more questions relating to the transaction history of a particular payment instrument;

receiving from the applicant answers to the one or more questions; and

based at least in part on the answers and on the transaction history of the particular payment instrument, authenticating the applicant as the rightful holder of the particular payment instrument or declining to authenticate the applicant as the rightful holder of the particular payment instrument.

25. The method of claim 24, further comprising:

identifying one or more patterns or anomalies in the transaction history of the particular payment instrument; and

framing at least one of the one or more questions so as to test the applicant'"'"'s knowledge of the one or more patterns or anomalies.