Browser Extension Secure Tokens for Authenticated Payment Autofill
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing browser extension applications face vulnerabilities in data security, with automatically populated data susceptible to interception, fraud, and corruption, and lack clear authority verification for user and recipient data usage.
Innovation Solution
A browser extension application generates secure tokens mapped to financial service accounts and populates payment fields with these tokens, ensuring secure submission and limiting recipient use to the user's intended purpose, with authentication through a second computing device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If conventional browser extension applications automatically populate fields with user data, then ease of operation is improved, but data security deteriorates due to vulnerability to interception, fraud, and corruption
Solution Approach 1:
The patent introduces secure tokens as an intermediary between user data and payment fields. Instead of directly submitting sensitive user data, the browser extension generates secure tokens that act as mediators - these tokens contain encrypted references to the actual data and can only be used for their intended purpose, thereby protecting the original data from interception and fraud while maintaining automatic population functionality
2Reliability
If secure tokens are generated and used instead of direct data submission, then data security is improved, but device complexity increases due to authentication requirements
Solution Approach 1:
The patent segments the authentication process into distinct components: token generation, token validation, and data submission. The browser extension handles token generation and submission, while a separate authentication service validates the tokens. This segmentation allows each component to be optimized independently and reduces the complexity burden on any single device
3Reliability
If user authentication is required before data submission, then authority verification is improved, but productivity decreases due to additional authentication steps
Solution Approach 1:
The patent implements preliminary authentication by requiring users to authenticate once when initially setting up their browser extension with their payment information. This preliminary action stores authentication credentials locally, eliminating the need for repeated authentication during subsequent transactions. The secure tokens generated from this preliminary authentication can be automatically submitted without requiring additional user intervention, thus maintaining both security and productivity
Data Source
AI summary
Methods and systems for a browser extension system are disclosed. In some embodiments, a browser extension server includes a communication device configured to communicate with a first computing device executing a browser extension application and a web browser application and a second computing device executing an authentication application. The browser extension server further includes a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include receiving from the first computing device an indication of a financial service account associated with the first computing device, detecting a payment field in a web page provided by the computing device through the web browser application and, in response, generating a secure token mapped to the financial service account. The operations may further include sending the second computing device an authentication request, receiving an authentication response, and populating the payment field with the secure token.


