Field 55 data relationships

• US 20090307075A1
• Filed: 06/05/2008
• Published: 12/10/2009
• Est. Priority Date: 06/05/2008
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Maw, Brian
• Granted Patent: US 7,962,390 B2
• Time in Patent Office: Days
• US Class Current: 705/14.260
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 30/0225 Avoiding frauds
• CPC Class Codes: G06Q 30/0238 at point-of-sale [POS]
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A data mining device, method, and apparatus configured to associate customer exclusive data from a payment card or device after a financial transaction. A financial transaction processing system comprises a report distribution management system, a data relationship manager, and a customer exclusive data association database. The report distribution management system receives financial transaction data. The data relationship manager determines an issuer associated with the financial transaction data, queries a subscription database for subscription data associated with the issuer and a core database for the issuer processing parameters. The processing parameters are applied to the financial transaction data and the subscription data. A customer exclusive data association database is updated with the financial transaction data once the processing parameters are applied.

Claims

1. A method of processing a financial transaction, the method comprising:

receiving financial transaction data;

determining an issuer associated with the financial transaction data;

querying a subscription database for subscription data associated with the issuer, the subscription database being stored on a computer-readable medium;

querying a core database for processing parameters associated with the issuer;

applying the processing parameters to the financial transaction data and the subscription data;

updating the customer exclusive data association database with the financial transaction data once the processing parameters are applied.

2. The method of claim 1 wherein the financial transaction data contains field 55 data.

3. The method of claim 2 further comprising:

associating the field 55 data with a customer record in the customer exclusive data database, the customer exclusive database being stored on a computer-readable medium;

updating the customer record with the associated field 55 data.

4. The method of claim 3 wherein the subscription data includes:

a list of reports, frequency of delivery, list of alerts and conditions under which they will be processed, transaction thresholds, preference data for customer contact, a list of loyalty programs, conditions for assigning rewards, a list of coupons, timeline for promotional periods, a list of data available to acquirers or merchants, a list of tags to be included on reports, conditions to produce risk or fraud reports, or currency preference.

5. The method of claim 4 wherein the processing parameters include:

issuer routing information, acquirer routing information, merchant routing information, processing timeline, settlement window timeline, file preferences, stand-in parameters, data storage timeframe, recovery parameters, timeout parameters, failover conditions, or support staff contact information.

6. The method of claim 5 further comprising:

querying the core database for issuer billing parameters associated with the processing parameters.

7. The method of claim 6 further comprising:

billing the issuer for applying the processing parameters.

8. A system of processing a financial transaction, the system comprising:

a report distribution management system configured to receive financial transaction data;

a data relationship manager configured to determine an issuer associated with the financial transaction data, to query a subscription database for subscription data associated with the issuer, the subscription database being stored on a computer-readable medium, to query a core database for processing parameters associated with the issuer, and to applying the processing parameters to the financial transaction data and the subscription data;

a customer exclusive data association database configured to update the financial transaction data once the processing parameters are applied.

9. The system of claim 8 wherein the financial transaction data contains field 55 data.

10. The system of claim 9 wherein the data relationship manager further associates the field 55 data with a customer record in the customer exclusive data database, the customer exclusive database being stored on a computer-readable medium, and the data relationship manager is configured to update the customer record with the associated field 55 data.

11. The system of claim 10 wherein the subscription data includes:

a list of reports, frequency of delivery, list of alerts and conditions under which they will be processed, transaction thresholds, preference data for customer contact, a list of loyalty programs, conditions for assigning rewards, a list of coupons, timeline for promotional periods, a list of data available to acquirers or merchants, a list of tags to be included on reports, conditions to produce risk or fraud reports, or currency preference.

12. The system of claim 11 wherein the processing parameters include:

issuer routing information, acquirer routing information, merchant routing information, processing timeline, settlement window timeline, file preferences, stand-in parameters, data storage timeframe, recovery parameters, timeout parameters, failover conditions, or support staff contact information.

13. The system of claim 12 wherein the data relationship manager further queries the core database for issuer billing parameters associated with the processing parameters.

14. The system of claim 13 further comprising:

a subscription interface configured to bill the issuer for applying the processing parameters.

15. A computer readable medium, encoded with data and instructions, that when executed by a computing-device causes the computing-device to:

receive financial transaction data;

determine an issuer associated with the financial transaction data;

query a subscription database for subscription data associated with the issuer, the subscription database being stored on a computer-readable medium;

query a core database for processing parameters associated with the issuer;

apply the processing parameters to the financial transaction data and the subscription data;

update the customer exclusive data association database with the financial transaction data once the processing parameters are applied.

16. The computer readable medium of claim 15 wherein the financial transaction data contains field 55 data.

17. The computer readable medium of claim 16 further comprising:

associate the field 55 data with a customer record in the customer exclusive data database, the customer exclusive database being stored on a computer-readable medium;

update the customer record with the associated field 55 data.

18. The computer readable medium of claim 17 wherein the subscription data includes:

a list of reports, frequency of delivery, list of alerts and conditions under which they will be processed, transaction thresholds, preference data for customer contact, a list of loyalty programs, conditions for assigning rewards, a list of coupons, timeline for promotional periods, a list of data available to acquirers or merchants, a list of tags to be included on reports, conditions to produce risk or fraud reports, or currency preference.

19. The computer readable medium of claim 18 wherein the processing parameters include:

issuer routing information, acquirer routing information, merchant routing information, processing timeline, settlement window timeline, file preferences, stand-in parameters, data storage timeframe, recovery parameters, timeout parameters, failover conditions, or support staff contact information.

20. The computer readable medium of claim 19 further comprising:

query the core database for issuer billing parameters associated with the processing parameters.