Shared Wallet Browser Autofill With Risk-Based Payment Tokenization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional online checkout systems require users to input card details for each transaction, which is cumbersome due to the use of multiple cards from different issuers and various merchant checkout systems, lacking a unified and secure method for autofill.
Innovation Solution
A system utilizing a wallet server that performs a risk assessment, determines the need for step-up authentication, requests token information from a token service provider, and creates a secure payload for browser autofill, enabling seamless and secure payment transactions across multiple merchants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If users manually input card details for each transaction across multiple merchants, then security is maintained, but transaction time and user effort increase significantly
Solution Approach 1:
The system performs preliminary actions by storing payment instrument information in a shared wallet before transactions occur. During checkout, the browser autofill feature automatically retrieves and populates payment details from the shared wallet, eliminating the need for manual re-entry of card information across multiple merchants and significantly reducing transaction time and user effort
Solution Approach 2:
The shared wallet serves as a universal payment storage solution that works across multiple merchants and browsers. By implementing a multi-functionality principle, the system allows a single shared wallet to store and manage multiple payment instruments that can be automatically filled across different merchant checkout systems, eliminating the need for separate card storage at each merchant
2Productivity
If card information is stored at each merchant for future transactions, then checkout speed improves, but security risks and data management complexity increase
Solution Approach 1:
The shared wallet acts as an intermediary between users and merchants, centralizing payment instrument storage in a secure location. Instead of storing card information at each merchant, the system uses the shared wallet as a mediator that provides payment details during checkout through browser autofill, maintaining security while enabling fast checkout across multiple merchants
Solution Approach 2:
The system extracts sensitive card information from individual merchant systems and consolidates it into a single shared wallet. By taking out the payment data from multiple merchant databases and storing it centrally in the shared wallet with appropriate security measures, the system reduces security risks associated with distributed storage while maintaining quick access during transactions
3Adaptability or versatility
If multiple payment instruments from different issuers are supported, then user versatility improves, but system complexity and authentication requirements increase
Solution Approach 1:
The shared wallet is designed with multi-functionality to support multiple payment instruments from different issuers in a unified manner. The system handles various card types (credit, debit, prepaid) and issuers through a single interface, managing diversity of payment methods without increasing apparent complexity for users while enabling versatile payment options across different merchants
Data Source
AI summary
A computer-implemented method including receiving, at a wallet server, a request from a browser server for payload information associated with a selected payment instrument for an online checkout transaction. The method also can include performing, by the wallet server, a risk assessment for the selected payment instrument. The method additionally can include determining whether to perform a step-up authentication based on the risk assessment. The method further can include, upon determining to proceed with the online checkout transaction, requesting, by the wallet server, token information from a token service provider. The method additionally can include receiving, at the wallet server, the token information from the token service provider. The method further can include creating, by the wallet server, a secure payload comprising the token information. The method additionally can include sending, by the wallet server, the secure payload to the browser server for autofill in a browser. Other embodiments are described.