Methods for Customizing Secured Transactions that are Verified by a Money Source

Abstract

Methods for providing secure transactions in which a customization parameter and an encrypted transaction validation code are received from a user to positively identify a transaction for a user who has a first entity identifier. The validation code and first entity identifier are used by a money source which electronically verifies that the transaction is valid by use of the first entity identifier and the validation code while the first transaction is customized through use of the customization parameter.

1 . A method for providing one or more secure transactions between a first entity and at least one additional entity comprising:
 (a) receiving a customization parameter from the first entity;   (b) electronically generating an encrypted transaction validation code which positively identifies a transaction for a first entity, the first entity having a first entity identifier;   (c) electronically transferring the validation code and the first entity identifier to a second entity in a first transaction;   (d) electronically transferring the validation code and the first entity identifier from the second entity to a money source;   (e) electronically verifying that the first transaction is valid with the money source by use of the first entity identifier and the validation code; and   (f) customizing the first transaction through use of the customization parameter;   wherein the first entity identifier is transferred to the money source as an account number and the validation code is transferred to the money in a non-account data field.   
     
     
         2 . A method, comprising:
 (a) receiving an encrypted transaction validation code which positively identifies a first transaction for a first entity, the first entity having a first entity identifier;   (b) receiving a customization parameter for the first transaction;   (c) electronically verifying that the first transaction is valid by use of the first entity identifier and the validation code; and   (d) customizing the first transaction through use of the customization parameter;   wherein the first entity identifier is transferred to a money source as an account number and the validation code is transferred to the money source in a non-account data field.   
     
     
         3 . The method as recited in  claim 2 , wherein the validation code is formed by using a Triple Data Encryption Standard algorithm (“TEDS”). 
     
     
         4 . The method as recited in  claim 2 , wherein the customization variable is used to select between a first handling option and a second handling option between the money source and the first entity. 
     
     
         5 . The method as recited in  claim 4 , wherein the first and the second handling options are mechanisms to bill a first account and a second account and the first account and the second account are two separate accounts. 
     
     
         6 . The method as recited in  claim 5 , wherein the first entity is sent a single bill for charges to the first account and the second account. 
     
     
         7 . The method as recited in  claim 6 , wherein the first account is established with a first money source and the second account is established with a second money source and the second money source is different from the first money source. 
     
     
         8 . The method as recited in  claim 5 , wherein the first account is a credit account and the second account is a credit account. 
     
     
         9 . The method as recited in  claim 5 , wherein the first entity is sent a first bill for the first account and a separate bill for the second amount. 
     
     
         10 . The method as recited in  claim 4 , wherein the first and the second handling options are a first and a second mechanism for dealing with distribution of information concerning a plurality of payment card transactions. 
     
     
         11 . The method as recited in  claim 10 , wherein the first mechanism restricts the distribution from the money source to a third party of information relating to any payment card transaction in which the user payment card number is generated by use of a first user key. 
     
     
         12 . The method as recited in  claim 10 , wherein the first mechanism restricts the distribution from the money source to a second entity of personal information of the first entity relating to any payment card transaction in which the user payment card number is generated by use of a first user key. 
     
     
         13 . The method as recited in  claim 11 , wherein the money source receives consideration from the first entity for use of the first mechanism. 
     
     
         14 . The method as recited in  claim 10 , wherein the second mechanism permits the distribution from the money source to a third party of information relating to any payment card transaction in which the user payment card number is generated by use of a second user key. 
     
     
         15 . The method as recited in  claim 10 , wherein the second mechanism permits the distribution from the money source to a second entity of personal information of the first entity relating to any payment card transaction in which the user payment card number is generated by use of a second user key. 
     
     
         16 . The method as recited in  claim 14 , wherein the money source provides the first entity with consideration for use of the second mechanism. 
     
     
         17 . The method as recited in  claim 4 , wherein the first and the second handling options provide a mechanism for classifying the nature of the plurality of payment card transactions. 
     
     
         18 . The method as recited in  claim 4 , wherein the first handling option is used for business transactions and the second handling option is used for personal transactions. 
     
     
         19 . The method as recited in  claim 4 , wherein the first and the second handling options provide a mechanism for identifying either a first user or a second user as the first entity. 
     
     
         20 . The method as recited in  claim 19 , wherein approval of a payment card transaction for the first user is subject to different restrictions than approval of a payment card transaction for the second user. 
     
     
         21 . The method as recited in  claim 4 , wherein the first and the second handling options provide a mechanism for controlling what information is reported about the plurality of payment card transactions in a billing statement. 
     
     
         22 . The method as recited in  claim 2  wherein the money source obtains the customization variable from the validation code. 
     
     
         23 . The method as recited in  claim 2  wherein the customization variable is received through use of at least one button. 
     
     
         24 . A method for providing one or more secure transactions between a first entity and at least one additional entity comprising:
 (a) receiving an encrypted transaction validation code which positively identifies a first transaction for a first entity, the first entity having a first entity identifier;   (b) receiving a customization parameter for the first transaction;   (c) electronically verifying that the first transaction is valid by use of the first entity identifier and the validation code; and   (d) customizing the first transaction through use of the customization parameter;   wherein the money source validates the validation code by duplicating the encryption process used to create the validation code and by then comparing the result to the validation code received with the first transaction.   
     
     
         25 . The method as recited in  claim 24 , wherein the customization variable is used to select between a first handling option and a second handling option between the money source and the first entity. 
     
     
         26 . The method as recited in  claim 25 , wherein the first and the second handling options are mechanisms to bill a first account and a second account and the first account and the second account are two separate accounts. 
     
     
         27 . The method as recited in  claim 26 , wherein the first entity is sent a single bill for charges to the first account and the second account. 
     
     
         28 . The method as recited in  claim 27 , wherein the first account is established with a first money source and the second account is established with a second money source and the second money source is different from the first money source. 
     
     
         29 . The method as recited in  claim 26 , wherein the first account is a credit account and the second account is a credit account. 
     
     
         30 . The method as recited in  claim 26 , wherein the first entity is sent a first bill for the first account and a separate bill for the second amount. 
     
     
         31 . The method as recited in  claim 25 , wherein the first and the second handling options are a first and a second mechanism for dealing with distribution of information concerning a plurality of payment card transactions. 
     
     
         32 . The method as recited in  claim 31 , wherein the first mechanism restricts the distribution from the money source to a third party of information relating to any payment card transaction in which the user payment card number is generated by use of a first user key. 
     
     
         33 . The method as recited in  claim 31 , wherein the first mechanism restricts the distribution from the money source to a second entity of personal information of the user relating to any payment card transaction in which the user payment card number is generated by use of a first user key. 
     
     
         34 . The method as recited in  claim 32 , wherein the money source receives consideration from the first entity for use of the first mechanism. 
     
     
         35 . The method as recited in  claim 31 , wherein the second mechanism permits the distribution from the money source to a third party of information relating to any payment card transaction in which the user payment card number is generated by use of a second user key. 
     
     
         36 . The method as recited in  claim 31 , wherein the second mechanism permits the distribution from the money source to a second entity of personal information of the first entity relating to any payment card transaction in which the user payment card number is generated by use of a second user key. 
     
     
         37 . The method as recited in  claim 35 , wherein the money source provides the user with consideration for use of the second mechanism. 
     
     
         38 . The method as recited in  claim 25 , wherein the first and second handling options provide a mechanism for classifying the nature of a plurality of payment card transactions. 
     
     
         39 . The method as recited in  claim 25 , wherein the first handling option is used for business transactions and the second handling option is used for personal transactions. 
     
     
         40 . The method as recited in  claim 25 , wherein the first and the second handling options provide a mechanism for identifying either a first user or a second user as the first entity. 
     
     
         41 . The method as recited in  claim 40 , wherein approval of a payment card transaction for the first user is subject to different restrictions than approval of a payment card transaction for the second user. 
     
     
         42 . The method as recited in  claim 25 , wherein the first and the second handling options provide a mechanism for controlling what information is reported about a plurality of payment card transactions in a billing statement. 
     
     
         43 . The method as recited in  claim 24  wherein the money source obtains the customization variable from the validation code. 
     
     
         44 . A method, comprising:
 (a) receiving an encrypted transaction validation code which positively identifies a first transaction for a first entity, the first entity having a first entity identifier;   (b) receiving a customization parameter for the first transaction;   (c) electronically verifying that the first transaction is valid by use of the first entity identifier and the validation code; and   (d) customizing the first transaction through use of the customization parameter;   wherein the validation code is, at least in part, encrypted, and   wherein the money source validates the validation code by duplicating a validation code encryption process and by then comparing the result to the validation code received with the first transaction.   
     
     
         45 . The method as recited in  claim 44 , wherein the customization variable is used to select between a first handling option and a second handling option between the money source and the first entity. 
     
     
         46 . The method as recited in  claim 45 , wherein the first and the second handling options are mechanisms to bill a first account and a second account and the first account and the second account are two separate accounts. 
     
     
         47 . The method as recited in  claim 46 , wherein the first entity is sent a single bill for charges to the first account and the second account. 
     
     
         48 . The method as recited in  claim 47 , wherein the first account is established with a first money source and the second account is established with a second money source and the second money source is different from the first money source. 
     
     
         49 . The method as recited in  claim 46 , wherein the first account is a credit account and the second account is a credit account. 
     
     
         50 . The method as recited in  claim 46 , wherein the first entity is sent a first bill for the first account and a separate bill for the second amount. 
     
     
         51 . The method as recited in  claim 45 , wherein the first and the second handling options are a first and a second mechanism for dealing with distribution of information concerning a plurality of payment card transactions. 
     
     
         52 . The method as recited in  claim 51 , wherein the first mechanism restricts the distribution from the money source to a third party of information relating to any payment card transaction in which the user payment card number is generated by use of the first user key. 
     
     
         53 . The method as recited in  claim 51 , wherein the first mechanism restricts the distribution from the money source to a second entity of personal information of the first entity relating to any payment card transaction in which the user payment card number is generated by use of a first user key. 
     
     
         54 . The method as recited in  claim 52 , wherein the money source receives consideration from the first entity for use of the first mechanism. 
     
     
         55 . The method as recited in  claim 51 , wherein the second mechanism permits distribution from the money source to a third party of information relating to any payment card transaction in which the user payment card number is generated by use of a second user key. 
     
     
         56 . The method as recited in  claim 51 , wherein the second mechanism permits distribution from the money source to a second entity of personal information of the first entity relating to any payment card transaction in which the user payment card number is generated by use of a second user key. 
     
     
         57 . The method as recited in  claim 55 , wherein the money source provides the user with consideration for use of the second mechanism. 
     
     
         58 . The method as recited in  claim 45 , wherein the first and second handling options provide a mechanism for classifying the nature of a plurality of payment card transactions. 
     
     
         59 . The method as recited in  claim 45 , wherein the first handling option is used for business transactions and the second handling option is used for personal transactions. 
     
     
         60 . The method as recited in  claim 45 , wherein the first and the second handling options provide a mechanism for identifying either a first user or a second user as the first entity. 
     
     
         61 . The method as recited in  claim 60 , wherein approval of a payment card transaction for the first user is subject to different restrictions than approval of a payment card transaction for the second user. 
     
     
         62 . The method as recited in  claim 45 , wherein the first and the second handling options provide a mechanism for controlling what information is reported about a plurality of payment card transactions in a billing statement. 
     
     
         63 . The method as recited in  claim 44  wherein the money source obtains the customization variable from the validation code. 
     
     
         64 . The method as recited in  claim 44  wherein the customization variable is received through use of at least one button.