Tokenized Payment Plugin for Non-Wallet Merchant Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Consumers are unable to make payments using tokenized payment information on merchant websites that are not enrolled in digital wallet services, as the tokenized information is not recognizable by these merchants, and entering actual sensitive payment account information exposes it to security risks.
Innovation Solution
A plugin or software installed on user computing devices communicates with a wallet and token service provider to generate tokenized payment information in a format recognizable to the merchant, allowing consumers to use digital wallets even on non-wallet-enabled merchant sites, without the merchant needing to subscribe to a digital wallet service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If tokenized payment information is used, then security is improved, but compatibility with non-enrolled merchants deteriorates
Solution Approach 1:
The patent introduces a plugin as an intermediary component installed on the user's device that mediates between the digital wallet and the merchant system. The plugin captures tokenized payment information from the digital wallet and reformats it to be compatible with non-enrolled merchant systems, allowing secure tokenized payments to work universally without requiring merchant enrollment.
2Adaptability or versatility
If actual payment account information is transmitted, then compatibility is improved, but security deteriorates
Solution Approach 1:
The patent applies preliminary action by pre-tokenizing the payment account information in the digital wallet before transmission to the merchant. This tokenization process replaces sensitive account details with secure tokens in advance, so that when payment information is transmitted to non-enrolled merchants, compatibility is maintained while security is preserved through the pre-applied tokenization.
3Reliability
If digital wallet service enrollment is required, then security is improved, but device complexity deteriorates
Solution Approach 1:
The patent implements self-service by enabling the plugin on the user's device to autonomously handle tokenization and format conversion without requiring merchant enrollment or configuration. The system automatically manages the security protocols and token formatting, eliminating the need for complex merchant-side digital wallet service enrollment while maintaining security standards.
Data Source
AI summary
Provided are a system and method for generating and transmitting tokenized payment information. In one example, the method includes transmitting a request for payment information to a payment network, receiving tokenized payment information of a payment account from the payment network, and transmitting the tokenized payment information to a merchant. According to various exemplary embodiments, the tokenized payment information may include a tokenized account number representing an account number of the payment account and a tokenized credential representing an additional credential of the payment account.


