WikiPatents - Community Patent Review
Create Free Account  |  License or Sell Your Patent  |  WikiPatents Marketplace  |  WikiPatents Blog
Username:  Password:  
    
Advanced Search
System and method for merchant invoked electronic commerce    
United States Patent6092053   
Link to this pagehttp://www.wikipatents.com/6092053.html
Inventor(s)Boesch; Brian (Oak Hill, VA); Farrell; Patrick (Falls Church, VA); Light; Elliott (Rockville, MD); Eisenberg; R. Scott (Bethesda, MD)
AbstractA system and method for merchant invoked electronic commerce allowing consumers to purchase items over a network and merchants to receive payment information relating to the purchases. The system includes a server having software which gathers the purchasing information from a consumer to complete a purchasing transaction over a network. The system has a consumer data structure that stores purchasing information for registered consumers. The software is able to access the consumer data structure and enter the consumer's purchasing information during subsequent purchases. Having the software obtain and enter the consumer's purchasing information, the consumer does not have to enter the same information every time they purchase an item over the network. In alternate embodiments, the same technology can be applied to other arenas where a user may have to enter the same repetitive information.
   














 Title Information Submit all comments and votes
 
Patent Text Patent PDF Print Page Summary File History
Plain text PDF images Print Summary File History
Drawing from US Patent 6092053
System and method for merchant invoked electronic commerce - US Patent 6092053 Drawing
System and method for merchant invoked electronic commerce
Inventor     Boesch; Brian (Oak Hill, VA); Farrell; Patrick (Falls Church, VA); Light; Elliott (Rockville, MD); Eisenberg; R. Scott (Bethesda, MD)
Owner/Assignee     Cybercash, Inc. (Reston, VA)
Patent assignment
All assignments
Publication Date     July 18, 2000
Application Number     09/167,873
PAIR File History     Application Data   Transaction History
Image File Wrapper   Patent Term   Fees
Litigation
Filing Date     October 7, 1998
US Classification    
Int'l Classification    
Examiner     Trammell; James P.
Assistant Examiner     Tesfamariam; Mussie K.
Attorney/Law Firm     Roberts, Abokhair & Mardula
Address
Parent Case    
Priority Data    
USPTO Field of Search    
Patent Tags     merchant invoked electronic commerce
   
Enter a comma (,) or semicolon (;) between multiple tag words/phrases.
Describe this patent:
 Amusing   
 Clever   
 Complex   
 Efficient   
 Historic   
 Important   
 Innovative   
 Interesting   
 Practical   
 Simple   
[no votes]
Patent WIKI

Share information and news about this patent, including information and news about the technology, inventors, company, ligation and licensing.

 References Submit all comments and votes
 
*references marked with an asterisk below are user-added references
 U.S. References
 
Add a new US reference:  
ReferenceRelevancyCommentsReferenceRelevancyComments
5987140
Rowney

Nov,1999

[0 after 0 votes]
5960411
Hartman
705/26
Sep,1999

[0 after 0 votes]
5724424
Gifford
705/79
Mar,1998

[0 after 0 votes]
5715314
Payne
705/78
Feb,1998

[0 after 0 votes]
4799156
Shavit
705/26
Jan,1989

[0 after 0 votes]
 Foreign References
 Other References
 Market Review Submit all comments and votes
   
Market Size
Estimate the gross annual revenues of the relevant market sector:
> $10B
$5B - $10B
$2B - $5B
$500M - $2B
$100M - $500M
$10M - $100M
$1M - $10M
$500K - $1M
$100K - $500K
< $100K
[No votes]
$0
 
$0   $2.5B   $5B   $7.5B   $10B
Market Share
Estimate the percentage of the relevant market sector this invention will capture:
75% - 100%
50% - 74.99%
25% - 49.99%
10 - 24.99%
5 - 9.99%
2 - 4.99%
1 - 1.99%
< 1%
[No votes]
0.0%
 
0%   25%   50%   75%   100%
Reasonable Royalty
What percentage of gross sales should the inventor or assignee be paid?
75% - 100%
50% - 74.99%
25% - 49.99%
10 - 24.99%
5 - 9.99%
2 - 4.99%
1 - 1.99%
< 1%
[No votes]
0.0%
 
0%   25%   50%   75%   100%
Public's "Guesstimation" of Royalty Value
Market SizeN/A[No votes]
xMarket ShareN/A[No votes]
xReasonable RoyaltyN/A[No votes]

