METHOD AND APPARATUS TO PROVIDE SECURING PURCHASE TRANSACTIONS OVER A COMPUTER NETWORK

Abstract

A method and structure for providing secure credit facility transactions for purchasing goods and services over a computer network such as the Internet that stores user's privileged information and other transactional data on the user's own computer. The method includes encryption of all information before or during its storage to the user's hard drive. The method and system includes the ability for the user to complete electronic commerce (e-commerce) transactions without revealing certain of the encrypted information, such as credit card numbers, to the merchant. The method and system creates and controls sub-accounts on a single credit facility, such as a credit card, with unique user reporting and corresponding password identifiers. The method and system sets and control sub-accounts spending amounts and replenishment periods. The method enables the user to create and control recurring debit accounts on a single credit facility, such as a credit card, over varying transactional periods.

Claims

1. A method of securing transactions over a computer network comprising: encrypting customer information comprising a customer address and a customer credit card number as a plurality of customer codes on a storage device on a customer computer, said customer computer is connected to said computer network, and said customer information is stored on said storage device only in encrypted form; requiring a computer system identifier of said customer computer, and one of a private key, a password, and a personal access codes of a customer as an entry to said customer computer to access said customer codes on said storage device of said customer computer; supplying a customer code of said customer codes to a merchant in a transaction over said computer network; forwarding said customer code to a financial institution over said computer network; decrypting said customer code at said financial institution; and returning an authorization decision from said financial institution to said merchant over said computer network, said encrypting customer information comprises encrypting a different user name and different payment rules for each of said customer codes, and said payment rules comprise transaction limits, credit limits, and periodic spending limits.

2. The method in claim 1, further comprising passing said customer codes through an intermediate confirmation site on said computer network prior to forwarding said customer codes to said financial institution over said computer network, said intermediate confirmation site confirming whether said customer codes has a proper encryption format.

3. The method in claim 1, each of said customer codes includes a unique payment method.

4. The method in claim 1, each of said customer codes includes a different credit card number.

5. The method in claim 1, a group of said customer codes identifies a single credit organization for payment.

6. The method in claim 1, said periodic spending limits include monthly and weekly spending limits.

7. The method in claim 1, said supplying said customer code to said merchant supplies only encrypted information to said merchant.

8. A method of securing transactions over the Internet comprising: encrypting customer information comprising customer address and customer credit card number as a plurality of customer codes on a storage device on a customer computer, said customer computer is connected to said Internet, said customer information is stored on said storage device only in encrypted form; requiring a computer system identifier of said customer computer, and one of a private key, a password, and a personal access codes of a customer as an entry to said customer computer to access said customer codes on said storage device of said customer computer; supplying a customer code of said customer codes to a merchant in a transaction over said Internet; forwarding said customer code to a financial institution over said Internet; decrypting said customer code at said financial institution; and returning an authorization decision from said financial institution to said merchant over said Internet, said encrypting customer information comprises encrypting a different user name and different payment rules for each of said customer codes, and said payment rules comprise transaction limits, credit limits, and periodic spending limits.

9. The method in claim 8, further comprising passing said customer codes through an intermediate confirmation site on said Internet prior to forwarding said customer codes to said financial institution over said Internet, said intermediate confirmation site confirming whether said customer codes has a proper encryption format.

10. The method in claim 8, each of said customer codes includes a unique payment method.

11. The method in claim 8, each of said customer codes includes a different credit card number.

12. The method in claim 8, a group of said customer codes identifies a single credit organization for payment.

13. The method in claim 8, said periodic spending limits include monthly and weekly spending limits.

14. The method in claim 8, said supplying said customer code to said merchant supplies only encrypted information to said merchant.

