System, method and article of manufacture for dynamic negotiation of a network payment framework
First Claim
1. 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.
10 Assignments
0 Petitions
Accused Products
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.
559 Citations
44 Claims
-
1. 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. 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. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30)
-
-
31. 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. - View Dependent Claims (32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44)
-
Specification