# US 2017/0286952 A1 · Method and system for notifications triggered using data tracking algorithms

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286952 A1
- Document ID: US20170286952A1
- Status: Published application
- Kind: A1
- Application number: 15/085,149
- Filed: 2016-03-30
- Published: 2017-10-05
- Earliest claimed: 2016-03-30
- Assignees: Mastercard International Incorporated
- Applicants: MasterCard International Incorporated
- Inventors: Jean-Pierre GERARD; Andrey BIRUKOV
- Web page: https://patentgrep.com/patent/US20170286952A1

## CPC

- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- 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 monitoring for unwanted recurring transactions includes: storing account profiles, each including a primary account number, communication details, and transaction data entries having data related to a completed transaction including a paid amount, merchant identifier, and indication of being a recurring or non-recurring transaction; receiving a transaction message related to a payment transaction, the transaction message including a specific primary account number, transaction amount, specific merchant identifier, and indication of a recurring payment transaction; identifying a specific account profile that includes the specific primary account number; determining a likelihood of an unwanted recurring payment based on a lack of transaction data entries in the specific account profile that include the specific merchant identifier and an indication of being a recurring transaction; and transmitting a notification to a computing device based on the communication details included in the identified specific account profile, the notification indicating the unwanted recurring transaction.

## Claims

### Claim 1

A method for monitoring for unwanted recurring transactions, comprising:
storing, in an account database of a processing server, a plurality of account profiles, wherein each account profile includes a structured data set related to a transaction account including at least a primary account number, communication details, and a plurality of transaction data entries, each transaction data entry including data related to a completed transaction involving the related transaction account including at least a paid amount, merchant identifier, and indication of the related complete transaction being a recurring or non-recurring transaction;
receiving, by a receiving device of the processing server, a transaction message related to a payment transaction, wherein the transaction message is formatted pursuant to one or more standards and includes at least a plurality of data elements including at least a first data element configured to store a specific primary account number, a second data element configured to store a transaction amount, a third data element configured to store a specific merchant identifier, and a fourth data element configured to store an indication of a recurring payment transaction;
executing, by a querying module of the processing server, a query on the account database to identify a specific account profile where the included primary account number corresponds to the specific primary account number stored in the first data element included in the received transaction message;
determining, by a data identification module of the processing server, a likelihood of an unwanted recurring payment based on at least a lack of transaction data entries included in the identified specific account profile that include the specific merchant identifier and an indication of being a recurring transaction; and
electronically transmitting, by a transmitting device of the processing server, a data signal to a computing device based on the communication details included in the identified specific account profile, wherein the data signal is superimposed with at least data stored in the plurality of data elements included in the received transaction message.

### Claim 2 (depends on 1)

The method of claim 1, wherein the likelihood of an unwanted recurring payment is further based on the inclusion of at least one transaction data entry included in the identified specific account profile that includes the specific merchant identifier and an indication of being a non-recurring transaction.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
storing, in a merchant database, a plurality of merchant profiles, wherein each merchant profile includes a structured data set related to one or more high-risk merchants including at least an associated merchant identifier, wherein
the likelihood of an unwanted recurring payment is further based on the inclusion of the specific merchant identifier stored in the third data element included in the received transaction message in at least one merchant profile stored in the merchant database.

### Claim 4 (depends on 3)

The method of claim 3, wherein the likelihood of an unwanted recurring payment is even further based on a lack of transaction data entries included in the identified specific account profile that include the specific merchant identifier and an indication of being a non-recurring transaction.

### Claim 5 (depends on 1)

The method of claim 1, wherein the merchant identifier is one of: a merchant identification number and a merchant category code.

### Claim 6

A method for monitoring for unwanted recurring transactions, comprising:
storing, in an account database of a processing server, a plurality of account profiles, wherein each account profile includes a structured data set related to a transaction account including at least a primary account number, communication details, and a plurality of transaction data entries, each transaction data entry including data related to a completed transaction involving the related transaction account including at least a paid amount, merchant identifier, and indication of the related complete transaction being a recurring or non-recurring transaction;
receiving, by a receiving device of the processing server, a transaction message related to a payment transaction, wherein the transaction message is formatted pursuant to one or more standards and includes at least a plurality of data elements including at least a first data element configured to store a specific primary account number, a second data element configured to store a transaction amount, a third data element configured to store a specific merchant identifier, and a fourth data element configured to store an indication of a recurring payment transaction;
executing, by a querying module of the processing server, a query on the account database to identify a specific account profile where the included primary account number corresponds to the specific primary account number stored in the first data element included in the received transaction message;
identifying, by a data identification module of the processing server, at least one transaction data entry included in the identified specific account profile that includes the specific merchant identifier and an indication of being a recurring transaction;
determining, by the data identification module of the processing server, a likelihood of an unwanted recurring payment based on at least the transaction amount stored in the second data element included in the received transaction message and the paid amount included in each of the identified at least one transaction data entries; and
electronically transmitting, by a transmitting device of the processing server, a data signal to a computing device based on the communication details included in the identified specific account profile, wherein the data signal is superimposed with at least data stored in the plurality of data elements included in the received transaction message.

### Claim 7 (depends on 6)

The method of claim 6, wherein
each transaction data entry further includes a transaction date, and
the likelihood of an unwanted recurring payment is further based on the paid amount included in a specific transaction data entry of the identified at least one transaction data entries being of a predetermined amount less than the transaction amount stored in the second data element included in the received transaction message, wherein
the specific transaction data entry includes a transaction date more recent than the transaction date included in each other transaction data entry included in the identified at least one transaction data entries.

### Claim 8 (depends on 7)

