Abstract: Defining a relationship between an account and a group. Accounts corresponding to different products are linked together to create a group so that group processing can be performed at the group level while independent processing of the accounts is performed at the account level. The relationship between a dependent account and the group is specified by a dependent strategy. A dependent strategy specified group level processing options for the account. The relationships between the accounts and the group are flexible to accommodate changes in the status of the group cardholders.

Abstract: Defining a relationship between an account and a group. Accounts corresponding to different products are linked together to create a group so that group processing can be performed at the group level while independent processing of the accounts is performed at the account level. The relationship between a dependent account and the group is specified by a dependent strategy. A dependent strategy specifies group level processing options for the account. The relationships between the accounts and the group are flexible to accommodate changes in the status of the group cardholders.

Abstract: Processing a group of accounts corresponding to different products. A group of accounts are linked together to create a group so that group processing can be performed at the group level while independent processing of the accounts is performed at the account level. Typically, a group includes a key account and one or more dependent accounts. The relationships between the accounts and the group are flexible to accommodate changes in the status of the group cardholders. Group level processing includes authorizing transactions, applying group payments, creating group statements, creating cardholder communications, and administering reward programs. Each dependent account has an associated dependent strategy that specifies group level processing options for the dependent account.

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.

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.