15. A system comprising a non-transitory storage device storing instructions executable by a processor of a customer computer for securing transactions over a computer network, said instructions are executable by said processor of said customer computer to: encrypt customer information comprising customer address and customer credit card number as a plurality of customer code on a storage device on said customer computer, said customer information is stored on said storage device only in encrypted form; require a computer system identifier of said customer computer, and one of a private key, a password, and a personal access codes of a customer to access said customer codes; and supply a customer code of said customer codes to a merchant in a transaction over said computer network, wherein said customer computer includes a network connection to forward said customer code to a financial institution over said computer network, and wherein said financial institution decrypts said customer code and returns an authorization decision to said merchant over said computer network, said customer information comprises a different user name and different payment rules for each of said customer codes, and said payment rules comprise transaction limits, credit limits, and periodic spending limits.

16. The system in claim 15, said instructions are executable by said processor of said customer computer to pass said customer codes through an intermediate confirmation site on said computer network prior to forwarding said customer codes to said financial institution over said computer network, said intermediate confirmation site confirming whether said customer codes has a proper encryption format.

17. The system in claim 15, each of said customer codes includes a unique payment system.

18. The system in claim 15, each of said customer codes includes a different credit card number.

19. The system in claim 15, a group of said customer codes identifies a single credit organization for payment.

20. The system in claim 15, said periodic spending limits include monthly and weekly spending limits.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The foregoing and other objects, aspects and advantages will be better understood from the following detailed description of a preferred embodiment of the invention with reference to the drawings, in which:

[0018] FIG. 1 is a schematic architectural diagram of one embodiment of the invention;

[0019] FIG. 2 is a flow diagram illustrating an embodiment of the invention; and

[0020] FIG. 3 is a flow diagram illustrating an embodiment of the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION

[0021] Referring now to the drawings, and more particularly to FIG. 1, a schematic diagram of a preferred embodiment of the invention is illustrated. More specifically, FIG. 1 illustrates a personal computer 100 connected to a network 170. In addition, a code confirmation site 130, merchant site 140, financial institution 150, and credit agency 160 are also connected to the network 170. The arrangement of features shown in FIG. 1 is arbitrarily selected in order to illustrate the invention. One ordinarily skilled in the art would understand that many other arrangements of items could be utilized with the invention.

[0022] The personal computer 100 (which is sometimes referred to herein has the “customer computer”) comprises any form of computing device that is capable of connecting with the network 170. Therefore, the customer computer 100 can comprise a standard desktop personal computer, a mobile computer, a personal digital assistant, a cell phone, etc. In a preferred embodiment, the customer computer 100 includes a graphic user interface (GUI) 110, and a storage device 112, such as a magnetic hard drive or other read/write storage device. In addition, the customer computer 100 includes an encrypter 114, a network connection 116, a populator 118 and central processing unit (CPU) 120.

[0023] The financial institution 150 includes a database of historical address 154 obtained from the credit agency 160 and a comparator 152 that is utilized to check customer addresses, as discussed below.

[0024] The operation of the system shown in FIG. 1 is illustrated in flowchart form in FIG. 2. More specifically, the inventive system is added to the customer's computer 100. Using the graphic user interface 110, the customer preferably creates a password as shown in item 200 that will allow future access to the inventive system. The customer then supplies personal information such as Social Security number, address, date of birth, relatives' names, credit card information, banking information, employment information, etc. to the inventive system through the graphic user interface 110. The encrypter 114 immediately encrypts this information and stores the encrypted information as a customer code on the storage device 112, as shown in item 202.

[0025] An important feature of the invention is that the customers' personal information is only stored in encrypted form. Therefore, if an unauthorized user were able to access the user's storage device 112, the customers' personal information would be secure because of its encrypted nature.

[0026] The encryption process has three elements: 1) the encryption code itself, which is pared to the decryption code maintained by the financial institution; 2) the customer's private key, password and/or personal access code, which is created and controlled by the customer for accessing the encrypted information; and, 3) the customer's computer's system identifier that requires that the encrypted information may only be accessed on the customer's computer. Once the customer's information is entered, these three elements and the need to re-enter any of the information become transparent to all parties during any e-commerce transaction (e.g., dual key or public key).

