System for maintaining party data

• US 20050187938A1
• 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, Harrington, Teresa M.
• Application Number:
  US10/972,093
• Publication Number:
  US 20050187938A1
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 for use by a data processor that processes data for clients, said method comprising:

providing a party database for use in storing information about a plurality of parties;

generating a first internal party identifier;

assigning in said party database said first internal party identifier to party information describing a first party;

providing an agreement database for use in storing data about a plurality of agreements, each of said agreements having at least one agreement attribute;

generating a first internal agreement identifier;

assigning in said agreement database said first internal agreement identifier to said first agreement so that said data processor can identify said first agreement;

associating said first internal party identifier and said first internal agreement identifier so as identify said first party as playing a role on said first agreement.

2. The method as described in claim 1 wherein said associating comprises:

creating a data entry wherein said data entry comprises;

said first internal party identifier;

said first internal agreement identifier.

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

associating said data entry with an Agreement Party Role Type Code attribute.

4. The method as described in claim 3 wherein said Agreement Party Role Type Code attribute identifies said party as playing a merchant role on said first agreement.

5. The method as described in claim 3 wherein said Agreement Party Role Type Code attribute identifies said party as playing a processor role on said first agreement.

6. The method as described in claim 3 wherein said Agreement Party Role Type Code attribute identifies said party as playing an association role on said first agreement.

7. The method as described in claim 3 wherein said Agreement Party Role Type Code attribute identifies said party as playing a partner affiliate role on said first agreement.

8. The method as described in claim 3 wherein said Agreement Party Role Type Code attribute identifies said party as playing a third party role on said first agreement.

9. The method as described in claim 3 wherein said Agreement Party Role Type Code attribute identifies said party as playing a client role on said first agreement.

10. The method as described in claim 3 wherein said Agreement Party Role Type Code attribute identifies said party as playing a customer role on said first agreement.

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

associating said data entry with an Agreement Party Role Effective Date attribute so as to identify a point in time when the role played by said first party becomes effective.

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

associating said data entry with an Agreement Party Role End Date attribute so as to identify a point in time when the role played by said first party comes to an end.

13. A method of establishing a relationship between at least two parties to an agreement, said method for use by a service provider itself or a service provider that processes data for clients, said method comprising:

providing a party database for use in storing information about a plurality of parties;

generating a first internal party identifier;

assigning in said party database said first internal party identifier to, party information describing a first party;

generating a second internal party identifier;

assigning in said party database said second internal party identifier to party information describing a second party;

providing a party to party relationship database for recording a relationship between at least two parties;

receiving said first internal party identifier via said party database;

receiving said second internal party identifier via said party database;

associating said first internal party identifier and said second internal party identifier in said party to party relationship database so as to record a relationship between said first party and said second party.

14. The method as described in claim 13 wherein said associating said first internal party identifier and said second internal party identifier comprises:

creating a data entry wherein said data entry comprises;

said first internal party identifier; and

said first internal agreement identifier.

15. The method as described in claim 14 and further comprising:

associating said data entry with a Party to Party Relationship General Classification Type Code attribute so as to identify the type of relationship established between said first party and said second party.

16. The method as described in claim 14 wherein said Party to Party Relationship General Classification Type Code attribute identifies an individual to organization relationship.

17. The method as described in claim 14 wherein said Party to Party Relationship General Classification Type Code attribute identifies an individual to organization relationship.

18. The method as described in claim 17 and further comprising:

associating said data entry with an Individual to Organization Relationship Classification Type Code attribute.

19. The method as described in claim 18 wherein said Individual to Organization Relationship Classification Type Code attribute identifies an organization contact relationship.

20. The method as described in claim 18 wherein said Individual to Organization Relationship Classification Type Code attribute identifies an individual customer relationship.

21. The method as described in claim 14 wherein said Party to Party Relationship General Classification Type Code attribute identifies an organization to organization relationship.

22. The method as described in claim 14 wherein said Party to Party Relationship General Classification Type Code attribute identifies an organization to organization unit relationship.

23. The method as described in claim 14 wherein said Party to Party Relationship General Classification Type Code attribute identifies an organization unit relationship.

24. The method as described in claim 14 wherein said Party to Party Relationship General Classification Type Code attribute identifies an individual to individual relationship.