N/A

License Availablity
If you are NOT the owner or assignee, answer here:
Yes, license is available for purchase

No, license is not currently available



[No votes]
License Availablity
If you ARE the owner or assignee, answer here:
Yes, license is available for purchase

No, license is not currently available



[No votes]
Competitive Advantage
Does this invention have a significant competitive advantage over similar technologies?
Yes

No



[No votes]
Most helpful competitive advantage comment
[No comments]

Commercial Alternatives
Are there viable commercial alternatives for this invention?
Yes

No



[No votes]
Most helpful commercial alternative comment
[No comments]

 Technical Review Submit all comments and votes
 Claims Submit all comments and votes
 


We claim:

1. A system for merchant invoked electronic commerce comprising:

a network;

at least one consumer computer associated with at least one consumer and connected to the network, wherein the at least one consumer computer further comprises a web browser for accessing and communicating over the network;

at least one merchant computer associated with at least one merchant and connected to the network, wherein the at least one merchant computer further comprises web server software for hosting a web page and for executing client software for allowing the at least one merchant to send and receive information over the network; and

at least one consumer information server connected to the at least one consumer computer via the network and to the at least one merchant computer via the network, wherein the at least one consumer information server fer comprises consumer information server software, and wherein the client software further comprises instructions for forwarding a merchant's

offer to the at least one consumer information server via the consumer's web browser and the consumer information server software further comprises instructions for gathering purchasing information to complete a purchasing transaction.

2. The system in accordance with claim 1, wherein the consumer information server further comprises instructions to send the purchasing information to the at least one merchant computer.

3. The system in accordance with claim 1, wherein the network is selected from group consisting of the Internet, intranet, local area networks (LANS), and wide area networks (WANS).

4. The system in accordance with claim 1, wherein the client software further comprises instructions for instructing the consumer web browser to forward the merchant's offer to the consumer information server and to send a message to the consumer information server indicating whether a browser identifier is present in the consumer's web browser, and wherein the presence of a browser identifier indicates whether the consumer's web browser was previously used in conjunction with the system.

5. The system in accordance with claim 4, wherein the browser identifier is a cookie.

6. The system in accordance with claim 4, further comprising a consumer data structure which further comprises information pertaining to previous purchasing transactions by at least one registered consumer, and wherein a registered consumer is a consumer who has previously registered with the system.

7. The system in accordance with claim 6, wherein the consumer information server further comprises storage for storing the consumer data structure.

8. The system in accordance with claim 6, wherein the system further comprises at least one server for storing the consumer data structure.

9. The system in accordance with claim 4, wherein the system further comprises a merchant data structure which further comprises label-value pairs which represent merchant information that is necessary to identify the merchant and the merchant computer.

10. The system in accordance with claim 9, wherein the merchant information further comprises contact information, merchant identification number, at least one network location for the merchant computer, accepted payment card types, accepted currencies, and accepted payment methods.

11. The system in accordance with claim 9, wherein the consumer information server further comprises storage for storing the merchant data structure.

12. The system in accordance with claim 9, wherein the system further comprises at least one server for storing the merchant data structure.

13. The system in accordance with claim 4, further comprising:

a consumer data structure which further comprises information pertaining to previous purchasing transactions by at least one registered consumer, wherein a registered consumer is a consumer who has previously registered with the system and

a merchant data structure which further comprises label-value pairs which represent merchant information that is necessary to identify the merchant and the merchant computer.

14. The system in accordance with claim 13, wherein the consumer information server software further comprises instructions to select a consumer if the browser identifier identifies one or more registered consumers who have used the consumer's web browser in conjunction with the system.

15. The system in accordance with claim 14, wherein the consumer information server software further comprises instructions to gather the purchasing information pertaining to the selected registered consumer from the consumer data structure to complete a purchasing transaction.

16. The system in accordance with claim 15, wherein the consumer information server software further comprises instructions to select the purchasing information for a selected registered consumer that is acceptable to the merchant based on the merchant information in the merchant data structure.

17. The system in accordance with claim 16, wherein the consumer information server software further comprises instructions to gather the purchasing information to complete a purchasing transaction by prompting the registered consumer for additional purchasing information to complete a transaction if the consumer data structure is missing purchasing information to complete the purchasing transaction.

18. The system in accordance with claim 13, wherein the consumer information server software further comprises instructions to gather the purchasing information to complete a purchasing transaction by prompting the consumer for the purchasing information when the consumer is a non-registered consumer.