[0027] If the encryption code were to fall into the hands of an unauthorized party, access to the information would still require the customer's private key plus access to the information from customer's specific storage system (e.g., customer's computer's system identifier). An unauthorized user would need the decryption code to access the information, which code is maintained only by the financial institutions (credit issuers) and their authorized agents. This element of the “public key” or “dual key” format of the preferred embodiment of the present invention enhances the security of the customer's information.

[0028] Even if an unauthorized user overcomes the foregoing safeguards, the present invention requires the user to supply an authorized shipping address; a procedure that requires a separate secured transaction with the financial institution, confirmed by e-mail to the customer. Such steps make impractical the unauthorized access.

[0029] In another embodiment of the invention, the user can create multiple customer codes, each of which could include a different credit agency (e.g., a different credit card). Therefore, the invention allows the user to create a customer code for each of the credit cards the user owns.

[0030] In addition, many customer codes can be created for the same credit card. These additional customer codes can include different spending limits. This allows the user to establish different customer codes for budgetary or other similar reasons. For example, with the invention, a user could create customer codes for different items of a personal or business budget. Upon reaching a spending limit, no additional transactions (purchases) could be performed until the budget information is changed or updated. The budget plan could be updated automatically to allow periodic budgets to be automatically implemented. An example of this could include one customer code that uses a credit card to pay monthly charges to an internet service provider (ISP) for a specific period, e.g., one year. The customer code would include a monthly limit of the monthly ISP fee and a twelve-month limit on the transaction. The additional advantage to the customer of this embodiment is the ability to amend or cancel the transaction at any time by changing the stated limits.

[0031] Similarly, parents could create customer codes for each of their children, where each customer code potentially includes a different spending limit. In one embodiment, the spending limits can be updated periodically to provide a periodic allowance. This aspect of the invention allows parents to establish a monthly Internet-allowance for a child. The parents establish a separately authorized customer code together with periodic limits (e.g., monthly or weekly). The effect of this is that the parent would control the establishment and use of authorized sub-accounts.

[0032] The effect of these aspects of the invention is that the financial institution would continue to control qualifying a customer for credit. However, the customer would enjoy an increased control and use of that credit.

[0033] The customer codes preferably include the name, address and credit card number of the user in encrypted form. Once the customer codes have been established and stored in encrypted form on the storage 112, the invention operates in the background on the customer's computer 100 until the customer desires to make a purchase over the network 170. At the time of a purchase, the graphic user interface 110 provides the user with different payment options (customer codes). After the user selects the appropriate customer code, the populator 118 prepares to send the customer code to the merchant's site 140 by issuing an instruction to send the customer code out on the network 170 directed to the merchant site 140, as shown in item 204.

[0034] The operation of the functions in item 204 are shown in greater detail in FIG. 3. More specifically, the invention provides for the customer code to automatically populate the appropriate “checkout” box of the merchant site 140 using the populator 118. As shown in FIG. 3, when the customer gets to a checkout (purchase) window of a merchant site, (300) the customer places the cursor into the appropriate box (e.g., the credit card number field, customer code data fields, etc.) 302. Many merchant sites 140 may not have space for the customer code date field. Therefore, the invention allows the credit card number (or other similar payment filed) to be used by the merchant site. The encrypted customer code data field is longer than credit card numbers. Therefore, the only modification needed by the merchant site 140 to accommodate the invention is to allow longer encrypted data strings to be accepted by the credit card number field.

[0035] Once the user places the cursor in the appropriate box, they press a pre-established function key on the keyboard (or selects a button on the graphic user interface) (304) which brings up a user ID and password entry pop-up window (306). Upon entry of the proper user ID and password, the entire customer code is populated (written to) the field on the merchant site. The user does not need to enter their name, address, etc. because all that information is contained in the customer code. As discussed below, upon approval of the credit transaction, the financial institution 150 will return name, shipping address and credit authorization number (not credit card number) to the merchant site 140 so that the user does not need to input such information.

