Cloud Payments Platform with Pluggable Gateway Adapters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing platforms lack a native payment solution, requiring clients to integrate with multiple payment gateways with different APIs, leading to complexity and inconsistency in data models, making it difficult for clients to manage payment transactions across various payment gateways.

Innovation Solution

A cloud-based computing system with a payments platform that integrates payment gateway services, using a pluggable architecture to support various payment gateways through customizable adapters, allowing clients to perform payment transactions seamlessly across different payment gateways.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If clients integrate with multiple payment gateways directly using different APIs, then payment transaction capability is achieved, but integration complexity and data model inconsistency increase

Engineering Contradiction:
Improvepayment transaction capabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a payments platform as an intermediary layer between clients and multiple payment gateways. This platform provides standardized APIs that clients use, while the platform handles the complexity of integrating with different payment gateway services internally. The intermediary abstracts away the heterogeneity of different payment gateway APIs, allowing clients to perform payment transactions without directly dealing with multiple different API interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the payment processing system into distinct layers: the client layer, the payments platform layer, and the payment gateway layer. By dividing the system this way, the complexity of integrating with multiple payment gateways is isolated to the payments platform layer, while clients interact only with the simplified platform API. This segmentation allows each layer to be developed and maintained independently.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If clients integrate with multiple payment gateways directly, then payment transaction capability is achieved, but data model consistency deteriorates

Engineering Contradiction:
Improvepayment transaction capabilityVSAvoiddata model consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The payments platform provides a universal data model and standardized API interface that works across all payment gateway integrations. This universal interface ensures data model consistency by providing a single, consistent way for clients to interact with payment transactions regardless of which underlying payment gateway is being used. The platform translates between this universal data model and the various data models of different payment gateways internally.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If a pluggable architecture with customizable adapters is implemented, then adaptability to different payment gateways is improved, but system complexity increases

Engineering Contradiction:
Improvepayment gateway compatibilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a dynamic, pluggable architecture where payment gateway adapters can be added, removed, or updated without affecting the core payments platform. This dynamic design allows the system to adapt to different payment gateways through standardized adapter interfaces, while the underlying platform remains unchanged. The adaptability is achieved through modular components that can be configured at runtime.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent uses adapter patterns that create standardized copies or representations of different payment gateway interfaces. Each adapter translates the unique interface of a payment gateway into the standardized payments platform interface. This copying approach allows multiple different payment gateways to be supported through unified adapter implementations rather than requiring direct integration logic for each gateway.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If payment gateway integration is handled externally without native support, then implementation flexibility is maintained, but ease of operation decreases

Engineering Contradiction:
Improveimplementation flexibilityVSAvoidintegration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The payments platform provides self-service capabilities through standardized APIs and configuration interfaces that allow clients to easily integrate payment functionality without needing to implement complex custom integration logic. The platform handles authentication, transaction processing, and data normalization automatically, reducing the operational burden on clients while maintaining flexibility in supporting multiple payment gateways.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11887117B2Payments platform, method and system having external and internal operating modes for ingesting payment transaction data from payment gateway services at a cloud computing platform
Publication Date: 2024.01.30 SALESFORCE INC
  • US11887117B2 patent drawing
  • US11887117B2 patent drawing
  • US11887117B2 patent drawing

AI summary

A cloud-based computing system is provided that includes a payments platform for integrating payment gateway services with a cloud computing platform so that clients of the cloud computing platform can perform payment transactions with customers via the cloud computing platform. The payments platform can use external and internal operating modes for ingesting new or old payment transaction data from the payment gateway services at the cloud computing platform.