AUTOMATIC USER VALIDATION SYSTEM AND METHOD

• US 20130159188A1
• Filed: 12/17/2012
• Published: 06/20/2013
• Est. Priority Date: 12/16/2011
• Status: Abandoned Application

• Current Assignee: Saysearch Incorporated
• Original Assignee: Saysearch Incorporated
• Inventors: Andon, Charles A.
• Application Number:
  US13/717,623
• Publication Number:
  US 20130159188A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules

Abstract

Methods and apparatus support optional user authentication. Whether an authentication, or an enhanced type of authentication, is required before proceeding with a transaction can be determined on a user-by-user basis. Some credit card users subscribe to a service that provides the users with security tokens. Transactions involving these credit cards may require correct entry of a security token code, before the transactions are allowed to proceed. However, other credit card users, i.e., users who have not subscribed to the service, are not required to enter a security token code before their transactions are allowed to proceed.

Claims

1. An automatic user validation system for determining if a purported user may conduct a transaction, comprising:

a server configured to;

access a computerized database configured to store a plurality of records, wherein each record of the plurality of records corresponds to a respective user authorized to conduct a predetermined type of transaction and is configured to store a user identifier associated with the authorized user;

receive a user validation request, the request comprising an identifier of a purported user; and

send a message that indicates the purported user is valid, if the database does not contain a record storing a user identifier equivalent to the received identifier of the purported user.

2. A system according to claim 1, wherein:

each record of the plurality of records is further configured to store identification verification information, other than the user identifier, associated with each authorized user;

the user validation request further comprises data purportedly verifying identity of the purported user; and

the server is further configured to send a message that indicates the purported user is valid if;

the database contains a record storing a user identifier equivalent to the received identifier of the purported user, and

the received data purportedly verifying the identity of the purported user corresponds with the identity verification information stored in the record.

3. A system according to claim 2, wherein the server is further configured to send a message that indicates the purported user is invalid if:

the database contains a record storing a user identifier equivalent to the received identifier of the purported user, and

the received data purportedly verifying the identity of the purported user does not correspond with the identity verification information stored in the record.

4. A system according to claim 1, the system further comprising the database.

5. A system according to claim 2, the system further comprising the database.

6. A system according to claim 3, the system further comprising the database.

7. A system according to claim 3, wherein the identity verification information stored in the record is configured to enable verification of a passcode.

8. A system according to claim 3, wherein the identity verification information stored in the record is configured to enable verification of a code automatically generated by a security token.

9. A system according to claim 1, wherein the predetermined type of transaction comprises a financial transaction.

10. A system according to claim 1, wherein the predetermined type of transaction comprises a credit card transaction.

11. A system according to claim 1, wherein the predetermined type of transaction comprises accessing a computer.

12. A system according to claim 1, wherein the predetermined type of transaction comprises unlocking a lock.

13. A system according to claim 1, wherein the predetermined type of transaction comprises obtaining a service.

14. A system according to claim 1, wherein:

the user validation request comprises a transaction amount; and

the server is configured to send a message that indicates the purported user is valid, if the received transaction amount is less than a predetermined value.

15. A system according to claim 14, wherein:

each record of the plurality of records is configured to store a transaction amount threshold;

the server is configured to receive a value from an authorized user and to store the received value in the corresponding record as the transaction amount threshold; and

the server is configured to use the transaction amount threshold in the record as the predetermined value.

16. A system according to claim 1, wherein:

each record of the plurality of records is configured to store a verification initiation criterion; and

the server is configured to send a message that indicates the purported user is valid, if the verification initiation criterion is not satisfied.

17. An automatic user validation system for determining if a purported user may conduct a transaction, comprising:

a server configured to;

access a computerized database configured to store a plurality of records, wherein each record of the plurality of records corresponds to a respective user authorized to conduct a predetermined type of transaction and is configured to store a user identifier associated with the authorized user and identification verification information, other than the user identifier, associated with the authorized user;

receive a user validation request, the request comprising an identifier of a purported user and data purportedly verifying identity of the purported user; and

send a message that indicates the purported user is valid if;

the database contains a record storing a user identifier equivalent to the received identifier of the purported user, and