[0036] If multiple customer codes are established for different credit cards, the user can select a customer code, which includes information as to a credit card with a sufficient credit limit, desirable interest rate, etc. to make the purchase. The customer code itself is the encrypted personal information data stream and can be somewhat lengthy. Therefore, the graphic user interface provides a user-friendly selection menu with abbreviated names. For example, in one embodiment, a pull-down menu with credit card abbreviations is provided to allow the user to select the customer code to be used. If the user has established only one customer code, the pull down menu will include only that single customer code abbreviation. In a similar manner, different budget categories or children's names could also be utilized as the abbreviated names in the pull-down menu to select the appropriate customer code.

[0037] The user ID's are the customer codes abbreviations. An error message is generated if the user ID/password is incorrect (310) and processing returns to box 304 to retry the user ID/password. As is well-known a limited number of retries of the user ID/password will be allowed.

[0038] If the password/user ID is correct (308), the customer has the option to set up rules regarding payment (312), such as the automatic monthly ISP payments discussed above. If no special rules are to be established for payment, a single direct payment scheme is assumed and processing proceeds to box 316. On the other hand, if payment rules are to be established, another window pops-up (314) to lead the customer through a wizard to setup payment options such as transaction amounts, total credit limits, and/or time frames, etc.

[0039] In item 316, the invention then takes the previously encrypted sensitive customer data, and adds to it a purchase specific transaction number and rules (if any). The invention also encrypts such additional data (transaction number, rules, etc.) before attaching necessary routing information, and automatically populates the complete customer code into the customer code data field or credit card field 302. As mentioned above, the customer code is the encrypted data string of a number of data pieces including credit card number, rules, transaction number, customer name and address, etc.

[0040] Referring again to FIG. 2, in one embodiment the invention sends the customer code directly to the merchant site 140, as shown in item 208. In another embodiment, a code confirmation site 130 is utilized (item 206). In this embodiment, the customer code is directed to the code confirmation site 130 instead of to the merchant site 140 by the populator 118. The code confirmation site 130, controlled by the credit agency, determines whether the customer code has the proper format by allowing the credit agency to periodically update or change the public keys (e.g., the encryption and decryption codes). If the customer code is determined to be improper by the code confirmation unit 130, an error report is issued explaining that the customer code is improper, as shown in item 212. If the customer code is proper, it is sent to the merchant site 140 by the code confirmation unit 130, as shown in item 214.

[0041] Upon receipt of the customer code, the merchant site 140 forwards the customer code to the financial institution 150. An important feature of the invention is that confidential information is not provided to the merchant in unencrypted form at any time. Thus, the merchant is relieved of the responsibility for that information.

[0042] As shown in item 218, the financial institution decrypts the customer code. Next, while checking whether the credit transaction is acceptable (e.g., whether the customer has sufficient credit available), the financial institution also compares, using the comparator 152, the shipping address to which the goods are to be shipped against a historical database of acceptable shipping addresses 154 that is provided to the financial institution by the credit agency 160. This aspect of the invention prevents items from being improperly diverted by criminals to addresses other than the customer's address.

[0043] In one embodiment of the invention, the customer is able to establish multiple authorized shipping addresses directly with the credit agency. These addresses may include such alternatives as office or home. Each address is entered and stored on the customer's storage device with a separate encryption sequence as a separate customer code. At the time the customer is setting up new customer codes, new authorized addresses for the customer are sent (via e-mail or similar electronic transfer) directly from the customer computer 100 to the credit agency 160 over the network 170 and are augmented to the list of authorized addresses associated with the customer in the credit agencie's 160 databases.

