Payment Collection Device Direct Server Interaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing payment collection devices require multiple intermediaries and complex data links, leading to low efficiency and poor user experience due to the need for merchants to register payment receiving accounts on intermediate servers and payment accounts on separate payment servers, resulting in lengthy payment processing times.
Innovation Solution
A payment collection device that directly interacts with a target server managing both merchant and user accounts, allowing for a simplified data link by scanning payment codes to deduce payments from user accounts and add them to merchant accounts, eliminating the need for intermediate servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If an intermediate server is used to manage payment receiving accounts and connect merchant settlement devices with payment servers, then payment collection functionality can be implemented, but payment processing time increases and efficiency decreases
Solution Approach 1:
The patent extracts and removes the intermediate server from the payment system architecture. The merchant settlement device directly communicates with the payment server without routing through an intermediate server, eliminating unnecessary data transmission hops and reducing payment processing time while maintaining payment collection functionality.
Solution Approach 2:
The patent implements asymmetric account management where the payment server directly manages both user payment accounts and merchant payment receiving accounts. This asymmetric structure eliminates the need for symmetric intermediate management layers, allowing direct deduction from user accounts and direct crediting to merchant accounts, thereby reducing processing time.
2Adaptability or versatility
If multiple separate servers (intermediate server and payment server) are used to manage different account types, then account management flexibility is improved, but system complexity and data link length increase
Solution Approach 1:
The patent merges the functions of the intermediate server and payment server into a single payment server. This unified server manages both user payment accounts and merchant payment receiving accounts, reducing system complexity and shortening data links while maintaining the flexibility to handle different account types through software-based account management rather than separate physical servers.
3Reliability
If a code scanning device is connected to a merchant's settlement device for payment collection, then payment collection capability is achieved, but the number of intermediaries increases and efficiency decreases
Solution Approach 1:
The patent extracts the payment collection functionality from the merchant's settlement device and implements it directly in the code scanning device. The code scanning device independently communicates with the payment server to complete payment collection, removing the settlement device as an intermediary and improving payment collection efficiency.
Solution Approach 2:
The code scanning device performs payment collection autonomously by directly interacting with the payment server. It scans user payment codes, initiates payment requests, and receives confirmation without requiring manual intervention or connection to the merchant's settlement device, enabling self-service payment collection that improves efficiency.
Data Source
AI summary
Systems, methods, and storage media for payment collection are disclosed. An example method comprises: obtaining, at a code scanner, payment account information comprised in a payment code of a purchasing user by scanning the payment code; sending, at the code scanner, the payment account information to a processor; determining, at the processor, a payment amount due, to construct a payment request comprising the payment amount due, the payment account information, and the device identifier; sending, at the processor, the payment request to a communication module; and sending, at the communication module, the payment request to the target server for the target server to, according to the payment request, deduct the payment amount due from a payment account of the purchasing user corresponding to the payment account information, and add the payment amount due to the payment receiving account corresponding to the device identifier.