19. The system in accordance with claim 14, wherein the consumer information server software further comprises instructions to allow a registered consumer to enter information to identify the registered consumer thereby allowing the consumer information server software to access the registered consumer's information stored in the consumer data structure if the consumer information server software did not select the correct registered consumer.

20. The system in accordance with claim 19, wherein the information which can be entered to identify the registered consumer comprises a consumer identification number, email address, and a passphrase.

21. The system in accordance with claim 14, wherein the consumer information server software further comprises instructions to allow a registered consumer to enter information to identify the registered consumer thereby allowing the consumer information server software to access the registered consumer's information stored in the consumer data structure if the registered consumer was not associated with the consumer's web browser.

22. The system in accordance with claim 21, wherein the information which can be entered to identify the registered consumer comprises a consumer identification number, email address, and a passphrase.

23. The system in accordance with claim 14, wherein the consumer information server software further comprises instructions to prompt the selected consumer for the consumer's identification number and passphrase if the registered consumer was selected by the consumer information server software.

24. The system in accordance with claim 18, wherein the system further comprises a temporary data structure for storing for a limited amount of time purchasing information pertaining to a purchasing transaction.

25. The system in accordance with claim 1, wherein the merchant's offer comprises a merchant identifier, a price for the item, a digital signature of the merchant, and a transaction number.

26. The system in accordance with claim 25, wherein the merchant's offer further comprises a final price indicator which indicates that the price for an item is not final.

27. The system in accordance with claim 26, wherein the consumer information server software further comprises instructions which communicate the consumer's shipping address information to the merchant computer for calculating the final price for the item if the final price indicator indicates that the price for an item is not final.

28. The system in accordance with claim 27, wherein the consumer's shipping address information communicated to the merchant further comprises the city, state, country and mail code of the consumer's shipping address.

29. The system in accordance with claim 27, wherein the merchant computer further comprises instructions for calculating the final price for the item being purchased based on the consumer's shipping address information.

30. The system in accordance with claim 27, wherein the consumer's shipping address information communicated to the merchant further comprises the shipping means.

31. The system in accordance with claim 30, wherein the merchant computer further comprises instructions for calculating the final price for the item being purchased based on the consumer's shipping address information.

32. The system in accordance with claim 27, wherein the consumer's shipping address is the email address where the item is being sent for items which can be delivered over the network.

33. The system in accordance with claim 18, wherein the consumer information server software further comprises instructions to set a flag if a non-registered consumer elects to become a registered consumer.

34. The system in accordance with claim 33, wherein the consumer information server software further comprises instructions to prompt a non-registered consumer for registration information if the flag is set indicating that a non-registered consumer elected to become a registered consumer.

35. The system in accordance with claim 34, wherein the consumer information server software further comprises instructions to transfer the information stored in the temporary data structure to the consumer data structure when a non-registered consumer elects to become a registered consumer.

36. The system in accordance with claim 1, wherein the system further comprises a consumer transaction log for recording information relating to a registered consumer's purchasing transactions, wherein a registered consumer is a consumer who has previously registered with the system.

37. The system in accordance with claim 36, wherein the consumer information server further comprises storage for storing the consumer transaction log.

38. The system in accordance with claim 36, further comprising at least one server to store the consumer transaction log.

39. The system in accordance with claim 1, further comprising a merchant transaction log which stores label-value pairs relating to transactions performed by the at least one merchant.

40. The system in accordance with claim 39, wherein the consumer information server further comprises storage for storing the merchant transaction log.

41. The system in accordance with claim 39, further comprising at least one server for storing the merchant transaction log.

42. A method for merchant invoked electronic commerce over a network between at least one consumer having at least one consumer computer connected to the network, at least merchant having at least one merchant computer connected to the network, and at least one consumer information server connected to the network, wherein the method comprises: requesting a merchant's offer from at least one merchant over a network by at least one

consumer using a web browser on at least one consumer computer; invoking client software on the at least one merchant computer in response to the consumer's request for a merchant's offer, and wherein invoking the client software further comprises:

connecting the at least one consumer computer to the at least one consumer information server;

invoking the consumer information server software;

forwarding the merchant's offer to the least one consumer information server; and

gathering the purchasing information by the consumer information server to complete a purchasing transaction.

43. The method in accordance with claim 42, further comprising sending the purchasing information to the at least one merchant computer.

