Methods for Providing Secure Transactions

Abstract

Methods in which an encrypted transaction validation code is received which positively identifies a first transaction for a first entity, the first entity having a first entity identifier, and the first transaction is electronically verified as being valid by use of the first entity identifier and the validation code. The first entity identifier can be transferred as an account number and the validation code transferred to the money source in a non-account data field. A money source can validate 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. The validation code can be, at least in part, encrypted, and a money source can validate the validation code by duplicating a validation code encryption process and by then comparing the result to the validation code received.

1 . 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; and   (b) electronically verifying that the first transaction is valid by use of the first entity identifier and the validation code;   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.   
     
     
         2 . The method as recited in  claim 1 , wherein the validation code is transferred to the money source in an account number and the first entity identifier is transferred to the money source in a non-account data field. 
     
     
         3 . The method as recited in  claim 1 , wherein the validation code is used by the money source to identify a physical device to generate the validation code. 
     
     
         4 . The method as recited in  claim 1 , wherein the validation code is formed by using a Triple Data Encryption Standard algorithm (“TEDS”). 
     
     
         5 . The method as recited in  claim 1 , wherein the validation code and the first entity identifier are received in a form. 
     
     
         6 . The method as recited in  claim 1 , wherein the validation code is transmitted through an Address Verification System Billing Address. 
     
     
         7 . The method as recited in  claim 1 , wherein a unique validation code is assigned to each first entity which is valid only for at least one of mail order, telephone order, and Internet transactions, and which is used for multiple transactions with multiple merchants. 
     
     
         8 . The method as recited in  claim 1 , wherein the unique validation code includes a customization variable that is used to customize the first transaction. 
     
     
         9 . The method as recited in  claim 8 , further comprising sending the first entity a replacement apparatus for generating the encrypted transaction validation code in response to the customization variable. 
     
     
         10 . The method as recited in  claim 1 , wherein the validation code is readable from either a Track 1 or a Track 2 of an electronic device. 
     
     
         11 . The method as recited in  claim 10 , wherein the electronic device is an electronic card. 
     
     
         12 . The method as recited in  claim 1  wherein an electronic device generates the validation code. 
     
     
         13 . 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; and   (b) electronically verifying that the first transaction is valid by use of the first entity identifier and the validation code;   wherein a 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.   
     
     
         14 . The method as recited in  claim 13 , wherein the validation code is transferred to the money source in an account number and the first entity identifier is transferred to the money source in a non-account data field. 
     
     
         15 . The method as recited in  claim 13 , wherein the first entity identifier is transferred to the money source as an account number and the validation code is transferred to the money source in a non-account data field. 
     
     
         16 . The method as recited in  claim 13 , wherein the validation code is used by the money source to identify a physical device used to generate the validation code. 
     
     
         17 . The method as recited in  claim 13 , wherein the validation code is formed by using a Triple Data Encryption Standard algorithm (“TDES”). 
     
     
         18 . The method as recited in  claim 13  wherein the validation code and first entity identifier are received in a form. 
     
     
         19 . The method as recited in  claim 13  wherein the validation code is transmitted through an Address Verification System Billing Address. 
     
     
         20 . The method as recited in  claim 13  wherein a unique validation code is assigned to each first entity which is valid only for at least one of mail order, telephone order, and Internet transactions, and which is used for multiple transactions with multiple merchants. 
     
     
         21 . The method as recited in  claim 13  wherein the validation code is readable from either a Track 1 or a Track 2 of an electronic device. 
     
     
         22 . 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; and   (b) electronically verifying that the first transaction is valid by use of the first entity identifier and the validation code;   wherein the validation code is, at least in part, encrypted, and   wherein a 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.   
     
     
         23 . The method as recited in  claim 22 , wherein the validation code is transferred to the money source in an account number and the first entity identifier is transferred to the money source in a non-account data field. 
     
     
         24 . The method as recited in  claim 22 , wherein the first entity identifier is transferred to the money source as an account number and the validation code is transferred to the money source in a non-account data field. 
     
     
         25 . The method as recited in  claim 22 , wherein the validation code is used by the money source to identify a physical device used to generate the validation code. 
     
     
         26 . The method as recited in  claim 22 , wherein the validation code is formed by using a Triple Data Encryption Standard algorithm (“TDES”). 
     
     
         27 . The method as recited in  claim 22  wherein the validation code and first entity identifier are transferred to the second entity in a form. 
     
     
         28 . The method as recited in  claim 22  wherein the validation code is transmitted through an Address Verification System Billing Address. 
     
     
         29 . The method as recited in  claim 22  wherein the validation code is readable from either a Track 1 or a Track 2 of an electronic device.