Account Pool Processing System for Secure Payment Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing accounts payable systems face risks such as fraud and unauthorized access due to the transmission of sensitive account information, and they consume computational resources with credit limit adjustments and authorization match processes, which are not available to all suppliers.
Innovation Solution
Implementing a method where a server computer stores account information for multiple pools with different credit limits and selects an account from the pool with the lowest sufficient credit limit for each payment, reducing exposure to risks and conserving computational resources by minimizing unnecessary account control processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If account information is transmitted to suppliers for payment processing, then payment convenience is improved, but security risks increase due to potential fraud and unauthorized access
Solution Approach 1:
The patent segments the account information into multiple pools (first pool, second pool, etc.) with different credit limits. Each pool serves a specific payment range, allowing the system to select the appropriate pool based on the payment amount. This segmentation reduces security risks by limiting the exposure in each pool while maintaining payment convenience through automated selection.
Solution Approach 2:
Different pools of account information are assigned different credit limits and security characteristics based on local requirements. The system applies different security controls to different pools, with each pool optimized for specific payment scenarios. This local quality approach allows tailored security measures for each pool while maintaining overall system convenience.
2Reliability
If credit limit adjustments and authorization match processes are implemented, then security control is improved, but computational resource consumption increases
Solution Approach 1:
The system performs preliminary organization of account information into pools with predetermined credit limits before actual payment processing. This preliminary action eliminates the need for real-time credit limit adjustments and authorization matches during transaction processing, significantly reducing computational resource consumption while maintaining security control through the pre-established pool structure.
Solution Approach 2:
The patent extracts the credit limit verification and authorization match functions from the real-time transaction processing flow. Instead of performing these checks during each payment, the system has already organized accounts into pools with appropriate credit limits, removing the computational burden from the active transaction path while preserving security controls.
3Productivity
If account information is stored by suppliers temporarily, then payment processing capability is improved, but vulnerability to unauthorized access increases
Solution Approach 1:
By segmenting account information into multiple pools with different credit limits, the system reduces the amount of sensitive information any single supplier needs to handle. Each pool represents a limited scope of authority, reducing the impact of potential unauthorized access while maintaining full payment processing capability through the collective pools.
Solution Approach 2:
The system changes the parameter of credit limit assignment dynamically based on the payment amount and selected pool. This parameter change ensures that suppliers only access account information appropriate for the specific transaction size, reducing vulnerability to unauthorized access while maintaining the ability to process payments of various amounts through different pools.
Data Source
AI summary
Embodiments are directed to systems, apparatus, and methods for account pool processing. In some embodiments, a server computer can store account information for a first pool of accounts and a second pool of accounts. The server computer can receive a payment request message from a buyer that identifies a payment amount and a supplier, and can determine that the payment amount corresponds to the first or second pool of accounts. If the payment amount corresponds to the first pool of accounts, the server computer can select an account from the first pool of accounts, and can transmit account information for the selected account to the supplier. If the payment amount corresponds to the second pool of accounts, the server computer can select an account from the second pool of accounts, and can transmit account information for the selected account to the supplier.