US6061665A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System, method and article of manufacture for dynamic negotiation of a network payment framework
Assignee: Ent Services Development Corp LP
•
Filing: 1997-06-06
•
Granted: 2000-05-09
•
Expires: 2017-06-06
Abstract
Abstract A system that facilitates the coupling of a plurality of clients to one or more merchants utilizing a network to conduct commerce over the network is disclosed. When a client initiates a connection with a merchant, the merchant responds to the request for connection by transmitting one or more messages back to the client to determine a particular payment processing which entails determining a suitable payment instrument, a payment protocol and standard message formats for conducting the electronic commerce. The payment protocol comprises a message format, a protocol associated with the message format and a weight associated with each of the items associated with the payment processing. The weight is provided by both the client and the merchant to facilitate dynamic negotiation of a mutually acceptable payment processing. The negotiation results in the exchange of standard message formats that the client and the merchant are equipped to process efficiently and securely.
Inventors
- 👤 Ali Reza Bahreman
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-03 21:49
CPC Classifications
G; G06; G06Q; G06Q20/00; G06Q20/08; G06Q20/12; G06Q20/10; G06Q20/102
Claims Analysis
Total Claims: 47
Claim 1
Independent Claim
204 words
A method for negotiating a mutually acceptable payment processing framework between one or more client computers and one or more merchant computers coupled by a network, comprising the steps of: (a) generating a client message including a client token and transmitting the client message from the client computer to the merchant computer utilizing the network; (b) receiving the client message at the merchant computer, utilizing the client token to generate a merchant message including a merchant token containing one or more merchant acceptable payment processing frameworks, and transmitting the merchant message from the merchant computer to the client computer; (c) receiving the merchant message at the client computer, comparing the one or more merchant acceptable payment processing frameworks contained in the merchant token to one or more client acceptable payment processing frameworks; (d) selecting the mutually acceptable payment processing framework, generating a message including a negotiation finalization token indicating the mutually acceptable payment processing framework for the client computer and the merchant computer, and transmitting the message from the client computer to the merchant computer; and (e) receiving the message at the merchant computer, utilizing the negotiation finalization token to transmit an indicia of the mutually acceptable payment processing framework to the client computer.
Claim 2
Independent Claim
204 words
A method for negotiating a mutually acceptable payment processing framework between one or more client computers and one or more merchant computers coupled by a network, comprising the steps of: (a) generating a client message including a client token and transmitting the client message from the client computer to the merchant computer utilizing the network; (b) receiving the client message at the merchant computer, utilizing the client token to generate a merchant message including a merchant token containing one or more merchant acceptable payment processing frameworks, and transmitting the merchant message from the merchant computer to the client computer; (c) receiving the merchant message at the client computer, comparing the one or more merchant acceptable payment processing frameworks contained in the merchant token to one or more client acceptable payment processing frameworks; (d) selecting the mutually acceptable payment processing framework, generating a message including a negotiation finalization token indicating the mutually acceptable payment processing framework for the client computer and the merchant computer, and transmitting the message from the client computer to the merchant computer; and (e) receiving the message at the merchant computer, utilizing the negotiation finalization token to transmit an indicia of the mutually acceptable payment processing framework to the client computer.
Claim 3
Dependent Claim
13 words
The method as recited in claim 1, wherein the network is the Internet.
Claim 4
Dependent Claim
25 words
The method as recited in claim 1, including the step of generating the client token by transmitting a null token to a client negotiation manager.
Claim 5
Dependent Claim
22 words
The method as recited in claim 1, wherein the client token includes payment processing information that is acceptable to the client computer.
Claim 6
Dependent Claim
23 words
The method as recited in claim 1, wherein the client token includes a list of payment capability stubs without complete payment processing information.
Claim 7
Dependent Claim
30 words
The method as recited in claim 1, wherein the merchant computer extracts the client token from the client message and processes the client token utilizing a merchant computer negotiation manager.
Claim 8
Dependent Claim
19 words
The method as recited in claim 1, wherein the mutually acceptable payment processing framework includes a payment processing method.
Claim 9
Dependent Claim
18 words
The method as recited in claim 1, wherein the mutually acceptable payment processing framework includes a payment capability.
Claim 10
Dependent Claim
19 words
The method as recited in claim 1, wherein the mutually acceptable payment processing framework includes a secure payment protocol.
Claim 11
Dependent Claim
19 words
The method as recited in claim 9, wherein the secure payment protocol is a secure socket layer protocol (SSL).
Claim 12
Dependent Claim
104 words
The method as recited in claim 1, further comprising the steps of: (c1) selecting one or more mutually acceptable payment processing frameworks, generating a second client message including a second client token including the one or more mutually acceptable payment processing frameworks, and transmitting the second client message from the client computer to the merchant computer; and (c2) selecting at least one of the one or more mutually acceptable payment processing frameworks, generating a second merchant message including a second merchant token including the selected mutually acceptable payment processing frameworks, and transmitting the second merchant message from the merchant computer to the client computer.
Claim 13
Dependent Claim
14 words
The method as recited in claim 1, wherein steps (c1) and (c2) are repeated.
Claim 14
Dependent Claim
21 words
The method as recited in claim 1, wherein the mutually acceptable payment processing framework includes account information or an account proxy.
Claim 15
Dependent Claim
18 words
The method as recited in claim 1, wherein the mutually acceptable payment processing framework includes a payment instrument.
Claim 16
Dependent Claim
18 words
The method as recited in claim 1, wherein the mutually acceptable payment processing framework includes a payment mechanism.
Claim 17
Dependent Claim
18 words
The method as recited in claim 1, wherein the mutually acceptable payment processing framework includes a service provider.
Claim 18
Independent Claim
216 words
An apparatus for negotiating a mutually acceptable payment processing framework between one or more client computers and one or more merchant computers coupled by a network, comprising: (a) first software that generates a client message including a client token and transmitting the client message from the client computer to the merchant computer utilizing the network; (b) second software that receives the client message at the merchant computer, utilizes the client token to generate a merchant message including a merchant token containing one or more merchant acceptable payment processing frameworks, and transmits the merchant message from the merchant computer to the client computer; (c) third software that receives the merchant message at the client computer, compares the one or more merchant acceptable payment processing frameworks contained in the merchant token to one or more client acceptable payment processing frameworks; (d) fourth software that selects the mutually acceptable payment processing framework, generates a message including a negotiation finalization token indicating the mutually acceptable payment processing framework for the client computer and the merchant computer, and transmits the message from the client computer to the merchant computer; and (e) fifth software that receives the message at the merchant computer, utilizes the negotiation finalization token to transmit an indicia of the mutually acceptable payment processing framework to the client computer.
Claim 19
Independent Claim
216 words
An apparatus for negotiating a mutually acceptable payment processing framework between one or more client computers and one or more merchant computers coupled by a network, comprising: (a) first software that generates a client message including a client token and transmitting the client message from the client computer to the merchant computer utilizing the network; (b) second software that receives the client message at the merchant computer, utilizes the client token to generate a merchant message including a merchant token containing one or more merchant acceptable payment processing frameworks, and transmits the merchant message from the merchant computer to the client computer; (c) third software that receives the merchant message at the client computer, compares the one or more merchant acceptable payment processing frameworks contained in the merchant token to one or more client acceptable payment processing frameworks; (d) fourth software that selects the mutually acceptable payment processing framework, generates a message including a negotiation finalization token indicating the mutually acceptable payment processing framework for the client computer and the merchant computer, and transmits the message from the client computer to the merchant computer; and (e) fifth software that receives the message at the merchant computer, utilizes the negotiation finalization token to transmit an indicia of the mutually acceptable payment processing framework to the client computer.
Claim 20
Dependent Claim
29 words
The apparatus as recited in claim 17, wherein the Internet is utilized to transmit information between the one or more client computers and the one or more merchant computers.
Claim 21
Dependent Claim
23 words
The apparatus as recited in claim 17, wherein the client token is generated by transmitting a null token to a client negotiation manager.
Claim 22
Dependent Claim
22 words
The apparatus as recited in claim 17, wherein the client token includes payment processing information that is acceptable to the client computer.
Claim 23
Dependent Claim
23 words
The apparatus as recited in claim 17, wherein the client token includes a list of payment capability stubs without complete payment processing information.
Claim 24
Dependent Claim
30 words
The apparatus as recited in claim 17, wherein the merchant computer extracts the client token from the client message and processes the client token utilizing a merchant computer negotiation manager.
Claim 25
Dependent Claim
19 words
The apparatus as recited in claim 17, wherein the mutually acceptable payment processing framework includes a payment processing method.
Claim 26
Dependent Claim
18 words
The apparatus as recited in claim 17, wherein the mutually acceptable payment processing framework includes a payment capability.
Claim 27
Dependent Claim
19 words
The apparatus as recited in claim 17, wherein the mutually acceptable payment processing framework includes a secure payment protocol.
Claim 28
Dependent Claim
109 words
The apparatus as recited in claim 17, further comprising: (c1) a sixth software that selects one or more mutually acceptable payment processing frameworks, generates a second client message including a second client token including the one or more mutually acceptable payment processing frameworks, and transmits the second client message from the client computer to the merchant computer; and (c2) a seventh software that selects at least one of the one or more mutually acceptable payment processing frameworks, generates a second merchant message including a second merchant token including the selected mutually acceptable payment processing frameworks, and transmits the second merchant message from the merchant computer to the client computer.
Claim 29
Dependent Claim
21 words
The apparatus as recited in claim 17, wherein the mutually acceptable payment processing framework includes account information or an account proxy.
Claim 30
Dependent Claim
18 words
The apparatus as recited in claim 17, wherein the mutually acceptable payment processing framework includes a payment instrument.
Claim 31
Dependent Claim
18 words
The apparatus as recited in claim 17, wherein the mutually acceptable payment processing framework includes a payment mechanism.
Claim 32
Dependent Claim
18 words
The apparatus as recited in claim 17, wherein the mutually acceptable payment processing framework includes a service provider.
Claim 33
Dependent Claim
232 words
A computer program embodied on a computer-readable medium for negotiating a mutually acceptable payment processing framework between one or more client computers and one or more merchant computers coupled by a network, comprising: (a) a first code segment that generates a client message including a client token and transmitting the client message from the client computer to the merchant computer utilizing the network; (b) a second code segment that receives the client message at the merchant computer, utilizes the client token to generate a merchant message including a merchant token containing one or more merchant acceptable payment processing frameworks, and transmits the merchant message from the merchant computer to the client computer; (c) a third code segment that receives the merchant message at the client computer, compares the one or more merchant acceptable payment processing frameworks contained in the merchant token to one or more client acceptable payment processing frameworks; (d) a fourth code segment that selects the mutually acceptable payment processing framework, generates a message including a negotiation finalization token indicating the mutually acceptable payment processing framework for the client computer and the merchant computer, and transmits the message from the client computer to the merchant computer; and (e) a fifth code segment that receives the message at the merchant computer, utilizes the negotiation finalization token to transmit an indicia of the mutually acceptable payment processing framework to the client computer.
Claim 34
Dependent Claim
232 words
A computer program embodied on a computer-readable medium for negotiating a mutually acceptable payment processing framework between one or more client computers and one or more merchant computers coupled by a network, comprising: (a) a first code segment that generates a client message including a client token and transmitting the client message from the client computer to the merchant computer utilizing the network; (b) a second code segment that receives the client message at the merchant computer, utilizes the client token to generate a merchant message including a merchant token containing one or more merchant acceptable payment processing frameworks, and transmits the merchant message from the merchant computer to the client computer; (c) a third code segment that receives the merchant message at the client computer, compares the one or more merchant acceptable payment processing frameworks contained in the merchant token to one or more client acceptable payment processing frameworks; (d) a fourth code segment that selects the mutually acceptable payment processing framework, generates a message including a negotiation finalization token indicating the mutually acceptable payment processing framework for the client computer and the merchant computer, and transmits the message from the client computer to the merchant computer; and (e) a fifth code segment that receives the message at the merchant computer, utilizes the negotiation finalization token to transmit an indicia of the mutually acceptable payment processing framework to the client computer.
Claim 35
Dependent Claim
30 words
The computer program as recited in claim 31, wherein the Internet is utilized to transmit information between the one or more client computers and the one or more merchant computers.
Claim 36
Dependent Claim
24 words
The computer program as recited in claim 31, wherein the client token is generated by transmitting a null token to a client negotiation manager.
Claim 37
Dependent Claim
23 words
The computer program as recited in claim 31, wherein the client token includes payment processing information that is acceptable to the client computer.
Claim 38
Dependent Claim
24 words
The computer program as recited in claim 31, wherein the client token includes a list of payment capability stubs without complete payment processing information.
Claim 39
Dependent Claim
31 words
The computer program as recited in claim 31, wherein the merchant computer extracts the client token from the client message and processes the client token utilizing a merchant computer negotiation manager.
Claim 40
Dependent Claim
20 words
The computer program as recited in claim 31, wherein the mutually acceptable payment processing framework includes a payment processing method.
Claim 41
Dependent Claim
19 words
The computer program as recited in claim 31, wherein the mutually acceptable payment processing framework includes a payment capability.
Claim 42
Dependent Claim
20 words
The computer program as recited in claim 31, wherein the mutually acceptable payment processing framework includes a secure payment protocol.
Claim 43
Dependent Claim
112 words
The computer program as recited in claim 31, further comprising: (c1) a sixth code segment that selects one or more mutually acceptable payment processing frameworks, generates a second client message including a second client token including the one or more mutually acceptable payment processing frameworks, and transmits the second client message from the client computer to the merchant computer; and (c2) a seventh code segment that selects at least one of the one or more mutually acceptable payment processing frameworks, generates a second merchant message including a second merchant token including the selected mutually acceptable payment processing frameworks, and transmits the second merchant message from the merchant computer to the client computer.
Claim 44
Dependent Claim
22 words
The computer program as recited in claim 31, wherein the mutually acceptable payment processing framework includes account information or an account proxy.
Claim 45
Dependent Claim
19 words
The computer program as recited in claim 31, wherein the mutually acceptable payment processing framework includes a payment instrument.
Claim 46
Dependent Claim
19 words
The computer program as recited in claim 31, wherein the mutually acceptable payment processing framework includes a payment mechanism.
Claim 47
Dependent Claim
19 words
The computer program as recited in claim 31, wherein the mutually acceptable payment processing framework includes a service provider.
References Cited (Backward Citations)
US3651511A
Cited
US3956615A
Cited
US4277837A
Cited
US4303904A
Cited
US4454414A
Cited
US4877950A
Cited
US4906828A
Cited
US4630201A
Cited
EP0172670A2
Cited
US4614861A
Cited
US4689478A
Cited
US4766293A
Cited
EP0256768A2
Cited
EP0256768B1
Cited
US4799156A
Cited
US4859837A
Cited
US5644727A
Cited
US4968873A
Cited
EP0326699A2
Cited
US4935962A
Cited
US5030806A
Cited
US4992646A
Cited
US5594910A
Cited
US4984155A
Cited
EP0363122A2
Cited
EP0363122B1
Cited
US5016274A
Cited
US4992940A
Cited
EP0416482A2
Cited
US5175416A
Cited
EP0666681A2
Cited
US5220501A
Cited
US5452352A
Cited
WO1991016691A1
Cited
US5319542A
Cited
GB2251098A
Cited
US5221838A
Cited
US5465291A
Cited
US5383113A
Cited
EP0527639A2
Cited
US5440634A
Cited
WO1993008545A1
Cited
US5453601A
Cited
US5455407A
Cited
US5448045A
Cited
US5297030A
Cited
US5476259A
Cited
US5485510A
Cited
US5478993A
Cited
US5420405A
Cited
US5666493A
Cited
US5465206B1
Cited
US5465206A
Cited
US5506832A
Cited
EP0658862A2
Cited
EP0668579A2
Cited
US5461217A
Cited
US5557518A
Cited
US5703949A
Cited
US5649117A
Cited
US5590038A
Cited
US5459304A
Cited
US5715314A
Cited
US5590197A
Cited
US5677955A
Cited
US5742845A
Cited
US5768385A
Cited
US5671280A
Cited
US5671279A
Cited
US5754772A
Cited
US5729594A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-05-09 | 2003-11-08 | 2004-05-09 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-05-09 | 2007-11-08 | 2008-05-09 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-05-09 | 2011-11-08 | 2012-05-09 | $7700.00 | Window Closed / Lapsed |