System for maintaining transaction data

• US 20050187865A1
• Filed: 10/22/2004
• Published: 08/25/2005
• Est. Priority Date: 02/24/2004
• Status: Active Grant

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Miller, Thomas M., Grear, Michael B.
• Granted Patent: US 7,419,094 B2
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04M 15/48 Secure or trusted billing, e.g. trusted elements or encryption
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 2215/0156 Secure and trusted billing, e.g. trusted elements, encryption, digital signature, codes or double check mechanisms to secure billing calculation and information
• CPC Class Codes: H04M 2215/0196 Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking

Abstract

According to one embodiment of the invention, an architecture is provided for a data processing system that processes data for a service provider itself or a client of a service provider as in the case of a third party processor. The elements of the architecture can be managed separately. For example, the architecture can be organized around eight subject areas, such as account, party, communication point, presentation instrument, rules, balances, transactions, and product. Relationships between each of the subject areas as well as between sub-types of each subject area can be established to provide flexibility in the management of the data.

Claims

1. A method of associating transaction entries for use by a data processor, said method comprising:

providing a transaction database for storing transaction information;

generating a first transaction internal identifier;

assigning said first transaction internal identifier to data for a first transaction as a first transaction data entry;

storing said first transaction data entry in said transaction database;

generating a second transaction internal identifier;

assigning said second transaction internal identifier to data for a second transaction as a second transaction data entry;

storing said second transaction data entry in said transaction database;

providing a transaction relationship type code for describing the relationship between two transaction entries;

associating said transaction relationship type code with said first transaction internal identifier and with said second transaction internal identifier so as to describe the relationship between said first transaction data entry and said second transaction data entry.

2. The method as described in claim 1 and further comprising:

storing said transaction relationship type code and said first transaction internal identifier and said second transaction internal identifier in a transaction relationship database.

3. The method as described in claim 1 and further comprising:

retrieving said first transaction internal identifier from said transaction database.

4. The method as described in claim 3 and further comprising:

retrieving said second transaction internal identifier from said transaction database.

5. The method as described in claim 1 and further comprising:

associating said first transaction internal identifier as identifying the subject of said relationship; and

associating said second transaction internal identifier as identifying the object of said relationship.

6. The method as described in claim 1 wherein said first transaction internal identifier identifies an authorization transaction for a sale.

7. The method as described in claim 1 wherein said first transaction internal identifier identifies a sales transaction.

8. The method as described in claim 1 wherein said first transaction internal identifier identifies a chargeback transaction.

9. The method as described in claim 1 wherein said first transaction internal identifier identifies a chargeoff transaction.

10. The method as described in claim 1 wherein said first transaction internal identifier identifies retrieval request transaction.

11. The method as described in claim 1 wherein said first transaction internal identifier identifies a reversal transaction.

12. The method as described in claim 1 wherein said first transaction internal identifier identifies an adjustment transaction.

13. The method as described in claim 1 wherein said first transaction internal identifier identifies a return transaction.

14. The method as described in claim 1 wherein said first transaction internal identifier identifies a cash advance transaction.

15. The method as described in claim 1 wherein said first transaction internal identifier identifies a name change transaction for a party.

16. The method as described in claim 1 wherein said first transaction internal identifier identifies an address change transaction for a party.

17. The method as described in claim 1 wherein said first transaction internal identifier identifies a fee assessment transaction.

18. The method as described in claim 1 wherein said first transaction internal identifier identifies an interest assessment transaction.

19. The method as described in claim 1 wherein said first transaction internal identifier identifies bonus points earned transaction.

20. The method as described in claim 1 wherein said first transaction internal identifier identifies an allocation transaction.

21. The method as described in claim 1 wherein said first transaction internal identifier identifies a payment transaction.

22. The method as described in claim 1 wherein said first transaction internal identifier identifies a funds transfer transaction.

23. The method as described in claim 1 wherein said associating said transaction relationship type code with said first transaction internal identifier and with said second transaction internal identifier comprises:

grouping said first transaction internal identifier with said second transaction internal identifier and with said transaction relationship type code.