Push Transaction Tokenization for Secure Payment Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Consumers face challenges in making payments for goods or services without knowing the final amount, while also wanting to protect sensitive account information from unnecessary exposure to multiple parties.
Innovation Solution
A method involving a server computer that generates and transmits a token corresponding to a credential to a resource provider, allowing the resource provider to enter a transaction amount and process the payment, ensuring the consumer's account information remains secure and reducing fraud risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the consumer provides their account information to the resource provider for payment processing, then the payment can be processed, but the consumer's sensitive account information is exposed to multiple parties and fraud risk increases
Solution Approach 1:
A server computer acts as an intermediary between the consumer's communication device and the resource provider computer. The server receives transaction requests with credentials from the consumer device, processes the transaction, and communicates only with the resource provider about transaction status and amounts, never exposing the consumer's actual account information to the resource provider.
Solution Approach 2:
The system creates a representation of the transaction using a token that corresponds to the consumer's credential. This token serves as a copy that allows the resource provider to process the transaction without accessing the actual sensitive account information. The token is transmitted to the resource provider computer for entering the transaction amount.
2Adaptability or versatility
If the consumer wants to pay for goods or services without knowing the final amount, then flexibility is provided, but the transaction processing becomes more complex
Solution Approach 1:
The consumer initiates the transaction request in advance by providing their credential and the resource provider ID to the server computer before knowing the final amount. The server computer pre-processes this request and waits for the resource provider to input the transaction amount, allowing the consumer to proceed with the transaction early in the process.
Solution Approach 2:
The server computer mediates the asynchronous transaction process by holding the consumer's credential information securely while the resource provider determines the final amount. This intermediary role allows the transaction to progress without requiring the consumer to know the final amount upfront, while maintaining security and processing efficiency.
3Object-affected harmful factors
If the resource provider needs to enter the transaction amount after receiving the token, then the consumer's information remains secure, but the transaction process takes longer
Solution Approach 1:
The server computer performs preliminary processing by receiving the consumer's credential and generating the token in advance, before the resource provider needs to input the transaction amount. This pre-processing reduces the overall transaction time while maintaining security, as the sensitive information handling is completed before the resource provider's involvement.
Solution Approach 2:
The token serves as a ready-to-use copy of the consumer's credential that can be immediately transmitted to the resource provider computer. This eliminates the need for the resource provider to handle or store sensitive account information, maintaining security while enabling rapid transaction processing once the amount is entered.
Data Source
AI summary
Embodiments of the invention are directed to systems and methods for pushing tokenized payments to resource providers for goods or services, after the goods or services are received. A user may make a transaction request including a credential and a resource provider ID (e.g., a resource provider location) via a server computer. The server computer may generate a token corresponding to the credential and transmit it to the resource provider using the resource provider ID. Upon receiving the token, the resource provider may enter a transaction amount and send it with the token in an authorization request message. The transaction can then be processed according to standard transaction processing methods, as if the resource provider had initiated the transaction request.