Digital Wallet Linking for Repeated Card Input Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional online checkout systems require users to input card details each time, which is cumbersome due to the need to manage multiple cards from different issuers across various merchants with unique checkout systems.
Innovation Solution
A system and method for linking a digital wallet within a separate payment service, allowing users to integrate their wallet with a payment service account, enabling seamless card information management across multiple merchants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If users manually input card details for each transaction, then each merchant can process payments, but user convenience and time efficiency deteriorate due to repeated input requirements
Solution Approach 1:
The system performs preliminary actions by automatically detecting and storing card information from a user's digital wallet during the checkout process. The card details are captured and saved in advance for future transactions, eliminating the need for repeated manual input across different merchant sites.
Solution Approach 2:
A payment service intermediary system is introduced between the user's digital wallet and multiple merchant checkout systems. This intermediary automatically extracts card information from the wallet, manages card storage, and facilitates seamless payment processing across different merchants without requiring direct user intervention at each site.
2Adaptability or versatility
If users manage multiple cards from different issuers across various merchants, then payment options increase, but system complexity increases due to managing multiple checkout systems
Solution Approach 1:
The payment service system provides universal functionality that works across multiple merchant checkout systems simultaneously. It can detect, store, and manage multiple cards from different issuers in a centralized manner, allowing users to access their card portfolio uniformly regardless of which merchant site they are transacting with.
Solution Approach 2:
The intermediary payment service acts as a universal layer between the user's diverse card portfolio and the various merchant checkout systems. It automatically identifies available cards, presents them to the user in a unified interface, and handles the complexity of interfacing with different merchant payment systems in the background.
3Productivity
If card information is stored at each merchant, then future transactions become faster, but security risk increases due to multiple storage locations
Solution Approach 1:
The payment service intermediary serves as a secure centralized storage location for card information, replacing the need for merchants to store sensitive card data. The intermediary uses tokenization and encryption to protect card information while enabling fast transactions by retrieving stored card details and transmitting only secure tokens to merchants.
4Ease of operation
If automatic card detection is implemented, then user convenience improves, but system integration complexity increases between wallet and payment services
Solution Approach 1:
The payment service intermediary implements standardized communication protocols and APIs that simplify integration between digital wallets and payment processing systems. It handles the complex tasks of card information extraction, validation, and secure transmission, allowing automatic card detection to work seamlessly across different wallet and merchant systems without requiring complex custom integrations.
Data Source
AI summary
A computer-implemented method including determining, by a wallet server, whether a wallet of a user can be linked to a payment service account of the user. The method also can include causing a link option to be displayed to the user on a wallet user interface. The method additionally can include receiving, at the wallet server from the wallet user interface, a request to link the wallet to the payment service account. The method further can include sending, by the wallet server, card information for one or more payment cards in the wallet to a payment service server be added to the payment service account. Other embodiments are described.


