# US 8,543,508 B2 · Gateway abstraction layer

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,543,508 B2
- Document ID: US8543508B2
- Status: Granted
- Kind: B2
- Application number: 13/180,391
- Filed: 2011-07-11
- Published: 2012-01-12
- Granted: 2013-09-24
- Earliest claimed: 2010-07-09
- Assignees: Visa International Service Association
- Applicants: Edward Katzin; Mark Carlson
- Inventors: Edward Katzin; Mark Carlson
- Web page: https://patentgrep.com/patent/US8543508B2

## CPC

- G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q 20/027: {involving a payment switch or gateway}
- G06Q 20/0855: {involving a third party}
- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- 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
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## 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

### Claim 1

A gateway computer for integrating multiple transaction services from multiple transaction services providers to a plurality of users using a gateway abstraction layer (GAL) comprising:
a processor;
a network interface coupled to the processor;
a service requestor interface coupled to the network interface;
a service provider interface coupled to the network interface; and
an abstraction layer database,
wherein the service requestor interface is configured to receive requests comprising service requests from the plurality of users using a first application platform interface (API),
wherein the service provider interface is configured to:
parse service request data from the service requests; and
translate the service request data into a first data format to communicate with a plurality of service providers using a second API,
wherein the network interface is configured to:
parse transaction authorization request data from the service requests; and
translate the transaction authorization request data into a second data format to communicate with a plurality of acquirers or payment networks using a lookup table of communication standards in the abstraction layer database.

### Claim 2 (depends on 1)

The gateway computer of claim 1, wherein the service provide interface is further configured to:
initiate service calls to the plurality of service providers based on the transaction service request data; and
send results from the service calls to one or more of the users, acquirers or proprietary networks using the first API and the lookup table of communication standards.

### Claim 3 (depends on 2)

The gateway of claim 2, wherein the service requests comprise transaction authorization requests.

### Claim 4 (depends on 3)

The gateway of claim 3, wherein the transaction authorization requests comprises credit card payment authorization requests.

### Claim 5 (depends on 2)

The gateway computer of claim 2, wherein the service provider interface is further configured to, before the network interface sends transaction authorization requests based on the transaction authorization request data to the plurality of acquirers or payment networks, receive from the plurality of service providers messages indicating a positive result of service calls sent to the plurality of service providers.

### Claim 6 (depends on 1)

The gateway computer of claim 1, wherein the network interface is further configured to receive transaction authorization response data from the plurality of payment networks, and wherein the service requestor interface is further configured to:
translate the transaction authorization response data into a data format compatible with the first API; and
send the transaction authorization response data to the plurality of users over the first API.

### Claim 7 (depends on 1)

The gateway computer of claim 1, wherein the plurality of service providers provide transaction services relating to fraud detection, risk management, scoring, analytics, dispute resolution, and chargebacks.

### Claim 8

A method for providing services to a plurality of users using a gateway server comprising:
receiving a service request at the gateway server from one of the plurality of users over a first application platform interface (API);
parsing service request data from the service request using the gateway server;
accessing an abstraction layer database using the gateway server to determine one or more service providers;
translating the service request data into a first data format to communicate with the one or more service providers using the gateway server;
sending a service call based on the service request data and the abstraction layer database from the gateway server to the one or more service providers over a second API;
parsing transaction authorization request data from the service request using the gateway server;
translating the transaction authorization request data into a second data format to communicate with an acquirer or a payment network using the gateway server; and
sending a transaction authorization request based on the transaction authorization request data from the gateway server to the acquirer or payment network.

### Claim 9 (depends on 8)

The method of claim 8, further comprising receiving results at the gateway server from the one or more service providers and sending the results to the service requestor, the acquirer or the payment network.

### Claim 10 (depends on 9)

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

### Claim 11 (depends on 10)

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

### Claim 12 (depends on 8)

The method of claim 8, further comprising receiving an update from a service provider and updating the abstraction layer database based on the update.

### Claim 13 (depends on 12)

The method of claim 12, wherein the update can include a change to one or more communication standard associated with the service provider.

### Claim 14 (depends on 8)

The method of claim 8, further comprising:
receiving a transaction authorization response from the payment network;
translating the transaction authorization response into a data format compatible with the first API; and
sending the transaction authorization response to the one of the plurality of users over the first API.

### Claim 15 (depends on 8)

The method of claim 8, further comprising, before sending the transaction authorization request to the acquirer or payment network, receiving a message indicating a positive result of the service call from the one or more service providers over the second API.

### Claim 16 (depends on 8)

The method of claim 8, wherein the one or more service providers provide transaction services relating to two or more of: fraud detection, risk management, scoring, analytics, dispute resolution, and chargebacks.