WO2006034205A2 - Fraud risk advisor - Google Patents

Fraud risk advisor Download PDF

Info

Publication number
WO2006034205A2
WO2006034205A2 PCT/US2005/033502 US2005033502W WO2006034205A2 WO 2006034205 A2 WO2006034205 A2 WO 2006034205A2 US 2005033502 W US2005033502 W US 2005033502W WO 2006034205 A2 WO2006034205 A2 WO 2006034205A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
transaction
access
access location
address
Prior art date
Application number
PCT/US2005/033502
Other languages
French (fr)
Other versions
WO2006034205A3 (en
Inventor
David Helsper
Dennis Maicon
Original Assignee
Digital Envoy, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/943,454 external-priority patent/US20060064374A1/en
Application filed by Digital Envoy, Inc. filed Critical Digital Envoy, Inc.
Priority to JP2007532593A priority Critical patent/JP2008513893A/en
Priority to CA2580731A priority patent/CA2580731C/en
Priority to EP05794957A priority patent/EP1810235A4/en
Priority to AU2005286866A priority patent/AU2005286866A1/en
Publication of WO2006034205A2 publication Critical patent/WO2006034205A2/en
Publication of WO2006034205A3 publication Critical patent/WO2006034205A3/en
Priority to IL181966A priority patent/IL181966A/en
Priority to IL248891A priority patent/IL248891B/en
Priority to IL267487A priority patent/IL267487A/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation or account maintenance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/26Government or public services
    • G06Q50/265Personal security, identity or safety

Definitions

  • the present invention relates to techniques for detecting fraudulent online transactions.
  • the present invention provides methods, systems, and computer program products for operating a fraud engine that is capable of accepting an IP address and a number of factors relating to an end user in order to determine whether a transaction is fraudulent.
  • the present invention also relates to methods, systems, and computer program products for calculating a travel velocity between two access locations, determining if a transaction is fraudulent based on a user's travel velocity between two access locations, and determining if a transaction is fraudulent based on a transaction frequency.
  • the present invention provides methods, systems, and computer program products (hereinafter "method” or “methods” for convenience) for determining fraudulent online transactions.
  • an end user inputs parameters and rules concerning a particular transaction into the system. Based on the parameters, rules, and other information concerning a particular transaction, the system computes a score associated with the likelihood that the transaction is fraudulent. The score is then compared with various thresholds which may be set by the end user. If the score exceeds the thresholds, then the transaction is determined to be fraudulent. Data regarding the transaction may also be output to the end user. Upon review, the end user may change the fraud status of a given transaction.
  • Another embodiment of the present invention provides methods for calculating a travel velocity between a first and second access location, utilizing a travel velocity to determine if a transaction is fraudulent, as well as determining if a transaction is fraudulent based upon a computed transaction frequency.
  • FIG. 1 is a flow chart illustrating one embodiment of the present invention for determining whether an online transaction is fraudulent using an Online Fraud Mitigation Engine.
  • FIG. 2 is a block diagram of a computer system for implementing embodiments of the present invention.
  • FIG. 3 illustrates one embodiment of the present invention useful for calculating a travel velocity.
  • FIG. 4 illustrates another embodiment of the present invention useful for calculating a travel velocity.
  • FIG. 5 illustrates one embodiment of the present invention useful for calculating a user's travel velocity.
  • FIG. 6 illustrates one embodiment of the present invention useful for determining a fraudulent transaction using a travel velocity.
  • FIG. 7 illustrates one embodiment of the present invention useful for determining a fraudulent transaction using a transaction frequency.
  • FIG. 8 shows a logical overview of a computer system which may be used to carry out the various embodiments of the present invention.
  • FIG. 9 illustrates logically the arrangement of computers connected to the Internet in one embodiment of the present invention.
  • risk factor includes any factor used in a transaction that has some level of risk associated with it.
  • static risk factor includes any factor that does not change at run time.
  • dynamic risk factor includes any factor that has its value calculated at mn time.
  • risk value includes any number associated with a factor.
  • risk weight includes any number that determines how much influence a factor's risk value is to the outcome of a risk score.
  • rule includes any conditional statement that applies Boolean logic to risk values.
  • risk score includes any aggregation of risk values based on a computation of risk values and risk weights or a rule setting the risk score directly.
  • OFME online fraud mitigation engine
  • transaction includes any type of online activity, such as online banking account access, credit card transactions, online bill pay, wire transfers, stock trades, transactions utilizing personal information, and the like.
  • transaction identifier includes any unique system generated number that identifies a particular risk score model.
  • risk score model includes any set of logical rules, applicable static and dynamic factors, risk weights for the factors, a frau- score algorithm, a risk score threshold, and reason codes used to identify a fraudulent transaction.
  • the term "user” or “client” includes one or more persons, entities, or computers.
  • FIG. 8 is a block diagram illustrating an exemplary operating environment for performing the various embodiments.
  • This exemplary operating environment is only an example of an operating environment and is not intended to suggest any limitation as to the scope of use or functionality of operating environment architecture. Neither should the operating environment be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment.
  • the method can be operational with numerous other general purpose or special purpose computing system environments or configurations.
  • Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the method include, but are not limited to, personal computers, server computers, laptop devices, and multiprocessor systems. Additional examples include set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
  • the method may be described in the general context of computer instructions, such as program modules, being executed by a computer.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • the method may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer storage media including memory storage devices.
  • the method disclosed herein can be implemented via a general-purpose computing device in the form of a computer 801.
  • the components of the computer 801 can include, but are not limited to, one or more processors or processing units 803, a system memory 812, and a system bus 813 that couples various system components including the processor 803 to the system memory 812.
  • the processor 803 in Fig. 8 can be an x-86 compatible processor, including a PENTIUM rV, manufactured by Intel Corporation, or an ATHLON 64 processor, manufactured by Advanced Micro Devices Corporation. Processors utilizing other instruction sets may also be used, including those manufactured by Apple, IBM, or NEC.
  • the system bus 813 represents one or more of several possible types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.
  • such architectures can include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnects (PCI) bus also known as a Mezzanine bus.
  • ISA Industry Standard Architecture
  • MCA Micro Channel Architecture
  • EISA Enhanced ISA
  • VESA Video Electronics Standards Association
  • PCI Peripheral Component Interconnects
  • the bus 813, and all buses specified in this description can also be implemented over a wired or wireless network connection and each of the subsystems, including the processor 803, a mass storage device 804, an operating system 805, application software 806, data 807, a network adapter 808, system memory 812, an Input/Output Interface 810, a display adapter 809, a display device 811, and a human machine interface 802, can be contained within one or more remote computing devices 814a,b,c at physically separate locations, connected through buses of this form, in effect implementing a fully distributed system.
  • the operating system 805 in Fig. 8 includes operating systems such as MICROSOFT WINDOWS XP, WINDOWS 2000, WINDOWS NT, or WINDOWS 98, and REDHAT LINUX, FREE BSD, or SUN MICROSYSTEMS SOLARIS. Additionally, the application software 806 may include web browsing software, such as MICROSOFT INTERNET EXPLORER or MOZILLA FIREFOX, enabling a user to view HTML, SGML, XML, or any other suitably constructed document language on the display device 811.
  • web browsing software such as MICROSOFT INTERNET EXPLORER or MOZILLA FIREFOX
  • the computer 801 typically includes a variety of computer readable media. Such media can be any available media that is accessible by the computer 801 and includes both volatile and non- volatile media, removable and non-removable media.
  • the system memory 812 includes computer readable media in the form of volatile memory, such as random access memory (RAM), and/or non-volatile memory, such as read only memory (ROM).
  • RAM random access memory
  • ROM read only memory
  • the system memory 812 typically contains data such as data 807 and and/or program modules such as operating system 805 and application software 806 that are immediately accessible to and/or are presently operated on by the processing unit 803.
  • the computer 801 may also include other removable/non-removable, volatile/non ⁇ volatile computer storage media.
  • FIG. 8 illustrates a mass storage device 804 which can provide non- volatile storage of computer code, computer readable instructions, data structures, program modules, and other data for the computer 801.
  • a mass storage device 804 can be a hard disk, a removable magnetic disk, a removable optical disk, magnetic cassettes or other magnetic storage devices, flash memory cards, CD-ROM, digital versatile disks (DVD) or other optical storage, random access memories (RAM), read only memories (ROM), electrically erasable programmable read-only memory (EEPROM), and the like.
  • Any number of program modules can be stored on the mass storage device 804, including by way of example, an operating system 805 and application software 806. Each of the operating system 805 and application software 806 (or some combination thereof) may include elements of the programming and the application software 806.
  • Data 807 can also be stored on the mass storage device 804.
  • Data 804 can be stored in any of one or more databases known in the art. Examples of such databases include, DB2 ® , Microsoft ® Access, Microsoft ® SQL Server, Oracle ® , mySQL, PostgreSQL, and the like. The databases can be centralized or distributed across multiple systems.
  • a user can enter commands and information into the computer 801 via an input device (not shown).
  • input devices include, but are not limited to, a keyboard, pointing device (e.g., a "mouse"), a microphone, a joystick, a serial port, a scanner, and the like.
  • pointing device e.g., a "mouse”
  • microphone e.g., a microphone
  • joystick e.g., a joystick
  • serial port e.g., a "mouse”
  • serial port e.g., a scanner
  • USB universal serial bus
  • a display device 811 can also be connected to the system bus 813 via an interface, such as a display adapter 809.
  • a display device can be a cathode ray tube (CRT) monitor or a Liquid Crystal Display (LCD).
  • other output peripheral devices can include components such as speakers (not shown) and a printer (not shown) which can be connected to the computer 801 via Input/Output Interface 810.
  • the computer 801 can operate in a networked environment using logical connections to one or more remote computing devices 814a, b, c.
  • a remote computing device can be a personal computer, portable computer, a server, a router, a network computer, a peer device or other common network node, and so on.
  • Logical connections between the computer 801 and a remote computing device 814a, b, c can be made via a local area network (LAN) and a general wide area network (WAN).
  • LAN local area network
  • WAN general wide area network
  • a network adapter 808 can be implemented in both wired and wireless environments. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet 815.
  • application programs and other executable program components such as the operating system 805 are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computing device 801, and are executed by the data processor(s) of the computer.
  • An implementation of application software 806 maybe stored on or transmitted across some form of computer readable media.
  • An implementation of the disclosed method may also be stored on or transmitted across some form of computer readable media.
  • Computer readable media can be any available media that can be accessed by a computer.
  • Computer readable media may comprise “computer storage media” and “communications media.”
  • Computer storage media include volatile and non- volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
  • Fig. 9 illustrates a logical overview of the Internet 815 of one embodiment of the present invention.
  • One or more client computers 801 for example, such as the remote computing devices 814a, b, c depicted in Fig. 8, maybe connected to the Internet 815 as depicted at 901-1, 901-2, and 901-3.
  • one or more computers 902-1,902-2, and 902-3 of the type depicted at 801 may act as servers, providing web pages via HTTP request, database access, remote terminal services, digital file download or upload, or any other desired service.
  • one or more client computers, such as 901-1 may act as an Internet accessible server computer 902-1, and vice versa.
  • FIG. 1 is a flow chart illustrating steps for performing an online fraudulent transaction determination in accordance with the present invention.
  • input parameters are input into the OFME by an end user, for example, a banking institution.
  • the OFME provides a run-time environment for the selected risk score model.
  • the OFME provides a rules based engine for receiving input parameters; for example, a transaction identifier, an IP address, a date/time stamp, a unique identifier and a number of static factors for processing.
  • the OFME subsequently retrieves relevant information regarding an Internet user's IP address; for example, the Internet user's location from a NetAcuity server.
  • the operation of the NetAcuity server is discussed in U.S. Patent Application No. 09/832,959, which is commonly assigned to the assignee of the present application, which is herein incorporated by reference in its entirety.
  • a transaction identifier which is unique, associated with a given Internet based transaction is used by OFME to determine which risk score model should be utilized for a given transaction.
  • the Fraud Risk Advisor uses the unique identifier for tracking purposes. The results are then stored in a database.
  • Additional input parameters may be input into the OFME through end user supplied data.
  • the end user may utilize a hot file, suspect IP list, etc., which would be used by the OFME in the determination process.
  • the Fraud Risk Advisor proceeds to step 112.
  • the end user will select from a set of standard risk score models or end user defined risk score models to be used for a particular determination.
  • the pjesent invention proceeds to step 114 in which the OFME evaluates a given set of factors and determines a risk value for each given factor. Once the risk value has been determined for each factor associated with the OFME, the present invention proceeds to step 116 in which the OFME evaluates a given set of rules and determines a risk score.
  • the present invention proceeds to step 118 in which the OFME executes a risk score algorithm to determine an aggregate risk score.
  • the OFME uses the standard risk value from the rules evaluation, as well as -an optional static risk score to determine an aggregate risk score.
  • the rules based risk score could be assigned a value between O to 1,000. A risk score of O would be assigned to a transaction perceived to be highly fraudulent, while a risk score of 1,000 would be assigned to scores perceived to have a low risk of fraud.
  • the OFME determines whether the transaction proceeds to step 120 or step 122. If the score exceeds the predetermined threshold level, the OFME proceeds to step 120 because the transaction is determined to be fraudulent. Accordingly, the transaction is flagged and forwarded to the end user for further review along with each factor value and a reason code for each factor value. If the score is within predetermined threshold limits, the OFME proceeds to step 122 because the transaction is determined to be valid.
  • the end user receives output from the OFME for the pending transaction. If the transaction is determined to be fraudulent by the OFME, the end user receives the results from the OFME including factor values and reason codes for the transaction. In addition, the OFME will update the present invention's real-time statistics and store all relevant data, for example, the IP address, regarding the transaction in a database, even if the transaction is deemed valid. The stored data is used for both reporting purposes as well as analysis purposes for updating the risk score model's risk weights or removing certain factors or rules. The end user has the ability to override the results of the OFME and may flag a transaction determined to be valid as suspicious or deem a suspicious transaction valid.
  • FIG. 2 illustrates is an exemplary processing system 200 with which the invention may be used.
  • System 200 includes a user interface 220 in which an end user may input parameters, rules, and user defined functions to the OFME 202.
  • User interface 220 may comprise multiple user interfaces.
  • the user interface 220 also receives output data from the OFME 202 regarding a certain transaction.
  • the user interface 220 may be graphical or web based, or may use any other suitable input mechanism.
  • the OFME 202 acquires information associated with this data from, for example, a NetAcuity server 206, a validation server 204 and a behavior-tracking database 208.
  • Validation server 204 validates email addresses and area codes supplied by the end user for a given transaction.
  • Behavior tracking database 208 uses a unique identifier supplied by the end user associated with a given Internet user to determine whether a current Internet based transaction is in congruence with the normal behavior of the Internet user. This unique identifier is stored in the searchable behavior-tracking database 208.
  • the behavior-tracking database 208 is searched and geographic data along with an ISP and domain, which may also be stored with the unique identifier, is retrieved, if available. This information is then compared to the geographic data, ISP, and domain information associated with a current IP address for the current pending Internet based transaction. The result of the comparison, an access behavior factor, is used to determine whether the current pending Internet based transaction is fraudulent.
  • an automated challenge/response could be used to validate the Internet user accessing an account in real time. If there is no history for the current ⁇ address available in the behavior-tracking database 208 for the Internet user, the current geographic data, ISP and domain information associated with the current IP address is added to the behavior-tracking database 208. Accordingly, when an Internet user is creating an account, access behavior would not be used as a factor for fraud detection.
  • the unique identifier assigned to the Internet user may store multiple access, behaviors.
  • an Internet user may change their access behavior due to, for example, extended travel, change of residence, etc., the end user may override an access behavior violation returned by the OFME 202.
  • the OFME 202 uses the information supplied by the user interface 220, NetAcuity server 206, validation server 204 and behavior-tracking database 208 to determine a risk score associated with a given transaction. Once the OFME 202 computes the risk score, the risk score is sent along with any relevant information concerning the transaction to behavior tracking database 208, real time statistics database 212, user interface 220, and OFME data storage database 210.
  • OFME data storage database 210 may transfer data received from OFME 202 to OFME output warehouse storage 218 for long-term storage.
  • OFME data storage database 210 may transfer data received from OFME 202 to both a Reporting subsystem 214 and a Forensics subsystem 216 for processing and output to the user interface 220.
  • Forensics subsystem 216 provides the end user the ability to look-up information generated by running a risk score model. Thus, the end user can determine why a transaction is deemed suspicious or why a transaction was not deemed suspicious. Reporting subsystem 214 provides various reports to the end user, for example, the number of transaction flagged as being suspicious.
  • a method for calculating a travel velocity between a first access point and a second access point using a first and second IP address. Calculating a travel velocity has several practical uses, including determining a fraudulent transaction, network analysis, user profiling, user account verification and tracking, network access provider analysis, and advertising. Travel velocity may also be a factor utilized by the OFME 202 to determine a fraudulent transaction.
  • FIG. 3 illustrates one embodiment of the present invention useful for calculating travel velocity.
  • a first access location is determined based on a first Internet Protocol ("IP") address 301.
  • IP Internet Protocol
  • a first access time is determined 302.
  • a second access location is determined based on a second ⁇ address 303.
  • a second access time is determined 304.
  • the travel velocity between the first access location and the second access location is calculated 305 as a function of the first access location 301 and the first access time 302, and the second access location 303 and the second access time 304.
  • FIG. 4 A further embodiment of the present invention useful for calculating a travel velocity is logically illustrated in FIG. 4. While the embodiment of FIG. 4 continues from step 305 of FIG. 3, no particular order of steps is expressly or implicitly required.
  • a distance between the first access location 301 and the second access location 303 is computed 401.
  • a time difference is computed 402 between the first access time 302 and a second access time 304.
  • the travel velocity is calculated 403 between the first access location 301 and the second access location 303 by dividing the computed distance 401 by the computed time difference 402.
  • the first IP address is 24.131.36.54
  • the first access time 302 is 1:00 PM EST.
  • Methods for determining the location corresponding to an £P address such as those provided by a NetAcuity server, are used to determine that the first IP address corresponds to the first location 301 of Atlanta, Georgia, USA.
  • a second IP address of 144.214.5.246 is provided, and the second access time 304 is 1 : 05 PM EST.
  • methods are used to determine that 144.214.5.246 corresponds to a second access location 303 of Hong Kong, China.
  • the distance between the first access location 301 of Atlanta, and the second access location 303 of Hong Kong is computed 401 to be approximately 8405 miles.
  • the computed time difference 402 between the first access time 302 of 1 :00 PM EST and the second access time 304 of 1 :05 PM EST is 5 minutes.
  • the computed distance 401 of 8405 miles is divided by the time difference 402 of 5 minutes, to calculate a travel velocity 403 of 8405 miles / 5 minutes, or 100,860 miles per hour, which is suspiciously high. Calculating a User's Travel Velocity
  • a method for calculating a user's travel velocity between a first access location and a second access location using a first and second IP address. Calculating a user's travel velocity has several practical uses, including determining a fraudulent transaction, network analysis, user profiling, user account verification and tracking, network access provider analysis, and advertising. A user's travel velocity may also be a factor utilized by the OFME 202 to determine a fraudulent transaction.
  • FIG. 5 illustrates one embodiment of the present invention useful for calculating a user's travel velocity.
  • a first access location 501 is determined for a user.
  • the first access location 501 may be determined in a variety of ways, such as using the user's EP address to determine the first access location 501, retrieving the first access location 501 from the user's behavior profile, or by using a user supplied first access location 501.
  • a first access time 502 is determined for the user.
  • a second access location is then determined for the user 503 based on the IP address of the user.
  • a second access time is determined for the user 504.
  • the method of the present embodiment calculates the travel velocity 505 of the user between the first access location 501 and the second access location 503.
  • the user's travel velocity maybe calculated using a variety of methods, including the method embodied in FIG. 4. hi a further embodiment based on FIG. 5, the first access location 501 and the first access time 502 are determined from a behavior profile associated with the user.
  • the first access location 501 can be determined based on the user's last valid access location, hi another embodiment, the second access location 503 and the second access time 504 are the user's current access location and current access time.
  • a method for determining if a transaction is fraudulent by using a user's travel velocity as a fraud factor. Determining if a transaction is fraudulent based upon a user's travel velocity has several practical uses, such as stopping and deterring the theft and use of personal information online, which may result from identify theft, phishing emails, hacking, spy ware, Trojans, and the like. Likewise, the same method may be used to determine if a transaction is legitimate.
  • FIG. 6 One embodiment of a method for determining if a transaction is fraudulent based upon a user's travel velocity is illustrated in FIG. 6.
  • the travel velocity of a user is computed 601 between a first access location and a second access location.
  • One embodiment for calculating a user's travel velocity is provided in FIG. 5 in steps 501 through 505.
  • Other methods for computing a travel velocity may also be employed in the embodiment of FIG. 6.
  • the various embodiments included herein for determine a fraudulent transaction may utilize the OFME 202.
  • Behavior profiles may be utilized in the embodiment of FIG. 6 and in other embodiments to determine if a transaction is fraudulent. For example, access locations, access times, IP addresses, geographical locations, area codes, telephone numbers, email addresses, transaction frequencies, and other factors may be stored in a behavior profile. Behavior profiles are useful because they allow one or more variables corresponding to one or more, factors to be persistently stored, enabling embodiments to determine not only the travel velocity or likelihood of fraud between a first access location and a second access location, but to determine a pattern of fraudulent activity over a plurality of access locations, times, IP addresses, and the like.
  • the behavior profile may be stored in a database such as the behavior tracking database 208 of the embodiment of FIG. 2.
  • the method of FIG. 6 determines if one or more additional factors based upon the user's IP address will be computed. While only the user's travel velocity need be computed at 601, additional factors, including factors based upon the user's IP address may be used in various embodiments. The types and number of additional factors computed 603 may vary among the different embodiments to optimize the determination of a fraudulent transaction.
  • an additional factor computed 603 comprises a country, region, or city associated with the IP address of the user.
  • a factor computed 603 maybe a proximity of the user in comparison to a purported location of the user associated with the IP address.
  • a factor computed 603 also may comprise the connection type of the user, such as dial-up, Integrated Services Digital Network (ISDN), cable modem, Digital Subscriber Line (DSL), Digital Signal 1 (Tl), or Optical Carrier 3 (OC3).
  • the factor 603 may also comprise a host type, such as personal network end point, corporate network end point, personal or corporate proxy, personal or corporate firewall, and the like.
  • Additional embodiments extending the embodiment of FIG. 6 may utilize factors supplied by the user, including an address supplied by a client for comparison with an address associated with the IP address, an area code and telephone number supplied by the client for comparison with an area code and telephone number stored in a database associated with the client, or an email address supplied by the client.
  • factors supplied by the user including an address supplied by a client for comparison with an address associated with the IP address, an area code and telephone number supplied by the client for comparison with an area code and telephone number stored in a database associated with the client, or an email address supplied by the client.
  • User supplied factors are useful to various embodiments of the present invention where the embodiments may assume that the user supplied factors are accurate as they are supplied directly by the user.
  • a factor is an access behavior associated with the user based on transaction habits stored in a database that are compared with a current transaction.
  • a factor may also comprise a frequency with which the transaction is attempted or executed within a predetermined amount of time, or a velocity with which a single IP address accesses or uses multiple unique identifiers within a specified period of time.
  • a client may participate in the determination of factors to be computed at 603. For example, in one embodiment, a client may assign a threshold level for one or more of the factors. The client may also create one or more user defined factors, and the client may also define constraint rules for one or more factors. Allowing the user to determine factors, assign threshold levels for factors, and constraint rules for factors allows the method of FIG. 6 to optimally determine if a transaction is fraudulent in a method tailored to the user.
  • the method determines if the transaction is fraudulent based upon the user's travel velocity and zero or more additional factors, such as those described above.
  • the determination 604 that a transaction is fraudulent or legitimate may occur in real time, near real time, or non-real time, based upon the particular implementation of the method of FIG. 6.
  • the user's travel velocity may be a factor utilized by the OFME 202 to determine a fraudulent transaction, and may be stored in a behavior profile residing in a behavior tracking database 208.
  • a method for determining if a transaction is fraudulent by using a computed transaction frequency.
  • a high transaction frequency may be useful, for example, where a user's personal information has been stolen and distributed to one or more individuals who intend to make multiple fraudulent online purchases with the personal information of the user.
  • a high transaction frequency may indicate a fraudulent transaction where a particular transaction is attempted repeatedly from the same IP address within a predetermined period of time.
  • a transaction may be fraudulent where the same or a similar transaction is attempted or executed multiple times and received by or at a single IP address. For example, suppose a person's credit card information is stolen and distributed among a group of persons who intend to use that information to make fraudulent purchases at a particular online retailer who operates an e-commerce server at a particular IP address.
  • the frequency with which multiple IP addresses attempt or execute a transaction received at a single IP address may indicate that a transaction is fraudulent.
  • the factors discussed above may be incorporated to determine a fraudulent transaction, such as travel velocity or access behaviors retrieved from user profiles.
  • Determining if a transaction is fraudulent based transaction frequency has several practical uses, such as stopping and deterring the theft and use of personal information online, which may result from identify theft, phishing emails, hacking, spy ware, Trojans, and the like. Likewise, the same methods may be used to determine if a transaction is legitimate.
  • the embodiment illustrated in FIG. 7 provides one method for utilizing a transaction frequency to determine a fraudulent transaction.
  • a frequency is computed with which a transaction is attempted from a first IP address within a predetermined period of time. For example, if an online purchase transaction originating from a first IP address is attempted or executed a hundred times within an hour, then the embodiment of FIG. 7 may determine that the transaction is fraudulent 702 based upon the computed transaction frequency 701.
  • the transaction frequency 701 may be computed in various ways, including by dividing the number of times a transaction is attempted or executed over the time period in which those transaction were attempted or executed.
  • the transaction frequency may also be a factor utilized by the OFME 202 of the embodiment of FIG. 2, and stored in a behavior profile residing in a behavior tracking database 208, also of FIG. 2.
  • Transaction frequency in another embodiment may be combined with the host type of the IP address or other factors to enhance the accuracy of the fraud determination. For example, extending the embodiment of Fig. 7, suppose that one or more transactions have been attempted from an IP address one hundred times within an hour. Without other information, a transaction frequency of 100 attempts per hour from an IP address may indicate a fraudulent transaction. However, if that IP address represents a network proxy or firewall which provides Internet access to multiple users, then a transaction frequency of 100 attempts per hour may in fact not indicate a likely fraudulent transaction. Therefore, comparing the transaction frequency to the host type of the IP address can optimize the fraud determination by decreasing false positives when the IP address represents a proxy, firewall, or other Internet gateway which provides access for multiple users, several of whom may be conducting one or more legitimate transactions. Other factors such as connection type, travel velocity, information retrieved from a behavior profile, geographic location, user supplied factors, and the like, may also be combined with transaction frequency to enhance the accuracy of the fraud determination.

Abstract

A fraudulent business transaction application (110) is provided for monitoring application based fraud (112). 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 (114). Methods are also provided for calculating travel velocity and transaction frequency, which are useful for determining a fraudulent transaction (120).

Description

FRAUD RISK ADVISOR
CROSS-REFERENCE TO RELATED APPLICATIONS
This PCT application claims priority to U.S. Application Serial No. 11/209,885 entitled "Fraud Risk Advisor," filed on August 23, 2005, which claims priority to U.S. Application Serial No. 10/943,454 entitled "Fraud Risk Advisor," filed on September 17, 2004, each herein incorporated by reference in its entirety.
Background Of The Invention
1. Field of the Invention
The present invention relates to techniques for detecting fraudulent online transactions. The present invention provides methods, systems, and computer program products for operating a fraud engine that is capable of accepting an IP address and a number of factors relating to an end user in order to determine whether a transaction is fraudulent.
The present invention also relates to methods, systems, and computer program products for calculating a travel velocity between two access locations, determining if a transaction is fraudulent based on a user's travel velocity between two access locations, and determining if a transaction is fraudulent based on a transaction frequency.
2. Description of the Related Art
The ease of hiding an identity on the Internet makes it difficult for financial services organizations to carry the "know your customer" mantra to the online world. Ia 2003 alone, Internet-related fraud accounted for 55% of all fraud reports according to the Federal Trade Commission, up nearly 45% from the previous year. In order for financial services organizations to continue successfully serving more of their customers online, creating a safe and secure environment is a top priority. Accordingly, there is a need and desire for a methods, systems, and computer program products for detecting and preventing fraudulent online transactions utilizing the IP address of a user.
Summary of The Invention
The present invention provides methods, systems, and computer program products (hereinafter "method" or "methods" for convenience) for determining fraudulent online transactions. In one embodiment, an end user inputs parameters and rules concerning a particular transaction into the system. Based on the parameters, rules, and other information concerning a particular transaction, the system computes a score associated with the likelihood that the transaction is fraudulent. The score is then compared with various thresholds which may be set by the end user. If the score exceeds the thresholds, then the transaction is determined to be fraudulent. Data regarding the transaction may also be output to the end user. Upon review, the end user may change the fraud status of a given transaction.
Another embodiment of the present invention provides methods for calculating a travel velocity between a first and second access location, utilizing a travel velocity to determine if a transaction is fraudulent, as well as determining if a transaction is fraudulent based upon a computed transaction frequency.
It will be apparent to those skilled in the art that various devices maybe used to carry out the systems, methods, or computer program products of the present invention, including cell phones, personal digital assistants, wireless communication devices, personal computers, or dedicated hardware devices designed specifically to carry out embodiments of the present invention.
Unless otherwise expressly stated, it is in no way intended that any method or embodiment set forth herein be construed as requiring that its steps be performed in a specific order. Accordingly, where a method, system, or computer program product claim does not specifically state in the claims or descriptions that the steps are to be limited to a specific order, it is no way intended that an order be inferred, in any respect. This holds for any possible non-express basis for interpretation, including matters of logic with respect to arrangement of steps or operational flow, plain meaning derived from grammatical organization or punctuation, or the number or type of embodiments described in the specification.
Brief Description Of The Drawings
The foregoing and other advantages and features of the invention will become more apparent from the detailed description of exemplary embodiments of the invention given below with reference to the accompanying drawings. FIG. 1 is a flow chart illustrating one embodiment of the present invention for determining whether an online transaction is fraudulent using an Online Fraud Mitigation Engine.
FIG. 2 is a block diagram of a computer system for implementing embodiments of the present invention.
FIG. 3 illustrates one embodiment of the present invention useful for calculating a travel velocity.
FIG. 4 illustrates another embodiment of the present invention useful for calculating a travel velocity.
FIG. 5 illustrates one embodiment of the present invention useful for calculating a user's travel velocity.
FIG. 6 illustrates one embodiment of the present invention useful for determining a fraudulent transaction using a travel velocity.
FIG. 7 illustrates one embodiment of the present invention useful for determining a fraudulent transaction using a transaction frequency.
FIG. 8 shows a logical overview of a computer system which may be used to carry out the various embodiments of the present invention.
FIG. 9 illustrates logically the arrangement of computers connected to the Internet in one embodiment of the present invention. hi the following detailed description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration of specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized, and that structural, logical and programming changes may be made without departing from the spirit and scope of the present invention.
Detailed Description of the Invention
Before the present methods, systems, and computer program products are disclosed and described, it is to be understood that this invention is not limited to specific methods, specific components, or to particular compositions, as such may, of course, vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting.
As used in the specification and the appended claims, the singular forms "a," "an" and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "an encoder" includes mixtures of encoders, reference to "an encoder" includes mixtures of two or more such encoders, and the like.
The term "risk factor" includes any factor used in a transaction that has some level of risk associated with it.
The term "static risk factor" includes any factor that does not change at run time.
The term "dynamic risk factor" includes any factor that has its value calculated at mn time.
The term "risk value" includes any number associated with a factor.
The term "risk weight" includes any number that determines how much influence a factor's risk value is to the outcome of a risk score.
The term "rule" includes any conditional statement that applies Boolean logic to risk values.
The term "risk score" includes any aggregation of risk values based on a computation of risk values and risk weights or a rule setting the risk score directly.
The term "online fraud mitigation engine" (OFME) includes any component of the present invention that accepts an EP address along with a number of factors to thereby create a risk score for a given transaction which can be used to determine if the transaction is fraudulent.
The term "transaction" includes any type of online activity, such as online banking account access, credit card transactions, online bill pay, wire transfers, stock trades, transactions utilizing personal information, and the like.
The term "transaction identifier" includes any unique system generated number that identifies a particular risk score model.
The term "risk score model" includes any set of logical rules, applicable static and dynamic factors, risk weights for the factors, a frau- score algorithm, a risk score threshold, and reason codes used to identify a fraudulent transaction.
The term "user" or "client" includes one or more persons, entities, or computers.
The terms "method(s)," "system(s)," and "computer program product(s)" may be used interchangeably within various embodiments of the present invention. The methods of the present invention can be carried out using a processor programmed to carry out the various embodiments of the present invention. FIG. 8 is a block diagram illustrating an exemplary operating environment for performing the various embodiments. This exemplary operating environment is only an example of an operating environment and is not intended to suggest any limitation as to the scope of use or functionality of operating environment architecture. Neither should the operating environment be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment.
The method can be operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the method include, but are not limited to, personal computers, server computers, laptop devices, and multiprocessor systems. Additional examples include set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The method may be described in the general context of computer instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The method may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The method disclosed herein can be implemented via a general-purpose computing device in the form of a computer 801. The components of the computer 801 can include, but are not limited to, one or more processors or processing units 803, a system memory 812, and a system bus 813 that couples various system components including the processor 803 to the system memory 812.
The processor 803 in Fig. 8 can be an x-86 compatible processor, including a PENTIUM rV, manufactured by Intel Corporation, or an ATHLON 64 processor, manufactured by Advanced Micro Devices Corporation. Processors utilizing other instruction sets may also be used, including those manufactured by Apple, IBM, or NEC. The system bus 813 represents one or more of several possible types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures can include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnects (PCI) bus also known as a Mezzanine bus. This bus, and all buses specified in this description can also be implemented over a wired or wireless network connection. The bus 813, and all buses specified in this description can also be implemented over a wired or wireless network connection and each of the subsystems, including the processor 803, a mass storage device 804, an operating system 805, application software 806, data 807, a network adapter 808, system memory 812, an Input/Output Interface 810, a display adapter 809, a display device 811, and a human machine interface 802, can be contained within one or more remote computing devices 814a,b,c at physically separate locations, connected through buses of this form, in effect implementing a fully distributed system.
The operating system 805 in Fig. 8 includes operating systems such as MICROSOFT WINDOWS XP, WINDOWS 2000, WINDOWS NT, or WINDOWS 98, and REDHAT LINUX, FREE BSD, or SUN MICROSYSTEMS SOLARIS. Additionally, the application software 806 may include web browsing software, such as MICROSOFT INTERNET EXPLORER or MOZILLA FIREFOX, enabling a user to view HTML, SGML, XML, or any other suitably constructed document language on the display device 811.
The computer 801 typically includes a variety of computer readable media. Such media can be any available media that is accessible by the computer 801 and includes both volatile and non- volatile media, removable and non-removable media. The system memory 812 includes computer readable media in the form of volatile memory, such as random access memory (RAM), and/or non-volatile memory, such as read only memory (ROM). The system memory 812 typically contains data such as data 807 and and/or program modules such as operating system 805 and application software 806 that are immediately accessible to and/or are presently operated on by the processing unit 803.
The computer 801 may also include other removable/non-removable, volatile/non¬ volatile computer storage media. Byway of example, FIG. 8 illustrates a mass storage device 804 which can provide non- volatile storage of computer code, computer readable instructions, data structures, program modules, and other data for the computer 801. For example, a mass storage device 804 can be a hard disk, a removable magnetic disk, a removable optical disk, magnetic cassettes or other magnetic storage devices, flash memory cards, CD-ROM, digital versatile disks (DVD) or other optical storage, random access memories (RAM), read only memories (ROM), electrically erasable programmable read-only memory (EEPROM), and the like.
Any number of program modules can be stored on the mass storage device 804, including by way of example, an operating system 805 and application software 806. Each of the operating system 805 and application software 806 (or some combination thereof) may include elements of the programming and the application software 806. Data 807 can also be stored on the mass storage device 804. Data 804 can be stored in any of one or more databases known in the art. Examples of such databases include, DB2®, Microsoft® Access, Microsoft® SQL Server, Oracle®, mySQL, PostgreSQL, and the like. The databases can be centralized or distributed across multiple systems.
A user can enter commands and information into the computer 801 via an input device (not shown). Examples of such input devices include, but are not limited to, a keyboard, pointing device (e.g., a "mouse"), a microphone, a joystick, a serial port, a scanner, and the like. These and other input devices can be connected to the processing unit 803 via a human machine interface 802 that is coupled to the system bus 813, but may be connected by other interface and bus structures, such as a parallel port, serial port, game port, or a universal serial bus (USB).
A display device 811 can also be connected to the system bus 813 via an interface, such as a display adapter 809. For example, a display device can be a cathode ray tube (CRT) monitor or a Liquid Crystal Display (LCD). In addition to the display device 811, other output peripheral devices can include components such as speakers (not shown) and a printer (not shown) which can be connected to the computer 801 via Input/Output Interface 810.
The computer 801 can operate in a networked environment using logical connections to one or more remote computing devices 814a, b, c. By way of example, a remote computing device can be a personal computer, portable computer, a server, a router, a network computer, a peer device or other common network node, and so on. Logical connections between the computer 801 and a remote computing device 814a, b, c can be made via a local area network (LAN) and a general wide area network (WAN). Such network connections can be through a network adapter 808. A network adapter 808 can be implemented in both wired and wireless environments. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet 815.
For purposes of illustration, application programs and other executable program components such as the operating system 805 are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computing device 801, and are executed by the data processor(s) of the computer. An implementation of application software 806 maybe stored on or transmitted across some form of computer readable media. An implementation of the disclosed method may also be stored on or transmitted across some form of computer readable media. Computer readable media can be any available media that can be accessed by a computer. By way of example, and not limitation, computer readable media may comprise "computer storage media" and "communications media." "Computer storage media" include volatile and non- volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
Fig. 9 illustrates a logical overview of the Internet 815 of one embodiment of the present invention. One or more client computers 801, for example, such as the remote computing devices 814a, b, c depicted in Fig. 8, maybe connected to the Internet 815 as depicted at 901-1, 901-2, and 901-3. Additionally, one or more computers 902-1,902-2, and 902-3 of the type depicted at 801 may act as servers, providing web pages via HTTP request, database access, remote terminal services, digital file download or upload, or any other desired service. Furthermore, one or more client computers, such as 901-1, may act as an Internet accessible server computer 902-1, and vice versa.
Online Fraud Mitigation Engine
FIG. 1 is a flow chart illustrating steps for performing an online fraudulent transaction determination in accordance with the present invention. At step 105, input parameters are input into the OFME by an end user, for example, a banking institution. The OFME provides a run-time environment for the selected risk score model. The OFME provides a rules based engine for receiving input parameters; for example, a transaction identifier, an IP address, a date/time stamp, a unique identifier and a number of static factors for processing. The OFME subsequently retrieves relevant information regarding an Internet user's IP address; for example, the Internet user's location from a NetAcuity server. The operation of the NetAcuity server is discussed in U.S. Patent Application No. 09/832,959, which is commonly assigned to the assignee of the present application, which is herein incorporated by reference in its entirety.
A transaction identifier, which is unique, associated with a given Internet based transaction is used by OFME to determine which risk score model should be utilized for a given transaction. The Fraud Risk Advisor uses the unique identifier for tracking purposes. The results are then stored in a database.
Additional input parameters may be input into the OFME through end user supplied data. For example, the end user may utilize a hot file, suspect IP list, etc., which would be used by the OFME in the determination process. Once the OFME receives the specified input parameters, the Fraud Risk Advisor proceeds to step 112. In step 112, the end user will select from a set of standard risk score models or end user defined risk score models to be used for a particular determination.
After the OFME loads the appropriate risk score model, the pjesent invention proceeds to step 114 in which the OFME evaluates a given set of factors and determines a risk value for each given factor. Once the risk value has been determined for each factor associated with the OFME, the present invention proceeds to step 116 in which the OFME evaluates a given set of rules and determines a risk score.
When the risk score has been determined by a rule match, the present invention proceeds to step 118 in which the OFME executes a risk score algorithm to determine an aggregate risk score. The OFME uses the standard risk value from the rules evaluation, as well as -an optional static risk score to determine an aggregate risk score. For example, the rules based risk score could be assigned a value between O to 1,000. A risk score of O would be assigned to a transaction perceived to be highly fraudulent, while a risk score of 1,000 would be assigned to scores perceived to have a low risk of fraud.
Dependent on the risk score calculated in step 118 and threshold limits defined by an end user, the OFME determines whether the transaction proceeds to step 120 or step 122. If the score exceeds the predetermined threshold level, the OFME proceeds to step 120 because the transaction is determined to be fraudulent. Accordingly, the transaction is flagged and forwarded to the end user for further review along with each factor value and a reason code for each factor value. If the score is within predetermined threshold limits, the OFME proceeds to step 122 because the transaction is determined to be valid.
At step 130, the end user receives output from the OFME for the pending transaction. If the transaction is determined to be fraudulent by the OFME, the end user receives the results from the OFME including factor values and reason codes for the transaction. In addition, the OFME will update the present invention's real-time statistics and store all relevant data, for example, the IP address, regarding the transaction in a database, even if the transaction is deemed valid. The stored data is used for both reporting purposes as well as analysis purposes for updating the risk score model's risk weights or removing certain factors or rules. The end user has the ability to override the results of the OFME and may flag a transaction determined to be valid as suspicious or deem a suspicious transaction valid.
FIG. 2 illustrates is an exemplary processing system 200 with which the invention may be used. System 200 includes a user interface 220 in which an end user may input parameters, rules, and user defined functions to the OFME 202. User interface 220 may comprise multiple user interfaces. The user interface 220 also receives output data from the OFME 202 regarding a certain transaction. The user interface 220 may be graphical or web based, or may use any other suitable input mechanism.
Once the OFME 202 receives data from the user interface 220, the OFME 202 acquires information associated with this data from, for example, a NetAcuity server 206, a validation server 204 and a behavior-tracking database 208. Validation server 204 validates email addresses and area codes supplied by the end user for a given transaction.
Behavior tracking database 208 uses a unique identifier supplied by the end user associated with a given Internet user to determine whether a current Internet based transaction is in congruence with the normal behavior of the Internet user. This unique identifier is stored in the searchable behavior-tracking database 208. When the Internet user performs an Internet based transaction, the behavior-tracking database 208 is searched and geographic data along with an ISP and domain, which may also be stored with the unique identifier, is retrieved, if available. This information is then compared to the geographic data, ISP, and domain information associated with a current IP address for the current pending Internet based transaction. The result of the comparison, an access behavior factor, is used to determine whether the current pending Internet based transaction is fraudulent. If an access behavior violation is determined, an automated challenge/response could be used to validate the Internet user accessing an account in real time. If there is no history for the current ~ address available in the behavior-tracking database 208 for the Internet user, the current geographic data, ISP and domain information associated with the current IP address is added to the behavior-tracking database 208. Accordingly, when an Internet user is creating an account, access behavior would not be used as a factor for fraud detection.
The unique identifier assigned to the Internet user may store multiple access, behaviors. In addition, because an Internet user may change their access behavior due to, for example, extended travel, change of residence, etc., the end user may override an access behavior violation returned by the OFME 202.
The OFME 202 uses the information supplied by the user interface 220, NetAcuity server 206, validation server 204 and behavior-tracking database 208 to determine a risk score associated with a given transaction. Once the OFME 202 computes the risk score, the risk score is sent along with any relevant information concerning the transaction to behavior tracking database 208, real time statistics database 212, user interface 220, and OFME data storage database 210.
In one embodiment, OFME data storage database 210 may transfer data received from OFME 202 to OFME output warehouse storage 218 for long-term storage. In addition, OFME data storage database 210 may transfer data received from OFME 202 to both a Reporting subsystem 214 and a Forensics subsystem 216 for processing and output to the user interface 220.
Forensics subsystem 216 provides the end user the ability to look-up information generated by running a risk score model. Thus, the end user can determine why a transaction is deemed suspicious or why a transaction was not deemed suspicious. Reporting subsystem 214 provides various reports to the end user, for example, the number of transaction flagged as being suspicious.
Calculating Travel Velocity
In one embodiment of the present invention, a method is provided for calculating a travel velocity between a first access point and a second access point using a first and second IP address. Calculating a travel velocity has several practical uses, including determining a fraudulent transaction, network analysis, user profiling, user account verification and tracking, network access provider analysis, and advertising. Travel velocity may also be a factor utilized by the OFME 202 to determine a fraudulent transaction.
FIG. 3 illustrates one embodiment of the present invention useful for calculating travel velocity. First, a first access location is determined based on a first Internet Protocol ("IP") address 301. Second, a first access time is determined 302. Third, a second access location is determined based on a second ~ address 303. Fourth, a second access time is determined 304. Finally, the travel velocity between the first access location and the second access location is calculated 305 as a function of the first access location 301 and the first access time 302, and the second access location 303 and the second access time 304.
A further embodiment of the present invention useful for calculating a travel velocity is logically illustrated in FIG. 4. While the embodiment of FIG. 4 continues from step 305 of FIG. 3, no particular order of steps is expressly or implicitly required. In this embodiment, a distance between the first access location 301 and the second access location 303 is computed 401. Second, a time difference is computed 402 between the first access time 302 and a second access time 304. Third, the travel velocity is calculated 403 between the first access location 301 and the second access location 303 by dividing the computed distance 401 by the computed time difference 402.
For illustration purposes only, according to the embodiment of FIG. 4, suppose that the first IP address is 24.131.36.54, and the first access time 302 is 1:00 PM EST. Methods for determining the location corresponding to an £P address, such as those provided by a NetAcuity server, are used to determine that the first IP address corresponds to the first location 301 of Atlanta, Georgia, USA. Next, a second IP address of 144.214.5.246 is provided, and the second access time 304 is 1 : 05 PM EST. Again, methods are used to determine that 144.214.5.246 corresponds to a second access location 303 of Hong Kong, China.
Next, the distance between the first access location 301 of Atlanta, and the second access location 303 of Hong Kong, is computed 401 to be approximately 8405 miles. The computed time difference 402 between the first access time 302 of 1 :00 PM EST and the second access time 304 of 1 :05 PM EST is 5 minutes. Then, the computed distance 401 of 8405 miles is divided by the time difference 402 of 5 minutes, to calculate a travel velocity 403 of 8405 miles / 5 minutes, or 100,860 miles per hour, which is suspiciously high. Calculating a User's Travel Velocity
In one embodiment of the present invention, a method is provided for calculating a user's travel velocity between a first access location and a second access location using a first and second IP address. Calculating a user's travel velocity has several practical uses, including determining a fraudulent transaction, network analysis, user profiling, user account verification and tracking, network access provider analysis, and advertising. A user's travel velocity may also be a factor utilized by the OFME 202 to determine a fraudulent transaction.
FIG. 5 illustrates one embodiment of the present invention useful for calculating a user's travel velocity. First, a first access location 501 is determined for a user. The first access location 501 may be determined in a variety of ways, such as using the user's EP address to determine the first access location 501, retrieving the first access location 501 from the user's behavior profile, or by using a user supplied first access location 501.
Second, a first access time 502 is determined for the user. A second access location is then determined for the user 503 based on the IP address of the user. Fourth, a second access time is determined for the user 504. Then, the method of the present embodiment calculates the travel velocity 505 of the user between the first access location 501 and the second access location 503. The user's travel velocity maybe calculated using a variety of methods, including the method embodied in FIG. 4. hi a further embodiment based on FIG. 5, the first access location 501 and the first access time 502 are determined from a behavior profile associated with the user. In other embodiments, the first access location 501 can be determined based on the user's last valid access location, hi another embodiment, the second access location 503 and the second access time 504 are the user's current access location and current access time.
Determining a Fraudulent Transaction hi one embodiment of the present invention, a method is provided for determining if a transaction is fraudulent by using a user's travel velocity as a fraud factor. Determining if a transaction is fraudulent based upon a user's travel velocity has several practical uses, such as stopping and deterring the theft and use of personal information online, which may result from identify theft, phishing emails, hacking, spy ware, Trojans, and the like. Likewise, the same method may be used to determine if a transaction is legitimate.
One embodiment of a method for determining if a transaction is fraudulent based upon a user's travel velocity is illustrated in FIG. 6. First, the travel velocity of a user is computed 601 between a first access location and a second access location. One embodiment for calculating a user's travel velocity is provided in FIG. 5 in steps 501 through 505. Other methods for computing a travel velocity may also be employed in the embodiment of FIG. 6. The various embodiments included herein for determine a fraudulent transaction may utilize the OFME 202.
Behavior profiles may be utilized in the embodiment of FIG. 6 and in other embodiments to determine if a transaction is fraudulent. For example, access locations, access times, IP addresses, geographical locations, area codes, telephone numbers, email addresses, transaction frequencies, and other factors may be stored in a behavior profile. Behavior profiles are useful because they allow one or more variables corresponding to one or more, factors to be persistently stored, enabling embodiments to determine not only the travel velocity or likelihood of fraud between a first access location and a second access location, but to determine a pattern of fraudulent activity over a plurality of access locations, times, IP addresses, and the like. The behavior profile may be stored in a database such as the behavior tracking database 208 of the embodiment of FIG. 2.
Second, the method of FIG. 6 determines if one or more additional factors based upon the user's IP address will be computed. While only the user's travel velocity need be computed at 601, additional factors, including factors based upon the user's IP address may be used in various embodiments. The types and number of additional factors computed 603 may vary among the different embodiments to optimize the determination of a fraudulent transaction.
If an additional factor is determined to be remaining 602, then that additional factor is computed 603. Next, the method of FIG. 6 then determines 602 and computes 603 remaining additional factors until no factors remain to be computed, causing the method of FIG. 6 to proceed to step 604.
In one embodiment based on the embodiment of FIG. 6, an additional factor computed 603 comprises a country, region, or city associated with the IP address of the user. In another embodiment extending the embodiment of FIG. 6, a factor computed 603 maybe a proximity of the user in comparison to a purported location of the user associated with the IP address. A factor computed 603 also may comprise the connection type of the user, such as dial-up, Integrated Services Digital Network (ISDN), cable modem, Digital Subscriber Line (DSL), Digital Signal 1 (Tl), or Optical Carrier 3 (OC3). The factor 603 may also comprise a host type, such as personal network end point, corporate network end point, personal or corporate proxy, personal or corporate firewall, and the like.
Additional embodiments extending the embodiment of FIG. 6 may utilize factors supplied by the user, including an address supplied by a client for comparison with an address associated with the IP address, an area code and telephone number supplied by the client for comparison with an area code and telephone number stored in a database associated with the client, or an email address supplied by the client. User supplied factors are useful to various embodiments of the present invention where the embodiments may assume that the user supplied factors are accurate as they are supplied directly by the user.
Further factors may be utilized by the embodiment of FIG. 6, such as where a factor is an access behavior associated with the user based on transaction habits stored in a database that are compared with a current transaction. A factor may also comprise a frequency with which the transaction is attempted or executed within a predetermined amount of time, or a velocity with which a single IP address accesses or uses multiple unique identifiers within a specified period of time.
In further embodiments of FIG. 6, a client may participate in the determination of factors to be computed at 603. For example, in one embodiment, a client may assign a threshold level for one or more of the factors. The client may also create one or more user defined factors, and the client may also define constraint rules for one or more factors. Allowing the user to determine factors, assign threshold levels for factors, and constraint rules for factors allows the method of FIG. 6 to optimally determine if a transaction is fraudulent in a method tailored to the user.
Next, in the embodiment of FIG. 6, the method determines if the transaction is fraudulent based upon the user's travel velocity and zero or more additional factors, such as those described above. The determination 604 that a transaction is fraudulent or legitimate may occur in real time, near real time, or non-real time, based upon the particular implementation of the method of FIG. 6. The user's travel velocity may be a factor utilized by the OFME 202 to determine a fraudulent transaction, and may be stored in a behavior profile residing in a behavior tracking database 208. Transaction Frequency
In one embodiment of the present invention, a method is provided for determining if a transaction is fraudulent by using a computed transaction frequency. A high transaction frequency may be useful, for example, where a user's personal information has been stolen and distributed to one or more individuals who intend to make multiple fraudulent online purchases with the personal information of the user. A high transaction frequency may indicate a fraudulent transaction where a particular transaction is attempted repeatedly from the same IP address within a predetermined period of time.
Likewise, a transaction may be fraudulent where the same or a similar transaction is attempted or executed multiple times and received by or at a single IP address. For example, suppose a person's credit card information is stolen and distributed among a group of persons who intend to use that information to make fraudulent purchases at a particular online retailer who operates an e-commerce server at a particular IP address. According to one embodiment of the present invention, the frequency with which multiple IP addresses attempt or execute a transaction received at a single IP address, such as the address of an e-commerce server, may indicate that a transaction is fraudulent. In further embodiments, the factors discussed above may be incorporated to determine a fraudulent transaction, such as travel velocity or access behaviors retrieved from user profiles.
Determining if a transaction is fraudulent based transaction frequency has several practical uses, such as stopping and deterring the theft and use of personal information online, which may result from identify theft, phishing emails, hacking, spy ware, Trojans, and the like. Likewise, the same methods may be used to determine if a transaction is legitimate. The embodiment illustrated in FIG. 7 provides one method for utilizing a transaction frequency to determine a fraudulent transaction.
First, in the embodiment of FIG. 7, a frequency is computed with which a transaction is attempted from a first IP address within a predetermined period of time. For example, if an online purchase transaction originating from a first IP address is attempted or executed a hundred times within an hour, then the embodiment of FIG. 7 may determine that the transaction is fraudulent 702 based upon the computed transaction frequency 701.
The transaction frequency 701 may be computed in various ways, including by dividing the number of times a transaction is attempted or executed over the time period in which those transaction were attempted or executed. The transaction frequency may also be a factor utilized by the OFME 202 of the embodiment of FIG. 2, and stored in a behavior profile residing in a behavior tracking database 208, also of FIG. 2.
Transaction frequency in another embodiment may be combined with the host type of the IP address or other factors to enhance the accuracy of the fraud determination. For example, extending the embodiment of Fig. 7, suppose that one or more transactions have been attempted from an IP address one hundred times within an hour. Without other information, a transaction frequency of 100 attempts per hour from an IP address may indicate a fraudulent transaction. However, if that IP address represents a network proxy or firewall which provides Internet access to multiple users, then a transaction frequency of 100 attempts per hour may in fact not indicate a likely fraudulent transaction. Therefore, comparing the transaction frequency to the host type of the IP address can optimize the fraud determination by decreasing false positives when the IP address represents a proxy, firewall, or other Internet gateway which provides access for multiple users, several of whom may be conducting one or more legitimate transactions. Other factors such as connection type, travel velocity, information retrieved from a behavior profile, geographic location, user supplied factors, and the like, may also be combined with transaction frequency to enhance the accuracy of the fraud determination.
While the invention has been described in detail in connection with exemplary embodiments, it should be understood that the invention is not limited to the above-disclosed embodiments. Rather, the invention can be modified to incorporate any number of variations; alternations, substitutions, or equivalent arrangements not heretofore described, but which are commensurate with the spirit and scope of the invention. In particular, the specific embodiments of the Fraud Risk Advisor described should be taken as exemplary and not limiting. For example, the present invention may be used in a web-based application. Accordingly, the invention is not limited by the foregoing description or drawings, but is only limited by the scope of the appended claims.

Claims

CLAIMSWe Claim:
1. A method for calculating a travel velocity between a first access location and a second access location, comprising the steps of:
(a) determining the first access location based on a first IP address;
(b) determining a first access time;
(c) determining the second access location based on a second IP address;
(d) determining a second access time; and
(e) calculating the travel velocity between the first access location and the second access location as a function of the first access location and the first access time and the second access location and the second access time.
2. The method of claim 1, wherein the calculating step comprises the steps of:
(a) computing a distance between the first access location and the second access location;
(b) computing a time difference between the first access time and the second access time; and
(c) calculating the travel velocity between the first access location and the second access location by dividing the computed distance by the computed time difference.
3. A method for calculating a user's travel velocity between a first access location and a second access location, comprising the steps of:
(a) determining for the user the first access location and a first access time;
(b) determining for the user the second access location based on the IP address of the user;
(c) determining for the user a second access time; and
(d) calculating the travel velocity of the user as a function of the first access location and the first access time and the second access location and the second access time.
4. The method of claim 3, wherein the first access location and the first access time are determined from a behavior profile associated with the user.
5. The method of claim 3, wherein the first access location is determined as a function of the user's IP address at the first access location.
6. The method of claim 3, wherein the second access location is stored in a behavior profile associated with the user.
7. The method of claim 3, wherein the first access location is based on the user's last valid access location.
8. The method of claim 3, wherein the second access location and the second access time are the user's current access location and current access time.
9. A method for determining if an online transaction is fraudulent, comprising the steps of:
(a) computing one or more factors based on the D? address of the user, wherein at least one factor is the travel velocity of the user between a first access location and a second access location; and
(b) determining whether the transaction is fraudulent based on the one or more factors.
10. The method of claim 9, wherein the determining step comprises determining whether the transaction is fraudulent by applying one or more rules to at least one factor.
11. The method of claim 9, wherein the user's travel velocity is determined according to the steps of:
(a) determining for the user the first access location based a first IP address;
(b) determining for the user a first access time;
(c) determining for the user the second access location based on a second IP address;
(d) determining for the user a second access time; and (e) calculating the user's travel velocity between the first access location and the second access location as a function of the first access location and the first access time and the second access location and the second access time.
12. The method of claim 11, wherein the calculating the user's travel velocity step comprises the steps of:
(a) computing a distance between the first access location and the second access location;
(b) computing a time difference between the first access time and the second access time; and
(c) calculating the travel velocity between the first access location and the second access location by dividing the computed distance by the computed time difference.
13. The method of claim 9, further comprising forwarding the determination to a client for further processing by the client.
14. The method of claim 9, further comprising generating a report based on the determination.
15. The method of claim 9, further comprising generating a risk score associated with the transaction.
16. The method of claim 15, further comprising storing the risk score in a database.
17. The method of claim 15, wherein a client assigns a threshold level for comparison with the risk score.
18. The method of claim 17, wherein the transaction is determined to be fraudulent when the risk score exceeds the threshold level.
19. The method of claim 15, wherein the risk score is generated in real time.
20. The method of claim 9, further comprising accessing the determination by a client.
21. The method of claim 9, wherein the client may designate whether or not the transaction is fraudulent.
.
22. The method of claim 9, wherein at least one of the one or more factors is static or dynamic.
23. The method of claim 9, wherein a factor comprises a country, region or city associated with the IP address.
24. The method of claim 9, wherein a factor is a proximity of the user in comparison to a purported location of the user associated with the IP address.
25. The method of claim 9, wherein a factor is an address supplied by a client for comparison with an address associated with the IP address.
26. The method of claim 9, wherein a factor is an area code and a telephone number supplied by a client for comparison with an area code and a telephone number stored in a database that is associated with the client.
27. The method of claim 9, wherein a factor is an email address supplied by a client for validation.
28. The method of claim 9, wherein a factor is an access behavior associated with the user based on transaction habits stored in a database that are compared with a current transaction.
29. The method of claim 9, wherein a factor is a frequency in which the transaction is attempted within a predetermined period of time.
30. The method of claim 9, wherein a factor is a velocity with which a single IP address accesses or uses multiple unique identifiers within a specified period of time.
31. The method of claim 9, wherein a client may assign a threshold level for at least one of the one or more factors.
32. The method of claim 9, wherein a client may create one or more user defined factors.
33. The method of claim 9, wherein a client may define constraint rules for at least one of the one or more factors.
34. The method of claim 9, wherein the first access location is determined from a behavior profile associated with the user.
35. The method of claim 9, wherein the first access location is based on the user's last valid access location.
36. The method of claim 9, wherein the second access location and the second access time are the user's current access location and current access time.
37. The method of claim 9, wherein information about the second access location is stored in a behavior profile associated with the user.
38. The method of claim 9, wherein information about the first access location and the second access location is stored in a database.
39. The method of claim 9, wherein a factor comprises a connection type associated with the IP address, where connection type includes dial-up, Integrated Services Digital Network (ISDN), cable modem, Digital Subscriber Line (DSL), Digital Signal 1 (Tl), or Optical Carrier 3 (OC3).
40. The method of claim 9, wherein a factor comprises a connection type stored in a behavior profile associated with the user, where connection type includes dial-up, Integrated Services Digital Network (ISDN), cable modem, Digital Subscriber Line (DSL), Digital Signal 1 (Tl)3 or Optical Carrier 3 (OC3).
41. The method of claim 9, wherein a factor comprises a host type associated with the IP address of the user, where host type includes network end point, network proxy, or network firewall.
42. The method of claim 9, wherein a factor comprises a domain name stored in a behavior profile associated with the user.
43. A method for determining if one or more online transactions are fraudulent, comprising the steps of:
(a) computing a transaction frequency with which the one or more transactions are attempted or executed from an IP address within a predetermined period of time;
(b) determining the host type associated with the IP address; and
(c) executing a function to determine if the one or more transactions are fraudulent, the function having as its input at least the transaction frequency and the host type.
44. The method of claim 43, wherein host type is network end point, network proxy, or network firewall.
45. The method of claim 44, wherein the function generates a risk score and the one or more transactions are determined to be fraudulent when the risk score exceeds a threshold level.
46. The method of claim 45, wherein the function compares the transaction frequency to the host type in order to optimize the risk score.
47. The method of claim 46, wherein for a predetermined transaction frequency, the function generates a relatively higher risk score when the host type is a network end point then when the host type is a network proxy or a network firewall.
48. A method for determining a fraudulent transaction, comprising the steps of: (a) receiving an IP address associated with an Internet user; (b) computing a plurality of factors based on the IP address associated with a transaction conducted by the Internet user; and
(c) determining based on the IP address and the computation whether the transaction is fraudulent.
49. The method of claim 48, further comprising forwarding the determination to a client for further processing by the client.
50. The method of claim 48, further comprising generating a report based on the determination.
51. The method of claim 48, further comprising generating a risk score associated with the transaction.
52. The method of claim 51 , further comprising storing the risk score in a database.
53. The method of claim 51 , wherein a client assigns a threshold level for comparison with the risk score.
54. The method of claim 53, wherein the transaction is determined to be fraudulent when the risk score exceeds the threshold level.
55. The method of claim 51 , wherein the risk score is generated in real time.
56. The method of claim 48, further comprising accessing the determination by a client.
57. The method of claim 56, wherein the client may override the determination that the transaction is fraudulent.
58. The method of claim 48, wherein the client may designate a transaction not determined to be fraudulent as a fraudulent transaction.
59. The method of claim 48, wherein the plurality of factors are static or dynamic.
60. The method of claim 59, wherein the static factors comprise a country, region or city associated with the IP address.
61. The method of claim 59, wherein a dynamic factor is a proximity of the Internet user in comparison to a purported location of the Internet user associated with the IP address.
62. The method of claim 59, wherein a static factor is an address supplied by a client for comparison with the address associated with the IP address.
63. The method of claim 59, wherein a static factor is an area code and telephone number supplied by a client for comparison with an area code and telephone number stored in a database that is associated with the Internet user.
64. The method of claim 59, wherein a static factor is an email address supplied by a client for validation.
65. The method of claim 59, wherein a dynamic factor is an access behavior associated with the Internet user based on transaction habits stored in a database that are compared with the transaction.
66. The method of claim 59, wherein a dynamic factor is a frequency in which the transaction is attempted within a predetermined period of time.
67. The method of claim 59, wherein a client may assign a threshold level for the static and dynamic factors.
68. The method of claim 59, wherein a client may create user defined dynamic factors.
69. The method of claim 59, wherein a dynamic factor is determined by a static factor.
70. The method of claim 48, wherein a client may define constraint rules for the factors.
PCT/US2005/033502 2004-09-17 2005-09-19 Fraud risk advisor WO2006034205A2 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
JP2007532593A JP2008513893A (en) 2004-09-17 2005-09-19 Fraud risk advisor
CA2580731A CA2580731C (en) 2004-09-17 2005-09-19 Fraud risk advisor
EP05794957A EP1810235A4 (en) 2004-09-17 2005-09-19 Fraud risk advisor
AU2005286866A AU2005286866A1 (en) 2004-09-17 2005-09-19 Fraud risk advisor
IL181966A IL181966A (en) 2004-09-17 2007-03-15 Fraud risk advisor
IL248891A IL248891B (en) 2004-09-17 2016-11-10 Fraud risk advisor
IL267487A IL267487A (en) 2004-09-17 2019-06-19 Fraud risk advisor

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US10/943,454 US20060064374A1 (en) 2004-09-17 2004-09-17 Fraud risk advisor
US10/943,454 2004-09-17
US11/209,885 2005-08-23
US11/209,885 US7497374B2 (en) 2004-09-17 2005-08-23 Fraud risk advisor

Publications (2)

Publication Number Publication Date
WO2006034205A2 true WO2006034205A2 (en) 2006-03-30
WO2006034205A3 WO2006034205A3 (en) 2006-06-15

Family

ID=36090578

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2005/033502 WO2006034205A2 (en) 2004-09-17 2005-09-19 Fraud risk advisor

Country Status (7)

Country Link
US (3) US7497374B2 (en)
EP (1) EP1810235A4 (en)
JP (3) JP2008513893A (en)
AU (1) AU2005286866A1 (en)
CA (1) CA2580731C (en)
IL (3) IL181966A (en)
WO (1) WO2006034205A2 (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007125316A2 (en) * 2006-04-25 2007-11-08 Uc Group Ltd. Systems and methods for conducting financial transactions over a network
JP2008090831A (en) * 2006-09-08 2008-04-17 Ihc:Kk Article managing system
JP2009211448A (en) * 2008-03-05 2009-09-17 Hitachi Ltd Product certification system
JP2009535692A (en) * 2006-04-26 2009-10-01 デジタル エンボイ, インコーポレイテッド Smart cookies for fraud analysis
US7941370B2 (en) 2006-04-25 2011-05-10 Uc Group Limited Systems and methods for funding payback requests for financial transactions
US8832809B2 (en) 2011-06-03 2014-09-09 Uc Group Limited Systems and methods for registering a user across multiple websites
WO2017011345A1 (en) * 2015-07-10 2017-01-19 Fair Isaac Corporation Mobile attribute time-series profiling analytics
WO2017095713A1 (en) * 2015-11-30 2017-06-08 Microsoft Technology Licensing, Llc Techniques for detecting unauthorized access to cloud applications based on velocity events
WO2021076738A1 (en) * 2019-10-17 2021-04-22 Saudi Arabian Oil Company Geographical account locking system and method

Families Citing this family (136)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8209246B2 (en) 2001-03-20 2012-06-26 Goldman, Sachs & Co. Proprietary risk management clearinghouse
US7958027B2 (en) * 2001-03-20 2011-06-07 Goldman, Sachs & Co. Systems and methods for managing risk associated with a geo-political area
US8121937B2 (en) 2001-03-20 2012-02-21 Goldman Sachs & Co. Gaming industry risk management clearinghouse
US8140415B2 (en) 2001-03-20 2012-03-20 Goldman Sachs & Co. Automated global risk management
US7313545B2 (en) * 2001-09-07 2007-12-25 First Data Corporation System and method for detecting fraudulent calls
US7386510B2 (en) * 2001-09-07 2008-06-10 First Data Corporation System and method for detecting fraudulent calls
US9412123B2 (en) 2003-07-01 2016-08-09 The 41St Parameter, Inc. Keystroke analysis
US20060010072A1 (en) * 2004-03-02 2006-01-12 Ori Eisen Method and system for identifying users and detecting fraud by use of the Internet
US10999298B2 (en) 2004-03-02 2021-05-04 The 41St Parameter, Inc. Method and system for identifying users and detecting fraud by use of the internet
US7853533B2 (en) * 2004-03-02 2010-12-14 The 41St Parameter, Inc. Method and system for identifying users and detecting fraud by use of the internet
US7992204B2 (en) * 2004-05-02 2011-08-02 Markmonitor, Inc. Enhanced responses to online fraud
US7457823B2 (en) 2004-05-02 2008-11-25 Markmonitor Inc. Methods and systems for analyzing data related to possible online fraud
US8769671B2 (en) * 2004-05-02 2014-07-01 Markmonitor Inc. Online fraud solution
US7913302B2 (en) 2004-05-02 2011-03-22 Markmonitor, Inc. Advanced responses to online fraud
US20070299915A1 (en) * 2004-05-02 2007-12-27 Markmonitor, Inc. Customer-based detection of online fraud
US8041769B2 (en) 2004-05-02 2011-10-18 Markmonitor Inc. Generating phish messages
US7870608B2 (en) 2004-05-02 2011-01-11 Markmonitor, Inc. Early detection and monitoring of online fraud
US9203648B2 (en) * 2004-05-02 2015-12-01 Thomson Reuters Global Resources Online fraud solution
US8442953B2 (en) 2004-07-02 2013-05-14 Goldman, Sachs & Co. Method, system, apparatus, program code and means for determining a redundancy of information
US8996481B2 (en) 2004-07-02 2015-03-31 Goldman, Sach & Co. Method, system, apparatus, program code and means for identifying and extracting information
US8762191B2 (en) 2004-07-02 2014-06-24 Goldman, Sachs & Co. Systems, methods, apparatus, and schema for storing, managing and retrieving information
US8510300B2 (en) 2004-07-02 2013-08-13 Goldman, Sachs & Co. Systems and methods for managing information associated with legal, compliance and regulatory risk
US20080010678A1 (en) * 2004-09-17 2008-01-10 Jeff Burdette Authentication Proxy
US7497374B2 (en) * 2004-09-17 2009-03-03 Digital Envoy, Inc. Fraud risk advisor
US20060248021A1 (en) * 2004-11-22 2006-11-02 Intelius Verification system using public records
US11308477B2 (en) 2005-04-26 2022-04-19 Spriv Llc Method of reducing fraud in on-line transactions
US7653188B2 (en) * 2005-07-20 2010-01-26 Avaya Inc. Telephony extension attack detection, recording, and intelligent prevention
US11818287B2 (en) 2017-10-19 2023-11-14 Spriv Llc Method and system for monitoring and validating electronic transactions
US20070129999A1 (en) * 2005-11-18 2007-06-07 Jie Zhou Fraud detection in web-based advertising
EP2021995A4 (en) * 2005-12-06 2011-06-01 Berman Joel Method and system for scoring quality of traffic to network sites
US11301585B2 (en) 2005-12-16 2022-04-12 The 41St Parameter, Inc. Methods and apparatus for securely displaying digital images
US8938671B2 (en) 2005-12-16 2015-01-20 The 41St Parameter, Inc. Methods and apparatus for securely displaying digital images
US7815106B1 (en) * 2005-12-29 2010-10-19 Verizon Corporate Services Group Inc. Multidimensional transaction fraud detection system and method
US20090260075A1 (en) * 2006-03-28 2009-10-15 Richard Gedge Subject identification
US8151327B2 (en) * 2006-03-31 2012-04-03 The 41St Parameter, Inc. Systems and methods for detection of session tampering and fraud prevention
JP4921875B2 (en) * 2006-07-13 2012-04-25 ヤフー株式会社 Network transaction fraud detection method
US7757943B2 (en) * 2006-08-29 2010-07-20 Metavante Corporation Combined payment/access-control instrument
US8027439B2 (en) 2006-09-18 2011-09-27 Fair Isaac Corporation Self-calibrating fraud detection
US20080086638A1 (en) * 2006-10-06 2008-04-10 Markmonitor Inc. Browser reputation indicators with two-way authentication
US20080103798A1 (en) * 2006-10-25 2008-05-01 Domenikos Steven D Identity Protection
US8359278B2 (en) * 2006-10-25 2013-01-22 IndentityTruth, Inc. Identity protection
US20080168453A1 (en) * 2007-01-09 2008-07-10 Caterpillar Inc. Work prioritization system and method
US8484742B2 (en) 2007-01-19 2013-07-09 Microsoft Corporation Rendered image collection of potentially malicious web pages
US11257080B2 (en) 2007-05-04 2022-02-22 Michael Sasha John Fraud deterrence for secure transactions
US8078515B2 (en) 2007-05-04 2011-12-13 Michael Sasha John Systems and methods for facilitating electronic transactions and deterring fraud
US10853855B2 (en) * 2007-05-20 2020-12-01 Michael Sasha John Systems and methods for automatic and transparent client authentication and online transaction verification
US20080283593A1 (en) * 2007-05-18 2008-11-20 Bank Of America Corporation Compromised Account Detection
US11354667B2 (en) 2007-05-29 2022-06-07 Spriv Llc Method for internet user authentication
US9060012B2 (en) * 2007-09-26 2015-06-16 The 41St Parameter, Inc. Methods and apparatus for detecting fraud with time based computer tags
US20090106846A1 (en) * 2007-10-23 2009-04-23 Identity Rehab Corporation System and method for detection and mitigation of identity theft
US20090182653A1 (en) * 2008-01-07 2009-07-16 Daylight Forensic & Advisory Llc System and method for case management
EP2288987A4 (en) 2008-06-12 2015-04-01 Guardian Analytics Inc Modeling users for fraud detection and analysis
US9542687B2 (en) 2008-06-26 2017-01-10 Visa International Service Association Systems and methods for visual representation of offers
US8312033B1 (en) 2008-06-26 2012-11-13 Experian Marketing Solutions, Inc. Systems and methods for providing an integrated identifier
US9390384B2 (en) * 2008-07-01 2016-07-12 The 41 St Parameter, Inc. Systems and methods of sharing information through a tagless device consortium
US20100005013A1 (en) * 2008-07-03 2010-01-07 Retail Decisions, Inc. Methods and systems for detecting fraudulent transactions in a customer-not-present environment
US8943549B2 (en) * 2008-08-12 2015-01-27 First Data Corporation Methods and systems for online fraud protection
US20100051684A1 (en) * 2008-09-02 2010-03-04 William Lewis-Jennings Powers Fraud geospeed alerting method and system
US20100106611A1 (en) * 2008-10-24 2010-04-29 Uc Group Ltd. Financial transactions systems and methods
US8090648B2 (en) * 2009-03-04 2012-01-03 Fair Isaac Corporation Fraud detection based on efficient frequent-behavior sorted lists
US20100235909A1 (en) * 2009-03-13 2010-09-16 Silver Tail Systems System and Method for Detection of a Change in Behavior in the Use of a Website Through Vector Velocity Analysis
US20100235908A1 (en) * 2009-03-13 2010-09-16 Silver Tail Systems System and Method for Detection of a Change in Behavior in the Use of a Website Through Vector Analysis
US9112850B1 (en) 2009-03-25 2015-08-18 The 41St Parameter, Inc. Systems and methods of sharing information through a tag-based consortium
US20100293090A1 (en) * 2009-05-14 2010-11-18 Domenikos Steven D Systems, methods, and apparatus for determining fraud probability scores and identity health scores
US10290053B2 (en) 2009-06-12 2019-05-14 Guardian Analytics, Inc. Fraud detection and analysis
US8412626B2 (en) * 2009-12-10 2013-04-02 Boku, Inc. Systems and methods to secure transactions via mobile devices
US9652802B1 (en) 2010-03-24 2017-05-16 Consumerinfo.Com, Inc. Indirect monitoring and reporting of a user's credit data
US11792314B2 (en) 2010-03-28 2023-10-17 Spriv Llc Methods for acquiring an internet user's consent to be located and for authenticating the location information
US8548857B2 (en) 2010-07-10 2013-10-01 William Jennings STEVISON Method and system for detection of credit card fraud
WO2012054646A2 (en) 2010-10-19 2012-04-26 The 41St Parameter, Inc. Variable risk engine
US9147042B1 (en) 2010-11-22 2015-09-29 Experian Information Solutions, Inc. Systems and methods for data verification
US8725644B2 (en) * 2011-01-28 2014-05-13 The Active Network, Inc. Secure online transaction processing
EP2676197B1 (en) 2011-02-18 2018-11-28 CSidentity Corporation System and methods for identifying compromised personally identifiable information on the internet
JP5541215B2 (en) * 2011-03-31 2014-07-09 ダイキン工業株式会社 Unauthorized use detection system
US9665854B1 (en) 2011-06-16 2017-05-30 Consumerinfo.Com, Inc. Authentication alerts
US8726379B1 (en) 2011-07-15 2014-05-13 Norse Corporation Systems and methods for dynamic protection from electronic attacks
US9083733B2 (en) 2011-08-01 2015-07-14 Visicom Media Inc. Anti-phishing domain advisor and method thereof
US8819793B2 (en) 2011-09-20 2014-08-26 Csidentity Corporation Systems and methods for secure and efficient enrollment into a federation which utilizes a biometric repository
US11030562B1 (en) 2011-10-31 2021-06-08 Consumerinfo.Com, Inc. Pre-data breach monitoring
US10754913B2 (en) 2011-11-15 2020-08-25 Tapad, Inc. System and method for analyzing user device information
JP2013109736A (en) * 2011-11-24 2013-06-06 Katsuyoshi Nagashima Identity confirmation device, identity confirmation system, identity confirmation method for the same system, and computer program
US9633201B1 (en) 2012-03-01 2017-04-25 The 41St Parameter, Inc. Methods and systems for fraud containment
US9521551B2 (en) 2012-03-22 2016-12-13 The 41St Parameter, Inc. Methods and systems for persistent cross-application mobile device identification
CN103457923A (en) * 2012-06-05 2013-12-18 阿里巴巴集团控股有限公司 Method, device and system for controlling different-place login
EP2880619A1 (en) 2012-08-02 2015-06-10 The 41st Parameter, Inc. Systems and methods for accessing records via derivative locators
WO2014078569A1 (en) 2012-11-14 2014-05-22 The 41St Parameter, Inc. Systems and methods of global identification
US9146969B2 (en) * 2012-11-26 2015-09-29 The Boeing Company System and method of reduction of irrelevant information during search
US20140258169A1 (en) * 2013-03-05 2014-09-11 Bental Wong Method and system for automated verification of customer reviews
US8812387B1 (en) 2013-03-14 2014-08-19 Csidentity Corporation System and method for identifying related credit inquiries
US9633322B1 (en) 2013-03-15 2017-04-25 Consumerinfo.Com, Inc. Adjustment of knowledge-based authentication
US10664936B2 (en) 2013-03-15 2020-05-26 Csidentity Corporation Authentication systems and methods for on-demand products
US9887983B2 (en) 2013-10-29 2018-02-06 Nok Nok Labs, Inc. Apparatus and method for implementing composite authenticators
US10706132B2 (en) * 2013-03-22 2020-07-07 Nok Nok Labs, Inc. System and method for adaptive user authentication
US10270748B2 (en) 2013-03-22 2019-04-23 Nok Nok Labs, Inc. Advanced authentication techniques and applications
CA2811733A1 (en) * 2013-04-02 2014-10-02 Ontario Lottery And Gaming Corporation System and method for retailer risk profiling
US9721147B1 (en) 2013-05-23 2017-08-01 Consumerinfo.Com, Inc. Digital identity
CN103279869A (en) * 2013-05-24 2013-09-04 北京京东尚科信息技术有限公司 Method and device for determining information treatment targets
US20140379339A1 (en) * 2013-06-20 2014-12-25 Bank Of America Corporation Utilizing voice biometrics
US10902327B1 (en) 2013-08-30 2021-01-26 The 41St Parameter, Inc. System and method for device identification and uniqueness
JP2015130013A (en) * 2014-01-06 2015-07-16 テンソル・コンサルティング株式会社 Transaction processing system, method and program
US9521164B1 (en) * 2014-01-15 2016-12-13 Frank Angiolelli Computerized system and method for detecting fraudulent or malicious enterprises
US10373240B1 (en) 2014-04-25 2019-08-06 Csidentity Corporation Systems, methods and computer-program products for eligibility verification
US20150310442A1 (en) * 2014-04-25 2015-10-29 Mastercard International Incorporated Methods, systems and computer readable media for determining criminal propensities in a geographic location based on purchase card transaction data
JP5731726B1 (en) * 2014-06-26 2015-06-10 楽天株式会社 Information processing apparatus, information processing method, and information processing program
US9118714B1 (en) * 2014-07-23 2015-08-25 Lookingglass Cyber Solutions, Inc. Apparatuses, methods and systems for a cyber threat visualization and editing user interface
US9942250B2 (en) 2014-08-06 2018-04-10 Norse Networks, Inc. Network appliance for dynamic protection from risky network activities
US10091312B1 (en) 2014-10-14 2018-10-02 The 41St Parameter, Inc. Data structures for intelligently resolving deterministic and probabilistic device identifiers to device profiles and/or groups
US10339527B1 (en) 2014-10-31 2019-07-02 Experian Information Solutions, Inc. System and architecture for electronic fraud detection
US10832298B2 (en) * 2015-09-22 2020-11-10 Raise Marketplace Inc. Method and apparatus for a digital exchange item marketplace network including buyer, seller, and device verification
USD814494S1 (en) 2015-03-02 2018-04-03 Norse Networks, Inc. Computer display panel with an icon image of a live electronic threat intelligence visualization interface
USD810775S1 (en) 2015-04-21 2018-02-20 Norse Networks, Inc. Computer display panel with a graphical live electronic threat intelligence visualization interface
US9923914B2 (en) * 2015-06-30 2018-03-20 Norse Networks, Inc. Systems and platforms for intelligently monitoring risky network activities
US11151468B1 (en) 2015-07-02 2021-10-19 Experian Information Solutions, Inc. Behavior analysis using distributed representations of event data
US10531228B2 (en) * 2015-12-16 2020-01-07 Sk Planet Co., Ltd. Approaching user detection, user authentication and location registration method and apparatus based on RF fingerprint
JP6275108B2 (en) * 2015-12-28 2018-02-07 デジタル・アドバタイジング・コンソーシアム株式会社 Information processing apparatus, information processing method, and program
US10373162B2 (en) * 2016-01-25 2019-08-06 Mastercard International Incorporated Systems and methods for validating data elements of a transmitted computer message
US11423414B2 (en) * 2016-03-18 2022-08-23 Fair Isaac Corporation Advanced learning system for detection and prevention of money laundering
CN109564610A (en) * 2016-06-02 2019-04-02 瓦罗尼斯系统有限公司 Audit, which logs in, to be strengthened
US10769635B2 (en) 2016-08-05 2020-09-08 Nok Nok Labs, Inc. Authentication techniques including speech and/or lip movement analysis
US10637853B2 (en) 2016-08-05 2020-04-28 Nok Nok Labs, Inc. Authentication techniques including speech and/or lip movement analysis
US10999320B2 (en) * 2016-11-16 2021-05-04 Microsoft Technology Licensing, Llc Velocity event identification system
US10523643B1 (en) 2017-05-01 2019-12-31 Wells Fargo Bank, N.A. Systems and methods for enhanced security based on user vulnerability
US11062316B2 (en) * 2017-08-14 2021-07-13 Feedzai—Consultadoria e Inovaçâo Tecnológica, S.A. Computer memory management during real-time fraudulent transaction analysis
US10699028B1 (en) 2017-09-28 2020-06-30 Csidentity Corporation Identity security architecture systems and methods
US10896472B1 (en) 2017-11-14 2021-01-19 Csidentity Corporation Security and identity verification system and architecture
US11868995B2 (en) 2017-11-27 2024-01-09 Nok Nok Labs, Inc. Extending a secure key storage for transaction confirmation and cryptocurrency
US11831409B2 (en) 2018-01-12 2023-11-28 Nok Nok Labs, Inc. System and method for binding verifiable claims
US10893053B2 (en) * 2018-03-13 2021-01-12 Roblox Corporation Preventing unauthorized account access based on location and time
US10911234B2 (en) 2018-06-22 2021-02-02 Experian Information Solutions, Inc. System and method for a token gateway environment
US11164206B2 (en) * 2018-11-16 2021-11-02 Comenity Llc Automatically aggregating, evaluating, and providing a contextually relevant offer
JP7151870B2 (en) * 2019-03-19 2022-10-12 日本電気株式会社 Score distribution conversion device, score distribution conversion method, and score distribution conversion program
US11792024B2 (en) 2019-03-29 2023-10-17 Nok Nok Labs, Inc. System and method for efficient challenge-response authentication
CA3150122A1 (en) 2019-10-01 2021-04-08 Mastercard Technologies Canada ULC Feature encoding in online application origination (oao) service for a fraud prevention system
JP7323436B2 (en) * 2019-11-21 2023-08-08 株式会社日立製作所 Multiple media use system and multiple media use method
CN111372242B (en) * 2020-01-16 2023-10-03 深圳市卡牛科技有限公司 Fraud identification method, fraud identification device, server and storage medium
US20240005329A1 (en) * 2020-11-10 2024-01-04 Nippon Telegraph And Telephone Corporation Determination apparatus, determination method and program

Family Cites Families (122)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4714918A (en) * 1984-04-30 1987-12-22 International Business Machines Corporation Window view control
US5042032A (en) 1989-06-23 1991-08-20 At&T Bell Laboratories Packet route scheduling in a packet cross connect switch system for periodic and statistical packets
US5115433A (en) 1989-07-18 1992-05-19 Metricom, Inc. Method and system for routing packets in a packet communication network
US4939726A (en) 1989-07-18 1990-07-03 Metricom, Inc. Method for routing packets in a packet communication network
US5557518A (en) 1994-04-28 1996-09-17 Citibank, N.A. Trusted agents for open electronic commerce
US5819226A (en) 1992-09-08 1998-10-06 Hnc Software Inc. Fraud detection using predictive modeling
US5490252A (en) 1992-09-30 1996-02-06 Bay Networks Group, Inc. System having central processor for transmitting generic packets to another processor to be altered and transmitting altered packets back to central processor for routing
JPH0746661A (en) * 1993-07-27 1995-02-14 Nec Corp System and equipment for mobile radio communication
US5488608A (en) 1994-04-14 1996-01-30 Metricom, Inc. Method and system for routing packets in a packet communication network using locally constructed routing tables
US5657389A (en) * 1995-05-08 1997-08-12 Image Data, Llc Positive identification system and method
US5719918A (en) * 1995-07-06 1998-02-17 Newnet, Inc. Short message transaction handling system
US5878126A (en) 1995-12-11 1999-03-02 Bellsouth Corporation Method for routing a call to a destination based on range identifiers for geographic area assignments
US5809118A (en) 1996-05-30 1998-09-15 Softell System and method for triggering actions at a host computer by telephone
US5862339A (en) 1996-07-09 1999-01-19 Webtv Networks, Inc. Client connects to an internet access provider using algorithm downloaded from a central server based upon client's desired criteria after disconnected from the server
US6837436B2 (en) 1996-09-05 2005-01-04 Symbol Technologies, Inc. Consumer interactive shopping system
US5948061A (en) 1996-10-29 1999-09-07 Double Click, Inc. Method of delivery, targeting, and measuring advertising over networks
US6012088A (en) 1996-12-10 2000-01-04 International Business Machines Corporation Automatic configuration for internet access device
US6421726B1 (en) 1997-03-14 2002-07-16 Akamai Technologies, Inc. System and method for selection and retrieval of diverse types of video data on a computer network
US7020622B1 (en) 1997-06-10 2006-03-28 Linkshare Corporation Transaction tracking, managing, assessment, and auditing data processing system and network
US6029154A (en) 1997-07-28 2000-02-22 Internet Commerce Services Corporation Method and system for detecting fraud in a credit card transaction over the internet
US7403922B1 (en) * 1997-07-28 2008-07-22 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
JP3296261B2 (en) 1997-09-02 2002-06-24 セイコーエプソン株式会社 Terminal device, information providing system, information obtaining method, information providing method, and recording medium
US6035332A (en) 1997-10-06 2000-03-07 Ncr Corporation Method for monitoring user interactions with web pages from web server using data and command lists for maintaining information visited and issued by participants
AU1940199A (en) 1997-12-24 1999-07-19 America Online, Inc. Asynchronous data protocol
US6108642A (en) 1998-02-02 2000-08-22 Network Sciences Company, Inc. Device for selectively blocking remote purchase requests
US6185598B1 (en) 1998-02-10 2001-02-06 Digital Island, Inc. Optimized network resource location
US6122624A (en) 1998-05-28 2000-09-19 Automated Transaction Corp. System and method for enhanced fraud detection in automated electronic purchases
US6327574B1 (en) 1998-07-07 2001-12-04 Encirq Corporation Hierarchical models of consumer attributes for targeting content in a privacy-preserving manner
JP2000040064A (en) * 1998-07-24 2000-02-08 Ntt Data Corp Certifying system of network access
US6859791B1 (en) 1998-08-13 2005-02-22 International Business Machines Corporation Method for determining internet users geographic region
US6205480B1 (en) 1998-08-19 2001-03-20 Computer Associates Think, Inc. System and method for web server user authentication
JP2000092567A (en) * 1998-09-07 2000-03-31 Toyota Motor Corp Authenticating device for terminal equipment
US6130890A (en) 1998-09-11 2000-10-10 Digital Island, Inc. Method and system for optimizing routing of data packets
US6715080B1 (en) 1998-10-01 2004-03-30 Unisys Corporation Making CGI variables and cookie information available to an OLTP system
US6151631A (en) 1998-10-15 2000-11-21 Liquid Audio Inc. Territorial determination of remote computer location in a wide area network for conditional delivery of digitized products
US6374359B1 (en) 1998-11-19 2002-04-16 International Business Machines Corporation Dynamic use and validation of HTTP cookies for authentication
US6324585B1 (en) 1998-11-19 2001-11-27 Cisco Technology, Inc. Method and apparatus for domain name service request resolution
US7058597B1 (en) 1998-12-04 2006-06-06 Digital River, Inc. Apparatus and method for adaptive fraud screening for electronic commerce transactions
US6338082B1 (en) 1999-03-22 2002-01-08 Eric Schneider Method, product, and apparatus for requesting a network resource
US7685311B2 (en) 1999-05-03 2010-03-23 Digital Envoy, Inc. Geo-intelligent traffic reporter
US6757740B1 (en) 1999-05-03 2004-06-29 Digital Envoy, Inc. Systems and methods for determining collecting and using geographic locations of internet users
US6102406A (en) 1999-06-07 2000-08-15 Steven A. Miles Internet-based advertising scheme employing scavenger hunt metaphor
US6275470B1 (en) 1999-06-18 2001-08-14 Digital Island, Inc. On-demand overlay routing for computer-based communication networks
US6584505B1 (en) 1999-07-08 2003-06-24 Microsoft Corporation Authenticating access to a network server without communicating login information through the network server
US7885899B1 (en) 2000-02-08 2011-02-08 Ipass Inc. System and method for secure network purchasing
US6697824B1 (en) 1999-08-31 2004-02-24 Accenture Llp Relationship management in an E-commerce application framework
US6734886B1 (en) * 1999-12-21 2004-05-11 Personalpath Systems, Inc. Method of customizing a browsing experience on a world-wide-web site
US7167844B1 (en) 1999-12-22 2007-01-23 Accenture Llp Electronic menu document creator in a virtual financial environment
US6868525B1 (en) 2000-02-01 2005-03-15 Alberti Anemometer Llc Computer graphic display visualization system and method
US6954799B2 (en) 2000-02-01 2005-10-11 Charles Schwab & Co., Inc. Method and apparatus for integrating distributed shared services system
US7203315B1 (en) 2000-02-22 2007-04-10 Paul Owen Livesay Methods and apparatus for providing user anonymity in online transactions
EP1132797A3 (en) 2000-03-08 2005-11-23 Aurora Wireless Technologies, Ltd. Method for securing user identification in on-line transaction systems
US6973489B1 (en) * 2000-03-21 2005-12-06 Mercury Interactive Corporation Server monitoring virtual points of presence
US7493655B2 (en) 2000-03-22 2009-02-17 Comscore Networks, Inc. Systems for and methods of placing user identification in the header of data packets usable in user demographic reporting and collecting usage data
WO2001073652A1 (en) 2000-03-24 2001-10-04 Access Business Group International Llc System and method for detecting fraudulent transactions
JP2001282643A (en) * 2000-03-29 2001-10-12 Osaka Gas Co Ltd Access check system for remote access system
US6665715B1 (en) 2000-04-03 2003-12-16 Infosplit Inc Method and systems for locating geographical locations of online users
US20010051876A1 (en) 2000-04-03 2001-12-13 Seigel Ronald E. System and method for personalizing, customizing and distributing geographically distinctive products and travel information over the internet
US6684250B2 (en) * 2000-04-03 2004-01-27 Quova, Inc. Method and apparatus for estimating a geographic location of a networked entity
WO2001077868A2 (en) 2000-04-05 2001-10-18 Ruesch International, Inc. System, method and apparatus for international financial transactions
US7263506B2 (en) 2000-04-06 2007-08-28 Fair Isaac Corporation Identification and management of fraudulent credit/debit card purchases at merchant ecommerce sites
CA2305249A1 (en) 2000-04-14 2001-10-14 Branko Sarcanin Virtual safe
US6965881B1 (en) 2000-04-24 2005-11-15 Intel Corporation Digital credential usage reporting
US7072984B1 (en) 2000-04-26 2006-07-04 Novarra, Inc. System and method for accessing customized information over the internet using a browser for a plurality of electronic devices
CN1313897C (en) * 2000-05-19 2007-05-02 网景通信公司 Adaptive multi-tier authentication system
US6983379B1 (en) 2000-06-30 2006-01-03 Hitwise Pty. Ltd. Method and system for monitoring online behavior at a remote site and creating online behavior profiles
AU7182701A (en) 2000-07-06 2002-01-21 David Paul Felsher Information record infrastructure, system and method
US20020016831A1 (en) 2000-08-07 2002-02-07 Vidius Inc. Apparatus and method for locating of an internet user
JP2002064861A (en) * 2000-08-14 2002-02-28 Pioneer Electronic Corp User authentication system
AUPQ966400A0 (en) 2000-08-24 2000-09-21 Xemplex Pty Ltd Method of graphically defining a formula
US7155508B2 (en) 2000-09-01 2006-12-26 Yodlee.Com, Inc. Target information generation and ad server
WO2002023452A1 (en) 2000-09-12 2002-03-21 American Express Travel Related Services Company, Inc. Microchip-enabled online transaction system
AU2002228700A1 (en) * 2000-11-02 2002-05-15 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
US6839692B2 (en) 2000-12-01 2005-01-04 Benedor Corporation Method and apparatus to provide secure purchase transactions over a computer network
US20020169669A1 (en) 2001-03-09 2002-11-14 Stetson Samantha H. Method and apparatus for serving a message in conjuction with an advertisement for display on a world wide web page
JP2002278973A (en) 2001-03-16 2002-09-27 Matsushita Electric Ind Co Ltd Position information managing device and position information reference terminal
US7289522B2 (en) 2001-03-20 2007-10-30 Verizon Business Global Llc Shared dedicated access line (DAL) gateway routing discrimination
JP2002358417A (en) * 2001-03-30 2002-12-13 Mizuho Corporate Bank Ltd Method, system, and program for banking processing
US7865427B2 (en) 2001-05-30 2011-01-04 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
US7272575B2 (en) 2001-07-13 2007-09-18 Lilly Mae Vega Method and system for facilitating service transactions
US7165105B2 (en) 2001-07-16 2007-01-16 Netgenesis Corporation System and method for logical view analysis and visualization of user behavior in a distributed computer network
US6623439B2 (en) 2001-08-31 2003-09-23 Dj Orthopedics, Llc Contoured knee brace frame
US6986160B1 (en) 2001-08-31 2006-01-10 Mcafee, Inc. Security scanning system and method utilizing generic IP addresses
US6851062B2 (en) 2001-09-27 2005-02-01 International Business Machines Corporation System and method for managing denial of service attacks
PL350218A1 (en) * 2001-10-20 2003-04-22 Wojciech Wojciechowski Method of and system for providing extra security of payments effected by means of cheque cards
US6546493B1 (en) 2001-11-30 2003-04-08 Networks Associates Technology, Inc. System, method and computer program product for risk assessment scanning based on detected anomalous events
AU2002358564A1 (en) 2001-12-21 2003-07-09 International Business Machines Corporation Method and system for secure handling of electronic business transactions on the internet
US7843923B2 (en) * 2002-01-08 2010-11-30 Verizon Services Corp. Methods and apparatus for determining the port and/or physical location of an IP device and for using that information
US6745333B1 (en) 2002-01-31 2004-06-01 3Com Corporation Method for detecting unauthorized network access by having a NIC monitor for packets purporting to be from itself
US7185085B2 (en) 2002-02-27 2007-02-27 Webtrends, Inc. On-line web traffic sampling
US20030172036A1 (en) * 2002-03-05 2003-09-11 Idan Feigenbaum Online financial transaction veracity assurance mechanism
FR2837960B1 (en) * 2002-03-28 2004-07-09 Oberthur Card Syst Sa SECURE TRANSACTIONAL ELECTRONIC ENTITY BY MEASURING TIME
AUPS169002A0 (en) * 2002-04-11 2002-05-16 Tune, Andrew Dominic An information storage system
JP2003348270A (en) * 2002-05-22 2003-12-05 Konica Minolta Holdings Inc Apparatus, method and system for image forming
JP2004030286A (en) * 2002-06-26 2004-01-29 Ntt Data Corp Intrusion detection system and intrusion detection program
JP2004118456A (en) * 2002-09-25 2004-04-15 Japan Science & Technology Corp Authentication system of mobile terminal using position information
US20060146820A1 (en) 2002-11-26 2006-07-06 Robert Friedman Geo-intelligent traffic manager
US7725562B2 (en) 2002-12-31 2010-05-25 International Business Machines Corporation Method and system for user enrollment of user attribute storage in a federated environment
US7143095B2 (en) * 2002-12-31 2006-11-28 American Express Travel Related Services Company, Inc. Method and system for implementing and managing an enterprise identity management for distributed security
JP2004258845A (en) * 2003-02-25 2004-09-16 Ntt Data Systems Corp Personal identification device, behavior record method and transportation expense adjustment method
US20040199462A1 (en) 2003-04-02 2004-10-07 Ed Starrs Fraud control method and system for network transactions
US8082210B2 (en) * 2003-04-29 2011-12-20 The Western Union Company Authentication for online money transfers
US20050033641A1 (en) 2003-08-05 2005-02-10 Vikas Jha System, method and computer program product for presenting directed advertising to a user via a network
US7172634B2 (en) * 2003-08-25 2007-02-06 Eastman Chemical Company Ethylenically-unsaturated blue anthraquinone dyes
CN101073219A (en) * 2003-09-12 2007-11-14 Rsa安全公司 System and method for risk based authentication
US20050071417A1 (en) 2003-09-29 2005-03-31 Jeffrey Taylor Method and apparatus for geolocation of a network user
US20050076230A1 (en) 2003-10-02 2005-04-07 George Redenbaugh Fraud tracking cookie
US20050108102A1 (en) 2003-11-17 2005-05-19 Richard York Method, apparatus, and system for verifying incoming orders
WO2005053271A2 (en) * 2003-11-24 2005-06-09 America Online, Inc. Systems and methods for authenticated communications
US7373524B2 (en) 2004-02-24 2008-05-13 Covelight Systems, Inc. Methods, systems and computer program products for monitoring user behavior for a server application
US20060010072A1 (en) 2004-03-02 2006-01-12 Ori Eisen Method and system for identifying users and detecting fraud by use of the Internet
US20070067297A1 (en) 2004-04-30 2007-03-22 Kublickis Peter J System and methods for a micropayment-enabled marketplace with permission-based, self-service, precision-targeted delivery of advertising, entertainment and informational content and relationship marketing to anonymous internet users
US7225468B2 (en) 2004-05-07 2007-05-29 Digital Security Networks, Llc Methods and apparatus for computer network security using intrusion detection and prevention
US7634803B2 (en) 2004-06-30 2009-12-15 International Business Machines Corporation Method and apparatus for identifying purpose and behavior of run time security objects using an extensible token framework
US7808925B2 (en) 2004-09-10 2010-10-05 Digital Envoy, Inc. Methods and systems for determining reverse DNS entries
US7543740B2 (en) 2004-09-17 2009-06-09 Digital Envoy, Inc. Fraud analyst smart cookie
US20060064374A1 (en) * 2004-09-17 2006-03-23 David Helsper Fraud risk advisor
US20080010678A1 (en) * 2004-09-17 2008-01-10 Jeff Burdette Authentication Proxy
US7497374B2 (en) * 2004-09-17 2009-03-03 Digital Envoy, Inc. Fraud risk advisor
CA2606326A1 (en) 2005-04-29 2006-11-09 Bharosa Inc. System and method for fraud monitoring, detection, and tiered user authentication
US20070174082A1 (en) * 2005-12-12 2007-07-26 Sapphire Mobile Systems, Inc. Payment authorization using location data
US20080208760A1 (en) * 2007-02-26 2008-08-28 14 Commerce Inc. Method and system for verifying an electronic transaction

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of EP1810235A4 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8099329B2 (en) 2006-04-25 2012-01-17 Uc Group Limited Systems and methods for determining taxes owed for financial transactions conducted over a network
WO2007125316A3 (en) * 2006-04-25 2008-04-10 Uc Group Ltd Systems and methods for conducting financial transactions over a network
WO2007125316A2 (en) * 2006-04-25 2007-11-08 Uc Group Ltd. Systems and methods for conducting financial transactions over a network
US7941370B2 (en) 2006-04-25 2011-05-10 Uc Group Limited Systems and methods for funding payback requests for financial transactions
JP2009535692A (en) * 2006-04-26 2009-10-01 デジタル エンボイ, インコーポレイテッド Smart cookies for fraud analysis
JP2008090831A (en) * 2006-09-08 2008-04-17 Ihc:Kk Article managing system
JP2009211448A (en) * 2008-03-05 2009-09-17 Hitachi Ltd Product certification system
US8832809B2 (en) 2011-06-03 2014-09-09 Uc Group Limited Systems and methods for registering a user across multiple websites
WO2017011345A1 (en) * 2015-07-10 2017-01-19 Fair Isaac Corporation Mobile attribute time-series profiling analytics
WO2017095713A1 (en) * 2015-11-30 2017-06-08 Microsoft Technology Licensing, Llc Techniques for detecting unauthorized access to cloud applications based on velocity events
US10063554B2 (en) 2015-11-30 2018-08-28 Microsoft Technology Licensing, Llc. Techniques for detecting unauthorized access to cloud applications based on velocity events
US10523676B2 (en) 2015-11-30 2019-12-31 Microsoft Technology Licensing, Llc. Techniques for detecting unauthorized access to cloud applications based on velocity events
WO2021076738A1 (en) * 2019-10-17 2021-04-22 Saudi Arabian Oil Company Geographical account locking system and method

Also Published As

Publication number Publication date
US7438226B2 (en) 2008-10-21
US7708200B2 (en) 2010-05-04
JP5793629B2 (en) 2015-10-14
IL248891A0 (en) 2017-01-31
JP2015092404A (en) 2015-05-14
WO2006034205A3 (en) 2006-06-15
US7497374B2 (en) 2009-03-03
IL181966A (en) 2017-01-31
US20060287902A1 (en) 2006-12-21
IL181966A0 (en) 2008-04-13
JP2013145591A (en) 2013-07-25
US20060149580A1 (en) 2006-07-06
EP1810235A4 (en) 2009-07-08
CA2580731A1 (en) 2006-03-30
US20060282285A1 (en) 2006-12-14
AU2005286866A1 (en) 2006-03-30
EP1810235A2 (en) 2007-07-25
IL267487A (en) 2019-07-31
CA2580731C (en) 2019-01-15
IL248891B (en) 2019-07-31
JP2008513893A (en) 2008-05-01

Similar Documents

Publication Publication Date Title
US7708200B2 (en) Fraud risk advisor
US7673793B2 (en) Fraud analyst smart cookie
US20080010678A1 (en) Authentication Proxy
US20060064374A1 (en) Fraud risk advisor
CA2985028C (en) Gating decision system and methods for determining whether to allow material implications to result from online activities
US20050086166A1 (en) Systems and methods for fraud management in relation to stored value cards
US20130346311A1 (en) Method and System For Data Security Utilizing User Behavior and Device Identification
US8666829B1 (en) Detecting fraudulent event listings
AU2011265479B2 (en) Fraud risk advisor
CN112581291B (en) Risk assessment change detection method, apparatus, device and storage medium
CN115689567A (en) Risk control method, apparatus, device, medium, and program product

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

WWE Wipo information: entry into national phase

Ref document number: 181966

Country of ref document: IL

Ref document number: 2007532593

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2580731

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2005286866

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2005794957

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2005286866

Country of ref document: AU

Date of ref document: 20050919

Kind code of ref document: A

WWP Wipo information: published in national office

Ref document number: 2005286866

Country of ref document: AU

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWP Wipo information: published in national office

Ref document number: 2005794957

Country of ref document: EP

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
WWE Wipo information: entry into national phase

Ref document number: 248891

Country of ref document: IL