System, method and article of manufacture for a gateway payment architecture utilizing a multichannel, extensible, flexible architecture

• US 6,072,870 A
• Filed: 06/17/1996
• Issued: 06/06/2000
• Est. Priority Date: 06/17/1996
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Verifone, Inc. (Verifone Systems, Inc.)
• Inventors: Kramer, Glenn A., Nguyen, Trong, Haller, Daniel R.
• Primary Examiner(s): Gregory, Bernarr E.
• Application Number:
  US08/664,633
• Time in Patent Office: 1,450 Days
• Field of Search: 380/4, 380/9, 380/23, 380/24, 380/25, 380/28, 380/29, 380/49, 380/50, 380/59, 370/351, 370/389, 370/400, 370/401, 395/186, 395/187.01, 705/1, 705/26, 705/30, 705/35, 705/39, 705/40, 705/41, 705/42, 705/43, 705/44
• US Class Current: 705/79
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

Secure transmission of data is provided between a plurality of computer systems over a public communication system, such as the Internet. Secure transmission of data is provided from a customer computer system to a merchant computer system, and for the further secure transmission of payment information from the merchant computer system to a payment gateway computer system. The payment gateway system formats transaction information appropriately and transmits the transaction to the particular host legacy system. The host legacy system evaluates the payment information and returns a level of authorization of credit to the gateway which packages the information to form a secure transaction which is transmitted to the merchant which is in turn communicated to the customer by the merchant. The merchant can then determine whether to accept the payment instrument tendered or deny credit and require another payment instrument. An architecture that provides support for additional message types that are value-added extensions to the basic SET protocol, is provided by a preferred embodiment of the invention.

Claims

1. A method for communicating between a server, a gateway, and a host payment application, comprising the steps of:

(a) establishing a communication link between the server and the gateway;

(b) receiving encrypted payment information at the gateway;

(c) decrypting the payment information into one or more request data elements;

(d) formatting the one or more request data elements into a payment transaction request conforming to a protocol compatible with the host payment application; and

(e) transmitting the payment transaction request to the host payment application.

2. The method of claim 1, including the steps of:

(f) receiving a payment transaction response from the host payment application at the gateway;

(g) converting the payment transaction response into one or more response data elements;

(h) encrypting the one or more response data elements; and

(i) transmitting the encrypted one or more response data elements to the server.

3. The method of claim 1, including the step of receiving security information from the host payment application and accessing a database server to acquire information pertinent to payment processing.

4. The method of claim 3, including the step of performing database administration as part of the payment processing.

5. The method of claim 3, including the step of logging transactions in a database.

6. The method of claim 5, including the step of preparing reports based on information in the database.

7. The method of claim 1, wherein the encryption conforms with a protocol specified by one or more credit associations.

8. An apparatus for communicating between a server, a gateway, and a host payment application, comprising:

(a) means for establishing a communication link between the server and the gateway;

(b) means for receiving encrypted payment information at the gateway;

(c) means for decrypting the payment information into one or more request data elements;

(d) means for formatting the one or more request data elements into a payment transaction request conforming to a protocol compatible with the host payment application; and

(e) means for transmitting the payment transaction request to the host payment application.

9. An apparatus as recited in claim 8, including:

(f) means for receiving a payment transaction response from the host payment application at the gateway;

(g) means for converting the payment transaction response into one or more response data elements;

(h) means for encrypting the one or more response data elements; and

(i) means for transmitting the encrypted one or more response data elements to the server.

10. An apparatus as recited in claim 8, including means for receiving security information from the host payment application and accessing a database server to acquire information pertinent to payment processing.

11. An apparatus as recited in claim 10, including means for performing database administration as part of the payment processing.

12. An apparatus as recited in claims 10, including means for logging transactions in a database.

13. An apparatus as recited in claim 12, including means for preparing reports based on information in the database.

14. An apparatus as recited in claim 8, wherein the encryption conforms with a protocol specified by one or more credit associations.

15. A computer program embodied on a computer-readable medium for communicating between a server, a gateway, and a host payment application, comprising:

(a) a code segment for establishing a communication link between the server and the gateway;

(b) a code segment for receiving encrypted payment information at the gateway;

(c) a code segment for decrypting the payment information into one or more request data elements;

(d) a code segment for formatting the one or more request data elements into a payment transaction request conforming to a protocol compatible with the host payment application; and

(e) a code segment for transmitting the payment transaction request to the host payment application.

16. A computer program as recited in claim 15, including:

(f) a code segment for receiving a payment transaction response from the host payment application at the gateway;

(g) a code segment for converting the payment transaction response into one or more response data elements;

(h) a code segment for encrypting the one or more response data elements; and

(i) a code segment for transmitting the encrypted one or more response data elements to the server.

17. A computer program as recited in claim 15, including a code segment for receiving security information from the host payment application and accessing a database server to acquire information pertinent to payment processing.

18. A computer program as recited in claim 17, including a code segment for performing database administration as part of the payment processing.

19. A computer program as recited in claim 17, including a code segment for logging transactions in a database.

20. A computer program as recited in claim 19, including a code segment for preparing reports based on information in the database.

21. A computer program as recited in claim 15, wherein the encryption conforms with a protocol specified by one or more credit associations.

22. A computer program embodied on a computer-readable medium for communicating between a HTTP server, a gateway, and an existing host payment application, comprising:

(a) a code segment for establishing a communication link between the HTTP server and the gateway;

(b) a code segment for receiving encrypted payment information at the gateway;

(c) a code segment for decrypting the payment information into one or more request data elements;

(d) a code segment for formatting the one or more request data elements into a payment transaction request conforming to a protocol compatible with the host payment application; and

(e) a code segment for transmitting the payment transaction request to the existing host payment application.