44. The method in accordance with claim 42, further comprising the client software instructing the consumer web browser to forward the merchant's offer to the consumer information server and sending a message indicating whether a browser identifier is present in the consumer's web browser.

45. The method in accordance with claim 44, wherein the sending of a message indicating whether a browser identifier is present in the consumer's web browser further comprises the client software instructing the web browser to forward a message and wherein the browser identifier is a cookie.

46. The method in accordance with claim 44, further comprising selecting a registered consumer if the browser identifier indicates a plurality of registered consumers who have used the consumer's web browser, and wherein a registered consumer is a consumer who has previously registered with the system.

47. The method in accordance with claim 46, further comprising accessing a merchant data structure to determine the purchasing information the at least one merchant requires to complete a purchasing transaction.

48. The method in accordance with claim 47, further comprising accessing a consumer data structure to gather the purchasing information the at least one merchant requires to complete a purchasing transaction.

49. The method in accordance with claim 48, further comprising prompting the registered consumer for additional purchasing information to complete a purchasing transaction if the consumer data structure is missing purchasing information which is necessary for the at least one merchant to complete a purchasing transaction.

50. The method in accordance with claim 42, further comprising prompting the consumer for the purchasing information when the consumer is a non-registered consumer.

51. The method in accordance with claim 48, fer comprising a registered consumer entering identifying information to allow a registered consumer to identify the registered consumer thereby allowing the consumer information server software to access the registered consumer's information from the consumer data structure if the consumer information server software did not select the registered consumer.

52. The method in accordance with claim 51, wherein entering the identifying information further comprises a consumer entering the consumer's identification number, email address, and a passphrase.

53. The method in accordance with claim 48, further comprising a registered consumer entering identifying information to allow a registered consumer to identify the registered consumer thereby allowing the consumer information server software to access the registered consumer's information from the consumer data structure if the registered consumer is not associated with the consumer's web browser.

54. The method in accordance with claim 53, wherein entering the identifying information further comprises a consumer entering the consumer's identification number, email address, and a passphrase.

55. The method in accordance with claim 48, further comprising prompting the selected registered consumer to enter the consumer's identification number and passphrase when the registered consumer was selected by the consumer information server software.

56. The method in accordance with claim 50, further comprising storing the consumer's purchasing information in a temporary data structure when the consumer is a non registered consumer.

57. The method in accordance with claim 56, further comprising transferring the consumer's purchasing information from the temporary data structure when a non-registered consumer elects to become a registered consumer.

58. The method in accordance with claim 48, further comprising sending the consumer's shipping address information to the merchant computer when a final price indicator in the merchant's offer indicates that the price for an item is not final.

59. The method in accordance with claim 58, wherein sending the consumer's shipping address further comprises sending the consumer's city, state, country and mail code.

60. The method in accordance with claim 58, further comprising the merchant computer calculating a final price based on the consumer's shipping address.

61. The method in accordance with claim 42, further comprising recording information relating to a registered consumer's purchasing transactions, wherein a registered consumer is a consumer who has previously registered with the system.

62. The method in accordance with claim 42, further comprising recording label-value pairs relating to transactions performed by the at least one merchant.

63. A system for merchant invoked electronic commerce for gathering information to complete a purchasing transaction comprising:

a network;

at least one consumer computer for operation by a consumer desiring to purchase an item;

at least one merchant computer; and

at least one consumer information server;

said consumer computer, merchant computer and consumer information server being interconnected by the network;

said merchant computer being programmed to receive a consumer's request for a merchant's offer to purchase an item, and to cause a merchant's offer further comprising a transaction number associated with the merchant offer to be sent to the consumer;

said consumer information server being programmed to receive the transaction number and to gather and send the purchasing information to the merchant computer to complete the purchasing transaction; and

said merchant computer being further programmed to process the purchasing information to complete the purchasing transaction.

64. A system for accessor invoked software to allow the electronic delivery of information comprising:

an accessee computer associated with at least one accessee and connected to the network, wherein the accessee computer further comprises a web browser which allows the accessee to access and communicate over the network;

an accessor computer associated with at least one accessor and connected to the network, wherein the accessor computer further comprises web server software which operates a web page and client software which allows the at least one accessor to send and receive information;

at least one information server connected to the accessee computer via the network and to the accessor computer via the network, wherein the at least one information server further comprises information server software for gathering the purchasing information to complete a transaction, wherein when the at least one accessee makes a data request from the accessor, the client software is initiated thereby connecting the accessee computer to the at least one information server and forwards the accessee's data requests to the at least one information server via the accessee's web browser wherein the information server software gathers the data request information to complete the data request.

