System for maintaining presentation instrument data

• US 20050187864A1
• 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/971,832
• Publication Number:
  US 20050187864A1
• 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 storing data for use in implementing a transaction for an account, said method comprising:

storing data for identifying a presentation instrument for an account as an entry in a presentation instrument database;

generating an internal identifier for use with said entry;

assigning said internal identifier with said record so as to be able to retrieve said data for identifying said presentation instrument by referencing said internal identifier.

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

storing said internal identifier with said data for identifying said account.

3. The method as described in claim 1 wherein said storing said data for identifying said presentation instrument for said account comprises storing said data for identifying said presentation instrument without storing data identifying said account as part of said record.

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

storing an effective date for said presentation instrument as part of said entry so as to define when said presentation instrument can be used in implementing a transaction.

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

storing a maximum number of uses code as part of said record so as to govern how many times said presentation instrument may be used.

6. A method of storing data for use in implementing a transaction for a party, said method comprising:

storing data for identifying a presentation instrument for a party as an entry in a presentation instrument database;

generating an internal identifier for use with said record;

assigning said internal identifier with said record so as to be able to retrieve said data for identifying said presentation instrument by referencing said internal identifier.

7. The method as described in claim 6 and further comprising:

storing said internal identifier with said data for identifying said presentation instrument.

8. The method as described in claim 6 wherein said storing said data for identifying said presentation instrument for said party comprises storing said data for identifying said presentation instrument without storing data identifying said party as part of said entry.

9. The method as described in claim 6 and further comprising:

storing an effective date for said presentation instrument as part of said entry so as to define when said presentation instrument can be used in implementing a transaction.

10. The method as described in claim 6 and further comprising:

storing a maximum number of uses code as part of said entry so as to govern how many times said presentation instrument may be used.

11. A method of storing data for defining the characteristics of a presentation instrument device, said method comprising:

storing data as an entry for identifying a presentation instrument device for use as a presentation instrument in a presentation instrument device database;

generating an internal identifier for use with said entry;

assigning said internal identifier with said entry so as to be able to retrieve said data for identifying said presentation instrument device by referencing said internal identifier.

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

storing a PI device activation status code for use in determining when said PI device is available for use in conducting a transaction.

13. The method as described in claim 11 wherein said presentation instrument device comprises a plastic card.

14. The method as described in claim 11 wherein said presentation instrument device comprises a smart card.

15. The method as described in claim 11 wherein said presentation instrument device comprises a transponder.

16. The method as described in claim 11 wherein said presentation instrument device comprises a check.

17. A method of storing presentation instrument data, said method comprising:

providing a first database for storing a first record for a presentation instrument;

providing a second database for storing a second entry for a presentation instrument device, wherein said presentation instrument device is associated with said presentation instrument;

assigning a first internal identifier with said presentation instrument;

storing said first internal identifier assigned to said presentation instrument as part of said first entry;

assigning a second internal identifier with said presentation instrument device;

storing said second internal identifier assigned to said presentation instrument device as part of said second entry.

18. The method as described in claim 17 wherein said presentation instrument device is a credit card and wherein said presentation instrument is an account number.

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

storing a presentation instrument effective date as part of said first entry so as to indicate when said presentation instrument is valid.

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

storing a presentation instrument device as part of said first entry so as to indicate when said presentation instrument device is valid.