Payment Terminal Browser HTML5 Tag Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing unattended payment terminals are complex and costly to develop and maintain due to their proprietary nature, requiring specialized software and re-development for new functionalities, which hinders their widespread adoption and efficiency.

Innovation Solution

A method using a standardized HTML payment tag that allows browsers to communicate with payment terminals, initiating transactions and adapting to screen configurations, reducing the need for proprietary applications and enabling simpler, more efficient management of payment processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proprietary applications are used to manage payment terminals in kiosks, then payment processing functionality is achieved, but device complexity and development costs increase significantly

Engineering Contradiction:

Improvepayment processing functionalityVSAvoidsoftware complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by using a standardized web browser that can handle multiple payment terminal types and functionalities through a single interface. The browser universally supports HTML5 payment tags across different kiosk configurations, eliminating the need for separate proprietary applications for each payment terminal type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces an intermediary layer in the form of a web browser that mediates between the user interface and the payment terminal hardware. This browser acts as a universal mediator that can communicate with various payment terminals through standardized HTML tags, reducing the complexity of direct hardware integration.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If proprietary applications are developed for each kiosk configuration, then specific kiosk requirements are met, but development and maintenance costs increase

Engineering Contradiction:

Improvekiosk configuration adaptabilityVSAvoiddevelopment cost

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent uses parameter changes by allowing the HTML5 payment tag parameters to be dynamically adjusted based on kiosk configuration. The same browser-based payment interface can adapt to different kiosk setups by modifying the parameters within the payment tags, such as terminal identifiers, payment methods, and interface configurations, without requiring redevelopment.

Inventive Principle:

Principle #35Parameter changes

3Adaptability or versatility

If new features are added to payment terminal components, then functionality is improved, but application re-development is required

Engineering Contradiction:

Improvefeature functionalityVSAvoidsoftware maintenance

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies dynamics by making the payment interface adaptable and flexible through HTML5 tags. When new features are added to payment terminals, the browser can dynamically incorporate these features by updating the payment tag parameters without requiring complete re-development of the application. This dynamic approach allows the system to evolve with changing hardware capabilities.

Inventive Principle:

Principle #15Dynamics

4Device complexity

If standardized HTML payment tags are used, then device complexity is reduced, but compatibility with existing payment terminals must be ensured

Engineering Contradiction:

Improvesoftware complexityVSAvoidterminal compatibility

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent ensures terminal compatibility through the universal nature of HTML5 standards. The payment tags are designed to work across different browser versions and payment terminal types by adhering to standardized HTML5 specifications, ensuring broad compatibility while maintaining low software complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP3349161B1Method of handling a payment transaction, corresponding payment terminal and program

Publication Date: 2023.05.31 BANKS & ACQUIRERS INT HLDG SAS

Figure 1A~2
Figure 3
Figure 4~5

AI summary

The invention relates to a method for processing a payment transaction, a method implemented by an autonomous electronic payment transaction processing device, called a payment terminal (PT), said payment terminal (PT) comprising a processing processor (Prc) connected to at least one sales offer rendering means (Scr), and linked to at least one communication interface (CI) and to at least one contactless payment terminal (TPNfc).Such a process includes: - a transmission step (10), by a browser (Nav) installed within said payment terminal (BP), of a content retrieval request (RqOC) to a content server (SrvCnt); - a reception step (20), by said browser (Nav), from the content server (SrvCnt), of html content (HCnt) including at least one payment tag (HPEIt); - a processing step (30) of said html content (HCnt), delivering a view (Aff) of said html content (HCnt) on said at least one rendering means (Scr); - a preparation step (40), in anticipation and by the contactless payment terminal (TPNfc), of at least one payment transaction (PT#) based on attribute data of said at least one payment tag (HPEIt).