CREDIT APPLICANT AND USER AUTHENTICATION SOLUTION

• US 20100299261A1
• Filed: 08/13/2010
• Published: 11/25/2010
• Est. Priority Date: 08/08/2005
• Status: Active Application

• Current Assignee: Bradley A. Handler
• Original Assignee: Credit Lock LLC
• Inventors: Handler, Brad
• Application Number:
  US12/856,025
• Publication Number:
  US 20100299261A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• 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 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

The present invention provides a credit applicant and user authentication solution for authenticating the identity of a credit applicant or a credit user. In particular, a user of the authentication system establishes a user account and obtains authentication information. The user then provides the authentication information during a subsequent credit application or credit transaction to authenticate the user'"'"'s identity. Authentication information may be renewed after each application or transaction at specified time intervals, based on monetary thresholds, specific geographic limitations, or any other methodology specified by the user.

Claims

1. An authentication architecture to authenticate a user, the authentication architecture comprising one or more computer processors and storage configured as:

a user access layer enabling one or more user devices to provide and receive data within the authentication architecture, the data including data to establish a user authentication account, and a set of business rules established by the user for managing the user authentication account;

a user interface layer, coupled to the user access layer, to provide interface modules for interacting with the one or more user devices;

a user services layer, coupled to the user interface layer, to provide authentication services and associated services, the user services layer carrying out the business rules; and

a data storage layer, coupled to the user services layer, to store and provide data to the authentication services and associated services.

2. The authentication architecture of claim 1, further comprising a third-party access layer, coupled to the user services layer, to provide communication capabilities between the user services layer and third-party providers.

3. The authentication architecture of claim 1, wherein the authentication services further comprises a credit applicant authentication service.

4. The authentication architecture of claim 1, wherein the authentication services further comprises a credit use authentication service.

5. The authentication architecture of claim 1, wherein the associated services of the user services layer further comprise an account creation module to establish the user authentication account and to provide user authentication information.

6. The authentication architecture of claim 1, wherein the associated services of the user services layer further comprise an account modification module to modify the user authentication account and to renew the user authentication information.

7. The authentication architecture of claim 1, wherein the associated services of the user services layer further comprise a user notification module to provide information to a user regarding the user'"'"'s authentication account and transactions associated with the user authentication account.

8. The authentication architecture of claim 1, wherein the interface modules further comprise:

a computer network interface module to provide an interface to computers, computing devices, and biometric data devices over a computer network;

a device interface module to provide an interface to computers, computing devices, telephony device, and biometric data devices;

an interactive voice response module to provide an interface to telephony devices; and

an operator module to provide a customer service operator as an interface between a user and the user services layer.

9. The authentication architecture of claim 1, wherein the business rules include a requirement that the user receive notice of a transaction before the transaction is carried out.

10. The authentication architecture of claim 9, wherein the transaction is a specified type of transaction.

11. The authentication architecture of claim 1, wherein the business rules include the requirement that the user receive notice of a transaction after the transaction is carried out.

12. The authentication architecture of claim 11, wherein the transaction is a specified type of transaction.

13. The authentication architecture of claim 1, wherein the business rules include criteria under which authentication information is required from the user.

14. The authentication architecture of claim 1, wherein the business rules include conditions under which the user renews the user authentication information.

15. The authentication architecture of claim 14, wherein the conditions include renewing the user authentication information for a transaction above a specified monetary mount.

16. The authentication architecture of claim 14, wherein the conditions include renewing the user authentication information for a transaction within a specific geographic location.

17. The authentication architecture of claim 14, wherein the conditions including renewing the user authentication information for a transaction after a specified number of transactions have taken place.

18. The authentication architecture of claim 14, wherein the conditions including renewing the user authentication information for a transaction occurring within a specified time period from another transaction.

19. The authentication architecture of claim 14, wherein the business rules are maintained within a user profile associated with the user authentication account.

20. An authentication architecture for identifying the authenticity of a user, the architecture comprising one or more computer processors and storage configured as:

a user access layer enabling one or more user devices to provide and receive data within the authentication architecture, the data including data to establish a user account, and user authentication account information;

a user interface layer coupled to the user access layer to provide interface modules for interacting with the one or more user devices;

a user services layer coupled to the user interface layer to provide authentication services and associated services including notifying the user when the user'"'"'s authentication account information is used or modified; and

a data storage layer coupled to the user services layer to store and provide data to the authentication services and associated services, the data including user authentication information.

21. The authentication architecture of claim 20, wherein the notice includes information that a transaction has occurred using the user authentication information.

22. The authentication architecture of claim 21, wherein the notice includes the amount of the transaction.

23. The authentication architecture of claim 20 wherein the notice prompts the user to enter user authentication information.