[0044] As shown in item 220, if the shipping address is consistent with an address in the database 154 and the customer has sufficient credit, a confirmation code, name, address, and other required information is sent to the merchant 140, as shown in item 224. In this instance, the term “consistent” means that the two addresses must be substantially matching. Thus, if a small portion of the street number or zip code is incorrect or if the spelling of the street name is slightly off, the transaction is approved and a corrected address is provided to the merchant. However, if the shipping address is directed to an address that is not consistent with an authorized address for that customer (e.g. different state, different city, different street, etc.), an error report is issued to the merchant site 140 and an e-mail is sent to the customer explaining the improper transaction.

[0045] Credit agencies currently use addresses to help determine authorization. However, their criteria for what constitutes a “consistent” address varies. The present invention creates a system for eliminating error and fraud in these authorizations by “correcting” the address. It is then the merchant's responsibility to ensure that the product only ships to the authorized or corrected address. This aspect of the present invention adds a layer of security, allowing the customer to “intercept” and return any unauthorized shipments.

[0046] In one embodiment of the invention, the customer uses the “rule wizard” [314] to temporarily add a “non-permanent” shipping address, allowing the customer to send gifts, etc., to others. The customer's computer's system identifier and password are required to access the “wizard” for this non-recurring change. Additionally, a confirmation of this shipment to a non-authorized address is e-mailed to the customer so that the customer may be alerted if a fraudulent transaction were being attempted.

[0047] As mentioned above, the merchant site 140 preferably includes an input field (which may be the current credit card field) properly formatted to receive the customer code. The format of the input field is established by the credit agency 160 and is similarly required by the financial institution 150. There are a relatively small number of national credit agencies 160 (Visa®, MasterCard®, American Express®, etc.). The credit agency 160 can generally dictate the format of information that must be supplied by the more numerous financial institutions 150 that deal with the credit agency 160. In turn, merchant sites 140 that desired to deal with the financial institutions 150 must comply with the data format requirements of the financial institution 150 (and, in turn, the credit agency 160). Therefore, the invention is applicable to a network that continually adds and drops large numbers of merchant sites 140, such as the Internet. More specifically, as merchant sites 140 are added to the network, each merchant site 140 will comply with the requirements of the financial institution 150 and will include the specialized format of the customer code data field in their merchant sites 140. Therefore, the user should find the customer code data field on the vast majority of Web sites that allow customer purchases.

[0048] In other words, the invention works with the relatively small number of national credit agencies 160 to establish a format (that can potentially vary from credit card agency to credit card agency) that will be made available by the merchants 140. Because a limited number of credit agencies 160 control the majority of the online credit purchase transactions, the format of the customer code input field will be provided upon the vast majority of merchant sites 140. Thus, the invention provides the user with access to virtually all merchant sites 140 that desire to deal with financial institutions (which is virtually all merchant sites that desire to complete purchase transactions).

[0049] The credit agencies [160] are in the business of getting customers to use credit (e.g., their credit cards). Where the present invention creates security for the customer, together with additional control and use features, the credit agencies derive a promotional benefit for their credit facilities. Moreover, these beneficial features do not require extra steps. A benefit of the present invention is that it eliminates steps that include repeated entry of customer information or the posting of that information on third-party databases.

[0050] An important safety feature of the invention is that the merchant site 140 never gains access to the customer's confidential information, such as credit card numbers. To the contrary, the merchant site 140 only receives the encrypted customer code from the customer 100 and the transaction confirmation code (and possibly a corrected address) from the financial institution 150. Therefore, if any of the foregoing transactions over the network 170 are intercepted or if the merchant site suffers an unauthorized access of its records, the customer's credit card information will be secure.

[0051] Further, the invention avoids many of the problems associated with conventional secured network transactions. More specifically, all elements of the present invention must be in place for a transaction to be completed. Conventional systems provide one level of security to all transactions, so that if a database is breached all of the records on that “secured” site are accessible. The present invention protects individual records creating an additional level of security.

[0052] The benefits that flow from the present invention, as detailed above, include security to an individual customer's online credit and the customer's control and flexible use of that credit.

[0053] While the invention has been described in terms of preferred embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the appended claims.