This invention relates generally to authentication of financial account transactions (including non-monetary transactions or activities such as online banking logins) and, more specifically, to computerized authentication of transactions.
Financial fraud detection systems often presume that there is increased risk when a transaction on a customer's account occurs far from home. Thus, when customers of financial institutions travel, it is common for their attempted financial transactions while on the road to be declined. The frequency of these declined transactions has been a chronic problem for the financial industry. A common characteristic of compromised financial instruments is having a transaction far from home take place on the account. However, more often than not, distant transactions are legitimate. When organizations frequently decline these transactions, they lose not only their reputation as a dependable financial institution, but also lose significant revenue from lost fees related to the declined transactions. New authentication solutions have been introduced such as out-of-wallet questions, Chip and PIN, and Secure Code. However, easy and convenient authentication of customers continues to be elusive. Furthermore, these solutions can be enormously expensive. Additionally, some potential users have considered them to be too expensive to implement. For example, banks in the United States have elected to forego Chip and PIN as an anti-fraud solution for credit and debit cards. Additionally, many solutions such as out-of-wallet questions are cumbersome and intrusive to the customer.
Preferred and alternative examples of the present invention are described in detail below with reference to the following drawings:
Systems and methods for financial transaction authentication using travel-related information are disclosed herein. Systems and methods in accordance with an embodiment of the invention enhance existing financial transaction authentication solutions by analyzing travel-related purchase transactions for indications of future travel. When a bank normally would have flagged a distant-from-home transaction as risky, travel-related information can dramatically enhance the true understanding of the transaction risk, thereby ensuring better customer quality of service, increased authorizations and decreased false positive fraud indications.
Authentication using travel-related information provides financial institutions, processors and associations a new tool to increase approved transactions. From the resulting decreased fraud review workload in fraud operations centers, related organizations can transfer the new review capacity to finding additional fraudulent activities. To accomplish this, travel-related information is used that pertains to previously purchased travel-related transactions to identify the likelihood of future distant-from-home locations and timeframes of the bank customer. When a transaction occurs near locations that could be anticipated by an earlier transportation purchase by the bank customer, the transaction can be deemed less risky than if it were not known that the customer was going to be traveling to that location. The precise level of risk is determined by offline statistical modeling of variables generated from historic transaction data along with fraud results data. A statistical regression analysis or neural network modeling technique may be used, for example.
Financial institutions such as JPMorgan Chase & Co. (New York, N.Y. USA) and Citibank (New York, N.Y. USA), card associations such as Visa Inc. (San Francisco, Calif. USA) and MasterCard Worldwide (Harrison, N.Y. USA), processors such as Fiserv, Inc. (Brookfield, Wis. USA) and Total System Services, Inc. (TSYS) (Columbus, Ga. USA), and payment networks such as Automated Clearing House (ACH) and PayPal (San Jose, Calif. USA), rely on a combination of tools to attempt to authenticate financial transactions. Authentication using travel-related information strengthens current investments in authentication technology. For example, a currently installed fraud detection system may indicate that a Moscow-located transaction for a Houston-based customer looks highly risky. Using travel-related information, the Moscow transaction may be further analyzed by looking for a previous transaction for that customer for an airline-purchase transaction to or near Moscow. That planned-travel knowledge enables authentication solutions to better distinguish legitimate from truly risky distant transactions.
In the example shown, the network 110 facilitates communication between the customer 114 and the travel-related vendor 116, between the point of service 122 and the bank 112, between the merchants 118 and 120 and the bank 112, and between the system 100 and the bank 112. However, in other embodiments, other forms of communication may be used between some or all of these entities. For example, a separate payment processing network may be used for communications between the bank 112 and the point of service 122 and/or between the bank 112 and the merchants 118 and 120. Although a processor, memory, and interface is shown only for the system 100, it should be understood that the bank 112, the customer 114, the travel-related vendor 116, the first merchant 118, the second merchant 120, and the point of service 122 operate and communicate with computerized systems. Additionally, the computerized systems may include a display that allows transaction approval and decline messages to be viewed by a user. For example, a screen may be present at the point of service 122 that shows an approval or decline message or a display on a computerized device such as a mobile phone operated by the customer 114 may show an approval or decline message for transactions performed with the mobile phone.
In an example embodiment, the bank 112 serves as a credit card issuer to the customer 114. The customer 114 uses the credit card to make purchases from the travel-related vendor 116, such as an airline or a travel agent and/or purchases from the first merchant 118 and the second merchant 120. Later, the customer 114 uses the credit card at the point of service 122 which is located in a location that is at least a predetermined distance from the home of the customer 114.
Generally, the system 100 is designed to authenticate transactions where banks are concerned with various types of fraud characterized by (among other things) remote-from-home activity. In an example embodiment, the system has the ability to provide financial transaction authentication for at least the following non-limiting use cases: purchase transactions with a debit or credit card at a physical merchant terminal location; purchase transactions with a debit or credit card at an online merchant; purchase transactions with an alternative payment network such as Paypal at an online merchant; ATM activity with a debit or credit card; online banking related to an account with a debit card or credit card; and mobile banking related to an account with a debit card or credit card.
Later, at a block 214, during the travel-related to the earlier plane ticket purchase, the customer performs a financial transaction at a point-of-service such as the point of service 122 (e.g., merchant POS, ATM, PC, Mobile Phone) far from home. Then, at a block 216, the point-of-service device sends an authorization request to the financial institution such as the bank 112 for approval. Next, at a block 218, the bank's legacy fraud system indicates that the remote transaction is high risk and the account is flagged to be blocked. Then, at a block 220, the same authorization request is sent to the travel analysis platform from the bank 112. In some embodiments, the authorization request sent to the travel analysis platform from the bank 112 may differ in some manner from the initial authorization request from the point of service 122 to the bank 112. In some embodiments a merchant can send additional information to the travel analysis program, such as IP address information, purchase information and/or information related to the purchaser like an IP address used. Next, at a block 222, the travel analysis platform analyzes historic transaction detail for the account including the airline ticket purchase relating to planned travel that matches the geographic area and date of the new transaction. In an example embodiment, the processor 102 analyzes information previously stored in the travel-related purchase data store 108 based on programming instructions stored in the memory 104. Then, at a decision block 224, the transaction analysis platform determines whether there is low risk from the new transaction.
If the risk level is determined to be low, a message is sent from the travel analysis platform to the bank 112 to unblock the account at a block 226. In some embodiments, an indicator that corresponds to a level of the risk determined by the system 100 is sent rather than an unblock message. Then, at a block 228, a transaction approval is sent from the bank 112 to the point of service 122 based on the information received at the bank 112 from the system 100.
If the service performs in real time, an authorization response is sent with “Approve.” If the service performs in “one-behind” mode, the current transaction may still be blocked, but subsequent transactions could be approved. If it was determined at the decision block 224 that the risk level is not low, an indication is sent from the system 100 to the bank 112 that the risk level is high at a block 230. Then, at a block 232, a transaction decline is sent from the bank 112 to the point of service 122.
Later, at a block 412, the customer 114 performs a financial transaction at a predetermined distance from their home location. Next, at a block 414, the point-of-service device 122 (e.g., merchant terminal, ATM, PC, Mobile Phone) sends an authorization request to a financial institution such as the bank 112 for approval. Then, at a block 416, a bank's legacy fraud system, which is complemented by the systems and methods disclosed herein, indicates that the remote transaction is high risk and the account is flagged to be blocked. Next, at a block 418, the same authorization request is sent from the bank 112 to the travel analysis platform. In some embodiments, the authorization request sent to the travel analysis platform from the bank 112 may differ in some manner from the initial authorization request from the point of service 122 to the bank 112. Then, at a block 420, the travel analysis platform analyzes historic transaction detail for the account including the travel-related purchase information that matches the geographic area and date of the new transaction. Next, at a decision block 422, the transaction analysis platform determines whether there is low risk from the new transaction.
If risk level is determined to be low, a message is sent from the travel analysis platform to the bank 112 to unblock the account at a block 424. In some embodiments, an indicator that corresponds to a level of the risk determined by the system 100 is sent rather than an unblock message. Then, at a block 426, a transaction approval is sent from the bank 112 to the point of service 122 based on the information received at the bank 112 from the system 100. If the service performs in real time, an authorization response is sent with “Approve.” If the service performs in “one-behind” mode, the current transaction may still be blocked, but subsequent transactions could be approved. If it was determined at the decision block 422 that the risk level is not low, an indication is sent from the system 100 to the bank 112 that the risk level is high at a block 428. Then, at a block 430, a transaction decline is sent from the bank 112 to the point of service 122.
With regard to the methods 200 and 400 described in
Still with respect to the methods 200 and 400, additional factors may also be used in deriving variables. For example, when traveling in the past, whether the customer has visited this particular merchant before, or this particular chain. If so, this may be indicative of current legitimate travel. An additional factor is whether the customer has recently made purchases at merchant types that are highly indicative of pending legitimate travel such as travel services, dry cleaning, pre-paid airport parking, pre-paid car rental, or hotel reservations, for example. This might be determined from analyzing whether the merchant identifiers from purchases are within numeric blocks of merchant identifiers reserved for hotels and car rentals, for example. In other embodiments the system may analyze factors such as seasonality of travel; property ownership, reward card points, and/or previous travel habits.
Additional factors related to airline ticket purchases may also be used. The magnitude of the price for airline ticket purchases may be used, for example. Pricing information may be indicative of distance and also indicative of the time window between when the travel was purchased and when the travel occurs. Other variables related to likely destination location and distance from home may also be used based on what air carrier the travel will be on. For example, Hawaiian Air flies between the contiguous United States to Hawaii and only a few other places. Airlines such as British Air, Aer Lingus, Aeroflot, Air Nippon, and Quantas do not fly domestic U.S. routes. Knowing the air carrier to be used by a legitimate customer can help predict the reasonableness of the locations of purchases made far from the customer's home location.
While the preferred embodiment of the invention has been illustrated and described, as noted above, many changes can be made without departing from the spirit and scope of the invention. For example, additional or fewer steps may be performed in the methods 200 and 400 and/or some of the steps may be performed in a different order or concurrently. Additionally, although the system 100 is shown as being separate from the bank 112, the system 100 may be integrated within the systems of the bank 112 rather than existing as a separate system accessed over a network. Although the method 200 uses card posting information including a travel itinerary and method 400 uses travel-related purchase information without posting information or an itinerary, some embodiments may incorporate aspects of both methods such that both travel itinerary information from card posting data and travel-related purchase information such as purchases from a car rental company could be used. Different or additional travel-related purchase data elements may also be used than those described. Accordingly, the scope of the invention is not limited by the disclosure of the preferred embodiment. Instead, the invention should be determined entirely by reference to the claims that follow.
This application is a continuation of U.S. patent application Ser. No. 13/030,794, filed Feb. 11, 2011, which claims priority to and the benefit of the filing date of U.S. Provisional Patent Application No. 61/306,369 filed Feb. 19, 2010, which are all herein incorporated by reference in their entirity.
Number | Name | Date | Kind |
---|---|---|---|
6494666 | Wu et al. | Dec 2002 | B2 |
6612488 | Suzuki | Sep 2003 | B2 |
6832721 | Fujii | Dec 2004 | B2 |
6868391 | Hultgren | Mar 2005 | B1 |
6913194 | Suzuki | Jul 2005 | B2 |
6948656 | Williams | Sep 2005 | B2 |
7104444 | Suzuki | Sep 2006 | B2 |
7152788 | Williams | Dec 2006 | B2 |
7376431 | Niedermeyer | May 2008 | B2 |
7500607 | Williams | Mar 2009 | B2 |
7503489 | Heffez et al. | Mar 2009 | B2 |
7594605 | Aaron et al. | Sep 2009 | B2 |
7669759 | Zettner | Mar 2010 | B1 |
7684809 | Niedermeyer | Mar 2010 | B2 |
7697942 | Stevens | Apr 2010 | B2 |
7715824 | Zhou | May 2010 | B2 |
7720702 | Fredericks | May 2010 | B2 |
7739129 | Sweetland | Jun 2010 | B2 |
7743981 | Willaims | Jun 2010 | B2 |
7747535 | Mikan et al. | Jun 2010 | B2 |
7752135 | Brown et al. | Jul 2010 | B2 |
7757943 | D'Angelo | Jul 2010 | B2 |
8099368 | Coulter | Jan 2012 | B2 |
8116731 | Buhrrmann et al. | Feb 2012 | B2 |
8135624 | Ramalingam et al. | Mar 2012 | B1 |
8140403 | Ramalingam et al. | Mar 2012 | B2 |
8166068 | Stevens | Apr 2012 | B2 |
8191140 | Cohen | May 2012 | B2 |
8209755 | Cohen | Jun 2012 | B2 |
8255284 | Ramalingam et al. | Aug 2012 | B1 |
8280348 | Snyder et al. | Oct 2012 | B2 |
8285639 | Eden et al. | Oct 2012 | B2 |
8296235 | Hrabosky | Oct 2012 | B2 |
8315947 | Aaron et al. | Nov 2012 | B2 |
8332321 | Bosch | Dec 2012 | B2 |
8341029 | Ramalingam et al. | Dec 2012 | B1 |
8374634 | Dankar et al. | Feb 2013 | B2 |
8401906 | Ruckart | Mar 2013 | B2 |
8588748 | Buhrrman et al. | Nov 2013 | B2 |
8615465 | Boutcher et al. | Dec 2013 | B2 |
8632002 | Boutcher et al. | Jan 2014 | B2 |
20020026416 | Provinse | Feb 2002 | A1 |
20020032661 | Schuba | Mar 2002 | A1 |
20020123938 | Yu | Sep 2002 | A1 |
20030040987 | Hudson | Feb 2003 | A1 |
20030065569 | Danis | Apr 2003 | A1 |
20040167808 | Fredericks | Aug 2004 | A1 |
20050239445 | Karaoguz et al. | Oct 2005 | A1 |
20060131390 | Kim | Jun 2006 | A1 |
20060271552 | McChesney et al. | Nov 2006 | A1 |
20070055785 | Stevens | Mar 2007 | A1 |
20070192249 | Biffle | Aug 2007 | A1 |
20080022400 | Cohen | Jan 2008 | A1 |
20080054065 | D'Angelo | Mar 2008 | A1 |
20080065530 | Talbert | Mar 2008 | A1 |
20080086424 | Jambunathan | Apr 2008 | A1 |
20080110983 | Ashfield | May 2008 | A1 |
20080165060 | Songer et al. | Jul 2008 | A1 |
20080167989 | Conlin | Jul 2008 | A1 |
20080257959 | Oved | Oct 2008 | A1 |
20100023455 | Dispensa et al. | Jan 2010 | A1 |
20110208601 | Ferguson | Aug 2011 | A1 |
20120036073 | Basu | Feb 2012 | A1 |
20120226570 | Kemp | Sep 2012 | A1 |
Number | Date | Country | |
---|---|---|---|
20190279209 A1 | Sep 2019 | US |
Number | Date | Country | |
---|---|---|---|
61306369 | Feb 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13030794 | Feb 2011 | US |
Child | 16368380 | US |