System for maintaining account data

• US 20050185780A1
• 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.
• Application Number:
  US10/972,152
• Publication Number:
  US 20050185780A1
• Time in Patent Office: Days
• US Class Current: 379/114.170
• 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 an account by a service provider, said method comprising:

providing an account database for use in storing information for a plurality of accounts;

generating a first account internal identifier;

assigning in said account database as an entry for a first account said first account internal identifier and account data describing said first account;

wherein said account data describing said first account comprises an account client identifier.

2. The method as described in claim 1 wherein said account data further comprises:

an account authorization prohibited indicator.

3. The method as described in claim 1 wherein said account data further comprises:

an account authorization prohibited indicator.

4. The method as described in claim 1 wherein said account data further comprises:

an account bankruptcy indicator.

5. The method as described in claim 1 wherein said account data further comprises:

an account charged off indicator.

6. The method as described in claim 1 wherein said account data further comprises:

an account credit balance indicator.

7. The method as described in claim 1 wherein said account data further comprises:

an account delinquent balance indicator.

8. The method as described in claim 1 wherein said account data further comprises:

an account frozen indicator.

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

an account open indicator.

10. The method as described in claim 1 wherein said account data further comprises:

an account original open date indicator.

11. The method as described in claim 1 wherein said account data further comprises:

an account overlimit balance indicator.

12. The method as described in claim 1 wherein said account data further comprises:

an account party PI relationship policy code.

13. The method as described in claim 1 wherein said account data further comprises:

an account party PI relationship state code.

14. The method as described in claim 1 wherein said account data further comprises:

an account revoked indicator.

15. The method as described in claim 1 wherein said account data further comprises:

an account transaction valid catalyzation code.

16. The method as described in claim 1 wherein said account data further comprises:

a close inactive account code.

17. A method of managing a relationship between at least two accounts by a service provider, said method comprising:

providing an account database for use in storing information for a plurality of accounts;

generating a first account internal identifier;

assigning in said account database as an entry for a first account said first account internal identifier and account data describing said first account;

generating a second account identifier;

assigning an account to account relationship type code;

associating as an entry said first account internal identifier, said second account identifier, and said account to account relationship type code so as to indicate the relationship between said first account and said second account;

storing said entry in a computer storage device for use by said service provider.

18. The method as described in claim 17, wherein said second account identifier is a second account internal identifier for identifying an account managed by said service provider.

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

assigning in said account database as an entry for said second account said second account internal identifier and account data describing said second account.

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

designating said first party as a primary participant in said account to account relationship.

21. The method as described in claim 19 and further comprising:

designating said second party as a secondary participant in said account to account relationship.

22. The method as described in claim 20 and further comprising:

designating said second party as a secondary participant in said account to account relationship.

23. The method as described in claim 17 wherein said account to account relationship type code identifies an account diversion relationship.

24. The method as described in claim 17 wherein said account to account relationship type code identifies an account transfer relationship.

25. The method as described in claim 17 wherein said account to account relationship type code identifies a merchant reserve deposit account relationship.