IP Library Granted Patent US 12,450,618
Granted Patent B2
US 12,450,618 · App. 18/636,886 · Granted Oct 21, 2025

Reducing false positives using customer feedback and machine learning

Inventors: Timothy Kramme (Parker, TX); Elizabeth A. Flowers (Bloomington, IL); Reena Batra (Alpharetta, GA); Miriam Valero (Bloomington, IL); Puneit Dua (Bloomington, IL); Shanna L. Phillips (Bloomington, IL); Russell Ruestman (Minonk, IL); Bradley A. Craig (Normal, IL)
Assignee: State Farm Mutual Automobile Insurance Company
G06Q30/0185G06N5/046G06N20/00G06Q20/102G06Q20/20G06Q20/24G06Q20/3224G06Q20/34G06Q20/401G06Q20/4016G06Q20/407G06Q20/409G06Q30/0225G06V30/194G06V30/41G06Q30/0248
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,450,618
App. No.
18/636,886
Granted
Oct 21, 2025
Kind
B2
Abstract

A method of reducing a future amount of electronic fraud alerts includes receiving data detailing a financial transaction, inputting the data into a rules-based engine that generates an electronic fraud alert, transmitting the alert to a mobile device of a customer, and receiving from the mobile device customer feedback indicating that the alert was a false positive or otherwise erroneous. The method also includes inputting the data detailing the financial transaction into a machine learning program trained to (i) determine a reason why the false positive was generated, and (ii) then modify the rules-based engine to account for the reason why the false positive was generated, and to no longer generate electronic fraud alerts based upon (a) fact patterns similar to fact patterns of the financial transaction, or (b) data similar to the data detailing the financial transaction, to facilitate reducing an amount of future false positive fraud alerts.

Claims (64)

1. A computer-implemented method of predicting a fraud classification using fraud classification rules, comprising:

training, by a processor, a machine learning program using training data labeled with fraud classification labels, wherein:

the fraud classification labels identify types of fraud, of a set of different predetermined types of fraud, associated with respective historical transactions;

generating, by the processor, the fraud classification rules using the trained machine learning program; and

predicting, by the processor, and by applying the fraud classification rules to account data associated with a particular financial account, the fraud classification that:

corresponds to a transaction associated with the particular financial account, and

identifies a particular type of fraud, included in the set of different predetermined types of fraud, that is predicted to be associated with the transaction.

2. The computer-implemented method of claim 1 , further comprising:

receiving, by the processor, feedback indicating an accuracy of the fraud classification;

re-training, by the processor, the machine learning program using the feedback; and

updating, by the processor, the fraud classification rules based on the re-training of the machine learning program.

3. The computer-implemented method of claim 1 , wherein training the machine learning program comprises identifying factors, indicated by the training data, that correlate to the types of fraud, associated with the respective historical transactions, identified by the fraud classification labels.

4. The computer-implemented method of claim 3 , further comprising identifying, by the processor, different subsets of the factors that are respectively associated with the types of fraud.

5. The computer-implemented method of claim 3 , further comprising:

determining, by the processor, weights corresponding to the factors associated with the particular type of fraud; and

predicting, by the processor, the fraud classification based at least in part on the weights and instances of the factors that are indicated by the account data.

6. The computer-implemented method of claim 5 , wherein predicting the fraud classification comprises:

determining, by the processor, and based on the weights and the instances of the factors, a fraud classification score associated with the particular type of fraud; and

determining, by the processor, that the fraud classification score exceeds a threshold score.

7. The computer-implemented method of claim 1 , wherein predicting the fraud classification comprises:

predicting, by the processor, a first fraud classification associated with a first type of fraud, the first fraud classification being associated with a first fraud classification score;

predicting, by the processor, a second fraud classification associated with a second type of fraud, the second fraud classification being associated with a second fraud classification score; and

determining, by the processor, the particular type of fraud as one of the first type of fraud or the second type of fraud based on a higher score of the first fraud classification score and the second fraud classification score.

8. The computer-implemented method of claim 1 , wherein the set of different predetermined types of fraud comprises two or more of: counterfeiting, forgery, account takeover, lost card use, stolen card use, skimming, chargeback fraud, application fraud, or a lack of fraud.

9. The computer-implemented method of claim 1 , wherein the fraud classification is predicted in response to an indication of suspect activity associated with at least one of the transaction or the particular financial account.

10. A computer system configured to predict a fraud classification using fraud classification rules, the computer system comprising:

a processor; and

memory storing computer-executable instructions that, when executed by the processor, cause the computer system to:

