# US 2021/0264423 A1 · Systems and methods for automatically initiating chargeback transactions for dual message transactions

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

- Number: US 2021/0264423 A1
- Document ID: US20210264423A1
- Status: Published application
- Kind: A1
- Application number: 16/797,992
- Filed: 2020-02-21
- Published: 2021-08-26
- Earliest claimed: 2020-02-21
- Assignees: Mastercard International Incorporated
- Applicants: Mastercard International Incorporated
- Inventors: Patricia Rohlfing; Joan Lee Rohlfing; Desh Deepak Yog; Michael Scott Powell
- Web page: https://patentgrep.com/patent/US20210264423A1

## CPC

- G06Q 20/407: {Cancellation of a transaction}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/258: {Data format conversion from or to a database}
- G06Q 20/023: {the neutral party being a clearing house}
- G06Q 20/085: {involving remote charge determination or related payment systems}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 30/018: Certifying business or products
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A computing system for automatically initiating a chargeback transaction from a plurality of processed transactions is provided. The computing system comprises a processor in communication with a memory, and the processor is programmed to: (i) receive transaction data associated with a plurality of processed transactions, the transaction data including a plurality of account identifiers, a plurality of authorization messages, and a plurality of clearing messages associated with the plurality of processed transactions, (ii) match the plurality of authorization messages with the respective plurality of clearing messages for each processed transaction of the plurality of processed transactions, (iii) identify automatic chargeback-eligible transactions from the plurality of processed transactions by parsing the transaction data and by the matching of the authorization messages with the clearing messages, (iv) store the identified automatic chargeback-eligible transactions, and (v) automatically initiate a chargeback transaction for each identified automatic chargeback-eligible transaction.

## Claims

### Claim 1

A computing system for automatically initiating a chargeback transaction from a plurality of processed transactions, the computing system comprising at least one processor in communication with at least one memory, the at least one processor programmed to:
receive transaction data associated with a plurality of processed transactions, the transaction data including a plurality of account identifiers, a plurality of authorization messages, and a plurality of clearing messages associated with the plurality of processed transactions;
match the plurality of authorization messages with the respective plurality of clearing messages for each processed transaction of the plurality of processed transactions;
identify automatic chargeback-eligible transactions from the plurality of processed transactions by parsing the transaction data and by the matching of the authorization messages with the clearing messages;
store, in the at least one memory, the identified automatic chargeback-eligible transactions; and
automatically initiate a chargeback transaction for each identified automatic chargeback-eligible transaction.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the at least one processor is further programmed to:
store, in the at least one memory, legitimate account identifiers that are eligible to be used for initiating a transaction;
parse an account identifier from the received transaction data for each transaction of the plurality of processed transactions;
compare each received account identifier of the plurality of account identifiers to the legitimate account identifiers stored in the at least one memory;
identify whether each received account identifier matches any of the legitimate account identifiers stored in the at least one memory;
store, in the at least one memory, the identified account identifiers that do not match any of the legitimate account identifiers as not-on-file account identifiers; and
identify each transaction carried out with a not-on-file account identifier as an automatic chargeback-eligible transaction.

### Claim 3 (depends on 2)

The computing system of claim 2, wherein the at least one processor is further programmed to:
store, in the at least one memory, the identified account identifiers that match any of the legitimate account identifiers as on-file account identifiers;
for each processed transaction associated with on-file account identifiers, identify whether each processed transaction of the plurality of processed transactions includes a valid authorization message;
store, in the at least one memory, the identified processed transactions that do not include a valid authorization message as invalid authorization message transactions; and
identify each invalid authorization message transaction as an automatic chargeback-eligible transaction.

### Claim 4 (depends on 3)

