Mobile Merchant Device Security Enclave for Secure Payment Enrollment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic payment systems using mobile merchant communication devices lack secure methods for processing payment transactions, as they rely on customer-entered security data, which may not ensure the integrity of the merchant device and can compromise transaction security.

Innovation Solution

A mobile merchant communication device is configured with a security enclave to obtain and manage electronic secrets, enabling enrollment by a personalization server for secure payment transactions, using cryptographic keys and secure channels to authenticate and authorize transactions, ensuring only authorized devices can perform payments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a mobile merchant communication device is used to process payment transactions, then the ease of operation is improved, but the security and integrity of the transaction may be compromised

Engineering Contradiction:
Improveease of operationVSAvoidsecurity and integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The mobile merchant communication device is segmented into a main processing unit and a separate security enclave. The security enclave is a isolated, protected environment that stores sensitive data (electronic secrets, cryptographic keys) and performs security-critical operations independently from the main device operations, thus maintaining security while enabling mobile payment functionality

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A personalization server acts as an intermediary between the mobile merchant device and the payment network. This server enrolls devices, issues personalization data, and verifies device authenticity before allowing transaction processing, thereby ensuring security and integrity without compromising the ease of mobile operation

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If customer-entered security data is used for authentication, then the ease of operation is improved, but the risk of unauthorized access increases

Engineering Contradiction:
Improveease of operationVSAvoidrisk of unauthorized access
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The security enclave extracts and isolates the storage and processing of electronic secrets from the main device operations. Instead of relying solely on customer-entered data stored in accessible memory, the critical secrets are extracted to a protected enclave that controls access to security functions, reducing the risk of unauthorized access while maintaining ease of customer operation

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The security enclave performs preliminary security checks and validations before allowing transaction processing. Electronic secrets are pre-configured and validated in the secure enclave environment, ensuring that only authenticated and authorized transactions can proceed, thereby preventing unauthorized access before it can occur

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4250210B1Devices, methods and a system for secure electronic payment transactions
Publication Date: 2024.10.16 RUBEAN AG
  • EP4250210B1 patent drawingFigure 1
  • EP4250210B1 patent drawingFigure 2a
  • EP4250210B1 patent drawingFigure 2b

AI summary

A mobile merchant communication device (120) configured to be enrolled by a personalization server (140) for performing a payment transaction with a mobile consumer communication device (110) using a payment server (170) is disclosed. The mobile merchant communication device (120) comprises a user interface configured to receive an authentication request from a merchant (120a), wherein the authentication request comprises a first electronic secret. Moreover, the mobile merchant communication device (120) comprises a security enclave (121a) configured to, in response to the authentication request, obtain a second electronic secret for the mobile merchant communication device (120), and a communication interface (123) configured to transmit an enrollment request to the personalization server (140), wherein the enrollment request comprises the first electronic secret and the second electronic secret. The communication interface (123) is further configured, in response to the enrollment request, to receive personalization data from the personalization server (140), wherein the personalization data enables the mobile merchant communication device (120) to perform the payment transaction with the mobile consumer communication device (110).