train a machine learning program using training data labeled with fraud classification labels, wherein:

the fraud classification labels identify types of fraud, of a set of different predetermined types of fraud, associated with respective historical transactions;

generate, using the trained machine learning program, the fraud classification rules; and

predict, by applying the fraud classification rules to account data associated with a particular financial account, the fraud classification that:

corresponds to a transaction associated with the particular financial account, and

identifies a particular type of fraud, included in the set of different predetermined types of fraud, that is predicted to be associated with the transaction.

11. The computer system of claim 10 , wherein the computer-executable instructions further cause the computer system to:

receive feedback indicating an accuracy of the fraud classification;

re-train the machine learning program using the feedback; and

update the fraud classification rules based on re-training of the machine learning program.

12. The computer system of claim 10 , wherein the computer-executable instructions cause the computer system to train the machine learning program by identifying factors, indicated by the training data, that correlate to the types of fraud, associated with the respective historical transactions, identified by the fraud classification labels.

13. The computer system of claim 12 , wherein the computer-executable instructions cause the computer system to:

determine weights corresponding to the factors associated with the particular type of fraud; and

predict the fraud classification based at least in part on the weights and instances of the factors that are indicated by the account data.

14. The computer system of claim 10 , wherein the computer-executable instructions cause the computer system to predict the fraud classification by:

predicting a first fraud classification associated with a first type of fraud, the first fraud classification being associated with a first fraud classification score;

predicting a second fraud classification associated with a second type of fraud, the second fraud classification being associated with a second fraud classification score; and

determining the particular type of fraud as one of the first type of fraud or the second type of fraud based on a higher score of the first fraud classification score and the second fraud classification score.

15. The computer system of claim 10 , wherein the computer-executable instructions cause the computer system to predict the fraud classification in response to an indication of suspect activity associated with at least one of the transaction or the particular financial account.

16. One or more non-transitory computer-readable media storing computer-executable instructions for using fraud classification rules to predict a fraud classification that, when executed by a processor, cause the processor to:

train a machine learning program using training data labeled with fraud classification labels, wherein:

the fraud classification labels identify types of fraud, of a set of different predetermined types of fraud, associated with respective historical transactions;

generate, using the trained machine learning program, the fraud classification rules; and

predict, by applying the fraud classification rules to account data associated with a particular financial account, the fraud classification that:

corresponds to a transaction associated with the particular financial account, and

identifies a particular type of fraud, included in the set of different predetermined types of fraud, that is predicted to be associated with the transaction.

17. The one or more non-transitory computer-readable media of claim 16 , wherein the computer-executable instructions further cause the processor to:

receive feedback indicating an accuracy of the fraud classification;

re-train the machine learning program using the feedback; and

update the fraud classification rules based on re-training of the machine learning program.

18. The one or more non-transitory computer-readable media of claim 16 , wherein the computer-executable instructions cause the processor to train the machine learning program by identifying factors, indicated by the training data, that correlate to the types of fraud, associated with the respective historical transactions, identified by the fraud classification labels.

19. The one or more non-transitory computer-readable media of claim 16 , wherein the computer-executable instructions cause the processor to predict the fraud classification by:

predicting a first fraud classification associated with a first type of fraud, the first fraud classification being associated with a first fraud classification score;

predicting a second fraud classification associated with a second type of fraud, the second fraud classification being associated with a second fraud classification score; and

determining the particular type of fraud as one of the first type of fraud or the second type of fraud based on a higher score of the first fraud classification score and the second fraud classification score.