65. The system in accordance with claim 64, wherein the information server software further comprises instructions to send the data request information to the accessor for processing.

66. The system in accordance with claim 64 wherein the network is selected from group consisting of the Internet, intranet, local area networks (LANS), and wide area networks (WANS).

67. The system in accordance with claim 64, wherein the client software further comprises instructions for instructing the accessee web browser to forward the accessor's data request to the at least one information server and to send a message to the information server indicating whether a browser identifier is present in the accessee's web browser, and wherein the presence of a browser identifier indicates whether the accessee's web browser was previously used in conjunction with the system.

68. The system in accordance with claim 67, wherein the browser identifier is a cookie.

69. The system in accordance with claim 67, further comprising an accessee data structure which further comprises information pertaining to previous transactions by at least one registered accessee, and wherein a registered accessee is an accessee who has previously registered with the system.

70. The system in accordance with claim 69, wherein the information server further comprises storage for storing the accessee data structure.

71. The system in accordance with claim 69, wherein the system further comprises at least one server for storing the accessee data structure.

72. The system in accordance with claim 67, wherein the system further comprises an accessor data structure which further comprises label-value pairs which represent accessor information that is necessary to identify the accessor and the accessor computer.

73. The system in accordance with claim 72, wherein the accessor information further comprises contact information, accessor identification number, and at least one network location for the accessor computer.

74. The system in accordance with claim 72, wherein the information server further comprises storage for storing the accessor data structure.

75. The system in accordance with claim 72, wherein the system further comprises at least one server for storing the accessor data structure.

76. The system in accordance with claim 67, further comprising:

an accessee data structure which further comprises information pertaining to previous purchasing transactions by at least one registered accessee, wherein a registered accessee is an accessee who has previously registered with the system and

an accessor data structure which further comprises label-value pairs which represent accessor information that is necessary to identify the accessor and the accessor computer.

77. The system in accordance with claim 76, wherein the information server software further comprises instructions to select an accessee if the browser identifier identifies one or more registered accessees who have used the accessee's web browser in conjunction with the system.

78. The system in accordance with claim 77, wherein the information server software further comprises instructions to gather the data request information pertaining to the selected registered accessee from the accessee data structure to complete a transaction.

79. The system in accordance with claim 78, wherein the information server software further comprises instructions to select the data request information for a selected registered accessee that is acceptable to the accessor based on the accessor information in the accessor data structure.

80. The system in accordance with claim 79, wherein the information server software further comprises instructions to gather the data request information to complete a transaction by prompting the registered accessee for additional data request information necessary to complete a transaction if the accessee data structure is missing data request information necessary to complete the transaction.

81. The system in accordance with claim 76, wherein the information server software further comprises instructions to gather the data request information to complete a transaction by prompting the accessee for the necessary data request information when the accessee is a non-registered accessee.

82. The system in accordance with claim 77, wherein the information server software further comprises instructions to allow a registered accessee to enter information to identify the registered accessee thereby allowing the information server software to access the registered accessee's information stored in the accessee data structure if the information server software did not select the correct registered accessee.

83. The system in accordance with claim 82, wherein the information which can be entered to identify the registered accessee comprises an accessee identification number, email address, and a passphrase.

84. The system in accordance with claim 77, wherein the information server software further comprises instructions to allow a registered accessee to enter information to identify the registered accessee thereby allowing the information server software to access the registered accessee's information stored in the accessee data structure if the registered accessee was not associated with the accessee's web browser.

85. The system in accordance with claim 84, wherein the information which can be entered to identify the registered accessee comprises an accessee identification number, email address, and a passphrase.

86. The system in accordance with claim 77, wherein the information server software further comprises instructions to prompt the selected accessee for the accessee's identification number and passphrase if the registered accessee was selected by the information server software.

87. The system in accordance with claim 81, wherein the system further comprises a temporary data structure for storing for a limited amount of time data request information pertaining to a transaction.

88. The system in accordance with claim 65, wherein the accessee's data request comprises an accessor id, a digital signature of the accessor, and a transaction number.

89. The system in accordance with claim 81, wherein the information server software further comprises instructions to set a flag if a non-registered accessee elects to become a registered accessee.

90. The system in accordance with claim 89, wherein the information server software further comprises instructions to prompt a non-registered accessee for registration information if the flag is set indicating that a non-registered accessee elected to become a registered accessee.

