Payment authorisation process

• US 20060271497A1
• Filed: 05/24/2006
• Published: 11/30/2006
• Est. Priority Date: 05/24/2005
• Status: Abandoned Application

• Current Assignee: Direct Payment Solutions Ltd.
• Original Assignee: Direct Payment Solutions Ltd.
• Inventors: Dykes, Graeme John, Cullen, Andrew John
• Application Number:
  US11/439,214
• Publication Number:
  US 20060271497A1
• Time in Patent Office: Days
• US Class Current: 705/64
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists

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.

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.

2. An electronic commerce process as claimed in claim 1, wherein

said step of sharing data between said merchant gateway and said payment gateway includes sharing data that will relate to data that will indicate the outcome of the transaction;

in said step of causing said customer device to initiate a communication to said merchant gateway, said communication includes data indicative of the outcome of the transaction; and

said merchant gateway determines the outcome for said transaction based on said shared outcome data and said data received from said customer device.

3. An electronic commerce process as claimed in claim 2, wherein said shared outcome data is generated by the payment gateway for each individual transaction and is stored by said payment gateway at least until said transaction has completed or is regeneratable by the payment gateway as necessary.

4. An electronic commerce process as claimed in claim 1, wherein said step of receiving data at said merchant gateway indicating the success or failure of the transaction includes the steps of initiating a secure communication session between said merchant gateway and said payment gateway and receiving data from said payment gateway at said merchant gateway indicating the success or failure of the transaction.

5. An electronic commerce process as claimed in claim 1, wherein said details of said transaction compiled at said merchant gateway comprises one or more of a transaction amount, a customer identifier and an indicator of transaction type such as refund, payment, authorisation for future transaction or recurring transaction.

6. An electronic commerce process as claimed in claim 5, wherein said shared data that allows each gateway to uniquely identify communications relating to the transaction comprises data generated by said payment gateway as an encryption of at least data relating to said transaction and transmitted to said merchant gateway.

7. An electronic commerce process as claimed in claim 1, wherein said shared data that allows each gateway to uniquely identify communications relating to the transaction comprises data generated by said payment gateway and transmitted to said merchant gateway.

8. An electronic commerce process as claimed in claim 1, wherein causing the customer device to initiate a secure communication session with the payment gateway includes supplying an HTTP request to said customer device for initiating a request to said payment gateway, the data for the request including a transaction identifier.

9. An electronic commerce process as claimed in claim 8, wherein said step of causing said customer device to initiate a communication to said merchant gateway comprises supplying an HTTP request to said customer device, the data of the request including the transaction identifier.

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.

11. A merchant gateway programmed to implement an electronic commerce process as claimed in claim 10, wherein

said means for sharing data with said payment gateway shares data that will be used to communicate the outcome of the transaction,

said means for processing communications received from a customer device to confirm completion of a transaction extracts result data from said communication;

and

said means for determining the outcome of said transaction shared determines the outcome on the basis of said outcome data and said result data.

12. A merchant gateway programmed to implement an electronic commerce process as claimed in claim 11, wherein said means for sharing data with said payment gateway receives data from said payment gateway that will be used to communicate the outcome of the transaction and stores said received data for later reference in relation to said transaction.

13. A merchant gateway programmed to implement an electronic commerce process as claimed in claim 10, wherein said means for determining the outcome of said transaction includes means for initiating a secure communication session with said payment gateway to confirm the outcome of said transaction.

14. A merchant gateway programmed to implement an electronic commerce process as claimed in claim 11, wherein

said means for compiling the transaction data include means for receiving or calculating a transaction amount;

said means for compiling a transaction include means for receiving an indication of transaction type;

said means for providing said payment gateway with details of said transaction provides at least said transaction amount and said indicator of said transaction type (where applicable); and

said means for determining the outcome of said transaction includes means for initiating a secure communication session with said payment gateway to confirm the outcome of said transaction.

15. A merchant gateway programmed to implement an electronic commerce process as claimed in claim 11, wherein

said means for compiling the transaction data include means for receiving or calculating a transaction amount;

said means for compiling a transaction include means for receiving an indication of transaction type;

said means for compiling transaction data include means for receiving or retrieving a customer identifier;

