# US 2021/0241335 A1 · System and Method 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 2021/0241335 A1
- Document ID: US20210241335A1
- Status: Published application
- Kind: A1
- Application number: 17/253,877
- Filed: 2018-06-21
- Published: 2021-08-05
- Earliest claimed: 2018-06-21
- Assignees: Visa International Service Association
- Applicants: Visa International Service Association
- Inventors: Rohit Sukhija; Aditya Ashok Kale
- Web page: https://patentgrep.com/patent/US20210241335A1

## 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 method for processing a chargeback request associated with at least one online transaction associated with a user, comprising:
receiving from a computing device of a user, with at least one processor, a chargeback message associated with the at least one online transaction between the user and at least one merchant, wherein the chargeback message comprises at least one unfamiliar merchant name associated with the at least one merchant;
based at least partially on the unfamiliar merchant name in the chargeback message, determining, with at least one processor, at least one potential familiar merchant name associated with the at least one unfamiliar merchant name;
in response to determining the at least one potential familiar merchant name, scanning, with at least one processor, a browser history of the user comprising browser data;
determining, with at least one processor, based at least partially on the browser data, whether the user visited a website associated with the at least one potential familiar merchant name; and
in response to determining that the user visited the website associated with the at least one potential familiar merchant name, generating and communicating to the computing device, with at least one processor, a recommendation message comprising the at least one potential familiar merchant name.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving from the computing device in response to the recommendation message, with at least one processor, a confirmation message associating the at least one unfamiliar merchant name with the at least one potential familiar merchant name.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
in response to receiving the confirmation message, updating, with at least one processor, an association score of the at least one potential familiar merchant name, the association score indicating the likelihood that the at least one potential familiar merchant name is associated with an unfamiliar merchant name.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
in response to a second, subsequent chargeback message comprising the at least one unfamiliar merchant name, determining, with at least one processor, the at least one potential familiar merchant name based partially on the association score of the at least one potential familiar merchant name.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
receiving from the computing device in response to the recommendation message, with at least one processor, a rejection message disassociating the at least one unfamiliar merchant name with the at least one potential familiar merchant name; and
in response to the rejection message, initiating, with at least one processor, a fraud response protocol.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
in response to receiving the rejection message, updating, with at least one processor, an association score of the at least one potential familiar merchant name, the association score indicating the likelihood that the at least one potential familiar merchant name is associated with an unfamiliar merchant name.

### Claim 7 (depends on 1)

The method of claim 1, wherein the determining of the at least one potential familiar merchant name comprises:
scanning a database comprising a plurality of unfamiliar merchant names each associated with at least one potential familiar merchant name; and
determining the at least one potential familiar merchant name based at least partially on a match between at least one of the plurality of unfamiliar merchant names and the associated at least one potential familiar merchant name.

### Claim 8 (depends on 1)

The method of claim 1, wherein the determining of the at least one potential familiar merchant name comprises:
scanning, with at least one processor, at least one data resource by initiating a search process including at least a portion of the at least one unfamiliar merchant name; and
in response to the results of the search process, determining the at least one potential familiar merchant name.

### Claim 9 (depends on 8)

The method of claim 8, 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 10 (depends on 1)

The method of claim 1, wherein the determining of the at least one potential familiar merchant name comprises determining a plurality of potential familiar merchant names.

### Claim 11 (depends on 1)

The method of claim 1, wherein the at least one unfamiliar merchant name is a name corresponding to a payment gateway associated with the at least one potential familiar merchant name.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
communicating, with at least one processor, an update request to a merchant system of the at least one merchant associated with the at least one unfamiliar merchant name, the update request including instructions for the merchant system to update the at least one unfamiliar merchant name with the at least one potential familiar merchant name.

### Claim 13

A system for processing a chargeback request associated with an online transaction associated with a user comprising at least one processor programmed and/or configured to:
receive from a computing device of a user a chargeback message associated with the at least one online transaction between the user and at least one merchant, wherein the chargeback message comprises at least one unfamiliar merchant name associated with the at least one merchant;
based at least partially on the unfamiliar merchant name in the chargeback message, determine at least one potential familiar merchant name associated with the at least one unfamiliar merchant name;
in response to determining the at least one potential familiar merchant name, scan a browser history of the user comprising browser data;
determine, based at least partially on the browser data, whether the user visited a website associated with the at least one potential familiar merchant name; and
in response to determining that the user visited the website associated with the at least one potential familiar merchant name, generate and communicate to the computing device a recommendation message comprising the at least one potential familiar merchant name.

### Claim 14 (depends on 13)

The system of claim 13, wherein the at least one processor is further programmed and/or configured to:
receive from the computing device in response to the recommendation message a confirmation message associating the at least one unfamiliar merchant name with the at least one potential familiar merchant name.

### Claim 15 (depends on 14)

The system of claim 14, wherein the at least one processor is further programmed and/or configured to:
in response to receiving the confirmation message, update an association score of the at least one potential familiar merchant name, the association score indicating the likelihood that the at least one potential familiar merchant name is associated with an unfamiliar merchant name.

### Claim 16 (depends on 13)

The system of claim 13, wherein the at least one processor is further programmed and/or configured to:
receive from the computing device in response to the recommendation message a rejection message disassociating the at least one unfamiliar merchant name with the at least one potential familiar merchant name; and
in response to the rejection message, initiate a fraud response protocol.

### Claim 17 (depends on 16)

The system of claim 16, wherein the at least one processor is further programmed and/or configured to:
in response to receiving the rejection message, update an association score of the at least one potential familiar merchant name, the association score indicating the likelihood that the at least one potential familiar merchant name is associated with an unfamiliar merchant name.

### Claim 18 (depends on 13)

The system of claim 13, wherein to determine the at least one potential familiar merchant name, the at least one processor is programmed and/or configured to:
scan a database comprising a plurality of unfamiliar merchant names each associated with at least one potential familiar merchant name; and
determine the at least one potential familiar merchant name based at least partially on a match between at least one of the plurality of unfamiliar merchant names and the associated at least one potential familiar merchant name.

### Claim 19 (depends on 13)

The system of claim 13, wherein the at least one processor is further programmed and/or configured to:
scan at least one data resource by initiating a search process including at least a portion of the at least one unfamiliar merchant name; and
in response to the results of the search process, determine the at least one potential familiar merchant name.

### Claim 20 (depends on 19)

The system of claim 19, 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 at position 21

-22. (canceled)