91. The system in accordance with claim 90, wherein the information server software further comprises instructions to transfer the information stored in the temporary data structure to the accessee data structure when a non-registered accessee elects to become a registered accessee.

92. The system in accordance with claim 65, wherein the system further comprises an accessee transaction log for recording information relating to a registered accessee's transactions, wherein a registered accessee is an accessee who has previously registered with the system.

93. The system in accordance with claim 92, wherein the information server further comprises storage for storing the accessee transaction log.

94. The system in accordance with claim 92, further comprising at least one server to store the accessee transaction log.

95. The system in accordance with claim 65, further comprising an accessor transaction log which stores label-value pairs relating to transactions performed by the at least one accessor.

96. The system in accordance with claim 95, wherein the information server further comprises storage for storing the accessor transaction log.

97. The system in accordance with claim 95, further comprising at least one server for storing the accessor transaction log.

98. The system in accordance with claim 65, wherein the accessee is a potential mortgage borrower and the accessor is a mortgage lender.

99. The system in accordance with claim 98, wherein the data request information further comprises the information necessary for the mortgage lender to make a decision on whether to lend money to a borrower.

100. The system in accordance with claim 65, wherein the accessee is a potential student and the accessor is an educational institution.

101. The system in accordance with claim 100, wherein the data request information further comprises the information necessary for the educational institution to make a decision on whether to enroll a potential student at the educational institution.

102. A method for accessor invoked software to allow the electronic delivery of information over a network between at least one accessee having at least one accessee computer connected to the network, at least one accessor having at least one accessor computer connected to the network, and at least one information server connected to the network, wherein the method comprises:

requesting a data request from at least one accessor over a network by at least one accessee using a web browser on at least one accessee computer;

invoking client software on the at least one accessor computer in response to the accessee's request for a accessor's offer, and wherein invoking the client software further comprises:

connecting the at least one accessee computer to the at least one information server;

invoking the information server software;

forwarding the accessor's offer to the least one information server; and

gathering the purchasing information by the information server to complete a purchasing transaction.

103. The method in accordance with claim 102, further comprising sending the purchasing information to the at least one accessor computer.

104. The method in accordance with claim 102, further comprising the client software instructing the accessee web browser to forward the accessor's data request to the information server and sending a message indicating whether a browser identifier is present in the accessee's web browser.

105. The method in accordance with claim 104, wherein the sending of a message indicating whether a browser identifier is present in the accessee's web browser further comprises the client software instructing the web browser to forward a message and wherein the browser identifier is a cookie.

106. The method in accordance with claim 104, further comprising selecting a registered accessee if the browser identifier indicates a plurality of registered accessees who have used the accessee's web browser, and wherein a registered accessee is a accessee who has previously registered with the system.

107. The method in accordance with claim 106, further comprising accessing an accessor data structure to determine the data request information the at least one accessor requires to complete a transaction.

108. The method in accordance with claim 107, further comprising accessing an accessee data structure to gather the necessary data request information the at least one accessor requires to complete a transaction.

109. The method in accordance with claim 108, further comprising prompting the registered accessee for additional data request information to complete a transaction if the accessee data structure is missing data request information which is necessary for the at least one accessor to complete a transaction.

110. The method in accordance with claim 102, further comprising prompting the accessee for the necessary data request information when the accessee is a non-registered accessee.

111. The method in accordance with claim 108, further comprising a registered accessee entering identifying information to allow a registered accessee to identify the registered accessee thereby allowing the information server software to access the registered accessee's information from the accessee data structure if the information server software did not select the registered accessee.

112. The method in accordance with claim 111, wherein entering the identifying information further comprises the accessee entering the accessee's identification number, email address, and a passphrase.

113. The method in accordance with claim 108, further comprising a registered accessee entering identifying information to allow a registered accessee to identify the registered accessee thereby allowing the information server software to access the registered accessee's information from the accessee data structure if the registered accessee is not associated with the accessee's web browser.

114. The method in accordance with claim 113, wherein entering the identifying information further comprises the accessee entering the accessee's identification number, email address, and a passphrase.

115. The method in accordance with claim 111, further comprising prompting the selected registered accessee to enter the accessee's identification number and passphrase when the registered accessee was selected by the information server software.

116. The method in accordance with claim 110, further comprising storing the accessee's data request information in a temporary data structure when the accessee is a non-registered accessee.

117. The method in accordance with claim 116, further comprising transferring the accessee's data request information from the temporary data structure when a non-registered accessee elects to become a registered accessee.

