System for maintaining account and presentation instrument data

• US 20050187782A1
• Filed: 10/22/2004
• Published: 08/25/2005
• Est. Priority Date: 02/24/2004
• Status: Abandoned Application

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Grear, Michael B., Donlin, Gretchen, Bell, Richard T., Harrington, Teresa M.
• Application Number:
  US10/971,951
• Publication Number:
  US 20050187782A1
• Time in Patent Office: Days
• US Class Current: 705/64
• 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 storing data for a service business, said method comprising:

storing party data identifying a party as a separate set of data;

storing account data identifying an account as a separate set of data;

storing presentation instrument data identifying a presentation instrument as a separate set of data;

wherein said party data, said account data, and said presentation instrument data identify a party on an account accessible via said presentation instrument.

2. The method as described in claim 1 wherein said party data, said account data, and said presentation instrument data are stored on separate databases from one another.

3. The method as described in claim 1 wherein said party data, said account data, and said presentation instrument data are related together on a separate database.

4. The method as described in claim 1 and further comprising a first identifier assigned to said party data and a second identifier assigned to said account data and wherein said first identifier is associated with said second identifier so as to relate said party data with said account data.

5. The method as described in claim 1 and further comprising a first identifier assigned to said presentation instrument data and a second identifier assigned to said account data and wherein said first identifier is associated with said second identifier so as to relate said presentation instrument data with said account data.

6. The method as described in claim 1 and further comprising. assigning first identifier with said party data;

assigning a second identifier with said account data;

assigning a third identifier with said presentation instrument data;

associating said first identifier with said second identifier and with said third identifier so as to relate said party data with said account data and with said presentation instrument data.

7. The method as described in claim 6 wherein said associating said first identifier with said second identifier and with said third identifier comprises associating said first, second, and third identifiers in a set of identifiers.

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

storing a set of associative data for relating said party data, said account data, and said presentation instrument data.

9. The method as described in claim 1 wherein said associative data comprises:

a first internal identifier assigned to a set of data in said party data, a second internal identifier assigned to a set of data in said account data, and a third internal identifier assigned to a set of data in said presentation instrument data; and

wherein said first internal identifier, said second internal identifier, and said third internal identifier relate at least one party and at least one presentation instrument with an account.

10. The method as described in claim 9 and further comprising a fourth internal identifier for relating a second party with said account.

11. The method as described in claim 9 and further comprising a fourth internal identifier for relating a second presentation instrument with said account.

12. The method as described in claim 9 and further comprising a fourth internal identifier for relating a second party with said account and a fifth internal identifier for relating a second presentation instrument with said account.

13. A system for storing data for a service business, said system comprising:

a party database storing party data identifying a party as a separate set of data;

an account database storing account data identifying an account as a separate set of data;

a presentation instrument database storing presentation instrument data identifying a presentation instrument as a separate set of data;

wherein said party data, said account data, and said presentation instrument data identify a party on an account accessible via said presentation instrument.

14. The system as described in claim 13 wherein said party database, said account database, and said presentation instrument database each have a separate processor.

15. The system as described in claim 13 and further comprising:

a party-account-presentation instrument database for relating said party data and said account data and said presentation instrument data with one another.

16. The system as described in claim 13 and further comprising an associative database comprising a first identifier assigned to said party data and a second identifier assigned to said account data and wherein said first identifier is further associated with said second identifier so as to relate said party data with said account data.

17. The system as described in claim 13 and further comprising an associative database comprising a first identifier assigned to said presentation instrument data and a second identifier assigned to said account data and wherein said first identifier is further associated with said second identifier so as to relate said presentation instrument data with said account data.

18. The system as described in claim 13 and further comprising an associative database comprising:

a first identifier assigned to said party data;

a second identifier assigned to said account data;

a third identifier assigned to said presentation instrument data;

wherein said first identifier and said second identifier and said third identifier are associated so as to relate said party data with said account data and with said presentation instrument data.

19. The system as described in claim 18 wherein said first identifier, said second identifier, and said third identifier are associated in a set of identifiers.

20. The system as described in claim 13 and further comprising:

a set of associative data for relating said party data, said account data, and said presentation instrument data.

21. The system as described in claim 20 wherein said associative data comprises:

a first internal identifier assigned to a set of data in said party data, a second internal identifier assigned to a set of data in said account data, and a third internal identifier assigned to a set of data in said presentation instrument data; and

wherein said first internal identifier, said second internal identifier, and said third internal identifier relate at least one party and at least one presentation instrument with an account.

22. The system as described in claim 21 and further comprising a fourth internal identifier for relating a second party with said account.

23. The system as described in claim 21 and further comprising a fourth internal identifier for relating a second presentation instrument with said account.

24. The system as described in claim 21 and further comprising a fourth internal identifier for relating a second party with said account and a fifth internal identifier for relating a second presentation instrument with said account.