Encoded ATM Transaction Flows for Rapid Service Deployment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Adding new transactions to ATMs requires significant software changes, which is time-consuming and expensive, limiting the ability to quickly adapt to new transaction demands.

Innovation Solution

A method of encoding a transaction flow into a machine-readable code, such as a QR code, that can be executed by a self-service terminal or mobile device without prior knowledge, allowing for the creation and execution of new transaction types without modifying the ATM's software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If new transactions are added to an ATM by modifying software, then the transaction functionality is improved, but the implementation time and cost increase significantly

Engineering Contradiction:

Improvetransaction functionalityVSAvoidimplementation time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The transaction flow is segmented into discrete, encoded instructions that can be independently created, stored, and executed. Each transaction type is broken down into a sequence of states and actions that are encoded separately, allowing new transactions to be added by simply adding new encoded instruction sets rather than modifying the core ATM software architecture.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Transaction flows are pre-encoded into machine-readable format before being stored in the ATM's memory. The encoding process creates a ready-to-execute blueprint of the transaction sequence, including all states, inputs, and outputs. When a user initiates a transaction, the ATM simply retrieves and executes the pre-encoded instructions, eliminating the need for real-time software compilation or interpretation.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If new transactions are added to an ATM by modifying software, then the transaction functionality is improved, but the implementation cost increases

Engineering Contradiction:

Improvetransaction functionalityVSAvoidimplementation cost

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

Instead of creating custom software for each new transaction type, the system creates encoded copies of transaction flow instructions. These encoded representations are lightweight data structures that can be replicated and stored in the ATM's memory without requiring additional software development, testing, or certification processes.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The ATM's execution engine is designed to be universal, capable of interpreting and executing any encoded transaction flow regardless of the specific transaction type. This single universal interpreter handles cash withdrawals, deposits, transfers, and future transaction types alike, eliminating the need for separate software modules for each transaction category.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If the ATM software is updated to support new transactions, then the application transaction set is extended, but the system complexity increases

Engineering Contradiction:

Improveapplication transaction setVSAvoidsoftware complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The transaction flow logic is extracted from the ATM's core software and represented as external encoded instructions. The execution engine contains only the minimal logic needed to interpret these encoded instructions, while the actual transaction sequences are stored separately as data rather than hard-coded software. This separation keeps the system core simple while allowing extensive transaction variety.

Inventive Principle:

Principle #2Taking out (Extraction)

4Productivity

If traditional software changes are made to add transactions, then new transaction types can be executed, but the process becomes time-consuming and expensive

Engineering Contradiction:

Improvetransaction deployment speedVSAvoidsoftware update time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The traditional mechanical process of software development, compilation, installation, and testing is replaced with a digital encoding and retrieval process. Transaction flows are encoded into a standardized format that can be rapidly transmitted to and loaded into the ATM's memory, replacing the slow, manual software update process with an automated digital deployment mechanism.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12488326B2Transaction flow

Publication Date: 2025.12.02 NCR ATLEOS CORP

AI summary

A method of encoding a transaction flow is described. The method comprises: receiving information from a user about a transaction type to be executed; creating a transaction flow comprising a sequence of states, where at least some states include text to be displayed and inputs to be enabled for that state; and encoding the transaction flow into a machine-readable code.