118. The method in accordance with claim 102, further comprising recording information relating to a registered accessee's transactions, wherein a registered accessee is an accessee who has previously registered with the system.

119. The method in accordance with claim 102, farther comprising recording label-value pairs relating to transactions performed by the at least one accessor.

120. The system in accordance with claim 17, wherein the prompting of the registered consumer is presented with a brand.

121. The system in accordance with claim 120, wherein the brand is the merchant's brand.

122. The system in accordance with claim 18, wherein the prompting of the non-registered consumer is presented with a brand.

123. The system in accordance with claim 122, wherein the brand is the merchant's brand.
 Description Submit all comments and votes
 


FIELD OF THE INVENTION

This invention relates generally to a method and system where certain information pertaining to a consumer is stored on a server and is provided to a third party at the request of the consumer. More particularly, the present invention relates to a method and system where certain consumer information is stored on a server and is provided to a merchant thereby allowing the consumer to use an electronic payment system to purchase a product or service over a network in an easy and safe manner.

BACKGROUND OF THE INVENTION

With the emergence of the Internet, consumers and merchants are using the Internet to engage in electronic commerce. To purchase products over the Internet, consumers typically prefer to use electronic payment services. Such services offer a variety of features, including security, privacy, anonymity, and access to transaction histories. The basic model for such services requires a communication link between a consumer's computer and a merchant's computer, and a link between the merchant's computer and a payment server. To use such a payment service, consumers are required to install large amounts of software (commonly called "wallets") onto their computer for the purpose of storing an electronic representation of money or for identifying sources of payments. An example of electronic payment services include such services as SET Specification, HP, CyberCash, IBM, OTP, etc).

If a consumer installs the software for a wallet onto the consumer's computer, the consumer typically has to update the wallet software to correct bugs, to add features, or to improve service performance. Further, the wallet software is accessible only on the computer on which the wallet software is installed. As a result, the consumer must install a copy of the wallet software onto each computer from which the consumer desires to access the payment service.

Once the wallet from a payment service is installed, the consumer may be limited as to where the consumer can shop because of the proprietary nature of the electronic payment service business. Typically a consumer can only purchase a product or service from a merchant who accepts payments from the same payment service. As a result, merchants may opt to use a plethora of payment services thereby raising costs and requiring merchants to manage a variety of software programs.

Present payment services require consumers to go through a large number of steps to complete a transaction. Research has shown that the more steps a consumer is required to take to complete a transaction, the more likely that the consumer will terminate the purchase process prior to completing the purchase. Experience has also shown that, as impressive as wallets may be from a theoretical perspective, consumers don't like them and don't use them. As a consequence, transactions are performed over the Internet in non-secure environments or in inefficient manners, or both.

In order to avoid such problems, some inventions have created new types of systems. One such system requires consumers to use a payment server which sends an access message to a merchant thereby causing the desired product to be sent to the consumer. The access messages include such information as a product identifier and a message authenticator. The message identifier is necessary to identify which product is to be sent and the message authenticator is necessary to ensure that the access message is legitimate. Once the payment server authorizes the transaction, an access message is sent to the merchant. However, these type of systems go against the current mode of operation where merchants determine the authorization of a transaction. Merchants typically want to control the authorization of a transaction in the same manner as they are accustomed to. Presently, if a consumer purchases an item at a store, the merchant controls the authorization of the transaction.

Therefore, a need exists for a system that allows a consumer to send payment information to a merchant's computer over the Internet in a manner that offers security, allows access from any computer that has access to the Internet, delivers payment information to a merchant's computer regardless of the payment system that the merchant uses to process transactions, and allows system upgrades without dependency on the consumers.

SUMMARY OF THE INVENTION

It is therefore an object of the present invention to reduce the number of steps a consumer is required to perform in order to purchase a product over any network.

A further object of the present invention is to reduce the number of steps a consumer is required to perform in order to purchase a product over the Internet.

A further object of the present invention is to eliminate the need for consumers to leave a merchant's site to acquire an electronic form of payment.

A further object of the present invention is to eliminate wallet software which is permanently stored on the consumer's computers.

A further object of the present invention is to create a consumer information server for storing wallet software, that can be accessed

easily and transparently by a consumer.

A further object of the present invention is to allow the system administrator of the consumer information server to upgrade the software on such server at any time.

A further object of the present invention is to allow flexibility in providing new or modified services to the consumers via upgrades to software stored on the consumer information server.

