Configurable Transaction Status Interface for Payment Gateway Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Modern software applications face challenges in interoperating correctly with specialized services from third-party vendors, particularly in reconciling non-uniform transaction result coding schemes from thousands of payment gateways, leading to inefficient development and potential errors in processing transactions.

Innovation Solution

A configurable transaction status interface allows gateway vendors to map their transaction results to a uniform generic status code, enabling dynamic updates without impacting application deployment, and allowing each gateway to maintain its own mapping logic, thus simplifying development and ensuring accurate transaction processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers create custom software from scratch for each customer, then custom functionality can be delivered, but development time and complexity increase significantly

Engineering Contradiction:

Improvecustom functionalityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system segments the transaction processing functionality by separating gateway-specific coding schemes from application-level processing. Each gateway maintains its own status code mappings while the application layer uses a unified set of generic status codes, allowing independent customization without affecting other gateways or increasing overall development time.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The invention creates a universal interface layer that handles multiple gateway vendors through a common set of generic status codes. This multi-functional approach allows a single application to communicate with numerous different payment gateways using standardized interactions, eliminating the need for custom software development for each gateway.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If developers use hardcoded logic to reconcile transaction results, then transaction processing can be implemented, but adaptability to new gateways and updates is reduced

Engineering Contradiction:

Improvetransaction processingVSAvoidgateway compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system replaces static hardcoded logic with dynamic, configurable mappings. Gateway status code mappings are stored as metadata that can be dynamically updated without code changes, allowing the system to adapt to new gateways and changing gateway protocols while maintaining reliable transaction processing through the unified generic status code interface.

Inventive Principle:

Principle #15Dynamics

3Device complexity

If a unified status code system is implemented, then development complexity is reduced, but flexibility in handling gateway-specific coding schemes is limited

Engineering Contradiction:

Improvedevelopment complexityVSAvoidgateway-specific coding schemes

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The invention introduces an intermediary layer of generic status codes that mediates between gateway-specific coding schemes and application-level processing. This intermediary layer absorbs the complexity of gateway variations while presenting a simplified, uniform interface to the application, reducing development complexity without sacrificing the ability to handle diverse gateway protocols.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Measurement precision

If custom mapping logic is created for each gateway, then accurate transaction reconciliation is achieved, but maintenance and updates become difficult

Engineering Contradiction:

Improvetransaction result accuracyVSAvoidmaintenance ease

Core Design Contradiction:

Measurement precisionVSEase of manufacture

Solution Approach 1:

Instead of creating custom mapping logic for each gateway, the system uses template-based metadata structures that can be copied and configured for different gateways. This allows accurate transaction reconciliation to be achieved through configuration rather than custom code, making maintenance and updates easier as changes can be applied through metadata updates rather than code modifications.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11803370B2Configurable transaction status interface

Publication Date: 2023.10.31 SALESFORCE INC

AI summary

In a cloud computing environment, a configurable transaction status interface of an enterprise computing platform enables application developers to customize applications efficiently. The configurable transaction status interface includes a global variable that is populated using a method for implementing a configurable status map that maps a transaction result to the global variable without having to customize the application. The configurable transaction status interface allows third party vendors of transaction gateways to use the configurable status map to map one or more of their gateway-specific transaction results to a generic status defined in the global variable. The vendors manage the configurable status map in their own namespace independently of the application with which they are interfacing.