# US 11,907,984 B2 · System, method, and computer program product for detecting and preventing “friendly fraud” > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,907,984 B2 - Document ID: US11907984B2 - Status: Granted - Kind: B2 - Application number: 17/897,509 - Filed: 2022-08-29 - Published: 2022-12-29 - Granted: 2024-02-20 - Earliest claimed: 2022-08-29 - Assignees: Visa International Service Association - Applicants: Visa International Service Association - Inventors: Rohit Sukhija; Aditya Ashok Kale - Web page: https://patentgrep.com/patent/US11907984B2 ## CPC - G06Q 30/0609: {Qualifying participants for shopping transactions (payment transaction verification G06Q20/401)} - G06Q 30/0613: {using intermediate agents} - G06Q 30/0185: {Product, service or business identity fraud} - G06Q 30/0631: {Recommending goods or services} - G06Q: INFORMATION 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 ## Abstract A method for processing a chargeback request associated with at least one online transaction associated with a user includes: receiving a chargeback message associated with the at least one online transaction; based at least partially on the unfamiliar merchant name in the chargeback message, determining at least one potential familiar merchant name associated with the at least one unfamiliar merchant name; scanning a browser history of the user including browser data; determining whether the user visited a website associated with the at least one potential familiar merchant name; and generating and communicating a recommendation message including the at least one potential familiar merchant name. A system for processing a chargeback request associated with at least one online transaction associated with a user is also disclosed. ## Claims ### Claim 1 A computer-implemented method, comprising: providing by a browser plug in of a web browser of a computing device, a message associated with an online transaction between a user and a merchant, wherein the message comprises an unfamiliar merchant name associated with the merchant, and wherein the unfamiliar merchant name is a name corresponding to a payment gateway associated with at least one potential familiar merchant name; determining, by the browser plug in of the web browser of the computing device, the at least one potential familiar merchant name based on the unfamiliar merchant name associated with the online transaction between the user and the merchant; scanning, by the browser plug in of the web browser, a browser history of the web browser for a predetermined payment pattern that includes the at least one potential familiar merchant name based on determining the at least one potential familiar merchant name, wherein the browser history of the web browser comprises browser data of the user, and wherein scanning the browser history of the web browser for the predetermined payment pattern that includes the at least one potential familiar merchant name comprises: scanning, by the browser plug in, the browser data of the browser history for the predetermined payment pattern that includes the at least one potential familiar merchant name based on the user device granting permission to the browser plug in to scan the browser data; identifying, by the browser plug in, the predetermined payment pattern in the browser data of the browser history; and identifying, by the browser plug in, a uniform resource location (URL) associated with the payment gateway in the browser data; and providing, by the browser plug in of the web browser, the at least one potential familiar merchant name in response to determining that the user visited a website associated with the at least one potential familiar merchant name. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, further comprising: receiving a message associated with the online transaction between the user and the merchant, wherein the message comprises the unfamiliar merchant name, and wherein the unfamiliar merchant name is a name corresponding to a payment gateway associated with the at least one potential familiar merchant name. ### Claim 3 (depends on 2) The computer-implemented method of claim 2, further comprising: updating an association score of the at least one potential familiar merchant name in response to receiving a second message, wherein the second message comprises the unfamiliar merchant name, and wherein the association score indicates a likelihood that the at least one potential familiar merchant name is associated with the unfamiliar merchant name. ### Claim 4 (depends on 3) The computer-implemented method of claim 3, further comprising: confirming a determination of the at least one potential familiar merchant name based on the association score of the at least one potential familiar merchant name in response to receiving a second message, wherein the second message comprises the unfamiliar merchant name. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, further comprising: receiving a rejection message disassociating the unfamiliar merchant name with the at least one potential familiar merchant name; and initiating a fraud response protocol in response to receiving the rejection message. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, wherein determining the at least one potential familiar merchant name comprises: scanning at least one data resource by initiating a search process including at least a portion of the unfamiliar merchant name; and determining the at least one potential familiar merchant name based on a result of the search process; wherein the at least one data resource comprises at least one of the following: the Internet, a remote database, a third party database, a crowd-sourced database, a database local to the computing device, a database associated with the user, or any combination thereof. ### Claim 7 A system, comprising: at least one processor of a computing device, wherein the at least one processor is programmed or configured to: provide, via a browser plug in of a web browser of the computing device, a message associated with a transaction between a user and a merchant, wherein the message comprises an unfamiliar merchant name associated with the merchant, and wherein the unfamiliar merchant name is a name corresponding to a payment gateway associated with at least one potential familiar merchant name; determine, via the browser plug in of the web browser, the at least one potential familiar merchant name based on the unfamiliar merchant name associated with the online transaction between the user and the merchant; scan, via the browser plug in of the web browser, a browser history of the web browser for a predetermined payment pattern that includes the at least one potential familiar merchant name in response to determining the at least one potential familiar merchant name, wherein the browser history of the web browser comprises browser data of the user, and wherein, when scanning the browser history of the web browser for the predetermined payment pattern that includes the at least one potential familiar merchant name, the at least one processor is programmed or configured to: scan, via the browser plug in, the browser data of the browser history for the predetermined payment pattern that includes the at least one potential familiar merchant name based on the user device granting permission to the browser plug in to scan the browser data; identify, via the browser plug in, the predetermined payment pattern in the browser data of the browser history; and identify, via the browser plug in, a uniform resource location (URL) associated with the payment gateway in the browser data; and provide, via the browser plug in of the web browser, the at least one potential familiar merchant name in response to determining that the user visited a website associated with the at least one potential familiar merchant name. ### Claim 8 (depends on 7) The system of claim 7, wherein the at least one processor is further programmed or configured to: receive a message associated with the online transaction between the user and the merchant, wherein the message comprises the unfamiliar merchant name, and wherein the unfamiliar merchant name is a name corresponding to a payment gateway associated with at least one potential familiar merchant name; and update an association score of the at least one potential familiar merchant name, wherein the association score indicates a likelihood that the at least one potential familiar merchant name is associated with the unfamiliar merchant name. ### Claim 9 (depends on 8) The system of claim 8, wherein the at least one processor is further programmed or configured to: confirm a determination of the at least one potential familiar merchant name based on the association score of the at least one potential familiar merchant name in response to receiving a message, wherein the message comprises the unfamiliar merchant name. ### Claim 10 (depends on 7) The system of claim 7, wherein the at least one processor is further programmed or configured to: receive a rejection message disassociating the unfamiliar merchant name with the at least one potential familiar merchant name; and initiate a fraud response protocol in response to receiving the rejection message. ### Claim 11 (depends on 10) The system of claim 10, wherein the at least one processor is further programmed or configured to: update an association score of the at least one potential familiar merchant name in response to receiving the rejection message, wherein the association score indicates a likelihood that the at least one potential familiar merchant name is associated with the unfamiliar merchant name. ### Claim 12 (depends on 7) The system of claim 7, wherein, when determining the at least one potential familiar merchant name, the at least one processor is programmed or configured to: scan at least one data resource by initiating a search process including at least a portion of the unfamiliar merchant name; and determine the at least one potential familiar merchant name based on a result of the search process; wherein the at least one data resource comprises at least one of the following: the Internet, a remote database, a third party database, a crowd-sourced database, a local database, a database associated with the user, or any combination thereof. ### Claim 13 A computer program product, the computer program product comprising at least one non-transitory computer-readable medium including one or more instructions that, when executed by at least one processor, cause the at least one processor to: provide, via a browser plug in of a web browser of the computing device, a message associated with at least one online transaction between a user and a merchant, wherein the message comprises an unfamiliar merchant name associated with the merchant, and wherein the unfamiliar merchant name is a name corresponding to a payment gateway associated with at least one potential familiar merchant name; determine, via the browser plug in of the web browser, at least one potential familiar merchant name based on the unfamiliar merchant name associated with the online transaction between the user and the merchant; scan, via the browser plug in of the web browser, a browser history of the web browser for a predetermined payment pattern that includes the at least one potential familiar merchant name in response to determining the at least one potential familiar merchant name, wherein the browser history of the web browser comprises browser data of the user, and wherein, when scanning the browser history of the web browser for the predetermined payment pattern that includes the at least one potential familiar merchant name, the at least one processor is programmed or configured to: scan, via the browser plug in, the browser data of the browser history for the predetermined payment pattern that includes the at least one potential familiar merchant name based on the user device granting permission to the browser plug in to scan the browser data; identify, via the browser plug in, the predetermined payment pattern in the browser data of the browser history; and identify, via the browser plug in, a uniform resource location (URL) associated with the payment gateway in the browser data; and provide the at least one potential familiar merchant name in response to determining that the user visited a website associated with the at least one potential familiar merchant name. ### Claim 14 (depends on 13) The computer program product of claim 13, wherein the one or more instructions further cause the at least one processor to: receive a confirmation message associating the unfamiliar merchant name with the at least one potential familiar merchant name. ### Claim 15 (depends on 14) The computer program product of claim 14, wherein the one or more instructions further cause the at least one processor to: update an association score of the at least one potential familiar merchant name in response to receiving the confirmation message, wherein the association score indicates a likelihood that the at least one potential familiar merchant name is associated with the unfamiliar merchant name. ### Claim 16 (depends on 15) The computer program product of claim 15, wherein the one or more instructions further cause the at least one processor to: confirm a determination of the at least one potential familiar merchant name based on the association score of the at least one potential familiar merchant name in response to receiving a second message, wherein the second message comprises the unfamiliar merchant name. ### Claim 17 (depends on 13) The computer program product of claim 13, wherein the one or more instructions further cause the at least one processor to: receive a rejection message disassociating the unfamiliar merchant name with the at least one potential familiar merchant name; initiate a fraud response protocol in response to receiving the rejection message; and update an association score of the at least one potential familiar merchant name in response to receiving the rejection message, wherein the association score indicates a likelihood that the at least one potential familiar merchant name is associated with the unfamiliar merchant name.