Fraud analyst smart cookie

• US 20070038568A1
• Filed: 04/26/2006
• Published: 02/15/2007
• Est. Priority Date: 09/17/2004
• Status: Active Grant

• Current Assignee: Digital Envoy, Inc. (Landmark Media Enterprises LLC)
• Original Assignee: Digital Envoy, Inc. (Landmark Media Enterprises LLC)
• Inventors: Helsper, David, Greene, Todd
• Granted Patent: US 7,543,740 B2
• Time in Patent Office: Days
• US Class Current: 705/50
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• 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/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0603 Catalogue ordering
• CPC Class Codes: G06Q 40/08 Insurance
• CPC Class Codes: G06Q 50/188 Electronic negotiation

Abstract

A fraudulent business transaction application (FBTA) is provided in embodiments of the present invention for monitoring fraudulent transactions. When a consumer supplies account access information in order to carry out an Internet business transaction, the FBTA uses an online fraud mitigation engine to detect phishing intrusions and identity theft. Embodiments are also provided for calculating travel velocity and transaction frequency, which are useful for determining a fraudulent transaction. Further embodiments are provided for authenticating a transaction using a cookie stored on a client device and a behavior profile stored on a server.

Claims

1. A method for authenticating a transaction, the method comprising the steps of:

a. storing on a server a behavior profile associated with a user, the behavior profile including one or more factors associated with the user, the behavior profile also including an encryption key associated with the user;

b. encrypting the one or more factors using an encryption key to create one or more encrypted factors;

c. storing a cookie on a client device, the cookie including the one or more encrypted factors;

d. initiating by the user the transaction using the client device;

e. deriving one or more factors from the transaction;

f. decrypting the one or more factors stored in the cookie using the encryption key to create one or more decrypted factors; and

g. authenticating the transaction by comparing the one or more factors in the behavior profile with the one or more decrypted factors.

2. The method of claim 1, wherein the authenticating step comprises authenticating the transaction by comparing the one or more decrypted factors with the one or more factors derived from the transaction.

3. The method of claim 1, wherein the authenticating step comprises authenticating the transaction by comparing the one or more factors in the behavior profile, the one or more decrypted factors, and the one or more factors derived from the transaction.

4. The method of claim 1, wherein a factor is at least one of an access location, access date, access time, geographical location, domain information, network Id, connection type, one or more IP addresses, user name, email address, debit card number, credit card number, bank account number, social security number, HTTP header information, travel velocity, telephone number, area code, transaction frequency, operating system, processor identification number, natural language, host type, demographic information, or advertising information.

5. The method of claim 4, wherein connection type is at least one of dial-up, Integrated Services Digital Network (ISDN), cable modem, Digital Subscriber Line (DSL), Digital Signal 1 (T1), or Optical Carrier 3 (OC3).

6. The method of claim 4, wherein host type is one or more of network end point, network proxy, or network firewall.

7-25. -25. (canceled)