Gateway abstraction layer

• US 9,846,905 B2
• Filed: 08/20/2013
• Issued: 12/19/2017
• Est. Priority Date: 07/09/2010
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Katzin, Edward, Carlson, Mark
• Primary Examiner(s): Abdi, Kambiz
• Assistant Examiner(s): Hamerski, Bolko
• Application Number:
  US13/971,250
• Publication Number:
  US 20130339250A1
• Time in Patent Office: 1,582 Days
• Field of Search: 705 44
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• 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/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
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

Systems, gateway computers, and methods for using a gateway abstraction layer and application platform interfaces for conducting service transactions are disclosed. A gateway abstraction layer computers can receive service requests in multiple message formats or communication protocols, transform those service requests into other message formats to process the service using one or more networks or third-party service providers. The results of the service request can then be translated back to the message format in which the original service request was received. The gateway abstraction layer can be maintained using update messages received from service providers.

Claims

1. A computer-implemented method comprising:

establishing, by a merchant or acquirer computer, communication with a gateway server;

transmitting, from the merchant or acquirer computer to the gateway server, a service request message including service request data or transaction authorization request data, wherein the service request message is intended for a service provider or a payment network, wherein the service request message is transmitted according to a first format over a first application platform interface (API) regardless of communication standard requirements of the service provider or the payment network, wherein the gateway server thereafter;

parses the service request data from the service request message, the service request data including a service provider identifier indicating the service provider;

accesses an abstraction layer database to determine the service provider using the service provider identifier;

translates, using the abstraction layer database, at least a portion of the service request data into a second data format to communicate with the service provider, the second data format being different from the first data format, the second data format satisfying the communication standard requirements of the service provider;

transmits a service call message to the service provider over a second API, the service call message including the translated service request data in the second data format;

parses the transaction authorization request data from the service request message, the transaction authorization request data including a payment network identifier indicating a payment network;

translates, using the abstraction layer database, at least a portion of the transaction authorization request data into a third data format to communicate with the payment network, the second data format being different than the third data format, the third data format satisfying communication standard requirements of the payment network;

transmits a transaction authorization request message to the payment network, the transaction authorization request message including the translated transaction authorization request data in the third data format; and

manages changes to the communication standard requirements of the service provider and the payment network such that the second format complies with the communication standard requirements of the service provider and the third format complies with the communication standard requirements of the payment network.

2. The method of claim 1, wherein the gateway server receives a result from the service provider and transmits the result to the merchant computer, the acquirer computer, or the payment network.

3. The method of claim 2, wherein the abstraction layer database comprises a lookup table of communication standards or APIs.

4. The method of claim 3, wherein the lookup table comprises a mapping of translations between the first API and the second API.

5. The method of claim 1, wherein the gateway server receives an update from the service provider and updates the abstraction layer database based on the update.

6. The method of claim 5, wherein the update includes a change to one or more communication standards associated with the service provider.

7. The method of claim 1, wherein the gateway server receives a transaction authorization response message from the payment network and translates the transaction authorization response message into a data format compatible with the first API, and wherein the method further comprises:

receiving, by the merchant or acquirer computer from the gateway server, the translated transaction authorization response message over the first API.

8. The method of claim 1, wherein, before transmitting the transaction authorization request message to the payment network, the gateway server receives a message indicating a positive result of the service call message from the service provider over the second API.

9. The method of claim 1, wherein the gateway server utilizes a canonical message format.

10. The method of claim 9, wherein the canonical message format is XML.

11. The method of claim 9, wherein the canonical message format is augmented for at least one of the service request message or the transaction authorization request message.

12. The method of claim 9, wherein the canonical message format is divided into datadict packages specific to the service provider or the payment network.

13. The method of claim 9, wherein the gateway server is configured to communicate with service endpoints for payment, mobile wallet, money transfer, and virtual currency transactions.

14. A computing device comprising:

a processor; and

a computer readable medium coupled to the processor, wherein the computer readable medium includes code executable by the processor for implementing a method comprising;

establishing communication with a gateway server;

