SYSTEM FOR PERSONAL AUTHORIZATION CONTROL FOR CARD TRANSACTIONS

• US 20080228648A1
• Filed: 05/28/2008
• Published: 09/18/2008
• Est. Priority Date: 03/05/2002
• Status: Abandoned Application

• Current Assignee: Akshey Shawn Vij, Lynn Kemper, Robin O'Connell
• Original Assignee: Akshey Shawn Vij, Lynn Kemper, Robin O'Connell
• Inventors: O'Connell, Robin, Vij, Akshey Shawn, KEMPER, Lynn
• Application Number:
  US12/128,513
• Publication Number:
  US 20080228648A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G07F 7/08 by coded identity card or credit card or other personal identification means without personal verification means G07F7/02

Abstract

An authorization system allows for cardholder-provided parameters to a personal authorization subsystem. The parameters can be selected by the cardholder to limit the authorizations that would otherwise be granted on the card. The parameters can indicate limits by frequency, dollar amount, merchant, geographic location, time of day, combinations thereof, or the like. Authorization for a given transaction, even where authorized by an issuer and a network operator, might be denied based on self-constraints set by the cardholder. In some variations, messages are sent to the cardholder based on constraints set by the cardholder and transactions might be approved and messaged, or denied and messaged.

Claims

1-2. -2. (canceled)

3. A system comprising:

an authorization subprocessor configured to notify a user of a transaction based on a plurality of user selected notification and authorization parameters and constraints;

an authorization parameter table database coupled to the authorization subprocessor; and

an interface coupled to the authorization parameter table database, wherein the interface is configured to allow a user to select a combination of authorization constraints from a plurality of authorization constraints, and allows the user to select authorization parameters associated with the selected authorization constraints, and allows the user to select notification parameters, wherein the selected authorization constraints and the selected authorization parameters and the selected notification parameters are used by the authorization subprocessor to determine whether or not a notification is sent to the user.

4. The system of claim 3 wherein the authorization subprocessor is configured to notify the user of every transaction.

5. The system of claim 3 wherein the authorization subprocessor is configured to notify the user of transactions that satisfy the notification parameters.

6. The system of claim 3 wherein the notification parameters include listings of selectable values from which the user may select the notification parameters.

7. The system of claim 3 wherein the notification parameters include listings of selectable values from which the user may select the notification parameters, the selectable values including merchant types or times of day.

8. The system of claim 3 wherein the authorization subprocessor is configured to notify the user of transactions that do not exceed the selected authorization constraints and parameters but do satisfy the notification parameters.

9. The system of claim 3 wherein the user notification parameters allow a user to select a notification method including a mail message, an e-mail message, a pager message, an instant message, and a telephone message.

10. A method comprising:

receiving at an interface, a user selection of a combination of authorization constraints from a plurality of authorization constraints;

receiving at the interface, user selections of authorization parameters associated with the user selected constraints;

receiving at the interface, user selections of notification parameters; and

storing the user selected authorization constraints, the user selected authorization parameters, and the user selected notification parameters in an authorization parameter table database,

wherein an authorization subprocessor uses the user selected authorization constraints, the user selected authorization parameters, and the user selected notification parameters to determine if the user should be notified of a transaction.

11. The method of claim 10 further comprising using the authorization subprocessor to determine if the user is notified of the transaction.

12. The method of claim 10 wherein the transaction is a credit card transaction.

13. The method of claim 10 wherein the user is notified of every transaction.

14. The method of claim 10 wherein the notification parameters include listings of selectable values from which the user may select the notification parameters, the selectable values including merchant types or times of day.

15. A method comprising:

selecting a combination of user authorization constraints from a plurality of authorization constraints;

selecting user authorization parameters associated with the user selected authorization constraints;

selecting user notification parameters; and

providing the user selected authorization constraints, the user selected authorization parameters, and the user selected notification parameters to an interface, wherein the interface subsequently stores the user selected authorization constraints, the user selected authorization parameters, and the user selected notification parameters in an authorization parameter table database, and wherein an authorization subprocessor uses the user selected authorization constraints, the user selected authorization parameters, and the user selected notification parameters to determine if a user is notified of a transaction.

16. The method of claim 15 further comprising using the authorization subprocessor to determine if a notification is sent to the user.

17. The method of claim 15 wherein the transaction is a credit card transaction.

18. The method of claim 15 wherein the user is notified of every transaction.

19. The method of claim 15 wherein the notification parameters include listings of selectable values from which the user may select the notification parameters, the selectable values including merchant types or times of day.