20. The one or more non-transitory computer-readable media of claim 16 , wherein the computer-executable instructions cause the processor to predict the fraud classification in response to an indication of suspect activity associated with at least one of the transaction or the particular financial account.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 9, 2024
From: KRAMME, TIMOTHY; FLOWERS, ELIZABETH; BATRA, REENA; VALERO, MIRIAM; DUA, PUNEIT; PHILLIPS, SHANNA L.; RUESTMAN, RUSSELL; CRAIG, BRADLEY A.
To: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Reel/Frame 069172/0186 →
Continuity (8)
Continuation 17993758 · Nov 23, 2022
Continuation 17080476 · Oct 26, 2020
Continuation 15465832 · Mar 22, 2017
Provisional Application 62365699 · Jul 22, 2016
Provisional Application 62331530 · May 4, 2016
Provisional Application 62318423 · Apr 5, 2016
Provisional Application 62313196 · Mar 25, 2016
Related Publication 20240265405A1 · Aug 8, 2024
References Cited (137)
US 5748780A · Stolfo · 1998 [cited by applicant]
US 5819226A · Gopinathan et al. · 1998 [cited by applicant]
US 5862183A · Lazaridis et al. · 1999 [cited by applicant]
US 6330546B1 · Gopinathan et al. · 2001 [cited by applicant]
US 6839682B1 · Blume et al. · 2005 [cited by applicant]
US 7458508B1 · Shao et al. · 2008 [cited by applicant]
US 7686214B1 · Shao et al. · 2010 [cited by applicant]
US 7793835B1 · Coggeshall et al. · 2010 [cited by applicant]
US 8073691B2 · Rajakumar · 2011 [cited by applicant]
US 8078515B2 · John · 2011 [cited by applicant]
US 8140418B1 · Casey et al. · 2012 [cited by applicant]
US 8650080B2 · O'Connell et al. · 2014 [cited by applicant]
US 9230280B1 · Maag et al. · 2016 [cited by applicant]
US 9390240B1 · Brisebois · 2016 [cited by examiner]
US 9483765B2 · Sahadevan et al. · 2016 [cited by applicant]
US 9721253B2 · Gideoni et al. · 2017 [cited by applicant]
US 9779403B2 · Ranganath et al. · 2017 [cited by applicant]
US 9858575B2 · Meredith et al. · 2018 [cited by applicant]
US 9916606B2 · Stroh · 2018 [cited by applicant]
US 9947055B1 · Roumeliotis · 2018 [cited by applicant]
US 10013646B2 · Ching · 2018 [cited by applicant]
US 10043071B1 · Wu · 2018 [cited by applicant]
US 10373140B1 · Chang · 2019 [cited by examiner]
US 10565585B2 · Sharan et al. · 2020 [cited by applicant]
US 10949852B1 · Kramme et al. · 2021 [cited by applicant]
US 20020133721A1 · Adjaoute · 2002 [cited by applicant]
US 20020165854A1 · Blayvas et al. · 2002 [cited by applicant]
US 20050097046A1 · Singfield · 2005 [cited by applicant]
US 20050154676A1 · Ronning et al. · 2005 [cited by applicant]
US 20060149674A1 · Cook et al. · 2006 [cited by applicant]
US 20070187491A1 · Godwin et al. · 2007 [cited by applicant]
US 20080005037A1 · Hammad et al. · 2008 [cited by applicant]
US 20080288299A1 · Schultz · 2008 [cited by applicant]
US 20090106134A1 · Royyuru · 2009 [cited by applicant]
US 20100094767A1 · Miltonberger · 2010 [cited by applicant]
US 20100114776A1 · Weller et al. · 2010 [cited by applicant]
US 20100305993A1 · Fisher · 2010 [cited by applicant]
US 20110055074A1 · Chen et al. · 2011 [cited by applicant]
US 20110184845A1 · Bishop · 2011 [cited by applicant]
US 20110225064A1 · Fou · 2011 [cited by applicant]
US 20110238566A1 · Santos · 2011 [cited by examiner]
US 20110238575A1 · Nightengale et al. · 2011 [cited by applicant]
US 20110258118A1 · Ciurea · 2011 [cited by applicant]
US 20110264612A1 · Ryman-Tubb · 2011 [cited by applicant]
US 20120109821A1 · Barbour et al. · 2012 [cited by applicant]
US 20120245967A1 · Dispensa et al. · 2012 [cited by applicant]
US 20120254243A1 · Zeppenfeld et al. · 2012 [cited by applicant]
US 20130018781A1 · Prada Peyser et al. · 2013 [cited by applicant]
US 20130339186A1 · French · 2013 [cited by examiner]
US 20140058914A1 · Song et al. · 2014 [cited by applicant]
US 20140074762A1 · Campbell · 2014 [cited by applicant]
US 20140101050A1 · Clarke et al. · 2014 [cited by applicant]
US 20140122325A1 · Zoldi et al. · 2014 [cited by applicant]
US 20140172697A1 · Ward · 2014 [cited by examiner]
US 20140200929A1 · Fitzgerald et al. · 2014 [cited by applicant]
US 20140207674A1 · Schroeder et al. · 2014 [cited by applicant]
US 20140244503A1 · Sadlier · 2014 [cited by applicant]
US 20140250011A1 · Weber · 2014 [cited by applicant]
US 20140266669A1 · Fadell et al. · 2014 [cited by applicant]
US 20140279503A1 · Bertanzetti et al. · 2014 [cited by applicant]
US 20140279745A1 · Esponda · 2014 [cited by examiner]
US 20140283094A1 · Coggeshall et al. · 2014 [cited by applicant]
US 20150026047A1 · Johnson, Jr. · 2015 [cited by applicant]
US 20150032604A1 · Kearns et al. · 2015 [cited by applicant]
US 20150046220A1 · Gerard et al. · 2015 [cited by applicant]
US 20150081324A1 · Adjaoute · 2015 [cited by applicant]
US 20150081349A1 · Johndrow et al. · 2015 [cited by applicant]
US 20150106265A1 · Stubblefield et al. · 2015 [cited by applicant]
US 20150120502A1 · Jung et al. · 2015 [cited by applicant]
US 20150134512A1 · Mueller · 2015 [cited by applicant]
US 20150148061A1 · Koukoumidis et al. · 2015 [cited by applicant]
US 20150178733A1 · Kozloski et al. · 2015 [cited by applicant]
US 20150186888A1 · Katz et al. · 2015 [cited by applicant]
US 20150193768A1 · Douglas et al. · 2015 [cited by applicant]
US 20150242856A1 · Dhurandhar et al. · 2015 [cited by applicant]
US 20150254659A1 · Kulkarni et al. · 2015 [cited by applicant]
US 20150262184A1 · Wang et al. · 2015 [cited by applicant]
US 20150262195A1 · Bergdale et al. · 2015 [cited by applicant]
US 20150269946A1 · Jones · 2015 [cited by examiner]
US 20150363833A1 · Basheer et al. · 2015 [cited by applicant]
US 20160027103A1 · Benamour et al. · 2016 [cited by applicant]
US 20160086184A1 · Carpenter et al. · 2016 [cited by applicant]
US 20160125721A1 · Hughes et al. · 2016 [cited by applicant]
US 20160140562A1 · Birukov et al. · 2016 [cited by applicant]
US 20160148127A1 · Harkey et al. · 2016 [cited by applicant]
US 20160148211A1 · Stibel et al. · 2016 [cited by applicant]
US 20160217509A1 · Eggleston, IV et al. · 2016 [cited by applicant]
US 20160283715A1 · Duke et al. · 2016 [cited by applicant]
US 20160283945A1 · Gonzalez · 2016 [cited by applicant]
US 20160337390A1 · Sridhara et al. · 2016 [cited by applicant]
US 20170070484A1 · Kruse et al. · 2017 [cited by applicant]
US 20170103398A1 · Napsky et al. · 2017 [cited by applicant]
US 20170169431A1 · Groarke et al. · 2017 [cited by applicant]
US 20170178134A1 · Senci et al. · 2017 [cited by applicant]
US 20170221062A1 · Katz et al. · 2017 [cited by applicant]
US 20170270526A1 · Fitzgerald · 2017 [cited by applicant]
US 20170323345A1 · Flowers et al. · 2017 [cited by applicant]
US 20230316284A1 · Kramme · 2023 [cited by applicant]
US 20240303664A1 · Kramme et al. · 2024 [cited by applicant]
US 20240370875A1 · Timothy et al. · 2024 [cited by applicant]
US 20250005557A1 · Kolchin · 2025 [cited by applicant]
US 20250014043A1 · Kramme · 2025 [cited by applicant]
CA 2741408 · 2010 [cited by applicant]
EP 3203436 · 2022 [cited by applicant]
WO WO2006021088 · 2006 [cited by applicant]
WO WO2009048843A1 · 2009 [cited by applicant]
Office Action for U.S. Appl. No. 18/207,069, mailed on May 28, 2024, Kramme, “Reducing False Positives Using Customer Feedback and Machine Learning”, 22 pages. [cited by applicant]
Office Action for U.S. Appl. No. 18/207,069, mailed on Sep. 4, 2024, Kramme, “Reducing False Positives Using Customer Feedback and Machine Learning”, 22 pages. [cited by applicant]
Cho, et. al., “Detection and Response of Identity Theft within a Company Utilizing Location Information,” International Conference on Platform Technology and Service (PlatCon), Feb. 2016 , 5 pages. [cited by applicant]
Expert System, “What is Machine Learning? A definition”, Mar. 7, 2017, retrieved on Jan. 31, 2020: <<https://expertsystem.com/machine-learning-definition/>>. [cited by applicant]
Final Office Action dated Jul. 24, 2020 for U.S. Appl. No. 15/931,560, “Identifying Chargeback Scenarios Based Upon Non-Compliant Merchant Computer Terminals”, Kramme, 61 pages. [cited by applicant]
Joe-Uzuegbu, et. al., “Application virtualization techniques for malware forensics in social engineering,” 2015 International Conference on Cyberspace (Cyber—Abuja), Abuja, Nov. 4, 2015, pp. 45-56. [cited by applicant]
Non Final Office Action dated Feb. 5, 2020 for U.S. Appl. No. 15/465,827 “Reducing False Positives Using Customer Data and Machine Learning” Kramme, 34 pages. [cited by applicant]
Non Final Office Action dated Apr. 8, 2020 for U.S. Appl. No. 15/466,014 “Identifying False Positive Geolocation-Based Fraud Alerts” Kramme, 26 pages. [cited by applicant]
Non Final Office Action dated Apr. 9, 2020 for U.S. Appl. No. 15/465,977 “Document-Based Fraud Detection” Kramme, 10 pages. [cited by applicant]
Non Final Office Action dated Jul. 21, 2020 for U.S. Appl. No. 15/465,981 “Identifying Fraudulent Instruments and Identification” Kramme, 33 pages. [cited by applicant]
Non Final Office Action dated Nov. 17, 2020 for U.S. Appl. No. 15/465,821, “Reducing False Positives Based Upon Customer Online Activity”, Kramme, 19 pages. [cited by applicant]
Non Final Office Action dated Dec. 22, 2020 for U.S. Appl. No. 15/465,856, “Identifying Potential Chargeback Scenarios Using Machine Learning”, Kramme, 23 pages. [cited by applicant]
Office Action dated Jan. 7, 2021 for U.S. Appl. No. 15/465,868, Kramme, “Facilitating Fraud Dispute Resolution Using Machine Learning”, 16 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/465,868, mailed on Jun. 17, 2021, Kramme, “Facilitating Fraud Dispute Resolution Using Machine Learning”, 29 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/465,880, mailed on Dec. 12, 19, mailed on Dec. 12, 19, Kramme, “Preempting or Resolving Fraud Disputes Relating to Introductory Offer Expirations”, 39 Pages. [cited by applicant]
Office action for U.S. Appl. No. 15/465,977, mailed on Dec. 12, 2019, Kramme, “Document-Based Fraud Detection”, 10 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/465,981, mailed on Oct. 6, 2021, Kramme, “Identifying Fraudulent Instruments and Identification”, 35 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 16/988,157, mailed Aug. 1, 2022, Kramme, “Preempting or Resolving Fraud Disputes Relating to Billing Aliases”, 32 pages. [cited by applicant]
Office Action for U.S. Appl. No. 16/988,157, mailed on Jan. 19, 2023, Kramme, “Preempting or Resolving Fraud Disputes Relating to Billing Aliases”, 27 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/078,744, mailed on Dec. 27, 2021, Kramme, “Reducing False Positives Using Customer Data and Machine Learning”, 28 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/080,476, mailed May 20, 2022, Kramme, “Reducing False Positives Using Customer Feedback and Machine Learning”, 22 pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/080,476, mailed on Oct. 20, 2022, Kramme, “Reducing False Positives Using Customer Feedback and Machine Learning”, 23 Pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/465,838, mailed on Jul. 1, 2019, Kramme, “Detecting Financial Fraud Using Spending Pattern Data for Individual Cardholders”, 39 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/465,842, mailed on Nov. 27, 2019, Kramme, “Automated Fraud Classification Using Machine Learning”, 30 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/465,871, mailed on Oct. 31, 2019, Kramme, “Preempting or Resolving Fraud Disputes Relating to Billing Aliases”, 31 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/465,977, mailed on Jun. 11, 2019, Kramme, “Document-Based Fraud Detection”, 10 pages. [cited by applicant]
ProgrammableWeb website, “MasterCard Merchant Identifier API”, Oct. 14, 2015, <<https://web.archive.org/web/20151014154922/http://www.programmableweb.com/api/mastercard-merchant-identifier>>, 3 pages. [cited by applicant]
Office Action for U.S. Appl. No. 18/207,081, mailed on Nov. 4, 2024, Kramme, “Reducing False Positive Fraud Alerts for Online Financial Transactions”, 10 pages. [cited by applicant]
Mspy, “Browsing History—Cell Phone Tracking”, Mar. 16, 2015, retrieved from <<https://web.archive.org/ web/20150316130955/https://www.mspy.com/browsing-history.html>>. [cited by applicant]
Office Action for U.S. Appl. No. 18/624,826, dated Apr. 21, 2025, Kramme, “Identifying False Positive Geolocation-Based Fraud Alerts,” 29 pages. [cited by applicant]
Office Action for U.S. Appl. No. 18/222,199, dated Apr. 18, 2025, 34 pages. [cited by applicant]