Browser Plugin for Automatic Payment Field Population
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing online payment systems do not allow consumers to use a preferred third-party payment provider for transactions with online merchants that do not natively support that provider, leading to inconvenience and security concerns.
Innovation Solution
A plugin component is introduced that automatically populates payment fields on online merchant checkout pages using a third-party payment provider, even if the merchant does not natively support that provider, by authenticating the user and tokenizing their payment information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If consumers use third-party payment providers for online transactions, then payment convenience and security are improved, but compatibility with online merchants is worsened
Solution Approach 1:
The patent introduces a browser plugin as an intermediary layer between the consumer's payment provider and the online merchant. This plugin acts as a mediator that translates payment provider-specific protocols into merchant-compatible formats, enabling third-party payment providers to work with merchants who do not natively support them. The plugin injects itself into the merchant's checkout page, creating a bridge that allows seamless payment processing without requiring direct merchant integration.
2Ease of manufacture
If consumers manually enter payment information with each merchant, then payment setup is simplified, but time consumption and inconvenience are worsened
Solution Approach 1:
The patent implements preliminary action by pre-configuring payment information and authentication credentials in the browser plugin before the consumer visits any merchant site. The plugin stores payment tokens, authentication details, and payment provider configurations in advance, so that when a consumer visits a merchant site, the payment information is already prepared and can be automatically retrieved and filled in without manual entry. This eliminates the need for consumers to repeatedly set up payment information with different merchants.
Solution Approach 2:
The browser plugin performs self-service by automatically detecting merchant checkout pages, identifying required payment fields, and autonomously filling in payment information without consumer intervention. The plugin monitors the page for checkout forms, automatically extracts payment data from the consumer's stored credentials, and populates the appropriate fields on the merchant site. This automation eliminates manual data entry while maintaining security through encrypted credential storage and tokenization.
3Adaptability or versatility
If online merchants integrate multiple payment providers, then payment versatility is improved, but system complexity is worsened
Solution Approach 1:
The patent positions the browser plugin as an intermediary that handles the complexity of multiple payment provider integrations on the consumer side rather than requiring merchants to implement complex multi-provider support. The plugin contains the complexity by maintaining an abstract layer that communicates with different payment providers using their specific protocols while presenting a unified interface to the merchant's checkout page. This shifts the integration burden from the merchant to the consumer's browser, allowing merchants to maintain simple, single-provider integrations while still supporting multiple payment methods through the plugin's mediation.
Data Source
AI summary
An engagement by a user with respect to an interactive component is detected. The interactive component is embedded in a first display area of an electronic device. The first display area displays a plurality of fields of an online merchant checkout page. A second display area is launched in response to the detected engagement of the interactive component. The second display area contains information with respect to a payment provider. User input is received via the second display area. The user input contains information regarding an account that the user has with the payment provider. The user is authenticated based on the user input. User account information pertaining to the payment provider is accessed. At least a portion of the user account information is tokenized. At least one of the fields of the online merchant checkout page is automatically populated with the tokenized portion of the user account information.