Dynamic Payment Financing via Tokenized Identity Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in securely handling credit card transactions while preventing the entry of personal identity information and in offering flexible payment options at the point of sale without exposing sensitive credit card data.
Innovation Solution
The system utilizes a mapping between a merchant's program (e.g., loyalty program user identifiers) and card numbers of co-brand credit cards, allowing for the display of alternative payment options without sharing actual credit card numbers. This is achieved through an API provided by the credit card issuer, enabling real-time offers based on user profiles without accessing sensitive data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If credit card data is stored for card-on-file transactions, then payment convenience is improved, but security risks increase and data exposure occurs
Solution Approach 1:
The patent extracts sensitive credit card data from the merchant's system entirely. Instead of storing card numbers, the system uses tokenization where the card issuer retains the actual card data and only shares encrypted tokens or mapped program identifiers with the merchant. This removes the harmful element (sensitive data) from the merchant's environment while preserving payment convenience through automated lookup of stored payment methods.
Solution Approach 2:
The patent introduces an intermediary layer (the card issuer's system) that mediates between the cardholder and merchant. The issuer acts as a trusted third party that stores the actual card data securely and provides only necessary payment authorization information to the merchant without exposing sensitive card numbers. This intermediary structure enables convenient repeat payments while maintaining security through centralized data protection.
2Adaptability or versatility
If credit card information is shared between merchant and issuer for co-branded transactions, then flexible payment options can be offered, but data security is compromised and exchange overhead increases
Solution Approach 1:
The patent creates a copy-based system where the merchant receives encrypted copies or tokens of card identifiers rather than actual card data. The system maps program identifiers to card accounts through encrypted lookups, allowing the merchant to offer co-branded payment options without handling or storing sensitive card information. This copying approach enables versatile payment processing while maintaining security through cryptographic protection of data copies.
Solution Approach 2:
The patent transforms the data exchange model by changing parameters from sharing full card numbers to sharing only encrypted tokens or mapped program identifiers. The system modifies the identification parameters used in transactions - instead of using card account numbers directly, it uses transformed identifiers that maintain the ability to route payments and apply co-branded benefits without exposing actual card data. This parameter transformation enables flexible payment options while reducing data exposure risks.
3Productivity
If program to card number mapping is implemented, then real-time offer identification is enabled, but system complexity increases
Solution Approach 1:
The patent implements preliminary action by pre-establishing the mapping between program identifiers and card accounts during enrollment or account setup. The mapping relationships are created and stored in advance in secure databases controlled by the card issuer. When a transaction occurs, the system simply performs a lookup using the pre-existing mapping rather than performing complex real-time analysis. This preliminary setup enables fast real-time offer identification while reducing operational complexity during actual transactions.
Data Source
AI summary
A system for dynamically revising a merchant page by one or more processors communicatively coupled to webservers hosting merchant pages may be configured to receive from a webserver a transaction amount and a unique identifier of a user interacting with the page without an input of a credit card number of the user and without the webserver accessing the credit card number in a data storage, identify, using the unique identifier and without receiving personally identifiable information from the webserver, a user profile including at least one dataset corresponding to a credit card of the user, and upon identifying an attribute of an alternative payment option for the user based on the user profile, generate an instruction to the webserver to dynamically render the page by displaying at least one interactive element including the alternative payment option based on an indicator of the credit card of the user.