The computing system of claim 3, wherein the at least one processor is further programmed to:
store, in the at least one memory, the identified transactions that include a valid authorization message as present authorization message transactions;
for each processed transaction associated with valid authorization message transactions, identify whether each processed transaction of the plurality of processed transactions includes a valid clearing message that was processed within a predetermined time period;
store, in the at least one memory, the identified processed transactions that do not include a valid clearing message processed within the predetermined time period as invalid clearing message transactions; and
identify each invalid clearing message transaction as an automatic chargeback-eligible transaction.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein the at least one processor is further programmed to:
aggregate each identified automatic chargeback-eligible transaction;
format each aggregated transaction into a single and standardized data file format; and
transmit the formatted single data file to a payment processing network to initiate the chargeback transactions.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein the at least one processor is further programmed to:
determine, based upon the plurality of authorization messages, whether each received account identifier is associated with an account that is in one of a good standing and a bad standing, wherein accounts in good standing have at least one of a positive balance, an open status, and an active status, and wherein accounts in bad standing have at least one of a zero balance, a negative balance, a suspended status, and an inactive status;
store, in the at least one memory, the identified account identifiers associated with accounts in bad standing as bad standing account identifiers;
compare each received account identifier of the plurality of account identifiers to the bad standing account identifiers stored in the at least one memory; and
identify each transaction carried out with the bad standing account identifiers as an automatic chargeback-eligible transaction.

### Claim 7 (depends on 1)

The computing system of claim 1, wherein the at least one processor is further programmed to:
receive, from an issuer computing device, additional rules associated with automatically initiating chargeback transactions;
identify automatic chargeback-eligible transactions from the plurality of processed transactions based upon the received additional rules; and
automatically initiate chargeback transactions for each identified automatic chargeback-eligible transaction.

### Claim 8 (depends on 1)

The computing system of claim 1, wherein the plurality of transactions includes dual message transactions, debit transactions, and prepaid transactions.

### Claim 9

A computer-implemented method for automatically initiating a chargeback transaction from a plurality of processed transactions, the method implemented by a computing system including at least one processor in communication with at least one memory, the method comprising:
receiving transaction data associated with a plurality of processed transactions, the transaction data including a plurality of account identifiers, a plurality of authorization messages, and a plurality of clearing messages associated with the plurality of processed transactions;
matching the plurality of authorization messages with the respective plurality of clearing messages for each processed transaction of the plurality of processed transactions;
identifying automatic chargeback-eligible transactions from the plurality of processed transactions by parsing the transaction data and by the matching of the authorization messages with the clearing messages;
storing, in the at least one memory, the identified automatic chargeback-eligible transactions; and
automatically initiating a chargeback transaction for each identified automatic chargeback-eligible transaction.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9 further comprising:
storing, in the at least one memory, legitimate account identifiers that are eligible to be used for initiating a transaction;
parsing an account identifier from the received transaction data for each transaction of the plurality of processed transactions;
comparing each received account identifier of the plurality of account identifiers to the legitimate account identifiers stored in the at least one memory;
identifying whether each received account identifier matches any of the legitimate account identifiers stored in the at least one memory;
storing, in the at least one memory, the identified account identifiers that do not match any of the legitimate account identifiers as not-on-file account identifiers; and
identifying each transaction carried out with a not-on-file account identifier as an automatic chargeback-eligible transaction.

### Claim 11 (depends on 10)

The computer-implemented method of claim 10 further comprising:
storing, in the at least one memory, the identified account identifiers that match any of the legitimate account identifiers as on-file account identifiers;
for each processed transaction associated with on-file account identifiers, identifying whether each processed transaction of the plurality of processed transactions includes a valid authorization message;
storing, in the at least one memory, the identified processed transactions that do not include a valid authorization message as invalid authorization message transactions; and
identifying each invalid authorization message transaction as an automatic chargeback-eligible transaction.

### Claim 12 (depends on 11)

The computer-implemented method of claim 11 further comprising:
storing, in the at least one memory, the identified transactions that include a valid authorization message as present authorization message transactions;
for each processed transaction associated with valid authorization message transactions, identifying whether each processed transaction of the plurality of processed transactions includes a valid clearing message that was processed within a predetermined time period;
storing, in the at least one memory, the identified processed transactions that do not include a valid clearing message processed within the predetermined time period as invalid clearing message transactions; and
identifying each invalid clearing message transaction as an automatic chargeback-eligible transaction.

### Claim 13 (depends on 12)

The computer-implemented method of claim 12 further comprising:
aggregating each identified automatic chargeback-eligible transaction;
formatting each aggregated transaction into a single and standardized data file format; and
transmitting the formatted single data file to a payment processing network to initiate the chargeback transactions.

### Claim 14 (depends on 9)

