Payment Card URL Authentication for Scalable Fraud Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication solutions for payment cards lack flexibility and scalability, failing to adequately address fraud and security issues as the number of cards increases.
Innovation Solution
Implement URL-based authentication using static and dynamic URLs assigned to or generated by payment cards, which are authenticated by a server using a unique card identifier and private key, ensuring secure access to account-related operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional authentication solutions are used for payment cards, then the authentication process is simple, but the system lacks flexibility and scalability to address fraud and security issues as the number of cards increases
Solution Approach 1:
The patent introduces a server as an intermediary component that handles authentication requests. The server receives URLs from client devices, extracts card identifiers, compares them against expected values stored in a database, and returns authentication results. This intermediary architecture allows the system to scale efficiently without requiring complex client-side processing, resolving the contradiction between adaptability and complexity.
Solution Approach 2:
The authentication process is segmented into distinct functional components: URL generation by the card, URL transmission to the client device, request transmission to the server, card identifier extraction by the server, comparison against expected values, and authentication decision. This segmentation allows each component to be optimized independently, improving overall system flexibility while maintaining manageable complexity.
2Reliability
If complex URLs with card identifiers are used for authentication, then security against fraud is improved, but the difficulty of detecting and measuring authentication requests increases
Solution Approach 1:
The server extracts the card identifier from the URL parameter and uses it for authentication comparison. By isolating the critical authentication data (the card identifier) from the rest of the URL structure, the system maintains security through complex URLs while simplifying the detection and measurement process to a straightforward string comparison operation.
3Quantity of substance
If more payment cards are issued to increase customer coverage, then the number of authenticated cards increases, but the security problems and fraud detection difficulty are exacerbated
Solution Approach 1:
Instead of storing sensitive card data directly in the database, the system stores only the expected card identifiers associated with URLs. When authentication is needed, the server extracts the card identifier from the URL and compares it against the stored expected value. This copying approach allows the system to handle millions of cards securely without storing sensitive information, thereby increasing the number of authenticated cards while maintaining security.
Data Source
AI summary
Systems, methods, articles of manufacture for authentication of payment cards. A server may assign, in a database, an expected card identifier to a contactless card, the contactless card associated with an account. The server may receive, from a client device, a request comprising a uniform resource locator (URL), a parameter of the URL comprising a card identifier, wherein the URL is transmitted by the contactless card to the client device. The server may extract the card identifier from the URL and compare the extracted card identifier to the expected card identifier in the database. The server may determine, based on the comparison, that the extracted card identifier matches the expected card identifier. The server may authenticate the request based on the extracted card identifier matching the expected card identifier, and transmit, to the client device, an indication specifying that the request was authenticated.