SYSTEM FOR PERSONAL AUTHORIZATION CONTROL FOR CARD TRANSACTIONS

• US 20070205270A1
• Filed: 05/11/2007
• Published: 09/06/2007
• Est. Priority Date: 03/05/2002
• Status: Active Grant

• Current Assignee: Akshey Vij, Lynn Kemper, Robin O'Connell
• Original Assignee: Akshey Vij, Lynn Kemper, Robin O'Connell
• Inventors: Kemper, Lynn, O'Connell, Robin, Vij, Akshey
• Granted Patent: US 7,427,021 B2
• Time in Patent Office: Days
• US Class Current: 235/380
• 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;

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

a web server database interface coupled to the authorization parameter table database, wherein the web server database interface is configured to be in communication with a browser, wherein the browser is capable of allowing a user to select a combination of authorization constraints from a plurality of authorization constraints, and is capable of allowing a user to select specific authorization parameters associated with the selected authorization constraints, wherein the selected authorization constraints and the selected authorization parameters are capable of being used by an authorization subprocessor to determine whether or not a transaction is authorized.

4. The system of claim 3 wherein the plurality of authorization constraints comprises at least two of the following:

(i) a day of the week that a purchase is made, (ii) a time of day that the purchase is made, (iii) a merchant category, (iv) a transaction limit, and (v) a cash advance.

5. The system of claim 3 further comprising the browser operatively coupled to the web server database interface.

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

7. The system of claim 3 wherein the specific authorization parameters include listings of selectable values from which the user may select the specific authorization parameters, the selectable values including specific predetermined amounts of money or days of the week.

8. The system of claim 3 wherein the transaction is a credit card transaction.

9. The system of claim 3 wherein the browser is additionally capable of allowing a user to select an activity report or notification option for notifying the user of purchases made.

10. A method comprising:

receiving at a web server database interface and from a browser in communication with the web server database interface, a selection of a combination of authorization constraints from a plurality of authorization constraints;

receiving at the web server database interface, selections of specific authorization parameters associated with the selected constraints; and

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

wherein an authorization subprocessor uses the selected authorization constraints and the selected authorization parameters to determine if a conducted transaction is authorized or not.

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

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

13. The method of claim 10 wherein the plurality of authorization constraints comprises at least two of the following:

(i) a day of the week that a purchase is made, (ii) a time of day that the purchase is made, (iii) a merchant category, (iv) a transaction limit, and (v) a cash advance

14. The method of claim 10 wherein the specific authorization parameters include listings of selectable values from which the user may select the specific authorization parameters, the selectable values including predetermined amounts of money or days of the week.

15. A method comprising:

selecting a combination of authorization constraints from a plurality of authorization constraints using a web browser;

selecting specific authorization parameters associated with the selected authorization constraints using the web browser; and

providing the selected authorization constraints and the selected authorization parameters to a web server database interface, wherein the web server database interface subsequently stores the selected authorization constraints and the selected authorization parameters in an authorization parameter table database, and wherein an authorization subprocessor uses the selected authorization constraints and the selected authorization parameters to determine if a conducted transaction is authorized or not.

16. The method of claim 15 further comprising using the authorization subprocessor to determine if the transaction is authorized.

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

18. The method of claim 15 wherein the plurality of authorization constraints comprises at least two of the following:

(i) a day of the week that a purchase is made, (ii) a time of day that the purchase is made, (iii) a merchant category, (iv) a transaction limit, and (v) a cash advance

19. The method of claim 15 wherein the specific authorization parameters include listings of selectable values from which the user may select the specific authorization parameters, the selectable values including specific predetermined amounts of money or days of the week.