High-Security Toggle System for Digital Payment Card Display
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Digital payment card data is vulnerable to unauthorized access, as it is often displayed without adequate security measures, putting sensitive information like account numbers, expiration dates, and CVV at risk, especially before the physical card is issued or activated.
Innovation Solution
A high-security display system that uses tokenization to generate a digital payment card with a tokenized PAN, expiration date, and security code, requiring multiple verification levels to access sensitive data subsets, including biometric and two-step authentication, ensuring secure access and dynamic security codes for each transaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If digital payment card data is displayed immediately upon issue before physical card arrival, then user access to payment functionality is improved, but security vulnerability to bad actors increases
Solution Approach 1:
The payment card data is segmented into multiple subsets displayed at different verification levels. The first subset contains non-sensitive information accessible at default security level, while the second subset contains sensitive information (CVV, full account number) accessible only after upgraded verification. This segmentation allows immediate partial access while protecting sensitive data.
Solution Approach 2:
The display system dynamically adjusts the security level and accessible data subsets based on verification status. The verification module can upgrade from default to first and second security levels in response to user signals, dynamically controlling what portions of the payment card data are displayed. This dynamic adjustment resolves the contradiction by enabling fast initial access while maintaining security controls for sensitive information.
2Reliability
If multiple verification levels are implemented to secure sensitive data, then security level is improved, but system complexity increases
Solution Approach 1:
The verification process is segmented into distinct levels (default, first, second security levels), each corresponding to specific data subsets. This segmentation allows the system to implement robust multi-level verification without presenting a single complex verification barrier, as users only encounter verification steps necessary for their current access needs.
Solution Approach 2:
The system performs preliminary verification actions at the default security level to grant access to non-sensitive information immediately. This preliminary action avoids requiring full verification for all data, reducing the perceived complexity while maintaining security. Users only proceed to additional verification steps when they specifically need access to sensitive information subsets.
3Reliability
If tokenization is used to replace PAN with token, then data security is improved, but data accessibility for transactions may be affected
Solution Approach 1:
The system creates a digital copy of the payment card with tokenized data that functions equivalently to the physical card for transaction purposes. The tokenized PAN, expiration date, and security code are displayed when appropriate verification levels are achieved, providing the same accessibility needed for transactions while using secure tokenized values instead of actual card numbers.
Solution Approach 2:
The token acts as an intermediary between the actual PAN and the transaction processing system. Instead of displaying or transmitting the real card number, the tokenized version serves as a secure substitute that maintains transactional functionality while protecting the underlying sensitive data. This intermediary approach resolves the contradiction by enabling transaction accessibility through tokenized representations.
Data Source
AI summary
Systems, methods, and apparatus are provided for a high-security display of distinct subsets of a digital payment card dataset. A payment card issuer may import token data to generate a digital payment card for a user. In some embodiments, the digital payment card may include the token place of a payment card PAN, a token expiration date in place of a payment card expiration date, and a token security code in place of a card CVV. The user may access the digital payment card data at a high security display that toggles to different subsets of the payment card dataset. The display may require different levels of verification to access each subset of the dataset. The user may execute a transaction using the digital payment card data.