transmitting, to the gateway server, a service request message including service request data or transaction authorization request data, wherein the service request message is intended for a service provider or a payment network, wherein the service request message is transmitted according to a first format over a first application platform interface (API) regardless of communication standard requirements of the service provider or the payment network, wherein the gateway server thereafter;

parses the service request data from the service request message, the service request data including a service provider identifier indicating the service provider;

accesses an abstraction layer database to determine the service provider using the service provider identifier;

translates, using the abstraction layer database, at least a portion of the service request data into a second data format to communicate with the service provider, the second data format being different from the first data format, the second data format satisfying the communication standard requirements of the service provider;

transmits a service call message to the service provider over a second API, the service call message including the translated service request data in the second data format;

parses the transaction authorization request data from the service request message, the transaction authorization request data including a payment network identifier indicating a payment network;

translates, using the abstraction layer database, at least a portion of the transaction authorization request data into a third data format to communicate with the payment network, the second data format being different than the third data format, the third data format satisfying communication standard requirements of the payment network;

transmits a transaction authorization request message to the payment network, the transaction authorization request message including the translated transaction authorization request data in the third data format; and

manages changes to the communication standard requirements of the service provider and the payment network such that the second format complies with the communication standard requirements of the service provider and the third format complies with the communication standard requirements of the payment network.

15. The computing device of claim 14, wherein the gateway server receives a result from the service provider and transmits the result to the merchant computer, the acquirer computer, or the payment network.

16. The computing device of claim 15, wherein the abstraction layer database comprises a lookup table of communication standards or APIs.

17. The computing device of claim 16, wherein the lookup table comprises a mapping of translations between the first API and the second API.

18. The computing device of claim 14, wherein the gateway server receives an update from the service provider and updates the abstraction layer database based on the update.

19. The computing device of claim 18, wherein the update includes a change to one or more communication standards associated with the service provider.

20. The computing device of claim 14, wherein the gateway server receives a transaction authorization response message from the payment network and translates the transaction authorization response message into a data format compatible with the first API, and wherein the method further comprises:

receiving, by the computing device from the gateway server, the translated transaction authorization response message over the first API.

21. The computing device of claim 14, wherein, before transmitting the transaction authorization request message to the acquirer computer or payment network, the gateway server receives a message indicating a positive result of the service call message from the service provider over the second API.

22. A computer-implemented method comprising:

receiving, by a service provider computer of a service provider from a gateway server, a service call message, wherein the gateway server is configured to;

establish communication with one of a plurality of merchant or acquirer computers;

receive a service request message including service request data or transaction authorization request data, wherein the service request message is intended for the service provider or a payment network, wherein the service request message is transmitted according to a first format from the one of the plurality of merchant or acquirer computers over a first application platform interface (API) regardless of communication standard requirements of the service provider or the payment network;

parse the service request data from the service request message, the service request data including a service provider identifier indicating the service provider;

access an abstraction layer database to determine the service provider using the service provider identifier;

translate, using the abstraction layer database, at least a portion of the service request data into a second data format to communicate with the service provider computer, the second data format being different from the first data format, the second data format satisfying the communication standard requirements of the service provider;

transmit the service call message to the service provider computer over a second API, the service call message including the translated service request data in the second data format;

parse the transaction authorization request data from the service request message, the transaction authorization request data including a payment network identifier indicating a payment network;

translate, using the abstraction layer database, at least a portion of the transaction authorization request data into a third data format to communicate with the payment network, the second data format being different than the third data format, the third data format satisfying communication standard requirements of the payment network;

transmit a transaction authorization request message to the payment network, the transaction authorization request message including the translated transaction authorization request data in the third data format; and

manage changes to the communication standard requirements of the service provider and the payment network such that the second format complies with the communication standard requirements of the service provider and the third format complies with the communication standard requirements of the payment network.

23. The method of claim 22, further comprising:

processing, by the service provider computer, the service call message;

generating, by the service provider computer, a result based on the processing of the service call message; and

transmitting, by the service provider computer to the gateway server, the result, wherein the gateway server is further configured to transmit the result to the merchant computer or the payment network.

24. The method of claim 23, wherein the abstraction layer database comprises a lookup table of communication standards or APIs.

25. The method of claim 24, wherein the lookup table comprises a mapping of translations between the first API and the second API.