Authentication Computing Device for Payment Transaction Rule Relaxation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic account authentication systems face challenges in allowing accountholders to quickly retry a payment transaction after a decline, often resulting in inconvenience and potential fraud, as they require additional authentication data that may not be readily available, leading to embarrassment and increased fraud risks.
Innovation Solution
An authentication computing device that receives a decline message, transmits an authorization rules relaxation message to the accountholder's device, authenticates additional authentication data, and enhances the authorization request message with a rules relaxation identifier to allow the issuer to modify transaction decline systems, enabling the accountholder to retry the transaction successfully.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the issuer enforces strict authorization rules to detect fraud, then fraud detection capability is improved, but legitimate transactions are incorrectly declined causing customer inconvenience
Solution Approach 1:
The system performs preliminary authentication of the accountholder before allowing transaction reattempts. The authentication computing device verifies the accountholder's identity through additional authentication data, and only then relaxes the authorization rules. This preliminary action ensures that legitimate users can retry transactions while maintaining fraud detection for unauthorized users.
2Productivity
If the system allows multiple rapid transactions to be processed, then transaction speed is improved, but fraud risk increases due to suspicious activity patterns
Solution Approach 1:
The system implements a feedback mechanism where the authentication computing device receives information about rapid successive transactions, authenticates the accountholder, and then provides feedback by relaxing authorization rules for authenticated users. This feedback loop allows the system to distinguish between legitimate rapid transactions (authenticated) and suspicious ones (unauthenticated), maintaining both speed and security.
3Reliability
If the accountholder must provide additional authentication data for transaction reattempts, then security is improved, but user convenience deteriorates when data is not readily available
Solution Approach 1:
The system enables self-service authentication where the accountholder's computing device automatically provides the additional authentication data without requiring manual intervention or lookup of personal information. The authentication computing device receives the authentication data from the accountholder's device and processes it automatically, eliminating the need for time-consuming telephone calls or manual data entry.
4Measurement precision
If the system requires telephone contact with the issuer for declined transactions, then authentication verification is improved, but customer experience deteriorates due to delays and embarrassment
Solution Approach 1:
The authentication computing device acts as an intermediary between the accountholder and the issuer. Instead of requiring direct telephone contact between the accountholder and issuer representative, the authentication computing device receives additional authentication data from the accountholder's device, verifies it, and communicates with the issuer automatically. This intermediary role maintains authentication verification while eliminating the inconvenience of telephone calls and waiting on hold.
Data Source
AI summary
A method of authenticating an accountholder for relaxing payment transaction authorization rules is provided. The method is implemented using an authentication computing device in communication with a memory device. The method includes receiving a transaction decline message from an issuer via a transaction message channel, transmitting an authorization rules relaxation message to an accountholder computing device via an authentication message channel separate from the transaction message channel, receiving an authorization rules relaxation response message via the authentication message channel, authenticating the authorization rules relaxation response message as originating from the accountholder, receiving an authorization request message associated with a reattempted payment transaction, inserting a rules relaxation identifier into the authorization request message, providing the authorization request message to the issuer computing device, causing modification of transaction decline systems, and receiving an approval message denoting authorization rules relaxation and acceptance of the second payment transaction by the issuer.


