Payment Code Segmentation for Secure Offline Transactions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing payment technologies face vulnerabilities due to malicious codes, loss of mobile terminals, and hacking of payment servers, particularly with offline payments using barcodes that can be wrongly exposed or hacked, leading to security concerns.

Innovation Solution

A payment system that uses one-time authentication codes (OTP) by storing and concatenating first and second partial payment codes, encrypting them, and performing re-arrangement or masking operations to generate a payment code, which is then verified through a payment authority, incorporating a certification unit to ensure user authentication and secure payment processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a barcode indicating payment information is used for offline payment, then payment convenience is improved, but security is worsened due to wrongful exposure or hacking of the barcode

Engineering Contradiction:

Improvepayment convenienceVSAvoidpayment security

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The payment code is divided into two separate partial payment codes: a first partial payment code stored in the user terminal and a second partial payment code stored in the payment server. Both parts are required to reconstruct the full payment code, preventing unauthorized use if one part is compromised.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary verification by comparing certification values before processing the payment. The payment server compares a certification value received from the user terminal with a pre-stored certification value to verify authenticity before completing the transaction.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If payment information is stored in the mobile terminal, then payment speed is improved, but security risk is worsened due to loss of terminal or malicious codes

Engineering Contradiction:

Improvepayment speedVSAvoidsecurity risk

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

Payment information is segmented into two partial codes stored in different locations (user terminal and payment server). This segmentation ensures that even if the terminal is lost or compromised, the attacker cannot reconstruct the full payment code without accessing both storage locations.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The payment server acts as an intermediary that holds the second partial payment code and performs verification. This intermediary role prevents direct exposure of full payment information in the user terminal while enabling fast local processing.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If a single payment code is used for authentication, then ease of use is improved, but authentication strength is worsened

Engineering Contradiction:

Improveease of useVSAvoidauthentication strength

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The authentication mechanism is segmented into two components: the first partial payment code in the user terminal and the second partial payment code in the payment server. Both must be combined and verified to complete authentication, significantly strengthening the authentication process while maintaining ease of use.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary verification of certification values before completing the authentication process. This preliminary check ensures that only authenticated users can successfully combine the partial codes and complete payments.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9864983B2Payment method, payment server performing the same and payment system performing the same

Publication Date: 2018.01.09 LG CNS CO LTD

AI summary

A payment server that includes a payment request receiving unit configured to receive a payment request code including a first partial payment code, and a payment code determination unit configured to determine a second partial payment code based on the received payment request code. The payment server also includes a payment code generation unit configured to generate a payment code based on the first and second partial payment codes, the payment code being payable by a user.