|Publication number||WO1995016971 A1|
|Publication date||22 Jun 1995|
|Filing date||13 Dec 1994|
|Priority date||16 Dec 1993|
|Also published as||DE69431306D1, DE69431306T2, EP0734556A1, EP0734556A4, EP0734556B1, EP1235177A2, EP1235177A3, US5724424, US6049785, US6195649, US6199051, US6205437, US20100057561|
|Publication number||PCT/1994/14319, PCT/US/1994/014319, PCT/US/1994/14319, PCT/US/94/014319, PCT/US/94/14319, PCT/US1994/014319, PCT/US1994/14319, PCT/US1994014319, PCT/US199414319, PCT/US94/014319, PCT/US94/14319, PCT/US94014319, PCT/US9414319, WO 1995/016971 A1, WO 1995016971 A1, WO 1995016971A1, WO 9516971 A1, WO 9516971A1, WO-A1-1995016971, WO-A1-9516971, WO1995/016971A1, WO1995016971 A1, WO1995016971A1, WO9516971 A1, WO9516971A1|
|Inventors||David K. Gifford|
|Applicant||Open Market, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (7), Non-Patent Citations (1), Referenced by (143), Classifications (43), Legal Events (7)|
|External Links: Patentscope, Espacenet|
DIGITAL ACTIVE ADVERTISING BACKGROUND OF THE INVENTION The recent rapid growth of information applications on international public packet-switched computer networks such as the Internet suggests that public computer networks have the potential to establish a new kind of open marketplace for goods and services. Such a marketplace ecuId be created with a network sales system that comprises a plurality of buyer and merchant computers, means for the users of the buyer computers to display digital advertisements from the merchant computers, and means for the users to purchase products described by the advertisements.
A network based sales system will need to allow users to preview products at little or no cost, and will need to make a large number of product advertisements available in a convenient manner. In addition, the shopping system will need to include easy-to-use facilities for a user to purchase desired products using a merchant independent payment method. In addition the network sales will need to allow new buyers and merchants to enter the market. A central requirement for a marketplace is a payment mechanism, but at present no merchant independent payment mechanism is available for computer networks that permits users to utilize conventional financial instruments such as credit cards, debit cards, and demand deposit account balances. We expect that both retail payment and wholesale payment mechanisms will be required for networks, with consumers using the retail mechanism for modest size purchases, and institutions using the wholesale mechanism for performing settlement between trading partners. For wide acceptance the retail mechanism will need to be a logical evolution of existing credit-card, debit-card, and Automated Clearing House facilities, while for acceptance the wholesale mechanism will need to be an evolved version of corporate electronic funds transfer. These problems of have been approached in the past by network based sales systems wherein, for example, each merchant maintains an account for each user. A user must establish an account with each merchant in advance in order to be able to utilize the merchant. The prior art network based sales systems are not designed to allow users to use their existing credit card and demand deposit accounts for payment, nor are they designed to allow for programs to be included in digital advertisements. According, therefore, it is a primary objective of this invention to provide a user interactive network sales system in which the user can freely use any merchant of choice and utilize existing financial instruments for payment. Other objects include a network sales system which provides a high-quality user interface, which provides users with a wide variety and large volume of advertisements, which is easily extensible to new services, and which is easily expanded to new applications within the existing infrastructure of the system.
Still other objects of the invention are to provide a network payment system that will authorize payment orders and remove part of the risk of fraud from merchants. An unavoidable property of public computer networks is that they are comprised of switching, transmission, and host computer components controlled by many individuals and organizations. Thus it is impossible for a network payment system to depend upon a specified minimum required degree of software, hardware, and physical security for all of the components in a public network. For example, secret keys stored in a given user's personal computer can be compromised, switches can be tampered with to redirect traffic, and transmission facilities can be intercepted and manipulated.
The risk of performing retail payment in a public network is compounded by statutes that make a payment system operator in part liable for the security lapses of its users. Existing Federal statutes in the United
States, including the Electronic Funds Transfer Act and the Consumer Credit Protection Act, require the operator of a payment mechanism to limit consumer liability in many cases. Payment system operators may have other fiduciary responsibilities for wholesale transactions. Similar responsibilities exist in other countries for retail and wholesale transactions.
In existing credit card payment systems, a credit card's issuing bank takes on the fraud risk associated with misuse of the card when a merchant follows established card acceptance protocols. Acceptance protocols can include verifying a card holder's signature on the back of their card and obtaining authorization for payments over a certain value. However, in network based commerce a merchant can not physically examine a purchasers credit card, and thus the fraud risk may revert to the merchant in so called "card not present" transactions. Many merchants can not qualify to take this risk because of their limited financial resources. Thus the invention is important to allow many merchants to participate in network based commerce.
Other objects of the invention include utilizing existing financial instruments such as credit cards, debit cards, and demand deposit accounts for merchant payments. Existing network payment systems do not connect to the financial system for authorization and are not compatible with conventional financial instruments. Existing network payment systems include the Simple Network Payment Protocol [Dukach, S., SNPP: A Simple Network Payment Protocol, MIT Laboratory for Computer Science, Cambridge, MA, 1993.], Sirbu's Internet Billing Server [Sirbu, M. A. , Internet Billing Service Design and Prototype Implementation, Information Networking Program, Carnegie-Mellon University, 1993], and NetCash [Medvinsy, G. , and Newman, B. C. , NetCash: A Design for Practical Electronic Currency on the Internet, Proc. 1st ACM Conf. on Comp. and Comm. Security, November, 1993].
A further object of the invention is to allow users in an untrusted network environment to use conventional financial instruments without requiring modification to existing financial system networks.
The following definitions apply to the present invention. A principal is a person, company, institution, or other entity that is authorized to transact business as part of a network payment system. A payment order describes the identity of a sender, a payment amount, a beneficiary, and a sender unique once. A sender is a principal making a payment. A beneficiary is a principal to be paid by the payment system. A sender unique nonce is an identifier that is used only once by a given sender. An example of sender unique nonces are unique timestamps. An external account is an account that can be used to settle a payment order for either a sender or a beneficiary in the external financial system. Examples of external accounts include demand deposit accounts and credit card accounts. An external device is a physical object that is kept in the possession of a user for the purpose of identifying the user. A network payment system is a service that authorizes and executes digital payment orders that are backed by external accounts. A payment system authenticates a payment order, checks for sufficient funds or credit, and then originates funds transfer transactions to carry out the payment order. A payment system acknowledges acceptance or rejection of a payment order. More than one payment system may exist on a given network, and a given payment system may operate on more than one host to increase its reliability, availability, and performance. An authenticator is a digital value that is appended to a payment order and becomes part of the payment order that authenticates the payment order as genuine. SUMMARY OF THE INVENTION
The invention relates to a network sales system for enabling users to purchase products using a plurality of buyer computers that communicate over a network with a plurality of merchant computers. Each merchant computer has a database of digital advertisements. Each digital advertisement includes a price and a product abstract. Buyer computers request, display, and respond to digital advertisements from merchant computers. Users can purchase products with their buyer computers after they have specified an account to pay for the purchase. A network payment service is used to authorize the purchase before merchant fulfillment is performed.
In a particular aspect of the invention, the merchant computer can request account information when it is not provided by the buyer computer. In another aspect of the invention, the buyer computer can present to a merchant a pre-authorized payment order that is obtained from a network payment system.
In another aspect of the invention, an electronic sales system contains digital advertisements that include programs. The programs are executed on behalf of a user by a buyer computer, and can lead to a purchase request directed to a merchant computer that performs product fulfillment. In another aspect of the invention a network payment system executes payment orders. A payment order includes a sender, a beneficiary, a payment amount, and a nonce identifier. A payment order is signed by a client computer with an authenticator that is checked by the payment system. Payment orders are backed by accounts in the banking system, and are authorized by the network payment system by sending messages into a financial authorization network that knows the status of these accounts. The payment system accomplishes settlement by sending messages into an existing financial system network.
In another aspect, payment orders are authenticated based on the delivery address they specify. In another aspect, the payment system will specify in its authorization legal delivery addresses. In another aspect, authenticators for payment orders are based on one-time transaction identifiers that are known only to the user and the payment system. In another aspect, payment orders for a given sender are only accepted from certain client computer network addresses. In another aspect, the network payment system sends messages into a financial authorization system in real-time before the network payment system will authorize a payment order. BRIEF DESCRIPTION OF THE DRAWINGS Other objects, features, and advantages of the invention will appear from the following description taken together with the drawings in which:
Figure 1 is a block diagram of a typical network sales system in accordance with the invention; Figure 2 is a screen snapshot of a buyer computer display of an overview page from a merchant computer;
Figure 3 is a screen snapshot of a buyer computer display of a page of digital advertisements from a merchant computer;
Figure 4 is a screen snapshot of a buyer computer display of an account query page;
Figure 5 is a screen snapshot of a buyer computer display of a fulfillment page; Figure 6 is a flow chart illustrating the processing of a sale between a buyer computer and a merchant computer;
Figure 7 is a flow chart illustrating the alternate processing of payment order means for obtaining missing payment information;
Figure 8 is a screen snapshot of a buyer computer display of an overview page from a merchant computer that contains a query input by the user;
Figure 9 is a screen snapshot of a buyer computer display of digital advertisements in response to a user's query;
Figure 10 is a screen snapshot of a buyer computer screen of a purchase confirmation;
Figure 11 is a screen snapshot of a buyer display of a fulfillment page like Figure 5;
Figure 12 is a flow chart illustrating an alternate processing of a sale between a buyer computer and a merchant computer where a payment order is pre- authorized; Figure 13 is a block diagram of a typical network payment system in accordance with the invention;
Figure 14 is a flow chart illustrating the authentication, authorization, and settlement of a payment order; Figure 15 is a flow chart illustrating an alternate processing of the authentication and verification of a payment order where transaction identifiers are used; and Figure 16 is a flow chart illustrating an alternate processing of the authorization of a payment order where real-time approval from the financial authorization network may not be obtained.
DESCRIPTION OF A PARTICULAR PREFERRED EMBODIMENT A network sales system 200 as shown in Figure 1 employs a network 67 to interconnect a plurality of buyer computers 61 and 62, merchant computers 63 and 64, each merchant computer with respective digital advertisement databases 65 and 66, and a payment computer 68. A user of the system employs a buyer computer to retrieve advertisements from the merchant computers, and to purchase goods of interest. A payment computer is used to authorize a purchase transaction.
A digital advertisement includes a product description and a price. In digital advertisement database 65 prices and descriptions may be stored separately, and one price may apply to many product descriptions.
In an alternate embodiment, the network sales system further includes external devices that are kept in the possession of users so that the users can authenticate themselves when they use a buyer computer.
The software architecture underlying the particular preferred embodiment is based upon the hypertext conventions of the World Wide Web. Appendix A describes the Hypertext Markup Language (HTML) document format used to represent digital advertisements. Appendix B describes the HTML forms fill out support in Mosaic 2.0, Appendix C is a description of the Hypertext Transfer Protocol (HTTP) between buyer and merchant computers, and Appendix D describes how documents are named with Uniform Resource Locators (URLs) in the network of computers. A document is defined to be any type of digital data broadly construed, such as multimedia documents that include text, audio, and video, and documents that contain programs.
Figure 2 shows an overview screen that has been retrieved from a merchant computer by a buyer computer and displayed by the buyer computer. It includes links 1, 2, and 3 that when activated by a user cause the buyer's computer to take specified actions. In the case of link l, the document shown in Figure 3 is retrieved from a merchant computer and displayed. In the case of link 2, a short audio segment is retrieved from a merchant computer and played. In the case of link 3, the query that can be entered into the query dialog box 4 is sent to a merchant computer, and a document is retrieved from the merchant computer and displayed.
Figure 3 shows a document that contains three digital advertisements. The digital advertisements have been retrieved from the merchant computer after the activation of link 3. The merchant computer may set the prices contained in the advertisements based on the on the identity of the user as determined, for example, by the network address of the requesting buyer computer. The document includes links 5, 6, and 7 that are used to purchase the products described by the advertisements. For example, if link 5 is activated the missing payment information document shown in Figure 4 is retrieved from the merchant computer and displayed.
Figure 4 is a missing payment information document that is used to gather user account information for the requested purchase in an HTML form. Radio buttons 8, 9, 10, 11, 12 are used to select a means of payment, dialog box 13 is used to enter an account number, dialog box 14 is used to enter an optional authenticator for the account, purchase button 15 is used to send the account information to the merchant computer and proceed with the purchase, link 16 is used to abort the purchase and return to the document shown in Figure 2, and dialog box 17 is used to enter optional user information that is associated with the purchase and ultimately used by a financial institution as part of a textual billing identifier for the purchase transaction. If provided, this additional information is included in the payment order for the purchase.
Figure 5 is a fulfillment document 18 that is produced once valid account information is provided to the missing payment information document in Figure 4 and purchase button 15 is activated.
Figure 6 is a flowchart that more fully describes the information flow in the purchase transaction shown in Figures 2 to 5. An initial user inquiry 19 from activating link 1 results in the HTTP request 20 for a specific document with a specified URL. The URL specifies the name of the merchant computer. The merchant computer retrieves the document given the URL at 21, and returns it to the buyer computer at 22. The buyer computer displays the resulting HTML document at 23. When the user activates link 5, an HTTP request 25 is sent to the merchant computer requesting the document.
In an alternate embodiment, document 22 is executed at 23 as a program. A program is defined as a set of instructions that can exhibit conditional behavior based upon user actions or the environment of the buyer computer. As is known to those skilled in the art, there are many techniques for representing programs as data. The program can be interpreted or it can be directly executed by the buyer computer. The program when executed will cause the buyer computer to interact with - li ¬ the user leading to the user purchase request 24, and the purchase message 25.
The merchant computer then attempts to construct a payment order at 26 using the information it has gathered about the user. The buyer computer may have previously supplied certain credentials using fill out forms or other account identification means such as providing the network address of the buyer computer in the normal course of communication. If the buyer computer is able to construct a complete payment order at 26 the payment order is sent to a payment computer for authorization at 27. If a payment order can be constructed, processing continues at 28.
Alternatively, the buyer computer may construct the payment order at 24 and send it to the merchant computer at 25. In this case, the payment order assembly steps at 26, at the merchant computer, may only need to forward the payment order from the buyer computer. A payment order includes user account information, merchant account information, an amount, and a nonce identifier that has not been previously used for the same user account. Variations of payment orders can be constructed, including payment orders that specify user or merchant identifiers in place of account information, payment orders that specify ά. valid time period, payment orders that specify foreign currencies, and payment orders that include comment strings. Part of the process of constructing a payment order is creating a corresponding authenticator using one of the authenticator methods described below.
In the illustrated embodiment of Figures 3 and 4, the merchant computer does not have sufficient information to construct a payment order at 26 and thus at 33 (Figure 7) constructs and returns a missing payment information document in response to request 25. Operation 33 includes in the constructed document appropriate form fields based on what information the merchant computer has already collected from the user. The document is returned to the buyer computer at 34 and is displayed at 35. When the user presses the purchase button 15, the contents of the form are transmitted to the merchant computer, at 36, to a specific URL name, using an HTTP request. Based on the supplied form fields, the merchant computer constructs a complete payment order. Alternatively, the buyer computer may construct the payment order at 35 and send it to the merchant computer as part of step 36. In this case, the payment order assembly steps 37 at the merchant computer simply passes on the payment order from the buyer computer. The payment order is sent to the payment computer in a message at 38.
In either case, the flowchart continues in Figure 6 where the payment computer checks the authorization of the payment order at 28. If the payment system authorizes the request, an authorization message at 29 is returned to the buyer computer, and the merchant computer checks at 30 that the authorization message came from the payment computer using the authenticator mechanism described below. Assuming that the authorization message is valid, the merchant computer performs fulfillment at 30, returning the purchased product in response at 31. In our example in Figure 5 the response at 31 is document 18 that was the logical target of link 5. If the payment system does not authorize the payment order then response 31 is a rejection of the user's purchase request.
In an alternate embodiment, step 30 can encrypt the document using a key that is known to the buyer computer. As is known to those skilled in the art, the key can be communicated to the merchant computer using convention key distribution protocols. In this manner the document will be protected from disclosure to other users.
The fulfillment step at 30 can alternatively schedule a physical product to be shipped via ordinary mail or other means. This can be accomplished by updating a fulfillment request database or by sending a message to a shipping system. In this case the response at 31 is a confirmation that the product has been scheduled to ship. In this way the network sales system can implement an electronic mail order system.
Figures 8, 9, 10, and 11 show a second example that uses query based access to digital advertisements. It is assumed that the previous example was used by the user immediately before at the same buyer computer. Figure 8 shows the overview screen where the query "movie review" has been entered into dialog box 39. When the user activates process button 40, the merchant searches databases as described by the URL attached to button 40, and creates a response document as shown in Figure 9.
Figure 9 shows digital advertisements 39, 40, 41, 42, 43, and 44 that were found in response to the query initiated by button 40. A scroll bar 45 shows that there are additional digital advertisements that are not shown. When link 46 is activated, the missing account information document shown in Figure 10 is returned by the merchant computer.
Figure 10 shows that the merchant computer has partial information on the buyer's account. Message 47 shows that the merchant computer already knows the buyer's account number. Purchase button 48 will send the optional user reference string in dialog box 50 to the merchant computer described by the URL behind button 48 and purchase the product corresponding to digital advertisement 39. Cancel link 49 will return the user to the document shown in Figure 2.
When purchase button 48 is activated, a document 51 is sent by the merchant computer and displayed by the buyer computer as shown in Figure 11.
Figure 12 shows an alternative method of processing a sales transaction. In this method when the user requests a purchase at 52, the buyer computer constructs a payment order at 53 and sends it for approval to the payment computer at 54. The payment computer authorizes the payment order at 55; and when the payment order is authorized, returns an unforgable certificate at 56 that the payment order is valid. Means of creating such unforgable certificates are described in authenticator method number one below. If at step 55 the payment order is not authorized, a rejection message is sent at 56 and the sales transaction is terminated.
The buyer computer then proceeds at 57 to send a pre-authorized purchase request to the merchant computer. The unforgable certificate 56 is included in a purchase message at 57 that is sent at 58 to the merchant computer. Based upon the pre-authorized payment order the merchant computer performs fulfillment at 59 and returns the product at 60. In a variation, the merchant computer at 59 checks to ensure the payment order has not been previously used. This can be accomplished by checking with a payment computer or maintaining a merchant computer database of previously accepted payment orders. The unforgable certificate created at step 56 does not need to include the user account information. This variation is useful if the user wishes to make purchases and remain anonymous to the merchant. A Network Payment System
A network payment system 300 as shown in Figure 13, employs a public packet-switched network 69 to interconnect a plurality of client computers 70 and 71, and a plurality of payment computers such as 72, each payment computer having an account database 73, a settlement database 74, an authorized address database 75, a sender credential database 76, a financial system interface 77, and a real-time authorization interface 78. The interfaces 77 and 78 may be implemented by a single communications line.
In an alternate embodiment, the network payment system further includes external devices that are kept in the possession of users so that the users can authenticate themselves when they use a buyer computer. Account database 73 maintains temporal spending amounts, such as the amount spent in the current day, and also maintains temporal spending limits. The account database may also maintain a translation between principal identifiers and external account identifiers. Settlement database 74 records committed payment orders along with any authorization information for the orders that was obtained from interface 78. Address database 75 maintains for each sender a list of authorized buyer computer and delivery addresses. Credential database 76 maintains a list of credentials for principals and information that can be used to authenticate principals.
Figure 14 is a flowchart that describes the operation of the payment system. A client computer 71 constructs a payment order at 79, and computes and adds an authenticator to the payment order at 80. The payment order is sent at 81 to a payment computer, where the authenticator is verified at 82 to ensure that the payment order was originated by the sender it describes. Below we present different means of implementing 80 and 82.
If the payment order is authentic and address restrictions are desired, at 83, either or both of the client computer address or the specified delivery address can be checked against address database 75. If address restrictions are desired and if the addresses in the payment order are not in the database, the payment computer sends a rejection message to the client computer. Address database 75 specifies, for each principal, acceptable client computer addresses and delivery addresses. A delivery address can be a network address, or a street address for packaged goods. As is known in the art, database 75 can include wild-card specifications and similar techniques to reduce its size. For example, database 75 could contain an entry for principal identifier "*§acme.com" restricting legal delivery addresses to "computer: *.com", "computer: cmu.edu", and "surface: *, 34 Main Street, Anytown, USA", indicating that any user at the company Acme can order products to be delivered to the network address at Acme or the university CMU, or to anyone at 34 Main Street, Anytown, USA.
If payment order address restrictions are not desired or have been checked, processing continues at 84 where the payment order is checked for replay and temporal spending limits. Replay is checked for by making sure that the sender did not previously present a payment order with the same nonce by checking an index of committed payment orders by nonce in settlement database 74. If nonces are based on time, then a payment order that is older than an administratively determined value can be rejected out of hand. Time based nonces or sequential nonces permit old nonces to be removed from the settlement database 74. If a payment order has been previously processed or its nonce is too old, the payment order computer sends a rejection message to the client.
After the payment order passes the replay check, temporal spending limits are checked in account database 73. These spending limits can be applied on a per sender, per group of senders, and per payment system basis to limit fraud risk. The limits can be applied to any duration of time, for example a maximum spending amount per hour or per day. If the payment order would violate a spending limit, the payment computer sends a rejection message to the client.
Once the payment order passes the temporal spending check at 84, a message is constructed at 85 to check that the external account that backs the sender's payment system account has adequate funds or credit. If the sender identifier in the payment order is not already an account number in the external financial system, it is translated into a corresponding account number in the external financial system using account database 73. A real-time authorization request message is sent at 86 to the external financial system over interface 78. If the external financial system approves authorization request 86, an authorization message is returned at 87. If request 86 is not approved, the payment computer sends a rejection message to the client at 87.
In a variation of the above described approach, processing continues at 95 after 84. At 95 real-time authorization is only obtained when the total of a sender's payments since the last real-time authorization reaches a preset value, or the payment order is over a preset amount. These preset values can be optionally recorded on a per principal basis in database 73 or can be administratively determined for all principals. In this manner, the number of messages to the external financial system can be reduced. In addition, the payment system can avoid making real-time authorization requests for small payments when the risk is acceptable to the payment system operator. If real-time authorization is necessary, processing continues at 85 after 95. If real-time authorization is not necessary for a request, at 100 the payment order amount is added to the sender's total of payments since the last real¬ time authorization in database 73, and processing continues at 88. In another variation after 100 a check is made at 101 in database 73 to see if a background authorization process should be scheduled. A background authorization process permits the payment computer to continue its normal processing while it checks with the financial authorization network on the sender's account. This mechanism can be used to limit payment system risk. If the background authorization fails, the account is suspended by so updating database 73. If the sender's total of payments since last authorization is over a preset value stored in 73 then a background authorization process is scheduled at 102. Otherwise processing continues at 88.
In another variation, at 95 and 101 authorizations are obtained based on the amount spent since last authorization and time since la'st authorization.
At 88 the payment order is committed to execution and is recorded in settlement database 74. Recorded with the payment order in database 74 are portions of authentication message 87 that show that the payment computer contacted the remote financial system. The amount of the payment order is added to running temporal spending records in database 73, and an authorization message is sent to the client computer at 90. The authorization message includes the payment order. In an alternate embodiment, at 90 the authorization message contains a truncated payment order that includes at least the payment order's sender and the payment order's unique nonce. In an alternate embodiment, the authorization message sent to the client at 90 includes at least one legal delivery addresses for the sender as determined from database 75.
Authorization message 90 must be transmitted in such a way that the client computer can be sure that it came from the payment computer. At 89 a payment system specific authenticator is added payment order. At 91 this authenticator is checked by the client computer. The steps at 89 are a dual of step 80, and the steps at 91 are a dual of step 82. The authentication means for steps 89 and 91 are described below.
Finally, settlement is performed at 92 in the external financial system 77 between external accounts that correspond to the sender and the beneficiary. If settlement is accomplished as part of real-time authorization at steps 86 and 87, as may occur in a real¬ time debit network, then no other steps need to be taken. If settlement is not accomplished as part of the authorization process, then financial system messages are sent to interface 77 to effect settlement. Depending on the external accounts involved, these messages may include electronic funds transfer messages or automated clearinghouse messages.
In an alternate embodiment, at 92 settlement messages are sent to reconcile net transfer balances between principles on a temporal basis, for example once a day. In this embodiment the number of settlement messages can be less than the number of payment orders. Authenticators may be created and checked using one of the following methods. The payment computer can use any of the first four methods, and the client computer can use any of the methods described.
In a first method for authenticators, at steps 80 or 89, a digest of the payment order is signed by the sending computer using a public-key cryptographic system such as RSA. This signature is used as the authenticator. As is well known in the art, the signing can be accomplished using a private key created from a public-key pair, where the signing key is only known by the signer, and the other public key is known to the receiving computer. At the payment computer the public key corresponding to each sender is kept in credential database 76. The private key for the payment service is also kept in database 76. At steps 82 or 91, the signature of the received message is checked using the public key known to the receiving computer.
In a second method for authenticators, at steps 80 or 89, a digest of the payment order is signed by the sending computer with a private key cryptosystem such as DES. This signature is used as the authenticator. At the payment computer, the private key corresponding to each sender is kept in credential database 76. At step 80, a digest of the payment order is signed by the client computer, and at step 89 a digest of the payment order with an added approval code is signed by the payment computer using the same private key. At steps 82 or 91, the signature of the received message is checked using the shared private key.
In a third method for authenticators, at step 80 the authenticator is computed by a protected device external to the system such as a Smart-Card. A protected device is specifically designed to be extremely difficult both to replicate and to compromise. In this method, the payment order is communicated at 80 to a Smart-Card. The Smart-Card computes and signs a digest of the payment order, and then communicates the signature back at 80 to be used as an authenticator. A Smart-Card produced authenticator uniquely associates a payment order with its creating Smart-Card. This is accomplished by having the Smart-Card contain a secret key "K" that is used to create a digital signature of the payment order. "K" is never released outside of the Smart-card. The Smart-Card is designed to make it computationally infeasible to compute "K" even with possession of the device. In this method, at step 82, a signature checking key from database 76 is used to check the authenticator. In an alternate embodiment, a user must manually signal their acceptance of each payment order on an input device that is part of the external device before the authenticator is created by the external device.
In a fourth method for authenticators, at steps 80 or 89, a network address is used as an authenticator. At steps 82 or 91, a digest of the payment order is sent back to the specified network address along with a random password. The computer at the specified network address must then return the payment order digest along with the password. If the network guarantees to deliver messages to the proper network address, this method will guarantee that the user or computer at the specified network address approves of the payment order. Assuming that network delivery is trusted, this method can be used to authenticate a sender computer's network address in a payment order. Alternatively, electronic mail can be used to send such confirmation messages between a user and the payment system.
In a fifth method for authenticators, at step 80, the authenticator is produced by an external device that produces a sequence of non-predicable transaction identifiers that are device specific. The authenticator is entered by the user into the client computer by reading its display. One such device is described in U.S. Patent 4,856,062. According to this method, at step 91, the authenticator can be checked using the sender specific fixed cede of the device which is kept in database 76. This sequence of steps is also shown in Figure 15 at steps 93 and 94.
In a sixth method for authenticators, at step 80, the authenticator is obtained by querying the user for a transaction identifier that is the next string from a physical list of one-time authorization strings. Such as list could be produced on a card, and the user can cross off authorization strings as they are used. According to this method, at step 91, the authenticator is checked against the next expected string from the sender using database 76. Database 76 can hold for each sender a list of random authorization strings, or can hold a sender specific secret key that was used to generate the list of authentication strings along with how many strings have been used so far. This sequence of steps is also shown in Figure 15 at 93 and 94.
In a seventh method for authenticators, at step 80 the authenticator is a previously obtained personal identification number (PIN) for the user. In this method in 91 the authenticator is checked against the expected PIN for the sender using database 76.
As will be obvious to one skilled in the art, any of the methods for creating authenticators can be used together to increase system security. For example, authenticator method six can be used to create an authenticator based on a transaction identifier, and then a payment order including a transaction identifier can be given a further authenticator using authenticator method one. In this example the resulting authenticators would be checked with their respective methods. A digest of a payment order can be created with an algorithm such as MD5 [R. Rivest, The MD5 Message- Digest Algorithm, MIT Laboratory for Computer Science, Network Working Group Request for Comments 1321] . Alternatively, a digest can be the entire payment order or other functions of the payment order's component parts.
In addition in both the sales and payment systems alternate authenticator techniques can be used such as those described by Voydock and Kent in "Security
Mechanisms in High-level Network Protocols", Computing Surveys Vol. 15, No. 2, June 1983. As will be appreciated by those skilled in the art, two-way authenticated byte-stream or remote procedure call interface connections that protect against replay can replace our message based authenticators.
Additions, subtractions, deletions, and other modifications of the described embodiment will be apparent to those practiced in the art and are within the scope of the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4775935 *||22 Sep 1986||4 Oct 1988||Westinghouse Electric Corp.||Video merchandising system with variable and adoptive product sequence presentation order|
|US4799156 *||1 Oct 1986||17 Jan 1989||Strategic Processing Corporation||Interactive market management system|
|US4812628 *||27 Mar 1987||14 Mar 1989||Visa International Service Association||Transaction system with off-line risk assessment|
|US4922521 *||8 Mar 1989||1 May 1990||U.S. Philips Corporation||System for providing secure telecommunication access to a computer|
|US4935870 *||3 Aug 1988||19 Jun 1990||Keycom Electronic Publishing||Apparatus for downloading macro programs and executing a downloaded macro program responding to activation of a single key|
|US4992940 *||13 Mar 1989||12 Feb 1991||H-Renee, Incorporated||System and method for automated selection of equipment for purchase through input of user desired specifications|
|US5025373 *||30 Jun 1988||18 Jun 1991||Jml Communications, Inc.||Portable personal-banking system|
|1||*||See also references of EP0734556A4|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|WO1997022074A1 *||11 Dec 1996||19 Jun 1997||Cybergold, Inc.||Method for trading customer attention for advertisement|
|WO1997023838A1 *||23 Dec 1996||3 Jul 1997||Catalina Marketing International, Inc.||System and method for providing shopping aids and incentives to customers through a computer network|
|WO1997032257A1 *||26 Feb 1997||4 Sep 1997||Aim Corporation||Communication system capable of providing user with picture meeting characteristics of user and terminal equipment and information providing device used for the same|
|WO1997032258A1 *||26 Feb 1997||4 Sep 1997||Aim Corporation||Communication system for distributing such message as advertisement to user of terminal equipment|
|WO1997046946A1 *||5 Jun 1997||11 Dec 1997||Aim Corporation||Terminal, information providing device, system, and recording medium|
|WO1998021677A1 *||14 Nov 1997||22 May 1998||Matsushita Electric Industrial Co., Ltd.||Personal electronic settlement system, its terminal, and management apparatus|
|WO1998030964A2 *||9 Jan 1998||16 Jul 1998||Buyonet International Ab||A system for secure data transmission over an electronic link|
|WO1998030964A3 *||9 Jan 1998||13 Aug 1998||Buyonet Internat||A system for secure data transmission over an electronic link|
|WO1999010850A1 *||13 Jul 1998||4 Mar 1999||The Chase Manhattan Bank||Apparatus and method for automated processing of product purchases and purchase transaction validations|
|WO1999057864A1 *||29 Apr 1999||11 Nov 1999||British Telecommunications Public Limited Company||Communications system for electronic commerce|
|WO2000026867A1 *||19 Oct 1999||11 May 2000||Maz Mikroelektronik Anwendungszentrum Hamburg Gmbh||Method for the electronic payment via internet|
|WO2001016784A3 *||30 Aug 2000||2 Aug 2001||Emmanuelle Cornuejols||Communication method and device|
|WO2001055979A1 *||24 Jan 2001||2 Aug 2001||Smarttrust Systems Oy||Payment device and method for secure payment|
|WO2001059731A1 *||9 Feb 2001||16 Aug 2001||Internet Cash.Com||Methods and systems for making secure electronic payments|
|WO2001090861A2 *||25 May 2001||29 Nov 2001||Echarge Corporation||Secure transaction protocol|
|WO2001090861A3 *||25 May 2001||13 Jun 2002||Echarge Corp||Secure transaction protocol|
|WO2002001517A1 *||26 Jun 2000||3 Jan 2002||Mover S.P.A.||A method for carrying out electronic commerce transactions|
|WO2002005224A2 *||10 Jul 2001||17 Jan 2002||Paypal, Inc.||System and method for verifying a financial instrument|
|WO2002005224A3 *||10 Jul 2001||24 Jul 2003||Paypal Inc||System and method for verifying a financial instrument|
|WO2002025606A2 *||20 Sep 2001||28 Mar 2002||Soma Networks, Inc.||Point of sale terminal|
|WO2002025606A3 *||20 Sep 2001||2 Oct 2003||Everitt Long||Point of sale terminal|
|WO2002059849A1 *||26 Jan 2001||1 Aug 2002||Ihsan Iskender Pak||Method and system for preventing credit card fraud|
|WO2003042938A2 *||14 Nov 2002||22 May 2003||Encorus Technologies Gmbh||Payment protocol and data transmission method and data transmission device for conducting payment transactions|
|WO2003042938A3 *||14 Nov 2002||4 Dec 2003||Dirk Ammermann||Payment protocol and data transmission method and data transmission device for conducting payment transactions|
|WO2003091959A1 *||26 Nov 2002||6 Nov 2003||Ismail Adam Karolia||Payment instrument and system|
|WO2003107230A1 *||18 Dec 2002||24 Dec 2003||Vilmos Andras||Set of equipment for the preparation and execution of the financial performance of a business transaction between a seller and a buyer|
|WO2004023412A1 *||5 Sep 2002||18 Mar 2004||Pti Systems Inc.||Method of electronic commerce transaction verification|
|DE10108872B4 *||15 Feb 2001||11 Apr 2013||Deutsche Telekom Ag||Verfahren zur Ermöglichung der Entschlüsselung von übertragenen Informationen|
|EP0779587A2 *||11 Sep 1996||18 Jun 1997||Kabushiki Kaisha N.K Kikaku||On-line shopping system and the method of payment settlement|
|EP0779587A3 *||11 Sep 1996||15 Oct 1997||N K Kikaku Kk||On-line shopping system and the method of payment settlement|
|EP0803105A1 *||24 Oct 1995||29 Oct 1997||Open Market, Inc.||Network sales system|
|EP0803105A4 *||24 Oct 1995||29 Apr 1998||Open Market Inc||Network sales system|
|EP0816997A2 *||23 Jun 1997||7 Jan 1998||Sun Microsystems, Inc.||Dynamic display advertising|
|EP0816997A3 *||23 Jun 1997||8 Sep 1999||Sun Microsystems, Inc.||Dynamic display advertising|
|EP0848343A2 *||11 Dec 1997||17 Jun 1998||Hitachi, Ltd.||Shopping system|
|EP0848343A3 *||11 Dec 1997||3 Feb 1999||Hitachi, Ltd.||Shopping system|
|EP0858697A1 *||30 Oct 1996||19 Aug 1998||First Virtual Holdings, Inc.||Computerized payment system for purchasing goods and services on the internet|
|EP0858697A4 *||30 Oct 1996||2 May 2002||First Virtual Holdings Inc||Computerized payment system for purchasing goods and services on the internet|
|EP0896703A1 *||27 Nov 1996||17 Feb 1999||Lsi Logic Corporation||Integrated network browser chip, network browser system, and method for network data communication|
|EP0896703A4 *||27 Nov 1996||4 Jul 2007||Lsi Logic Corp||Integrated network browser chip, network browser system, and method for network data communication|
|EP0907134A1 *||11 Sep 1997||7 Apr 1999||Esd Information Technology Entwicklungs GmbH||Method for computer supported payment transaction through payment systems|
|EP0923036A1 *||5 Jun 1997||16 Jun 1999||Aim Corporation||Terminal, information providing device, system, and recording medium|
|EP0923036A4 *||5 Jun 1997||6 Oct 2004||Global Media Online Inc||Terminal, information providing device, system, and recording medium|
|EP0954817A1 *||4 Sep 1997||10 Nov 1999||Priceline.Com Incorporated||Conditional purchase offer management systems|
|EP0954817A4 *||4 Sep 1997||26 Jul 2000||Priceline Com Inc||Conditional purchase offer management systems|
|EP0954818A2 *||9 Jan 1998||10 Nov 1999||Buyonet International||A system for secure data transmission over an electronic link|
|EP0954818A4 *||9 Jan 1998||6 Nov 2002||Buyonet Internat Inc||A system for secure data transmission over an electronic link|
|EP1017030A2 *||29 Dec 1999||5 Jul 2000||International Business Machines Corporation||Four-party credit/debit payment protocol|
|EP1020824A2 *||10 Dec 1999||19 Jul 2000||CheckFree Corporation||Technique for conducting secure transactions over a network|
|EP1020824A3 *||10 Dec 1999||20 Dec 2000||CheckFree Corporation||Technique for conducting secure transactions over a network|
|EP1079348A2 *||10 Aug 2000||28 Feb 2001||Creanet||Online payment method|
|EP1079348A3 *||10 Aug 2000||14 Mar 2001||Creanet||Online payment method|
|EP1126712A2 *||31 Jan 2001||22 Aug 2001||Sony Corporation||Data-providing system, transmission server, data terminal apparatus and data-providing method|
|EP1126712A3 *||31 Jan 2001||8 Feb 2006||Sony Corporation||Data-providing system, transmission server, data terminal apparatus and data-providing method|
|EP1131754A1 *||24 Sep 1999||12 Sep 2001||Oneclip.Com, Incorporated||Method of and system for distributing and redeeming electronic coupons|
|EP1131754A4 *||24 Sep 1999||23 Jul 2003||Catalina Marketing Int||Method of and system for distributing and redeeming electronic coupons|
|EP1190350A1 *||18 Feb 2000||27 Mar 2002||Louis C. Garbarino||System and method for processing financial transactions|
|EP1190350A4 *||18 Feb 2000||18 Oct 2006||Exxonmobil Oil Corp||System and method for processing financial transactions|
|EP1218838A1 *||7 Sep 2000||3 Jul 2002||Epacific Inc.||Method of and system for authorizing purchases made over a computer network|
|EP1218838A4 *||7 Sep 2000||25 Jan 2006||Epacific Inc||Method of and system for authorizing purchases made over a computer network|
|EP1313073A2 *||13 Mar 2002||21 May 2003||Encorus Technologies GmbH||Data transfer method and assembly with context identifier|
|EP1313073A3 *||13 Mar 2002||19 Nov 2003||Encorus Technologies GmbH||Data transfer method and assembly with context identifier|
|EP1657695A2 *||1 Aug 1997||17 May 2006||AT&T Corp.||Interactive multimedia advertising and electronic commerce on a hypertext network|
|EP1657695A3 *||1 Aug 1997||21 Jun 2006||AT&T Corp.||Interactive multimedia advertising and electronic commerce on a hypertext network|
|EP2209095A1 *||10 Jul 2001||21 Jul 2010||Paypal, Inc.||System and method for verifying a financial instrument|
|US5715314 *||24 Oct 1994||3 Feb 1998||Open Market, Inc.||Network sales system|
|US5794210 *||11 Dec 1995||11 Aug 1998||Cybergold, Inc.||Attention brokerage|
|US5855008 *||28 Aug 1997||29 Dec 1998||Cybergold, Inc.||Attention brokerage|
|US5890137 *||26 Jul 1996||30 Mar 1999||Kabushiki Kaisha N.K. Kikaku||On-line shopping system and the method of payment settlement|
|US5970469 *||26 Mar 1996||19 Oct 1999||Supermarkets Online, Inc.||System and method for providing shopping aids and incentives to customers through a computer network|
|US6014634 *||4 Aug 1997||11 Jan 2000||Supermarkets Online, Inc.||System and method for providing shopping aids and incentives to customers through a computer network|
|US6144988 *||23 Jul 1998||7 Nov 2000||Experian Marketing Solutions, Inc.||Computer system and method for securely formatting and mapping data for internet web sites|
|US6240396||4 Sep 1997||29 May 2001||Priceline.Com Incorporated||Conditional purchase offer management system for event tickets|
|US6327578 *||29 Dec 1998||4 Dec 2001||International Business Machines Corporation||Four-party credit/debit payment protocol|
|US6332133||14 Nov 1997||18 Dec 2001||Matsushita Electric Industrial Co., Ltd.||Personal electronic settlement system, its terminal, and management apparatus|
|US6356878||22 Dec 1997||12 Mar 2002||Priceline.Com Incorporated||Conditional purchase offer buyer agency system|
|US6366967||18 May 1999||2 Apr 2002||Datascape, Inc.||Open network system for i/o operation including a common gateway interface and an extended open network protocol with non-standard i/o devices utilizing device and identifier for operation to be performed with device|
|US6484153||4 Sep 1997||19 Nov 2002||Priceline.Com Incorporated||System and method for managing third-party input to a conditional purchase offer (CPO)|
|US6510418||4 Jan 1999||21 Jan 2003||Priceline.Com Incorporated||Method and apparatus for detecting and deterring the submission of similar offers in a commerce system|
|US6519584||26 Jun 1996||11 Feb 2003||Sun Microsystem, Inc.||Dynamic display advertising|
|US6553346||4 Sep 1997||22 Apr 2003||Priceline.Com Incorporated||Conditional purchase offer (CPO) management system for packages|
|US6560581||8 Jun 1998||6 May 2003||Visa International Service Association||System and method for secure electronic commerce transaction|
|US6601037||17 Jun 1999||29 Jul 2003||Usa Technologies, Inc.||System and method of processing credit card, e-commerce, and e-business transactions without the merchant incurring transaction processing fees or charges worldwide|
|US6622124||23 Jun 2000||16 Sep 2003||Usa Technologies, Inc.||Method of transacting an electronic mail, an electronic commerce, and an electronic business transaction by an electronic commerce terminal operated on a transportation vehicle|
|US6754641||11 Dec 2000||22 Jun 2004||Usa Technologies, Inc.||Dynamic identification interchange method for exchanging one form of identification for another|
|US6907315||22 May 2003||14 Jun 2005||Amazon.Com, Inc.||Method and system for displaying and editing of information|
|US7020774||30 Aug 2000||28 Mar 2006||Georges Marc Cornuejols||Communications method and device|
|US7206754 *||7 Jun 2000||17 Apr 2007||Donald Spector||System for issuing short life coupons or other promotional devices|
|US7207885||15 Jan 2004||24 Apr 2007||Espeed, Inc.||System and method for using a game controller device for electronic trading|
|US7225142||1 Aug 1996||29 May 2007||At&T Corp.||Interactive multimedia advertising and electronic commerce on a hypertext network|
|US7240022||19 May 1998||3 Jul 2007||Mypoints.Com Inc.||Demographic information gathering and incentive award system and method|
|US7386508||23 Dec 1998||10 Jun 2008||Priceline.Com, Incorporated||Method and apparatus for facilitating a transaction between a buyer and one seller|
|US7415526||1 Feb 2001||19 Aug 2008||Sony Corporation||Data-providing system, transmission server, data terminal apparatus and data-providing method|
|US7430537||10 Jul 2001||30 Sep 2008||Paypal, Inc.||System and method for verifying a financial instrument|
|US7472074||13 Apr 1998||30 Dec 2008||Priceline.Com Incorporated||Method and apparatus for a commercial network system designed to facilitate buyer-driven conditional purchase offers|
|US7516089||18 Feb 1999||7 Apr 2009||Pricline.Com Incorporated||System and method for allocating business to one of a plurality of sellers in a buyer driven electronic commerce system|
|US7599850 *||19 Jun 2000||6 Oct 2009||Catalina Marketing Corporation||Method of and system for managing promotions for purchase transactions over a network|
|US7620619||18 Nov 1999||17 Nov 2009||Priceline.Com Incorporated||Conditional purchase offer management system|
|US7640240||26 Sep 2006||29 Dec 2009||Coupons.Com Incorporated||System and method for augmenting content in electronic documents with links to contextually relevant information|
|US7664672||18 Feb 2000||16 Feb 2010||Priceline.Com Incorporated||Conditional purchase offer management system|
|US7720712||12 Apr 2000||18 May 2010||Amazon.Com, Inc.||Placing a purchase order using one of multiple procurement options|
|US7810134||22 Jan 2007||5 Oct 2010||First Data Corporation||Authentication system for financial transactions|
|US7827062||12 Mar 2004||2 Nov 2010||Google Inc.||Method of delivery, targeting, and measuring advertising over networks|
|US7844488||12 Mar 2004||30 Nov 2010||Doubleclick Inc.||Method of delivery, targeting, and measuring advertising over networks|
|US7930207||12 Mar 2004||19 Apr 2011||Google Inc.||Method of delivery, targeting, and measuring advertising over networks|
|US7966222 *||12 Jun 1997||21 Jun 2011||Catalina Marketing Corporation||System and method for distributing information through cooperative communication network sites|
|US7991701||1 Sep 2010||2 Aug 2011||Visa International Service Association||Online payer authentication service|
|US8024260||9 Jun 2000||20 Sep 2011||Paypal Inc.||Method for transmitting a code|
|US8046255||23 Apr 2008||25 Oct 2011||Mypoints.Com Inc.||System and method for generating personalized offers through an information gathering system|
|US8050967||23 Apr 2008||1 Nov 2011||Mypoints.Com Inc.||System and method for tracking user activity in an incentive award system|
|US8082180||16 Dec 2009||20 Dec 2011||Priceline.Com Incorporated||Conditional purchase offer management system|
|US8082221||2 Oct 2009||20 Dec 2011||Priceline.Com Incorporated||Conditional purchase offer management system|
|US8086653||18 Feb 2000||27 Dec 2011||Priceline.Com Incorporated||Conditional purchase offer management system|
|US8095450||25 Sep 2007||10 Jan 2012||Priceline.Com Incorporated||Method and apparatus for facilitating a transaction between a buyer and one seller|
|US8135650||24 Nov 2008||13 Mar 2012||Priceline.Com, Incorporated||Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers|
|US8170945||29 Jun 2005||1 May 2012||Bgc Partners, Inc.||System and method for providing security to a game controller device for electronic trading|
|US8224691||16 Feb 2000||17 Jul 2012||Catalina Marketing Corporation||System and method for distributing information through cooperative communication network sites|
|US8271395||24 May 2002||18 Sep 2012||Visa International Service Association||Online account authentication service|
|US8296204||26 Aug 2008||23 Oct 2012||Paypal Inc.||System and method for reducing RIKS associated with accepting a financial instrument|
|US8301556||19 Sep 2011||30 Oct 2012||Paypal Inc.||Method for transmitting a code|
|US8370259||8 Nov 2011||5 Feb 2013||Ebay, Inc.||Verifying the source of electronically exchanged value|
|US8417637||8 Nov 2011||9 Apr 2013||Paypal Inc.||Approving the use of the source of funds|
|US8469808||29 Jun 2005||25 Jun 2013||Bgc Partners, Inc.||System and method for managing a game controller device for electronic trading|
|US8515871||8 Nov 2011||20 Aug 2013||Paypal Inc.||Authorizing use of a financial instrument|
|US8533322||22 Mar 2012||10 Sep 2013||Experian Marketing Solutions, Inc.||Service for associating network users with profiles|
|US8548871||20 Feb 2009||1 Oct 2013||Priceline.Com Incorporated||System and method for allocating business to one of a plurality of sellers in a buyer driven electronic commerce system|
|US8566140||23 Apr 2008||22 Oct 2013||Mypoints.Com Inc.||Method for providing custom profile analysis in a demographic information system|
|US8566154||26 Feb 2002||22 Oct 2013||Google Inc.||Network for distribution of re-targeted advertising|
|US8600878||13 Sep 2012||3 Dec 2013||Ebay Inc.||Method for transmitting a code|
|US8676644||26 Sep 2002||18 Mar 2014||Google Inc.||Method of delivery, targeting, and measuring advertising over networks|
|US8700453||16 Jul 2012||15 Apr 2014||Catalina Marketing Corporation||System and method for distributing information through cooperative communication network sites|
|US8700481||17 Nov 2011||15 Apr 2014||Priceline.Com Incorporated||Conditional purchase offer management system|
|US8712920||26 Jan 2012||29 Apr 2014||Priceline.Com Incorporated||Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers|
|US8732066||17 Nov 2011||20 May 2014||Priceline.Com Incorporated||Method and apparatus for facilitating a transaction between a buyer and one seller|
|US8799208||7 Mar 2000||5 Aug 2014||E-Rewards, Inc.||Method and system for evaluating, reporting, and improving on-line promotion effectiveness|
|US8834278||23 Apr 2007||16 Sep 2014||Bgc Partners, Inc.||System and method for using a game controller device for electronic trading|
|US8840471||23 Apr 2007||23 Sep 2014||Bgc Partners, Inc.||System and method for using a game controller device for electronic trading|
|US9058340||9 Sep 2013||16 Jun 2015||Experian Marketing Solutions, Inc.||Service for associating network users with profiles|
|US9092817||23 Sep 2013||28 Jul 2015||Amazon Technologies, Inc.||Placing a purchase order using one of multiple procurement options|
|US9519915||23 Sep 1999||13 Dec 2016||Catalina Marketing Corporation||System and method for providing shopping aids and incentives to customer through a computer network|
|US9684916||25 Jun 2014||20 Jun 2017||Groupon, Inc.||Retail system for selling products based on a flexible product description|
|US9754302||2 Nov 2015||5 Sep 2017||Groupon, Inc.||Retail system for selling products based on a flexible product description|
|USRE40444 *||17 Jul 2003||29 Jul 2008||International Business Machines Corporation||Four-party credit/debit payment protocol|
|International Classification||G06Q10/00, G06Q20/00, G06Q30/00, G06F17/30, B65G61/00, G06F13/00, G07F7/00|
|Cooperative Classification||G06Q20/10, G06Q20/027, G06Q20/401, G06Q20/04, G06Q30/0251, G06Q20/385, G06Q20/085, G06Q20/02, G06Q30/0609, G06Q30/02, G07F7/00, G06Q20/12, G06Q30/0277, G06Q30/06, G06Q30/0253, G06Q10/087, G06Q30/0601, G06Q20/023|
|European Classification||G06Q20/04, G06Q30/02, G06Q20/12, G06Q20/02, G06Q30/06, G06Q10/087, G06Q20/385, G06Q20/023, G06Q20/10, G06Q30/0277, G06Q30/0253, G06Q20/401, G06Q30/0609, G06Q30/0601, G06Q20/027, G06Q20/085, G06Q30/0251, G07F7/00|
|22 Jun 1995||AL||Designated countries for regional patents|
Kind code of ref document: A1
Designated state(s): AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE
|22 Jun 1995||AK||Designated states|
Kind code of ref document: A1
Designated state(s): JP
|13 Sep 1995||121||Ep: the epo has been informed by wipo that ep was designated in this application|
|12 Oct 1995||DFPE||Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)|
|18 Jun 1996||WWE||Wipo information: entry into national phase|
Ref document number: 1995905366
Country of ref document: EP
|2 Oct 1996||WWP||Wipo information: published in national office|
Ref document number: 1995905366
Country of ref document: EP
|4 Sep 2002||WWG||Wipo information: grant in national office|
Ref document number: 1995905366
Country of ref document: EP