Virtual Wallet Server Payment Data Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtual wallets face challenges in integrating with merchant payment terminals, requiring sensitive information handling and cumbersome onboarding processes, which pose burdens on merchants and complicate integration with various shopping cart plug-ins.
Innovation Solution
A computer system comprising a checkout server and a virtual wallet server, with a process that receives a checkout request, enables payment using a registered virtual wallet, transmits shopping cart details, and processes payment using a payment vehicle identifier, reducing the need for sensitive information sharing and simplifying merchant onboarding through an interface server that maps requirements between different systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If virtual wallets transmit complete payment vehicle identifiers to merchants, then payment processing reliability is improved, but merchant compliance burden and security risk increase
Solution Approach 1:
The patent extracts and removes the complete payment vehicle identifier from the transaction data flow. Instead of transmitting the full identifier, the system uses a virtual wallet identifier that references the payment vehicle in the virtual wallet server's database. This extraction eliminates the need for merchants to handle sensitive complete identifiers while maintaining payment processing reliability through server-side verification.
Solution Approach 2:
The virtual wallet server acts as an intermediary between the consumer's payment vehicle and the merchant. The server receives the virtual wallet identifier, retrieves the associated complete payment vehicle identifier from its database, and processes the transaction without exposing the sensitive identifier to the merchant. This intermediary role reduces merchant compliance burden while ensuring reliable payment processing.
2Reliability
If virtual wallets require merchants to handle sensitive payment information, then payment security is improved, but ease of operation for merchants deteriorates
Solution Approach 1:
The sensitive payment information (complete payment vehicle identifier) is extracted from the merchant's environment entirely. The merchant only handles the non-sensitive virtual wallet identifier, while all sensitive data remains confined to the virtual wallet server's secure database. This maintains payment security through server-side handling while dramatically improving merchant ease of operation.
Solution Approach 2:
The virtual wallet server performs self-service by automatically retrieving and verifying payment vehicle information from its own database using the virtual wallet identifier. The merchant does not need to manually handle or validate sensitive payment data, as the system autonomously manages the sensitive information retrieval and verification processes.
3Adaptability or versatility
If virtual wallets integrate with multiple shopping cart plug-ins, then adaptability is improved, but device complexity increases
Solution Approach 1:
The virtual wallet identifier serves as a universal interface that works across multiple shopping cart plug-ins and merchant systems. Instead of creating separate integration mechanisms for each plugin, the system uses a single standardized virtual wallet identifier format that can be processed by any compliant system, achieving multi-functionality and broad adaptability without proportionally increasing complexity.
Solution Approach 2:
The virtual wallet server acts as a universal intermediary that handles all variations of shopping cart plug-ins through a single interface. The server receives virtual wallet identifiers from any plugin, manages the diverse integration requirements internally, and processes transactions uniformly. This intermediary approach enables high adaptability while containing integration complexity within the server rather than propagating it to each merchant system.
Data Source
AI summary
Disclosed herein is a computer system for making an electronic payment transaction. The system comprises a checkout server and a virtual wallet server. The checkout server and virtual wallet server each comprise at least one processor and at least one memory including computer program code. The computer program code of the checkout server and the virtual wallet server collectively configure the computer system to, with the respective at least one processor, receive, at the checkout server, a checkout request and enable payment for the electronic payment transaction using a virtual wallet registered on the virtual wallet server, the virtual wallet comprising a payment vehicle having a payment vehicle identifier comprising a number of characters for uniquely identifying the payment vehicle. The computer program code is further configured to cause the computer system to receive a virtual wallet identifier at the virtual wallet server, the virtual wallet identifier identifying the virtual wallet, send shopping cart details including a shopping cart value from the checkout server to the virtual wallet server, transmit, from the virtual wallet server to the checkout server, payment data comprising a proper subset of the characters from which the payment vehicle identifier can be inferred and receive a payment confirmation at the checkout server, confirming payment for the electronic payment transaction should be made using the payment vehicle. That payment confirmation is then sent to the virtual wallet server, and payment is processed for the shopping cart value using the payment vehicle.