Dynamic Application Preferred Name Display in EMV Cards

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The EMV standard does not allow for dynamic changes in the mnemonic information displayed to cardholders during the Application Selection process, limiting issuers' ability to communicate varying information such as balances or text strings throughout the lifecycle of an EMV payment application.

Innovation Solution

A method is introduced to dynamically modify and format data, allowing for a dynamic Application Preferred Name to be communicated to the cardholder, which can include a dynamic balance or text string, by incorporating this information into the File Control Information of the integrated circuit card, creating a variable-length dynamic File Control Information that can be returned to the terminal.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the Application Preferred Name is stored as static data in the File Control Information during EMV application initialization, then the data structure remains simple and compliant with EMV standards, but the mnemonic displayed to cardholders cannot be changed throughout the application lifecycle

Engineering Contradiction:
Improveability to change mnemonic informationVSAvoiddata structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Application Preferred_name is segmented into two distinct parts: a static component (stored in FCI during application initialization) and a dynamic component (stored separately in a file or record). This segmentation allows the static portion to remain compliant with EMV standards while the dynamic portion can be updated independently to change the displayed mnemonic throughout the application lifecycle.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An intermediary data structure or file is introduced between the static FCI and the dynamic mnemonic content. This intermediary holds the dynamic portion of the Application Preferred_name and allows it to be modified without affecting the static FCI structure, thus enabling mnemonic changes while maintaining EMV standard compliance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If the Application Preferred_name length is limited to 16 bytes as per EMV standard, then data transmission remains efficient and standardized, but the ability to convey detailed or variable information to cardholders is restricted

Engineering Contradiction:
Improveinformation communication capabilityVSAvoidtransaction processing efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The system transitions from a static 16-byte Application Preferred_name to a dynamic structure where the mnemonic can vary in length and content. The dynamic portion can be adjusted per transaction or per cardholder needs, allowing more detailed information communication while the static portion maintains the standardized 16-byte structure for efficient processing.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The length and content parameters of the Application Preferred_name are made changeable. Instead of being fixed at 16 bytes, the dynamic portion can vary in length and content based on the specific transaction context, cardholder requirements, or issuer preferences, thereby enhancing information communication capability without permanently increasing the base data structure size.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the File Control Information structure is kept fixed and standardized according to EMV specifications, then interoperability between terminals and cards is ensured, but dynamic modification of application identification data becomes impossible

Engineering Contradiction:
ImproveEMV standard compliance and interoperabilityVSAvoiddynamic data modification capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The FCI data structure is segmented into immutable static portions (maintaining EMV standard compliance and interoperability) and mutable dynamic portions (enabling modification of application identification data). This segmentation allows the static FCI to ensure reliable terminal-card communication while the dynamic portions can be updated to provide customized mnemonic information for different cardholders or transactions.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9600954B2Dynamic application name display
Publication Date: 2017.03.21 THALES DIS FRANCE SA
  • US9600954B2 patent drawing
  • US9600954B2 patent drawing
  • US9600954B2 patent drawing

AI summary

The present invention relates to a method for providing data during an Application Selection process from a processing device to an interface device, wherein it comprises a step of modifying dynamically at least a part of said data from transaction to transaction, said at least part of data being a dynamic data.