said means for providing said payment gateway with details of said transaction includes at least said transaction amount, said indicator of said transaction type (where applicable), a customer identifier or an indication to store customer details in said transaction data; and

said means for determining the outcome of said transaction includes means for initiating a secure communication session with said payment gateway to confirm the outcome of said transaction.

16. A merchant gateway programmed to implement an electronic commerce process as claimed in claim 10, wherein said means for sharing data indicating a unique identifier for said transaction with said payment gateway comprises means for receiving data indicating a unique identifier from said payment gateway and storing said identifier in association with the details of said transaction.

17. A merchant gateway programmed to implement an electronic commerce process as claimed in claim 10, wherein said means for causing said customer device to initiate a secure communication session with said payment gateway supplies an HTTP request to said customer device, the data of the request including data indicating the transaction.

18. A merchant gateway programmed to implement an electronic commerce process as claimed in claim 10, wherein said merchant gateway program includes a database, or means for accessing a database, of at least transaction details, and preferably also customer details, to store and retrieve transaction and/or customer details as necessary.

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.

20. A merchant gateway as claimed in claim 19, wherein said step of initialising the transaction with the payment gateway comprises supplying details of the transaction to the payment gateway, receiving a unique transaction identifier from the payment gateway, and said parsing incoming communications to recognise an indication that a customer has completed a transaction with a payment gateway comprises recognising the presence of a unique transaction identifier in said request.

21. A merchant gateway as claimed in claim 19, wherein said step of initialising said transaction with the payment gateway includes receiving data representative of possible transaction outcomes, and said step of confirming the result of the transaction comprises extracting data from said request and comparing said extracted data with said outcome data received from said payment gateway in said session initialising said transaction.

22. A merchant gateway as claimed in claim 19, wherein said step of confirming the result of said transaction includes initiating a secure communication session with said payment gateway to confirm the outcome for said transaction with said payment gateway, including supplying said identifier to said payment gateway for said payment gateway to identify said transaction.

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.

24. A payment gateway programmed to implement an electronic commerce process as claimed in claim 23, wherein

said means for participating in a secure communication session with said merchant gateway shares data that will be used to communicate the outcome of the transaction;

and

said means for communicating data indicating the outcome of said transaction causes said communication from said customer device to said merchant gateway to include data indicating the outcome of said transaction that is related to said data shared with said merchant gateway in said secure communication session.

25. A payment gateway programmed to implement an electronic commerce process as claimed in claim 23, wherein said means for communicating data indicating the outcome of said transaction to said merchant gateway comprises means for participating in a secure communication session with said merchant gateway including receiving an indication of a unique identifier for a transaction and providing data indicative of the outcome of said transaction to said merchant gateway.

26. A payment gateway programmed to implement an electronic commerce process as claimed in claim 23, wherein said means for sharing data indicating a unique identifier for said transaction with said merchant gateway comprises means for generating a transaction identifier for said transaction and means for supplying said transaction identifier to said merchant gateway.

27. A payment gateway programmed to implement an electronic commerce process as claimed in claim 26 wherein said transaction identifier comprises a unique identifier generated by said payment gateway as an encryption of at least data relating to said transaction.

28. A payment gateway programmed to implement an electronic commerce process as claimed in claim 23, wherein said means for causing said customer device to initiate a communication with said merchant gateway supplies an HTTP request to said customer device, the data for the request including a transaction identifier.

30. A payment gateway as claimed in claim 27, wherein

said payment gateway is programmed to share data that will be used to indicate the outcome of transaction with a said merchant gateway at the time of initialising a transaction;

and

to communicate said outcome to said merchant gateway by including data associated with said outcome for said transaction in data provided to said customer device for said hand off to said merchant gateway.

31. A payment gateway as claimed in claim 27, wherein said payment gateway is programmed to communicate said outcome of said transaction to said merchant gateway by parsing incoming communications to recognise:

(c) an indication that a merchant gateway wishes to confirm the outcome of a transaction; and

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.

33. A payment gateway programmed to implement an electronic commerce process as claimed in claim 32 wherein data indicating the identity of the transaction comprises a unique identifier generated by said payment gateway as an encryption of at least data relating to said transaction.