Last Used Account Identity Validation for Payment Infrastructure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional payment processing mechanisms require consumers to repeatedly go through consumer identity validation (CIV) even when using the same payment card at the same merchant, leading to excessive strain on payment infrastructure, inefficiency, and reduced scalability.
Innovation Solution
A computerized method for consumer identity validation in Secure Remote Commerce (SRC) that uses the last used card, where a processor receives a user identifier, sends it to SRC providers, determines the most recent last used card based on timestamps, and initiates payment processing with the associated provider, reducing the need for repeated CIV.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional CIV mechanisms require consumers to repeatedly go through the entire CIV process at each transaction, then consumer identity validation is performed, but excessive strain is placed on payment processing infrastructure and scalability is reduced
Solution Approach 1:
The system performs CIV validation in advance and stores the validated identity information. When the same consumer makes a subsequent transaction at the same merchant, the pre-performed CIV is retrieved and reused, eliminating the need to repeat the entire CIV process. This preliminary action resolves the contradiction by maintaining reliable CIV validation while dramatically improving transaction processing efficiency.
Solution Approach 2:
The system creates a copy of the consumer's validated identity information from the CIV process and stores it for future use. Instead of re-executing the entire CIV process, the system copies and reuses the previously validated identity data. This copying approach maintains validation reliability while reducing the computational strain on payment infrastructure during subsequent transactions.
2Reliability
If the entire CIV process is repeated at every transaction, then identity validation is ensured, but each transaction consumes more computing resources and energy
Solution Approach 1:
The CIV process is executed in advance and the results are cached. Subsequent transactions utilize this pre-computed validation data, eliminating the need to consume computing resources and energy for repeating the entire CIV process. This maintains identity validation reliability while significantly reducing the energy and computing resource consumption per transaction.
Solution Approach 2:
The system discards the notion of re-executing CIV and instead recovers and reuses the previously obtained validated identity information. By recovering and reusing this data, the system maintains validation reliability without incurring the repeated computing resource and energy costs of re-running CIV.
3Reliability
If traditional CIV infrastructure is used, then consumer identity can be validated, but the infrastructure is degraded by over-allocation of resources and reduced scaling potential
Solution Approach 1:
The system performs CIV validation in advance and stores the results, so that subsequent transactions can be processed without re-executing the full CIV process. This preliminary action reduces the resource allocation needed for each transaction, preventing infrastructure degradation and enabling the system to scale more effectively while maintaining validation capability.
Solution Approach 2:
The pre-performed CIV validation results are made universally applicable across multiple transactions. A single CIV validation serves multiple future transactions at the same merchant, reducing the overall resource burden on the infrastructure and enhancing scaling potential while maintaining reliable identity validation.
Data Source
AI summary
Examples provide consumer identity validation (CIV) via last used payment card, improving management of payment infrastructure resources. Examples enable the consumer to more efficiently complete CIV via at least one of a last used account or a last used card. By not requiring consumers to repeatedly go through the entire CIV process at each transaction at the same merchant when using the exact same card they used on a previous visit, excessive and unnecessary strain on the infrastructure is reduced, preventing degradation of the infrastructure. This enables allocating fewer computing resources to CIV, making deployments utilizing low-power or otherwise constrained equipment simpler and easier to maintain. Thus, scaling is enhanced. Individual CIV performance is more efficient, and less computing resources and energy are required across the entire infrastructure. A greater number of CIV transactions are executable in parallel, reducing transaction processing delays, bolstering stability, and reducing error rates.