# US 2018/0025354 A1 · Systems and methods for mapping non-validated data with validated data

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

- Number: US 2018/0025354 A1
- Document ID: US20180025354A1
- Status: Published application
- Kind: A1
- Application number: 15/216,925
- Filed: 2016-07-22
- Published: 2018-01-25
- Earliest claimed: 2016-07-22
- Assignees: Mastercard International Incorporated
- Applicants: MasterCard International Incorporated
- Inventors: Peter J. Groarke; Ionut Nistor
- Web page: https://patentgrep.com/patent/US20180025354A1

## CPC

- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q 20/382: {insuring higher security of 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 data mapping (DM) computing device including a processor and a memory in communication with the processor is provided. The processor receives a plurality of validated data messages associated with a plurality of transactions through a first communication channel and receives a non-validated data message associated with a first transaction through a second communication channel. Each validated data message includes a plurality of validated data elements with a validated merchant identifier. The non-validated data message includes a plurality of non-validated data elements with a non-validated merchant identifier. The processor further compares the validated data messages and the non-validated data message, identifies a validated data message that is associated with the first transaction based on the comparison, maps the non-validated merchant identifier and the validated merchant identifier of the identified validated message, and stores the mapped merchant identifiers in a linked identifier table within the memory.

## Claims

### Claim 1

A data mapping (DM) computing device comprising a processor and a memory in communication with the processor, wherein the processor is programmed to:
receive a plurality of validated data messages associated with a plurality of transactions through a first communication channel, each validated data message of the plurality of validated data messages including a plurality of validated data elements, the plurality of validated data elements includes a validated merchant identifier;
receive a non-validated data message associated with a first transaction through a second communication channel, the non-validated data message including a plurality of non-validated data elements, the plurality of non-validated data elements including a non-validated merchant identifier;
compare the plurality of validated data messages and the non-validated data message;
identify a validated data message of the plurality of validated data messages that is associated with the first transaction based on the comparison;
map the non-validated merchant identifier and the validated merchant identifier of the identified validated data message; and
store the mapped merchant identifiers in a linked identifier table within the memory.

### Claim 2 (depends on 1)

The DM computing device in accordance with claim 1, wherein the plurality of non-validated data elements includes a partial non-validated data element associated with a first set of validated data messages of the plurality validated data messages.

### Claim 3 (depends on 2)

The DM computing device in accordance with claim 2, wherein the partial non-validated data element is a partial primary account number (PAN).

### Claim 4 (depends on 1)

The DM computing device in accordance with claim 1, wherein the processor is further programmed to:
receive a candidate validated data message including a validated merchant identifier, the candidate validated data message associated with a second transaction;
compare the validated merchant identifier of the candidate validated data message to the linked identifier table;
identify a mapped merchant identifier stored in the linked identifier table that matches the validated merchant identifier; and
retrieve at least one mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.

### Claim 5 (depends on 4)

The DM computing device in accordance with claim 4, wherein the processor is further programmed to:
receive a second non-validated data message including a non-validated merchant identifier;
compare the non-validated merchant identifier of the second non-validated data message to the linked identifier table; and
determine that the second non-validated data message is associated with the second transaction based on the comparison.

### Claim 6 (depends on 1)

The DM computing device in accordance with claim 1, wherein the processor is further programmed to:
receive a second non-validated data message including a non-validated merchant identifier, the second non-validated data message associated with a second transaction;
compare the non-validated merchant identifier of the second non-validated data message to the linked identifier table;
identify a mapped merchant identifier stored in the linked identifier table that matches the non-validated merchant identifier; and
retrieve a mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.

### Claim 7 (depends on 6)

The DM computing device in accordance with claim 6, wherein the processor is further programmed to replace the non-validated merchant identifier of the second non-validated data message with the retrieved mapped merchant identifier.

### Claim 8 (depends on 6)

The DM computing device in accordance with claim 6, wherein the processor is further programmed to:
receive a candidate validated data message including a validated merchant identifier;
compare the candidate validated data message to the second non-validated data message; and
determine the candidate validated data message is associated with the second non-validated data message based, at least in part, on the validated merchant identifier of the candidate validated data message matching the retrieved mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.

### Claim 9

A method for linking non-validated data to validated data, the method comprising:
receiving, by a data mapping (DM) computing device, a plurality of validated data messages associated with a plurality of transactions through a first communication channel, each validated data message of the plurality of validated data messages including a plurality of validated data elements, the plurality of validated data elements includes a validated merchant identifier;
receiving a non-validated data message associated with a first transaction through a second communication channel, the non-validated data message including a plurality of non-validated data elements, the plurality of non-validated data elements including a non-validated merchant identifier;
comparing, by the DM computing device, the plurality of validated data messages and the non-validated data message;
identifying a validated data message of the plurality of validated data messages that is associated with the first transaction based on the comparison;
mapping, by the DM computing device, the non-validated merchant identifier and the validated merchant identifier of the identified validated data message; and
storing the mapped merchant identifiers in a linked identifier table.

### Claim 10 (depends on 9)

The method of claim 9, wherein the plurality of non-validated data elements includes a partial non-validated data element associated with a first set of validated data messages of the plurality validated data messages.

### Claim 11 (depends on 10)

The method in accordance with claim 10, wherein the partial non-validated data element is a partial primary account number (PAN).

### Claim 12 (depends on 9)

The method in accordance with claim 9 further comprising:
receiving, by the DM computing device, a candidate validated data message including a validated merchant identifier, the candidate validated data message associated with a second transaction;
comparing the validated merchant identifier of the candidate validated data message to the linked identifier table;
identifying a mapped merchant identifier stored in the linked identifier table that matches the validated merchant identifier; and
retrieving, by the DM computing device, at least one mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.

### Claim 13 (depends on 12)

The method in accordance with claim 12 further comprising:
receiving, by the DM computing device, a second non-validated data message including a non-validated merchant identifier;
comparing the non-validated merchant identifier of the second non-validated data message to the linked identifier table; and
determining, by the DM computing device, that the second non-validated data message is associated with the second transaction based on the comparison.

### Claim 14 (depends on 9)

The method in accordance with claim 9 further comprising:
receiving, by the DM computing device, a second non-validated data message including a non-validated merchant identifier, the second non-validated data message associated with a second transaction;
comparing the non-validated merchant identifier of the second non-validated data message to the linked identifier table;
identifying, by the DM computing device, a mapped merchant identifier stored in the linked identifier table that matches the non-validated merchant identifier; and
retrieving, by the DM computing device, a mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.

### Claim 15 (depends on 14)

The method in accordance with claim 14 further comprising replacing, by the DM computing device, the non-validated merchant identifier of the second non-validated data message with the retrieved mapped merchant identifier.

### Claim 16 (depends on 14)

The method in accordance with claim 14 further comprising:
receiving, by the DM computing device, a candidate validated data message including a validated merchant identifier;
comparing the candidate validated data message to the second non-validated data message; and
determining the candidate validated data message is associated with the second non-validated data message based, at least in part, on the validated merchant identifier of the candidate validated data message matching the retrieved mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.

### Claim 17

At least one non-transitory computer-readable storage media for linking non-validated data to validated data, the computer-readable storage media having computer-executable instructions embodied thereon, wherein, when executed by at least one processor, the computer-executable instructions cause the processor to:
receive a plurality of validated data messages associated with a plurality of transactions through a first communication channel, each validated data message of the plurality of validated data messages including a plurality of validated data elements, the plurality of validated data elements includes a validated merchant identifier;
receive a non-validated data message associated with a first transaction through a second communication channel, the non-validated data message including a plurality of non-validated data elements, the plurality of non-validated data elements including a non-validated merchant identifier;
compare the plurality of validated data messages and the non-validated data message;
identify a validated data message of the plurality of validated data messages that is associated with the first transaction based on the comparison;
map the non-validated merchant identifier and the validated merchant identifier of the identified validated data message; and
store the mapped merchant identifiers in a linked identifier table within the memory.

### Claim 18 (depends on 17)

The non-transitory computer-readable storage media in accordance with claim 17, wherein the plurality of non-validated data elements includes a partial non-validated data element associated with a first set of validated data messages of the plurality validated data messages.

### Claim 19 (depends on 18)

The non-transitory computer-readable storage media in accordance with claim 18, wherein the partial non-validated data element is a partial primary account number (PAN).

### Claim 20 (depends on 17)

The non-transitory computer-readable storage media in accordance with claim 17, wherein the computer-executable instructions further cause the processor to:
receive a candidate validated data message including a validated merchant identifier, the candidate validated data message associated with a second transaction;
compare the validated merchant identifier of the candidate validated data message to the linked identifier table;
identify a mapped merchant identifier stored in the linked identifier table that matches the validated merchant identifier; and
retrieve at least one mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.

### Claim 21 (depends on 20)

The non-transitory computer-readable storage media in accordance with claim 20, wherein the computer-executable instructions further cause the processor to:
receive a second non-validated data message including a non-validated merchant identifier;
compare the non-validated merchant identifier of the second non-validated data message to the linked identifier table; and
determine that the second non-validated data message is associated with the second transaction based on the comparison.

### Claim 22 (depends on 17)

The non-transitory computer-readable storage media in accordance with claim 17, wherein the computer-executable instructions further cause the processor to:
receive a second non-validated data message including a non-validated merchant identifier, the second non-validated data message associated with a second transaction;
compare the non-validated merchant identifier of the second non-validated data message to the linked identifier table;
identify a mapped merchant identifier stored in the linked identifier table that matches the non-validated merchant identifier; and
retrieve a mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.

### Claim 23 (depends on 22)

The non-transitory computer-readable storage media in accordance with claim 22, wherein the computer-executable instructions further cause the processor to replace the non-validated merchant identifier of the second non-validated data message with the retrieved mapped merchant identifier.

### Claim 24 (depends on 22)

The non-transitory computer-readable storage media in accordance with claim 22, wherein the computer-executable instructions further cause the processor to:
receive a candidate validated data message including a validated merchant identifier;
compare the candidate validated data message to the second non-validated data message; and
determine the candidate validated data message is associated with the second non-validated data message based, at least in part, on the validated merchant identifier of the candidate validated data message matching the retrieved mapped merchant identifier associated with the identified mapped merchant identifier from the linked identifier table.