A further object of the present invention is to reduce the number of payment parameters consumers are required to fill in when purchasing products over a network.

A further object of the present invention is to allow a consumer to conduct transactions using data stored on the consumer information server from any computer connected to the network on which the consumer information server resides.

A further object of the present invention is to allow consumer information to be provided to merchants using payment systems from various service providers.

A further object of the present invention is to use the architecture of the consumer information server to aid the consumer in distributing all manner of information, not just purchase/money information, to a variety of recipients when those recipients are to receive essentially the same information from one recipient to the next.

A further object of the present invention is to provide a mechanism for direct marketing to consumer wallet holders immediately before, during, or after completion of a transaction using a wallet.

The present invention is a system for presenting a consumer's purchasing information to a merchant's computer to allow a sale of goods or services to be consummated. The system comprises a computer associated with a consumer (the "consumer's computer"), a computer associated with a merchant (the "merchant's computer") and a server (the "consumer information server" or "CIS") on which the necessary and desirable information about the consumer is stored. The consumer's computer, the merchant's computer, and the CIS are connected to a network, such as the Internet, and communicate using communication protocols. The consumer's computer operates Web browser software (the "consumer's browser"). The merchant's computer operates as a web server, provides transaction processing, and performs other functions. The merchant's computer may be a single device, or may, at the merchant's discretion comprise a number devices which may or may not be co-located. The merchant's computer also operates software ("client software") that communicates with the CIS. The CIS operates CIS software which provides access to information stored in various databases, logs, and/or datastructures.

The present invention allows consumers to purchase products over a network and allows merchants to receive payment information relating to that purchase. During the shopping process, a consumer browses a merchant's Web site. The merchant's Web site includes goods and/or services (herein, "item") for sale. The merchant's Web site also operates client software. When the consumer requests a merchant's offer, the client software sends a browser readable file and the merchant's offer to the consumer's browser on the consumer's computer. The merchant's offer comprises in part a transaction number which is not representative of the product code or description. The browser readable file includes an address to the merchant's Web page and instructions that instruct the consumer's browser to communicate with the CIS software. The merchant's offer passes through the consumer's computer to the CIS software.

The CIS software returns a message to the consumer's browser and instructs the consumer's browser to display a graphic within an area reserved for the wallet within the merchant's Web page. The content of this graphic depends on whether or not the consumer is known to the CIS software.

If the consumer is known to the CIS software, the CIS software takes information contained in the merchant's offer, formats the information to allow the consumer's browser to display the merchant's offer, and sends the merchant's offer to the consumer's computer where the merchant's offer is displayed by the consumer's browser within the area reserved for the wallet within the merchant's Web page. The consumer is prompted to decide whether or not to purchase the item. Typically, this communication occurs by the consumer clicking on an object resulting in a message being communicated to the CIS.

If the consumer elects to purchase the item, the CIS software forwards information to the merchant's computer. The information includes information from the merchant's offer and the consumer's personal information (e.g., credit card number, address, shipping address) which is stored on the CIS. The merchant's computer then uses the information to complete the transaction.

If the consumer is unknown to the CIS software, the CIS software sends a form to the consumer's computer which is displayed within the area reserved for the wallet within the merchant's Web page. The form prompts the consumer to provide the purchasing information to complete the transaction. Once the consumer provides sufficient information to complete the transaction, the CIS software prompts the consumer to purchase the item. If the consumer elects to purchase the item, then the consumer is prompted to elect to have the information retained on the CIS for future use (the process herein referred to as "registration"). If the consumer answers "no", then the information is stored in a temporary data structure. Information stored in the temporary data structure is retained for a set amount of time and is not available for reuse by the consumer. If the consumer answers "yes", then the information pertaining to the consumer is stored in a data structure intended for the retention and future use by the consumer.

If the consumer elects to register with the CIS software, during the registration process, the consumer's browser is sent a browser identifier. In the preferred embodiment, the browser identifier is a cookie. The browser identifier contains data which is crypto graphically protected to enhance security. The browser identifier allows the CIS software to identify the consumer's browser and permits a customer to authenticate himself or herself, thereby permitting the CIS software to use the consumer's stored information in future transactions.

The system also allows consumers who are registered on a different browser to authorize the CIS software to use the consumer's stored information. This situation occurs when the CIS software cannot identify the browser identifier because there is no browser identifier in the consumer's browser or the browser identifier cannot be