Secure Registration Using Tokenized Payment Data Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing e-commerce systems lack secure methods for customer registration and transaction processing, particularly in online environments, where vendors are uncomfortable relying on third-party services for sensitive information handling, leading to security concerns and loss of control over customer data.
Innovation Solution
A system and method for secure customer registration and transaction processing using tokens generated by the vendor's server, which encrypts sensitive information and transmits it directly to payment servers without passing through partner servers, utilizing JavaScript and browser-based encryption, allowing two-click transactions and maintaining vendor control over the process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If vendors use third-party services to process transactions and store customer information, then transaction processing capability is improved, but security control and data privacy are worsened
Solution Approach 1:
The patent segments customer information into sensitive data (credit card numbers, CVV) and non-sensitive data (name, address). Sensitive information is encrypted and transmitted directly to payment processors, while non-sensitive information is shared with third-party vendors. This segmentation allows vendors to process transactions through third parties without exposing sensitive data, thus maintaining both transaction capability and security control.
Solution Approach 2:
The patent introduces encryption as an intermediary mechanism between the vendor and the payment processor. The encryption layer acts as a mediator that allows sensitive information to be transmitted securely through third-party systems without being exposed to them. The vendor can initiate transactions through partners while the encrypted sensitive data bypasses the partner's servers, going directly to the payment processor.
2Adaptability or versatility
If vendors collect and store complete customer information for transactions, then transaction flexibility is improved, but risk of data breaches is worsened
Solution Approach 1:
The patent extracts sensitive information from the vendor's data storage system and handles it through a separate, secure transmission channel directly to the payment processor. By taking out sensitive data from the vendor's control environment and processing it through a dedicated encrypted pathway, the system maintains transaction flexibility while removing the vulnerability of storing complete customer information at the vendor level.
Solution Approach 2:
The patent employs tokens as temporary, disposable representations of sensitive customer information. Instead of storing actual credit card numbers, the system uses tokens that are valid only for specific transactions and can be discarded afterward. These tokens provide the necessary transaction flexibility while minimizing long-term data retention and associated breach risks.
3Productivity
If vendors rely on outside companies for online presence and transaction processing, then operational efficiency is improved, but control over customer data is worsened
Solution Approach 1:
The patent implements preliminary encryption of sensitive customer information before it leaves the vendor's system. By performing this encryption action in advance, the vendor maintains control over the sensitive data throughout the transaction process, even when using third-party services. The preliminary encryption ensures that outside companies receive only encrypted data, preserving vendor control while still leveraging external operational efficiency.
Data Source
AI summary
Methods and apparatus for secure registration to enable transactions between a first user and a vendor that is facilitated by a payment server are disclosed. The method may comprise storing a form soliciting customer information including a plurality of fields, wherein at least one of the plurality of fields is associated with an attribute. The method including receiving a copy of the form including customer data in all of the plurality of fields and transmitting a first subset of the customer data based on the attribute associated with the first subset of the customer data. The method including receiving a token in response to the transmission of the first subset of customer data and transmitting the token and a second subset of the customer data, wherein the second subset is based on the attribute associated with the second subset of customer data.