The computer-implemented method of claim 9 further comprising:
determining, based upon the plurality of authorization messages, whether each received account identifier is associated with an account that is in one of a good standing and a bad standing, wherein accounts in good standing have at least one of a positive balance, an open status, and an active status, and wherein accounts in bad standing have at least one of a zero balance, a negative balance, a suspended status, and an inactive status;
storing, in the at least one memory, the identified account identifiers associated with accounts in bad standing as bad standing account identifiers;
comparing each received account identifier of the plurality of account identifiers to the bad standing account identifiers stored in the at least one memory; and
identifying each transaction carried out with the bad standing account identifiers as an automatic chargeback-eligible transaction.

### Claim 15

At least one non-transitory computer-readable storage media that includes computer-executable instructions for automatically initiating a chargeback transaction from a plurality of processed transactions, wherein when executed by a computing system including at least one processor in communication with at least one memory, the computer-executable instructions cause the at least one processor to:
receive transaction data associated with a plurality of processed transactions, the transaction data including a plurality of account identifiers, a plurality of authorization messages, and a plurality of clearing messages associated with the plurality of processed transactions;
match the plurality of authorization messages with the respective plurality of clearing messages for each processed transaction of the plurality of processed transactions;
identify automatic chargeback-eligible transactions from the plurality of processed transactions by parsing the transaction data and by the matching of the authorization messages with the clearing messages;
store, in the at least one memory, the identified automatic chargeback-eligible transactions; and
automatically initiate a chargeback transaction for each identified automatic chargeback-eligible transaction.

### Claim 16 (depends on 15)

The at least one non-transitory computer-readable storage media of claim 15, wherein the computer-executable instructions further cause the at least one processor to:
store, in the at least one memory, legitimate account identifiers that are eligible to be used for initiating a transaction;
parse an account identifier from the received transaction data for each transaction of the plurality of processed transactions;
compare each received account identifier of the plurality of account identifiers to the legitimate account identifiers stored in the at least one memory;
identify whether each received account identifier matches any of the legitimate account identifiers stored in the at least one memory;
store, in the at least one memory, the identified account identifiers that do not match any of the legitimate account identifiers as not-on-file account identifiers; and
identify each transaction carried out with a not-on-file account identifier as an automatic chargeback-eligible transaction.

### Claim 17 (depends on 16)

The at least one non-transitory computer-readable storage media of claim 16, wherein the computer-executable instructions further cause the at least one processor to:
store, in the at least one memory, the identified account identifiers that match any of the legitimate account identifiers as on-file account identifiers;
for each processed transaction associated with on-file account identifiers, identify whether each processed transaction of the plurality of processed transactions includes a valid authorization message;
store, in the at least one memory, the identified processed transactions that do not include a valid authorization message as invalid authorization message transactions; and
identify each invalid authorization message transaction as an automatic chargeback-eligible transaction.

### Claim 18 (depends on 17)

The at least one non-transitory computer-readable storage media of claim 17, wherein the computer-executable instructions further cause the at least one processor to:
store, in the at least one memory, the identified transactions that include a valid authorization message as present authorization message transactions;
for each processed transaction associated with valid authorization message transactions, identify whether each processed transaction of the plurality of processed transactions includes a valid clearing message that was processed within a predetermined time period;
store, in the at least one memory, the identified processed transactions that do not include a valid clearing message processed within the predetermined time period as invalid clearing message transactions; and
identify each invalid clearing message transaction as an automatic chargeback-eligible transaction.

### Claim 19 (depends on 18)

The at least one non-transitory computer-readable storage media of claim 18, wherein the computer-executable instructions further cause the at least one processor to:
aggregate each identified automatic chargeback-eligible transaction;
format each aggregated transaction into a single and standardized data file format; and
transmit the formatted single data file to a payment processing network to initiate the chargeback transactions.

### Claim 20 (depends on 15)

The at least one non-transitory computer-readable storage media of claim 15, wherein the computer-executable instructions further cause the at least one processor to:
determine, based upon the plurality of authorization messages, whether each received account identifier is associated with an account that is in one of a good standing and a bad standing, wherein accounts in good standing have at least one of a positive balance, an open status, and an active status, and wherein accounts in bad standing have at least one of a zero balance, a negative balance, a suspended status, and an inactive status;
store, in the at least one memory, the identified account identifiers associated with accounts in bad standing as bad standing account identifiers;
compare each received account identifier of the plurality of account identifiers to the bad standing account identifiers stored in the at least one memory; and
identify each transaction carried out with the bad standing account identifiers as an automatic chargeback-eligible transaction.
