Server Payment Service for Flexible Client Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing payment systems face challenges in handling diverse business logic across various payment methods, leading to inflexibility and high costs due to frequent changes and potential errors, especially in international markets where different data schemas and rules apply.

Innovation Solution

A server-based payment method service that controls the payment flow and options on client devices without requiring software updates, allowing new payment options and data schemas to be integrated while maintaining the native UI look and feel, enabling flexible handling of business rules and user interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If payment business logic is implemented on the client device, then payment processing can be performed locally, but any changes to payment methods or business rules require expensive and time-consuming client software updates

Engineering Contradiction:

Improvepayment processing reliabilityVSAvoidpayment method flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a server-based payment method service that acts as an intermediary between the client device and payment processors. This service handles all payment method logic, business rules, and data schemas on the server side, allowing the client to remain simple and stable while the server adapts to changing payment requirements. The service returns structured payment options to the client without requiring client software updates.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent moves the payment processing logic from the client dimension to the server dimension. By relocating the business logic handling to a remote service, the system gains flexibility in updating payment methods without affecting the client device, effectively solving the contradiction between reliability and adaptability.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If multiple payment methods with different data schemas are supported, then international market coverage is improved, but handling the diverse business logic becomes increasingly complex

Engineering Contradiction:

Improvepayment method diversityVSAvoidbusiness logic complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The server-based payment method service acts as an intermediary that handles the complexity of diverse payment methods, data schemas, and business rules. The client device simply interfaces with this service, which translates various payment method requirements into a unified structure, thereby supporting international markets without increasing client complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the payment processing system into distinct components: a simple client interface and a comprehensive server-based payment method service. This segmentation isolates the complexity of handling multiple payment methods and data schemas to the server side, while the client remains simple and maintainable.

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If client software is updated frequently to accommodate new payment methods and fix errors, then system adaptability improves, but update costs and time increase

Engineering Contradiction:

Improvepayment option flexibilityVSAvoidupdate deployment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The server-based payment method service absorbs all changes related to new payment methods, business rules, and error corrections. Since the service runs on the server, updates can be deployed immediately without requiring client software updates, eliminating the time loss associated with frequent client releases while maintaining full adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Speed

If payment processing is handled locally on the client device, then response speed is improved, but any errors or issues require expensive and time-consuming client releases to fix

Engineering Contradiction:

Improvepayment processing speedVSAvoiderror correction difficulty

Core Design Contradiction:

SpeedVSEase of repair

Solution Approach 1:

The server-based payment method service maintains fast response times by processing payment logic remotely and returning results to the client. When errors or issues arise, they can be corrected on the server side through simple service updates without requiring expensive and time-consuming client releases, thus improving ease of repair while maintaining speed.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9898766B2Payment processing for client devices

Publication Date: 2018.02.20 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A method of payment using a client device is disclosed. The payment can be made through a payment method service that can control the payment flow and options available to the user of a client device. Using the payment method service, new payment options with new data schemas and/or new process flows can be used by the client device, but without any need to update software stored on the client device. The payment method service can utilize the look and feel of the client device, such that the user views payment options in the native UI of the client device.