# US 2009/0276344 A1 · Field 55 parser

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

- Number: US 2009/0276344 A1
- Document ID: US20090276344A1
- Status: Published application
- Kind: A1
- Application number: 12/150,861
- Filed: 2008-04-30
- Published: 2009-11-05
- Earliest claimed: 2008-04-30
- Assignees: Visa U.S.A. Inc.
- Inventors: Brian Maw
- Web page: https://patentgrep.com/patent/US20090276344A1

## CPC

- G07F 7/0873: {Details of the card reader}
- G06Q 20/04: Payment circuits
- G06Q 20/403: {Solvency checks}
- G06Q 20/4037: {Remote solvency checks}
- G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q 40/12: Accounting
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- 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 payment device, method, and apparatus configured to parse customer exclusive data from a payment device or financial transaction data.

## Claims

### Claim 1

A method of processing a financial transaction associated with a financial transaction data packet, the method comprising:
receiving the financial transaction data packet from an acquirer;
extracting a data field from the financial transaction data packet, the data field formatted in Tag-Length-Value format;
parsing a data tag from the data field;
extracting card customer exclusive data from the data tag;
extracting a primary account number from the financial transaction data packet;
querying a cardholder database with the primary account number to determine whether there is a database customer exclusive data associated with the primary account number;
comparing the card customer exclusive data with the database customer exclusive data;
substituting the card customer exclusive data with the database customer exclusive data in a financial transaction when the card customer exclusive data with the database customer exclusive data do not match.

### Claim 2 (depends on 1)

The method of claim 1, wherein the data tag is Field 55.

### Claim 3 (depends on 2)

The method of claim 2, wherein the card customer exclusive data is a data element within Field 55.

### Claim 4 (depends on 3)

The method of claim 3, wherein the card customer exclusive data is data element 9F7C.

### Claim 5 (depends on 4)

The method of claim 4, wherein the card customer exclusive data includes loyalty, rewards, contact or discretionary data.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
presenting a cardholder loyalty or rewards information based on the card customer exclusive data or database customer exclusive data.

### Claim 7 (depends on 5)

The method of claim 5, further comprising:
generating a report from the financial transaction with the database customer exclusive data.

### Claim 8 (depends on 5)

The method of claim 5, further comprising:
storing information from the financial transaction with the database customer exclusive data in a log.

### Claim 9

A payment card processing system, comprising:
a cardholder database configured to store customer account information, the customer account information containing a primary account number;
a network interface configured to receive the financial transaction data packet from an acquirer;
a data parser configured to extract a data field from the financial transaction data packet, the data field formatted in Tag-Length-Value format; the data parser further configured to parse a data tag from the data field, extract card customer exclusive data from the data tag, and extract a primary account number from the financial transaction data packet;
a customer data manager configured to query the cardholder database with the primary account number to determine whether there is a database customer exclusive data associated with the primary account number, the customer data manager further configured to compare the card customer exclusive data with the database customer exclusive data and to substitute the card customer exclusive data with the database customer exclusive data in a financial transaction when the card customer exclusive data with the database customer exclusive data do not match.

### Claim 10 (depends on 9)

The system of claim 9, wherein the data tag is Field 55.

### Claim 11 (depends on 10)

The system of claim 10, wherein the card customer exclusive data is a data element within Field 55.

### Claim 12 (depends on 11)

The system of claim 11, wherein the card customer exclusive data is data element 9F14C.

### Claim 13 (depends on 12)

The system of claim 12, wherein the card customer exclusive data includes loyalty, rewards, contact or discretionary data.

### Claim 14 (depends on 13)

The system of claim 13, further comprising:
an alert monitor configured to present a cardholder loyalty or rewards information based on the card customer exclusive data or database customer exclusive data.

### Claim 15 (depends on 13)

The system of claim 13, further comprising:
a subscription interface configured to generate a report from the financial transaction with the database customer exclusive data.

### Claim 16 (depends on 13)

The system of claim 13, further comprising:
a subscription interface configured to store information from the financial transaction with the database customer exclusive data in a log.

### Claim 17

A computer-readable medium, encoded with data and instructions, that when executed by a computing-device causes the computing device to:
receive a financial transaction data packet from an acquirer;
extract a data field from the financial transaction data packet, the data field formatted in Tag-Length-Value format;
parse a data tag from the data field;
extract card customer exclusive data from the data tag;
extract a primary account number from the financial transaction data packet;
query a cardholder database with the primary account number to determine whether there is a database customer exclusive data associated with the primary account number;
compare the card customer exclusive data with the database customer exclusive data;
substitute the card customer exclusive data with the database customer exclusive data in a financial transaction when the card customer exclusive data with the database customer exclusive data do not match.

### Claim 18 (depends on 17)

The computer-readable medium of claim 17, wherein the data tag is Field 55.

### Claim 19 (depends on 18)

The computer-readable medium of claim 18, wherein the card customer exclusive data is a data element within Field 55.

### Claim 20 (depends on 19)

The computer-readable medium of claim 19, wherein the card customer exclusive data is data element 9F7C.
