Cloud Invoice Database Payment System Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current payment systems based on ATM cards, credit cards, and debit cards are vulnerable to security flaws as they allow third-party access to users' accounts, enabling unauthorized transactions and lack user control over the amount and recipient of payments.
Innovation Solution
A new payment system utilizing a global database of invoices, where sellers submit invoices to the database, and buyers can verify and pay them directly through their bank, eliminating third-party access and enabling user control over transactions, with features like optical recognition and QR codes for easy payment processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If ATM cards, credit cards, or debit cards are used for payment, then payment convenience is improved, but security is worsened due to third-party access to user accounts
Solution Approach 1:
The patent extracts the payment authorization function from physical cards and centralizes it in a cloud-based system. Instead of storing sensitive card data on physical cards or in decentralized systems, the invention stores payment authorization data exclusively in a cloud database, eliminating the security risks associated with physical card storage and third-party access.
Solution Approach 2:
The patent introduces a cloud-based payment system as an intermediary between users and merchants. This intermediary system verifies payment authorization by comparing transaction details against stored authorization data in the cloud database, preventing direct third-party access to user accounts while maintaining secure payment processing.
2Speed
If token payment systems or credit cards provide permission to withdraw money, then payment speed is improved, but control over amount and receiver is worsened
Solution Approach 1:
The patent applies local quality by making each payment authorization specific to a particular merchant, amount, and time window. Instead of providing general payment permissions, the system stores detailed authorization records that include merchant identifiers, amount ranges, and validity periods, allowing users to maintain precise control over each payment instance while enabling fast verification.
Solution Approach 2:
The patent changes the parameters of payment authorization from static card numbers to dynamic records containing multiple parameters (merchant ID, amount minimum, amount maximum, expiration time). This allows the system to verify payments by checking multiple parameters simultaneously, providing both speed and granular user control.
3Reliability
If a global database of invoices is implemented, then security is improved by preventing third-party access, but system complexity is worsened
Solution Approach 1:
The patent creates a universal cloud-based system that handles multiple functions: storing payment authorizations, verifying transactions, managing user accounts, and providing receipt generation. This multi-functional approach consolidates what would otherwise require multiple separate systems, reducing overall complexity while maintaining high security standards.
Solution Approach 2:
The system implements self-service mechanisms where users can view their payment history, generate receipts, and manage their authorization records through the cloud platform. This automation reduces the need for manual intervention and complex administrative systems, simplifying operations while maintaining security.
Data Source
AI summary
Systems and methods for secure purchasing are provided in which an invoice comprising an amount to be remitted and a merchant identification is generated. The invoice is transmitted to a remote invoice database. At a device associated with a consumer, the invoice identification is received. A request including the invoice identification is sent to the remote invoice database thereby retrieving information about the invoice including an amount to be remitted and a merchant identification. Responsive to receiving consumer confirmation of the invoice, an approval of the invoice is transmitted to an account database comprising at least one account corresponding to the consumer. At a device associated with the account database, after receiving invoice approval, the invoice amount is remitted to the merchant in the form of a bank check that identifies the merchant and a notification of the check and the merchant is stored in the remote account database.