Cloud Peripheral Control for Secure Payment Device Pairing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current payment processing systems require physical coupling of peripheral devices to a payment user interface, limiting mobility and flexibility, and expose sensitive information to local networks, with non-standardized APIs complicating integration with diverse peripheral devices.

Innovation Solution

A cloud-based solution decouples peripheral devices from payment UIs by using a server-based peripheral controller, enabling virtual connections and standardized interfaces, allowing devices from different vendors to communicate securely with a server rather than the UI.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If peripheral devices are physically coupled to payment UI, then device compatibility and reliability are improved, but system flexibility and mobility deteriorate

Engineering Contradiction:

Improvedevice compatibilityVSAvoidsystem flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

A server acts as an intermediary between peripheral devices and payment UI instances. The server receives commands from the payment UI, translates them into device-specific protocols, and communicates with the appropriate peripheral devices. This mediator architecture allows the payment UI to remain device-agnostic while maintaining reliable communication with diverse peripheral devices through standardized interfaces.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Device complexity

If payment UI directly communicates with peripheral devices, then integration simplicity is improved, but PCI compliance complexity and security exposure worsen

Engineering Contradiction:

Improveintegration simplicityVSAvoidPCI compliance complexity

Core Design Contradiction:

Device complexityVSObject-affected harmful factors

Solution Approach 1:

The payment information processing function is extracted from the local payment UI and moved to a secure server environment. The server handles all sensitive payment data transactions, while the local payment UI only communicates transaction details and receives results. This extraction removes sensitive payment processing from the local network scope, reducing PCI compliance complexity and security exposure at the point of sale.

Inventive Principle:

Principle #2Taking out (Extraction)

3Reliability

If device-specific drivers are installed at payment UI location, then peripheral device functionality is improved, but system portability and deployment flexibility worsen

Engineering Contradiction:

Improveperipheral device functionalityVSAvoidsystem portability

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The server serves as a centralized intermediary that maintains device-specific drivers and communication protocols. When a payment UI needs to communicate with a peripheral device, the server handles the driver-specific translation and device control. This allows peripheral device functionality to be maintained through server-side driver management while keeping the local payment UI portable and free from device-specific driver installation requirements.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12555085B2Cloud-based transaction processing

Publication Date: 2026.02.17 TEMPUS TECH

AI summary

A peripheral controller implemented on a server facilitates a transaction initiated at a payment user interface (UI). The peripheral controller is configured to pair the payment UI with a peripheral device, which is configured to receive payment information from a user. The peripheral controller also is configured to communicate with a payment processing system to facilitate processing of a payment request.