Payment Device Access Validation Without Certified EMV Terminals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing access control systems using smart cards require expensive special-purpose card writers and often use varying data formats or standards, necessitating different cards for each access type, and contactless payment devices like EMV cards cannot be used for access without certified terminals.
Innovation Solution
An access control system that maintains associations between payment numbers and personal identifiers, allowing standard payment devices to identify users based on their personal identifiers, enabling access to resources through a server that maps obfuscated payment numbers to access profiles, without the need for specialized card writers or certified terminals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If smart cards are used for access control, then access permission can be validated, but expensive special-purpose card writers are required for provisioning
Solution Approach 1:
The patent applies universality by enabling standard payment devices to serve dual purposes: both payment transactions and access control authentication. The access control system validates permissions using obfuscated payment numbers from conventional payment devices, eliminating the need for specialized smart card writers while maintaining secure access validation through the mapping of personal identifiers to obfuscated payment numbers in the access control database
2Adaptability or versatility
If varying data formats or standards are used for access cards, then security management can be customized, but different access cards are required for every different type of access
Solution Approach 1:
The patent implements universality by using a single standardized payment device format for multiple access types. The system achieves customization through the database layer where personal identifiers are mapped to obfuscated payment numbers, allowing different access permissions and resource types to be managed through software configuration rather than requiring physically different cards. This eliminates the need for multiple specialized access cards while maintaining tailored security management for different resources
Solution Approach 2:
The patent introduces an intermediary mapping layer between personal identifiers and obfuscated payment numbers in the access control database. This intermediary structure allows the system to translate a single standardized payment device into multiple access types by looking up the corresponding personal identifier and validating against stored access profiles, thereby eliminating the need for different card formats for different access types while maintaining customized security management
3Adaptability or versatility
If EMV contactless payment devices are used for access, then standard payment cards can be utilized, but expensive EMV-certified terminals are required
Solution Approach 1:
The patent extracts the essential authentication element (obfuscated payment number) from the EMV payment device and uses it for access control validation without requiring full EMV-certified terminal functionality. The system reads the payment device to obtain the obfuscated payment number, then validates it against the access control database, thereby separating the access control function from the payment processing function and eliminating the need for expensive EMV certification
Solution Approach 2:
The patent replaces expensive EMV-certified terminals with simpler, less costly terminal equipment that can read payment devices and extract obfuscated payment numbers for access validation. The system uses conventional payment devices and terminals rather than requiring costly certified infrastructure, achieving access control functionality through a more economical implementation that leverages existing payment device standards
Data Source
AI summary
An access control method comprises: providing access profiles for users, wherein each access profile comprises an access profile identifier and at least one personal identifier mapped to one or more obfuscated payment numbers, and wherein each of the at least one personal identifiers is a non-payment identifier issued by an identity provider;receiving, from a terminal of a service provider, a request to validate permission for a user of a payment device to access a resource made available by the service provider, the request comprising an obfuscated payment number read by the terminal from the payment device; determining whether there is a match of the obfuscated payment number read by the terminal and one of the obfuscated payment numbers of the access profiles; and transmitting at least one of the identifiers of the matched access profile to the service provider for matching to a stored identifier associated with the resource.