the received data purportedly verifying the identity of the purported user corresponds with the identity verification information stored in the record;

send a message that indicates the purported user is invalid, if;

the database contains a record storing a user identifier equivalent to the received identifier of the purported user, and

the received data purportedly verifying the identity of the purported user does not correspond with the identity verification information stored in the record; and

send a message that indicates validity of the purported user is unknown (wherein “

unknown is distinct from “

invalid”

) if;

the database does not contain a record storing a user identifier equivalent to the received identifier of the purported user.

18. A system according claim 17, the system further comprising the database.

19. A system according to claim 17, wherein the identity verification information stored in the record is configured to enable verification of a passcode.

20. A system according to claim 17, wherein the identity verification information stored in the record is configured to enable verification of a code automatically generated by a security token.

21. A system according to claim 17, wherein:

wherein the user validation request further comprises one of;

(a) data purportedly verifying identity of the purported user and (b) no data purportedly verifying identity of the purported user; and

the server is further configured to send a message that indicates the purported user is invalid if;

the database contains a record storing a user identifier equivalent to the received identifier of the purported user, and

the received request contains no data purportedly verifying identity of the purported user.

22. An automatic user validation system for determining if a purported user may conduct a transaction, comprising:

a server configured to;

access a computerized database configured to store a plurality of records, wherein each record of the plurality of records corresponds to a respective user authorized to conduct a predetermined type of transaction and is configured to store a user identifier associated with the authorized user;

receive a user validation request, the request comprising an identifier of a purported user; and

send a message that indicates validity of the purported user is unknown, if the database does not contain a record storing a user identifier equivalent to the received identifier of the purported user.

23. A system according to claim 22, wherein:

each record of the plurality of records is further configured to store identification verification information, other than the user identifier, associated with each authorized user;

the user validation request further comprises data purportedly verifying identity of the purported user; and

the server is further configured to send a message that indicates the purported user is valid if;

the database contains a record storing a user identifier equivalent to the received identifier of the purported user, and

the received data purportedly verifying the identity of the purported user corresponds with the identity verification information stored in the record.

24. A system according to claim 23, wherein the server is further configured to send a message that indicates the purported user is invalid, if:

the database contains a record storing a user identifier equivalent to the received identifier of the purported user, and

the received data purportedly verifying the identity of the purported user does not correspond with the identity verification information stored in the record.

25. A system for handling transactions involving respective users, the system comprising:

a computer comprising an interface configured to solicit, for each transaction, input of a user account identifier and user verification data, wherein entry of the user account identifier is required, but entry of the user verification data is optional, the computer being configured to;

communicate with a transaction authorization server to cause funds to be transferred, in relation to the transaction and the user account;

communicate with a user verification server, distinct from the transaction authorization server, to verify identity of a user, but not to cause funds to be transferred;

for each transaction, send the account identifier entered, and the user verification data, if entered, to the user verification server;

receive a response from the user verification server;

allow the transaction to proceed, if the response from the user verification server indicates the user is verified and a response from the transaction authorization server indicates the transaction is authorized; and

prevent the transaction from proceeding, if the response from the user verification server indicates the verification of the user failed.

26. A system according to claim 25, wherein:

each transaction has an associated transaction amount; and

for each transaction, the computer is configured to;

send the account identifier, and the user verification data, if entered, to the user verification server, if the associated transaction amount exceeds a predetermined value; and

allow the transaction to proceed, if the associated transaction amount is no greater than the predetermined value and the response from the transaction authorization server indicates the transaction is authorized.

27. A system according to claim 25, further comprising:

a database coupled to the computer and configured to store identification of at least one merchant-entered transaction type; and

wherein;

the computer is configured to determine whether to send the account identifier entered, and the user verification data, if entered, to the user verification server, based on a type of the transaction and the at least one merchant-entered transaction type stored in the database.

28. A system according to claim 25, wherein the user account identifier comprises a credit card account number.

29. A system according to claim 28, wherein the user verification data comprises an automatically-generated security token code.

30. A system according to claim 25, wherein the computer is configured to allow the transaction to proceed, if the response indicates verification of the user is unknown.