The method of claim 7, wherein the predetermined amount is thirty percent.

### Claim 9 (depends on 6)

The method of claim 6, wherein
each transaction data entry further includes a transaction date,
the data identification module identifies two or more transaction data entries that include the specific merchant identifier and an indication of being a recurring transaction, and
the likelihood of an unwanted recurring payment transaction is further based on a consistent increase in the paid amount included in a predetermined number of the identified two or more transaction data entries based on the paid amount and transaction date included in the identified two or more transaction data entries.

### Claim 10 (depends on 9)

The method of claim 9, wherein the consistent increase is an increase in the paid amount by at least a predetermined amount.

### Claim 11

A system for monitoring for unwanted recurring transactions, comprising:
an account database of a processing server configured to store a plurality of account profiles, wherein each account profile includes a structured data set related to a transaction account including at least a primary account number, communication details, and a plurality of transaction data entries, each transaction data entry including data related to a completed transaction involving the related transaction account including at least a paid amount, merchant identifier, and indication of the related complete transaction being a recurring or non-recurring transaction;
a receiving device of the processing server configured to receive a transaction message related to a payment transaction, wherein the transaction message is formatted pursuant to one or more standards and includes at least a plurality of data elements including at least a first data element configured to store a specific primary account number, a second data element configured to store a transaction amount, a third data element configured to store a specific merchant identifier, and a fourth data element configured to store an indication of a recurring payment transaction;
a querying module of the processing server configured to execute a query on the account database to identify a specific account profile where the included primary account number corresponds to the specific primary account number stored in the first data element included in the received transaction message;
a data identification module of the processing server configured to determine a likelihood of an unwanted recurring payment based on at least a lack of transaction data entries included in the identified specific account profile that include the specific merchant identifier and an indication of being a recurring transaction; and
a transmitting device of the processing server configured to electronically transmit a data signal to a computing device based on the communication details included in the identified specific account profile, wherein the data signal is superimposed with at least data stored in the plurality of data elements included in the received transaction message.

### Claim 12 (depends on 11)

The system of claim 11, wherein the likelihood of an unwanted recurring payment is further based on the inclusion of at least one transaction data entry included in the identified specific account profile that includes the specific merchant identifier and an indication of being a non-recurring transaction.

### Claim 13 (depends on 11)

The system of claim 11, further comprising:
a merchant database configured to store a plurality of merchant profiles, wherein each merchant profile includes a structured data set related to one or more high-risk merchants including at least an associated merchant identifier, wherein
the likelihood of an unwanted recurring payment is further based on the inclusion of the specific merchant identifier stored in the third data element included in the received transaction message in at least one merchant profile stored in the merchant database.

### Claim 14 (depends on 13)

The system of claim 13, wherein the likelihood of an unwanted recurring payment is even further based on a lack of transaction data entries included in the identified specific account profile that include the specific merchant identifier and an indication of being a non-recurring transaction.

### Claim 15 (depends on 11)

The system of claim 11, wherein the merchant identifier is one of: a merchant identification number and a merchant category code.

### Claim 16

A system for monitoring for unwanted recurring transactions, comprising:
an account database of a processing server configured to store a plurality of account profiles, wherein each account profile includes a structured data set related to a transaction account including at least a primary account number, communication details, and a plurality of transaction data entries, each transaction data entry including data related to a completed transaction involving the related transaction account including at least a paid amount, merchant identifier, and indication of the related complete transaction being a recurring or non-recurring transaction;
a receiving device of the processing server configured to receive a transaction message related to a payment transaction, wherein the transaction message is formatted pursuant to one or more standards and includes at least a plurality of data elements including at least a first data element configured to store a specific primary account number, a second data element configured to store a transaction amount, a third data element configured to store a specific merchant identifier, and a fourth data element configured to store an indication of a recurring payment transaction;
a querying module of the processing server configured to execute a query on the account database to identify a specific account profile where the included primary account number corresponds to the specific primary account number stored in the first data element included in the received transaction message;
a data identification module of the processing server configured to
identify at least one transaction data entry included in the identified specific account profile that includes the specific merchant identifier and an indication of being a recurring transaction, and
determine a likelihood of an unwanted recurring payment based on at least the transaction amount stored in the second data element included in the received transaction message and the paid amount included in each of the identified at least one transaction data entries; and
a transmitting device of the processing server configured to electronically transmit a data signal to a computing device based on the communication details included in the identified specific account profile, wherein the data signal is superimposed with at least data stored in the plurality of data elements included in the received transaction message.

### Claim 17 (depends on 16)

The system of claim 16, wherein
each transaction data entry further includes a transaction date, and
the likelihood of an unwanted recurring payment is further based on the paid amount included in a specific transaction data entry of the identified at least one transaction data entries being of a predetermined amount less than the transaction amount stored in the second data element included in the received transaction message, wherein
the specific transaction data entry includes a transaction date more recent than the transaction date included in each other transaction data entry included in the identified at least one transaction data entries.

### Claim 18 (depends on 17)

The system of claim 17, wherein the predetermined amount is thirty percent.

### Claim 19 (depends on 16)

The system of claim 16, wherein
each transaction data entry further includes a transaction date,
the data identification module identifies two or more transaction data entries that include the specific merchant identifier and an indication of being a recurring transaction, and
the likelihood of an unwanted recurring payment transaction is further based on a consistent increase in the paid amount included in a predetermined number of the identified two or more transaction data entries based on the paid amount and transaction date included in the identified two or more transaction data entries.

### Claim 20 (depends on 19)

The system of claim 19, wherein the consistent increase is an increase in the paid amount by at least a predetermined amount.
