Browser Extension Checkout Autofill Without Payee API Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing financial transaction systems lack efficient and secure methods for processing transactions that respect user preferences and protect against fraud while maintaining privacy and security.
Innovation Solution
A system and method utilizing a Rule-Module Nexus and User Account Registry, where a unique user code is stored in a portable nexus access token, enabling secure access to multiple financial accounts via a verification platform, preserving user preferences and detecting fraud through dual verification codes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional financial transaction systems are used, then processing speed is maintained, but security and fraud detection capabilities are insufficient
Solution Approach 1:
The system segments verification into multiple independent components: device verification (hardware ID), user verification (biometric or PIN), and transaction verification. Each component operates independently but contributes to the overall security decision, allowing complex security checks to be broken into manageable segments that enhance reliability without overwhelming system complexity.
Solution Approach 2:
The patent introduces an intermediary verification platform that acts as a mediator between the user device and the financial transaction system. This intermediary handles the complex verification logic, fraud detection algorithms, and communication protocols, shielding the core transaction system from complexity while maintaining enhanced security through multiple verification layers.
2Reliability
If multiple verification methods are implemented, then fraud detection is improved, but processing time increases
Solution Approach 1:
The system performs preliminary device verification and user authentication before the actual transaction processing begins. By completing verification steps in advance and caching verification results where appropriate, the system ensures fraud detection is thorough while minimizing the time impact on the core transaction execution.
Solution Approach 2:
The verification system uses periodic checks rather than continuous verification during transaction processing. Critical verification points are established at specific intervals (device connection, transaction initiation, confirmation), allowing the system to maintain strong fraud detection while avoiding constant verification overhead that would slow processing.
3Adaptability or versatility
If user preferences are stored and processed, then service personalization is improved, but data privacy risks increase
Solution Approach 1:
The patent extracts sensitive user preference data from the central verification platform and stores it locally on the user device. This extraction reduces the amount of sensitive data that needs to be transmitted and stored centrally, thereby minimizing data privacy risks while still enabling service personalization through local data processing.
Solution Approach 2:
The system enables self-service processing of user preferences at the device level, where the device itself manages and processes preference data without requiring constant central server intervention. This self-service approach allows personalization to be maintained while reducing data exposure to external systems, thereby lowering privacy risks.
Data Source
AI summary
A computer implemented method for enabling a payment transaction in a computer system executed at least partially by a computer of a user connected via a communication network to a remote computer comprising a database of payment-related data, said method comprising the steps of: a) accessing the payment-related data of a user from within the database, wherein a web browser extension on the user's computer is invoked by the user clicking on a web browser extension graphical user interface (GUI) widget displayed on the user's computer, wherein secure network access is established to access the user's payment-related data from within the database; b) presenting the user's payment-related data via a pop-up window displayed on the user's computer, without requiring application programming interface integration with a website or a web application of a payee, and without requiring a form re-direct away from the website or the web application of the payee; c) enabling the payment transaction, wherein the web browser extension invokes an auto-complete function to automatically populate fields of a checkout form presented from the website or the web application of the payee with the user's payment-related data.