System and method for managing accounts

• US 20030172039A1
• Filed: 03/05/2002
• Published: 09/11/2003
• Est. Priority Date: 03/05/2002
• Status: Active Grant

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Beck, Darren D., Guy, Robert C., Goering, Douglas A., Rivera, David G., Hames, Tony D., Snider, Diane Lyn, Bright, George D., Harrington, William F.
• Granted Patent: US 6,993,510 B2
• Time in Patent Office: Days
• US Class Current: 705/68
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/3676 Balancing accounts
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/403 Solvency checks

Abstract

A system for managing credit card accounts or the like, having a database for storing a permanent customer ID associated with each cardholder, an account ID for each account accessible by the cardholder, a presentation ID (card number) appearing on each card, and a role identifier. When a transaction is conducted at a terminal, the presentation ID is provided to a database management system, which then can retrieve the customer ID and the account ID (for the account being accessed). If a card is lost, stolen or otherwise rendered unusable, a security suspense record is inserted into the database in an account ID filed associated with the affected presentation ID. When the presentation ID associated with the lost or stolen card is provided to the system, the security suspense record is retrieved and causes the transaction to be invalidated. All other presentation IDs (and associated cards) for the affected account can continue to be used, thus eliminating the need to close the account. The role identifier permits account criteria (e.g., financial responsibility, credit limits, purchase restrictions, etc.) to be established for individual cardholders.

Claims

1. A system for managing accounts, wherein more than one customer may be associated with each account, wherein each customer has a role relating to such account, and wherein a customer may conduct a transaction for such account by using a presentation instrument issued to that customer, the system comprising:

a database for storing a customer ID associated with each customer, an account ID associated with each account, and a presentation ID associated with each presentation instrument, the database structured for relating each presentation ID to a specific customer and to one account used by that specific customer; and

a database management system for managing the data stored in the database and for posting transaction data to any account in response to receiving a presentation ID with such transaction data, the presentation ID being used by the data management system to access the account and thereby reflect that the transaction has been conducted for the account.

2. The system of claim 1, wherein the customer ID is permanent and does not appear on the presentation instrument as the presentation ID, so that if the presentation instrument is no longer useable, a new presentation ID may be issued and the new presentation ID related to the permanent customer ID in the database.

3. The system of claim 2, wherein the database management system assigns a security suspense record to the account ID for the account associated with the presentation instrument that is no longer useable.

4. The system of claim 3, wherein the database management system invalidates any transaction where a presentation ID is received that relates to an account ID having a security suspense record.

5. The system of claim 1, wherein the customer ID is permanent and if a new accounts is established for a customer, the account ID for the new account may be related to the permanent customer ID of that customer.

6. The system of claim 1, wherein the customer ID, and each account ID and presentation ID are different.

7. The system of claim 1, wherein the customer ID is different than either the account ID and presentation ID.

8. The system of claim 1, wherein the presentation ID may be the same as the account ID, but is different than the customer ID

9. The system of claim 1, wherein a customer may have one of at least two roles for any account, wherein one of those roles is a primary cardholder role, having primary financial responsibility for that account.

10. The system of claim 9, wherein the other of the roles is a secondary cardholder role, having the ability to conduct transactions under the account but not having primary financial responsibility for that account.

11. The system of claim 9, wherein the other of the roles provides the ability to conduct transactions under the account, with those transactions limited by a credit limit.

12. The system of claim 9, wherein the other of the roles has the ability to conduct transactions under the account, with such transactions tracked to enable the card issuer to market services to the customer having the other of the roles.

13. The system of claim 1, wherein the presentation instrument is a credit card, and wherein the presentation ID is a card number appearing on the credit card.

14. The system of claim 1, wherein the database is a relational database.

15. A method for managing accounts accessible by customers in order to conduct transactions, wherein a customer may conduct a transaction for at least one of the accounts by using a presentation instrument issued to that customer by an issuing institution, the method comprising:

providing a database;

storing in the database a customer ID associated with each customer, an account ID associated with each account, and a presentation ID used by each customer for accessing at least one of the accounts, the presentation ID being different than the customer ID;

structuring the database in order to relate, to each customer ID, the account ID for at least one account accessible by that customer, and the presentation ID issued to that customer for accessing such account; and

managing the database in order to post a transaction by a specific customer to a specific account in response to receiving transaction data with the presentation ID issued to the specific customer, the presentation ID being used by the data management system to retrieve the account ID of the specific account and thereby associate the transaction data with the specific customer and with the specific account.

16. The method of claim 15, further comprising:

storing a suspense record in connection with the account ID, when the presentation ID associated with that account ID is not longer useable.

17. The method claim 15, wherein an account may be accessed by more than one customer, and wherein the method further comprises:

providing a plurality of customer roles in connection with such account, wherein at least one of the roles is one having primary financial responsibility for the account.

18. The method of claim 17, wherein another one of the roles is one not having primary financial responsibility for the account.

19. The method claim 17, wherein credit limits for transactions conducted by customers for the account may be different for each of the customer roles.

20. The method claim 15, further comprising:

establishing transaction criteria for at least one of the roles, so that when the criteria is met, financial service information may be provided by the issuing institution to the customer having that role.

21. The method of claim 15, further comprising:

storing multiple account IDs in connection with the one customer ID associated with a customer having access to each account associated with the multiple account IDs; and

storing multiple presentation IDs, one associated with each of the multiple account IDs.

22. The method of claim 21, wherein each presentation ID is different than its associated account ID.

23. A system for managing accounts, wherein more than one customer may conduct a transaction in connection with an account, wherein each customer has a role relating to the account, and wherein a customer may conduct a transaction for the account by using a presentation instrument issued to that customer, the system comprising:

means for storing a customer ID associated with each customer, an account ID associated with each account, a presentation ID associated with each presentation instrument, and a role identifier associated with each customer and identifying a role that such customer has in connection with an account, the database structured for relating each presentation ID to both a specific customer and to an account used by that specific customer; and

means for managing the data stored in the database and for posting transaction data to any account in response to receiving a presentation ID with such transaction data, the presentation ID being used by the data management system to access the account and thereby reflect that the transaction has been conducted in connection with the account.