Payment authorisation process
First Claim
1. An electronic commerce process comprising the steps of:
- compiling, at a merchant gateway, details of a transaction that a customer wishes to enter into with a merchant;
in a secure communication session between said merchant gateway and a payment gateway sharing data that allows each gateway to uniquely identify communications relating to the transaction and sharing data representing at least a transaction amount in relation to the intended transaction;
causing the customer device to initiate a secure communication session with the payment gateway and pass data to the payment gateway enabling the payment gateway to identify the transaction;
completing the payment aspects of a transaction with said customer device in said secure communications session between said customer device and said payment gateway;
causing said customer device to initiate a communication to said merchant gateway, said communication including data indicative of the transaction; and
receiving data at said merchant gateway indicating the success or failure of the transaction.
1 Assignment
0 Petitions
Accused Products
Abstract
An electronic commerce process is described. The process compiling, at a merchant gateway, details of a transaction that a customer wishes to enter into with a merchant. In a secure communication session between the merchant gateway and a payment gateway sharing data that allows each gateway to uniquely identify communications relating to the transaction and sharing data representing at least a transaction amount in relation to the intended transaction. The merchant server causes a customer device to initiate a secure communication session with the payment gateway. During the secure communications session the customer device passing data to the payment gateway, the data enabling the payment gateway to identify the transaction. Payment aspects of a transaction are conducted in a secure communications session between the customer device and the payment gateway. When the payment aspects are concluded the payment server causes the customer device to initiate communication with the merchant gateway, the communication including data indicative of the transaction. Data indicative of the success or failure of the transaction is received by the merchant server. A merchant gateway programmed to implement the electronic commerce process is also described.
-
Citations
33 Claims
-
1. An electronic commerce process comprising the steps of:
-
compiling, at a merchant gateway, details of a transaction that a customer wishes to enter into with a merchant;
in a secure communication session between said merchant gateway and a payment gateway sharing data that allows each gateway to uniquely identify communications relating to the transaction and sharing data representing at least a transaction amount in relation to the intended transaction;
causing the customer device to initiate a secure communication session with the payment gateway and pass data to the payment gateway enabling the payment gateway to identify the transaction;
completing the payment aspects of a transaction with said customer device in said secure communications session between said customer device and said payment gateway;
causing said customer device to initiate a communication to said merchant gateway, said communication including data indicative of the transaction; and
receiving data at said merchant gateway indicating the success or failure of the transaction. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A merchant gateway programmed to implement an electronic commerce process, said program comprising:
-
means for compiling transaction data in an interactive session with a customer, means for initiating a secure communication session with a payment gateway, providing said payment gateway with details of said transaction and sharing with said payment gateway at least data indicating a unique identifier for said transaction, means for causing said customer device to initiate a secure communication session with said payment gateway associated with said unique transaction identifier, means for processing communications received from a customer device to confirm completion of a transaction; and
means for determining the outcome of said transaction. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A merchant gateway programmed to:
-
parse incoming communications to recognise (c) an indication that a customer intends to complete a transaction, and (d) an indication that a customer has completed a transaction with a payment gateway;
respond to instance (a) by initiating a secure communication session with a payment gateway to initialise the transaction with the payment gateway, and then handing off the customer device to the payment gateway; and
respond to instance (b) by extracting data indicating the identity of the transaction to which the communication relates and confirming the result of the transaction. - View Dependent Claims (20, 21, 22)
-
-
23. A payment gateway programmed to implement an electronic commerce process, said program comprising:
-
means for participating in a secure communication session with a merchant gateway, receiving details of an intended transaction and sharing with said merchant gateway at least data indicating a unique identifier for said transaction, means for participating in a secure communication session with a customer device to receive payment data, means for determining authorisation of a transaction according to said transaction details received from said merchant gateway and payment data received from said customer device, means for causing said customer device to initiate a communication with said merchant gateway, said communication including data indicative of said unique transaction identifier, and means for communicating data to said merchant gateway indicative of the outcome of said transaction. - View Dependent Claims (24, 25, 26, 27, 28, 30, 31)
-
-
29. A payment gateway programmed to:
-
parse incoming communications to recognise (c) an indication that a merchant wishes to set up a transaction for completion, (d) an indication that a customer wishes to complete the payment part of a transaction;
respond to instance (a) by participating in a secure communication session with said merchant gateway to initialise the transaction; and
respond to instance (b) by participating in a secure communication session with a customer device, including extracting data indicating the identity of the transaction to which the communication session relates and receiving payment data, confirming a payment authorisation on the basis of said transaction data and said payment data, and then handing off the customer device to the merchant gateway and communicating an outcome of the transaction to said merchant gateway.
-
- 32. responding to instance (c) by participating in a secure communication session with said merchant gateway, extracting data indicating the identity of the transaction to which the session relates and confirming the result of the transaction associated with said transaction identity to said merchant gateway.
Specification