Client Device Payment Authentication via Token
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Electronic payment transactions face challenges in security and government compliance due to the complexity and risk associated with transferring payment data, requiring a reduction in infrastructure for authentication.
Innovation Solution
A system and method for authenticating payments using a client device and a payment token device, where the merchant services module receives identifiers from the client device and payment token device, generates a request for user input, and initiates a transfer of funds upon approval, reducing the need for transferring sensitive payment data and achieving PCI compliance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional payment authentication infrastructure is used, then payment security and compliance are maintained, but system complexity and infrastructure requirements increase
Solution Approach 1:
The patent extracts the payment authentication function from the traditional merchant server infrastructure and relocates it to the client device. The client device performs authentication by communicating with the payment token device, eliminating the need for complex server-side authentication systems while maintaining security through client-based verification
Solution Approach 2:
The client device performs self-service authentication by directly communicating with the payment token device using identifiers and generating approvals locally. This self-service approach eliminates dependency on complex infrastructure for authentication, as the client device independently verifies payment credentials and generates approvals without requiring extensive server infrastructure
2Device complexity
If payment data transfer infrastructure is reduced, then compliance burden is decreased, but authentication reliability may be compromised
Solution Approach 1:
The patent introduces identifiers as intermediary elements that mediate between the client device and payment token device. These identifiers enable authentication without transferring sensitive payment data through complex infrastructure. The client device uses identifiers to communicate with the payment token device, generating approvals that can be verified without extensive data transfer infrastructure
Solution Approach 2:
The patent creates a simplified copy of the authentication process that operates at the client device level rather than requiring full infrastructure replication. The client device generates approvals based on communication with the payment token device, creating a lightweight authentication mechanism that maintains reliability without requiring complex data transfer infrastructure
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The function of authenticating payments leveraging a reduced infrastructure is disclosed. Systems and methods provide merchant services module 112 receiving a first identifier associated with a client device 130 and a second identifier associated with a set of items. The merchant services module 112 communicates with the client device 130 to generate a request for user input. The client device 130 communicates with a payment token device 140. The client device 130 generates an approval based on the communication between the payment token device and the client device 140,130. The merchant services module 112 receives approval from the client device 130. The merchant services module determines that the approval from the client device 130 corresponds to the second identifier that is associated with the set of items. The merchant services module provides the item(s) associated with the approval and the second identifier to the user of the client device.