Abstract:
A method is provided for conducting a transaction over a computer network (such as the Internet) where the remote wallet server conducts a transaction with a merchant computer in a format substantially compliant with a chip card electronic commerce protocol or specification, regardless of whether or not the payment card of the consumer involved in the transaction is a chip card.

Description:
BACKGROUND OF THE INVENTION  
         [0001]    This invention relates to a method and system for conducting electronic commerce with a remote wallet server.  
           [0002]    Electronic commerce over the Internet, and especially the World Wide Web portion of the Internet, is growing at a phenomenal rate. Merchants are taking advantage of the popularity of the World Wide Web by creating online catalogs on web sites, through which consumers can browse and order the merchants&#39; products and services.  
           [0003]    In a typical online transaction over the Internet, a consumer will browse a merchant&#39;s web site, identify items of interest, and add those items to the consumer&#39;s electronic shopping cart. When a consumer is ready to order, the consumer presses an order button, and a merchant sends the consumer a completed order form (typically an HTML-based form) to review and approve. If the consumer desires to complete the order, the consumer fills in the order form with payment and shipping information and returns the form to the merchant.  
           [0004]    A disadvantage to the typical process of conducting transactions over the Internet is that the data format used in the merchant HTML-based order forms varies considerably between merchants, and the consumer must therefore re-enter the same payment and shipping information for each merchant at which the consumer shops. Many consumers find the diversity of forms confusing and the process of manually filling in these forms tedious.  
           [0005]    In an effort to make online shopping more convenient for consumers, some companies have developed software applications called digital wallets. A digital wallet may store payment and shipping information on a consumer&#39;s computer and to use this information to automatically complete a merchant&#39;s order form. The digital wallet thus frees the consumer from having to manually re-enter payment and shipping information each time that the consumer makes an online purchase. Digital wallets have been developed as stand-alone applications, as helper applications to browsers, and as browser plug-ins.  
           [0006]    Because of the anonymous and open nature of the Internet, electronic commerce over the Internet raises concerns regarding the confidentiality and integrity of transmitted data and the proper authentication of parties involved in a transaction. Various methods of addressing these concerns have been developed and proposed. One such method is the SET™ protocol, which is promulgated and managed by SET Secure Electronic Transaction LLC (www.setco.org). The SET protocol is an open technical standard for the commerce industry developed by MasterCard™ International Inc. and others as a way to facilitate secure payment card transactions over the Internet. SET utilizes cryptography to ensure confidential and secure transmissions of data and digital certificates to create a trust chain throughout the transaction, verifying cardholder and merchant identities. The SET protocol is invoked after a consumer has completed the payment and other information on an order form and is ready to return the order form to the merchant.  
           [0007]    Typically, a digital wallet will include application code to perform encryption to ensure the confidentiality and integrity of payment information transmitted during an online transaction. For example, a digital wallet may contain application code to perform the SET protocol. The digital wallet may also include application code for transmitting information according to a standard electronic commerce protocol, such as the Electronic Commerce Modeling Language (ECML). The digital wallet may also include a digital certificate, which may be used to authenticate a consumer. The application code to perform these functions, especially the encryption function, may be lengthy. Therefore, a consumer may find the time to download digital wallet software over the Internet to be inconveniently long.  
           [0008]    To shorten the time required for downloading a digital wallet, remote wallet servers have been developed. A remote wallet server is a server that is remote from a consumer&#39;s computer and that stores the bulk of the application code for a digital wallet. The remote wallet server may also remotely store the consumer&#39;s payment and shipping information. When a remote wallet server is used, a consumer need only store a “thin” client application on his or her computer that communicates with the remote wallet server when the consumer is ready to complete an order with a merchant. The remote wallet server then acts as a proxy for the consumer, sending payment and other purchase-related information to the merchant.  
           [0009]    A problem that arises in connection with the use of a remote wallet server is how to authenticate the remote wallet server (which acts as a proxy for the cardholder) to the merchant. Assuming that a digital certificate approach (such as that used by SET) is used between a consumer and a merchant, it has been proposed that the remote wallet server store the consumer&#39;s authentication key (i.e., the private key of a cryptographic public key pair used for digital signatures) and the consumer&#39;s digital certificate. This approach is problematic because a remote wallet server may provide service to potentially millions of consumers. Therefore, using this approach, the remote wallet server would be required to store potentially millions of authentication keys and digital certificates. This approach is undesirable because it imposes enormous, secure storage requirements on the remote wallet server and because the storage of a large number of consumers&#39; sensitive information (i.e., authentication keys) in one place poses great security concerns.  
           [0010]    Another approach that has been proposed is for the remote wallet server to hold a set of its own authentication keys. Each authentication key in the set would be associated with multiple consumers. For example, if a remote wallet server provides service to one million consumers and holds a set of one thousand authentication keys, each authentication key could be associated with a thousand consumers. While this approach would allow the remote wallet server to store many fewer keys than the previous approach, the remote wallet server would still be required to store individual certificates for each consumer (since each certificate would contain individual consumer account information). This approach also has security concerns.  
           [0011]    Another approach that has been proposed is for the remote wallet server to store the private key of a recognized certificate signing entity, such as the financial institution that issues a consumer&#39;s payment card. The remote wallet server could then generate consumer digital certificates “on the fly” using the certificate signer&#39;s private key. While this approach eliminates the need for the remote wallet server to store consumer authentication keys and digital certificates, it raises other concerns. First, since the confidentiality of the private key of the certificate signer (e.g., issuing bank) is of utmost importance to establish trust in a certificate signed by the certificate signer, it is against the certificate signer&#39;s interest to share this private key with any other entity. Second, since public key pairs may have expiration dates, the remote wallet server may periodically, in a secure manner, need to be updated with a new version of the certificate signer&#39;s private key. Third, generating certificates on the fly could cause increased transaction processing times.  
           [0012]    Yet another approach that has been proposed, in the case where a consumer uses an integrated circuit card (also referred to as a “chip card” or “smart card”) as a payment card for an online transaction, is for the remote wallet server to simply pass a cryptogram generated by the consumer chip card to the merchant. The cryptogram will then be forwarded to the financial institution that issued the chip card. Since the chip card shares a secret with the card issuing institution (such as a DES cryptographic key) that it uses to generate the cryptogram, the identity of the chip card holder may be authenticated by the card issuing institution. A disadvantage to this approach, however, is that the cryptogram does not provide any information related to the remote wallet server involved in the transaction. In addition, this approach obviously does not apply to any transactions that do not involve chip cards. Since payment chip cards are not currently widespread, this approach currently does not have wide applicability.  
           [0013]    Accordingly, there exists a need for a method and system for authenticating a remote wallet server during an online transaction that substantially improves on the approaches discussed above.  
         SUMMARY OF THE INVENTION  
         [0014]    It is an object of the present invention to provide an improved system and method for authenticating a remote wallet server during on online transaction. According to an exemplary embodiment of the present invention, there is provided a method for conducting a transaction over a computer network (such as the Internet) where the remote wallet server conducts a transaction with a merchant computer in a format substantially compliant with a chip card electronic commerce protocol or specification, regardless of whether or not the payment card of the consumer involved in the transaction is a chip card.  
           [0015]    According to one aspect of the present invention, the remote wallet server and an issuer institution (such as a bank) have a shared secret data object (such as a cryptographic key), and the method of the present invention includes the steps of generating a cryptogram by the remote wallet server based on the shared secret data object and sending payment-related information and the cryptogram by the remote wallet server to the merchant computer during an online transaction. The merchant computer may then forward the cryptogram, through an existing payment infrastructure, to the issuer institution, which decrypts the cryptogram and authorizes or rejects the transaction.  
           [0016]    Advantageously, the present invention allows the authentication of remote wallet servers to be seamlessly integrated into existing payment infrastructures and to utilize existing point-of-sale chip card transaction methodologies. With the present invention, an issuer bank need only issue the cryptographic equivalent of a consumer chip card to a remote wallet server, where the chip card is approved by the issuer bank for the capture and storage of consumer payment accounts used in electronic commerce. For issuing institutions that already have the infrastructure to support consumer chip card transactions, no new infrastructure is needed to support the authentication of transactions initiated by remote wallet servers utilizing the present invention. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0017]    Exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings in which:  
         [0018]    [0018]FIG. 1 is a block diagram of a system for conducting electronic commerce according to a exemplary embodiment of the present invention; and  
         [0019]    [0019]FIG. 2 is a flow chart of a method of conducting electronic commerce according to an exemplary embodiment of the present invention. 
     
    
     DETAILED DESCRIPTION  
       [0020]    [0020]FIG. 1 is a block diagram of a system for conducting electronic commerce according to a exemplary embodiment of the present invention. The system includes a consumer computer  100 , a remote wallet server  200 , a merchant web server  300 , a merchant bank computer  400 , and an issuer bank computer  500 .  
         [0021]    The consumer computer  100  includes a web browser  102  for browsing web pages on the Internet, such as a merchant&#39;s web site. The consumer computer  100  also includes a thin wallet application  104  that allows the consumer computer  100  to communicate with the remote wallet server  200 . The thin wallet application  104  may be a stand-alone application, a helper application to the web browser  102 , or a plug-in for the web browser  102 .  
         [0022]    The remote wallet server  200  includes a digital wallet application  202 , which provides payment fimctionality for one or more consumers. The remote wallet server  200  also includes a secret cryptographic key  206 , which is shared with the issuer bank computer  500 . The issuer bank computer  500  has secret cryptographic key  502 , which is a copy of the secret key  206 . The remote wallet server also includes a cryptogram generator  204 , which uses the secret key  206  to generate a cryptogram.  
         [0023]    The merchant web server  300  hosts a web site for the merchant, which includes the merchant&#39;s online catalog of goods and/or services. The consumer computer  100 , remote wallet server  200 , and the merchant web server  300  are able to communicate with each other over the Internet.  
         [0024]    The merchant bank computer  400  is operated by or on behalf of a bank that holds a financial account of the merchant. For example, the merchant bank computer may be operated by a third party processor that the merchant bank has designated for processing of payment card authorizations. The merchant web server  300  is able to communicate with the merchant bank computer  400  either through the Internet or other communications link.  
         [0025]    The issuer bank computer  500  is operated by or on behalf of the bank that issued the payment card of the consumer. The merchant bank computer  400  (or third party payment processor designated by the merchant bank) and the issuer bank computer  500  are able to communicate with each other through a payment system network.  
         [0026]    [0026]FIG. 2 is a flow chart of an exemplary method of conducting electronic commerce using the system of FIG. 1. In step  1000 , the consumer browses the merchant&#39;s online catalog using the web browser  102 . The consumer may select items of interest and place them in his or her electronic shopping cart. When the consumer is finished browsing and selecting items, the consumer presses an order button to indicate to the merchant that the consumer desires to place an order.  
         [0027]    In step  1010 , in response to the pressing of the order button in step  1000 , the merchant sends the consumer an order form (which is typically an HTML-based form), with fields for the entry of payment and shipping information. In step  1020 , the consumer computer  100 , using the thin wallet application  104 , authenticates itself to the remote wallet server  200 . The method of authentication between the consumer computer and the remote wallet server is not addressed by the present invention and may be performed by any means known in the art, such as with the use of public key cryptography, shared symmetric cryptographic keys, or other proprietary authentication methods, including chip card authentication methods.  
         [0028]    After the consumer computer has authenticated itself to the remote wallet server, the consumer computer sends the order form to the remote wallet server and requests that the remote wallet server complete the transaction with the merchant. It is noted that the consumer payment and shipping information may be stored on either the consumer computer  100  or the remote wallet server  200 . If the payment and shipping information is stored on the consumer computer, the consumer computer will send this information to the remote wallet server with its request. If the payment and shipping information is stored on the remote wallet server, the consumer computer need not send this information to the remote wallet server with its request.  
         [0029]    In step  1040 , the remote wallet server fills in the information on the order form, if necessary. In step  1050 , the cryptogram generator  204  of the remote wallet server generates a cryptogram using the secret key  206 . The cryptogram generator  204  may be a software application or it may be a dedicated circuit within the remote wallet server  200 . Preferably, the cryptogram generator  204  and the secret key  206  are contained in a tamper-resistant hardware security module, which offers physical protection for the keys stored inside it. The cryptogram generator  204  may utilize any well-known cryptographic algorithm, such as, for example, the triple DES algorithm. Typically, the cryptogram generated will include both consumer account and purchase information.  
         [0030]    In step  1060 , the remote wallet server continues the dialog with the merchant—i.e., sends the completed order form and the cryptogram to the merchant using a chip card protocol. For example, the remote wallet server may conduct the transaction with the merchant using the protocol specified in the  EMV  96  Chip Electronic Commerce Specification , Version 1.0, December 1999 (available at http://www.emvco.com/specifications.cfin), which is incorporated by reference herein in its entirety. Thus, at the merchant computer, the transaction appears to involve a consumer chip card and is processed as such.  
         [0031]    In step  1070 , the merchant forwards the cryptogram to the merchant bank. In turn, in step  1080 , the merchant bank forwards the cryptogram to the issuer bank. In step  1090 , the issuer bank verifies the cryptogram and authorizes or rejects the transaction. The authorization or rejection is transmitted back to the merchant through the chain of communication.  
         [0032]    Advantageously, as described above, the present invention allows the authentication of remote wallet servers using existing payment infrastructures and existing point-of-sale chip card based transaction methodologies. According to the present invention, a bank need only issue the cryptographic equivalent of a consumer chip card to a remote wallet server, and assuming the bank already has the infrastructure to support consumer chip card based transactions, no new infrastructure is needed to support the authentication of transactions initiated by the remote wallet server. Moreover, the present invention allows any technology to be employed between the consumer computer and the remote wallet server for authentication and communication.  
         [0033]    Although the present invention has been described with reference to certain preferred embodiments, various modifications, alterations, and substitutions will be known or obvious to those skilled in the art without departing from the spirit and scope of the invention, as defined by the appended claims.