Payment Gateway Server Transaction Overhead Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current financial transaction authorization systems face inefficiencies and increased complexity due to high communication overhead and the need for redundant data transmissions, particularly in handling multiple transactions and maintaining state across multiple servers in a cluster.

Innovation Solution

A payment processing gateway and protocol that utilize a public network interface to communicate financial authorization requests, incorporating a supplemental header for transaction identification and caching of merchant invariant data to reduce overhead and optimize performance, allowing for simultaneous communication with multiple financial networks and efficient handling of authorization requests and responses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authorization systems transmit complete data sets with each transaction, then data completeness is ensured, but communication overhead increases

Engineering Contradiction:
Improvedata completenessVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and transmits only the supplemental header containing transaction-specific data, while merchant invariant data is cached separately at the gateway server. This extraction principle reduces the amount of data transmitted over the network while ensuring complete authorization processing through the combination of cached and transmitted data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The gateway server performs preliminary actions by caching merchant invariant data before transactions occur. This pre-caching eliminates the need to retransmit this data with each authorization request, reducing communication overhead while maintaining data completeness for authorization decisions.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If merchant invariant data is transmitted with every authorization request, then data availability is improved, but transmission time increases

Engineering Contradiction:
Improvedata availabilityVSAvoidtransmission time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-caching merchant invariant data at the gateway server before authorization requests are received. This eliminates the need for repeated transmissions of the same data, significantly reducing transmission time while ensuring data availability for processing authorization requests.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies local quality by storing merchant invariant data locally at the gateway server in a cache memory. This local storage allows rapid retrieval of merchant data without network transmission, improving both data availability and reducing transmission time compared to centralized retrieval for each transaction.

Inventive Principle:
Principle #3Local quality

3Reliability

If state information is maintained across multiple servers in a cluster, then system reliability is improved, but complexity of state management increases

Engineering Contradiction:
Improvesystem reliabilityVSAvoidstate management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements copying by replicating the cache memory state across multiple gateway servers in a cluster. Each server maintains a copy of the merchant invariant data cache, allowing any server to handle authorization requests independently. This copying approach improves system reliability through redundancy while keeping state management relatively simple through standardized data structures.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system segments the gateway server functionality across multiple independent servers, each capable of handling authorization requests autonomously. This segmentation distributes the processing load and improves reliability, as failure of one server does not affect others. The standardized cache memory structure maintains simplicity despite the distributed architecture.

Inventive Principle:
Principle #1Segmentation

4Measurement precision

If complete transaction data is transmitted over the network, then data accuracy is ensured, but network bandwidth consumption increases

Engineering Contradiction:
Improvedata accuracyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Measurement precisionVSLoss of energy

Solution Approach 1:

The patent extracts only the essential transaction-specific data in the supplemental header for transmission over the network, while merchant invariant data is retrieved from local cache. This extraction ensures data accuracy for the transaction being processed while minimizing network bandwidth consumption by avoiding transmission of redundant merchant data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

By pre-caching merchant invariant data at the gateway server, the system performs preliminary action that eliminates the need to retransmit this data with each authorization request. This maintains data accuracy for processing while significantly reducing network bandwidth consumption, as only the supplemental header needs to be transmitted.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7853525B2Electronic draft capture
Publication Date: 2010.12.14 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7853525B2 patent drawing
  • US7853525B2 patent drawing
  • US7853525B2 patent drawing

AI summary

A gateway server, point of sale device and protocol are provided for processing financial transactions. A public network interface is configured to couple to a public network and communicate financial authorization requests. The financial authorization requests can include, for example, transaction specific data, a merchant store or location invariant and a supplemental header. A gateway processor processes the financial transaction authorization requests and couples to a financial network interface configured to couple to at least one financial network. The gateway provides a response to the point of sale device based upon data received from the financial network and the authorization request.