Value Transfer Card Dormancy Detection and Token Revocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing value transfer cards stored by third-party computer systems becomes increasingly difficult due to their proliferation across various locations, leading to challenges in tracking and disabling dormant or unused cards to prevent fraud.
Innovation Solution
A computing system that identifies dormant entities by performing threshold-based comparisons on the time of last use of value transfer cards, sends notifications to clients to disable these cards, and transmits instructions via APIs to revoke tokens representing the cards, thereby preventing further use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If value transfer cards are stored by multiple third-party computer systems for future use, then the cards remain readily accessible for transactions, but tracking and managing the cards becomes increasingly difficult
Solution Approach 1:
The patent introduces a centralized card management system that acts as an intermediary between the cardholder and multiple third-party systems. This central system maintains a comprehensive registry of all stored card instances across different third parties, enabling the cardholder to track and manage their cards through a single interface without needing to directly monitor each third-party system.
Solution Approach 2:
The card management system provides universal functionality to manage value transfer cards across multiple third-party systems through a single platform. It can identify, track, and control card instances stored by any number of different third parties, making the system adaptable to various storage locations without requiring separate management mechanisms for each.
2Productivity
If value transfer cards are stored by numerous third-party systems, then transaction convenience is improved, but the risk of fraud from dormant or unused cards increases
Solution Approach 1:
The system implements feedback mechanisms that continuously monitor the status of stored card instances across third-party systems. By tracking usage patterns and identifying dormant cards, the system can alert cardholders and automatically disable suspicious or unused cards, creating a feedback loop that reduces fraud risk while maintaining convenience for active cards.
Solution Approach 2:
The card management system performs preliminary actions by proactively identifying dormant or unused card instances before they can be exploited for fraud. The system monitors card usage and disables potentially compromised cards in advance, preventing fraudulent transactions before they occur rather than reacting after fraud is detected.
3Reliability
If the card management system monitors and disables dormant cards across multiple third parties, then fraud prevention is improved, but the system complexity increases
Solution Approach 1:
The centralized card management system serves as an intermediary that simplifies fraud prevention by consolidating monitoring and control functions. Rather than requiring each third-party system to independently implement complex fraud detection and card disabling mechanisms, the central system handles these functions uniformly across all stored cards, reducing overall system complexity while maintaining high reliability.
Data Source
AI summary
In an aspect, a computer-implemented method is disclosed. The method includes: obtaining, from a transfer rail server, stored card data identifying one or more entities having a stored representation of a value transfer card and data indicating a time of last use of the value transfer card by at least one of the identified entities; identifying a dormant entity based on the data indicating the time of last use of the value transfer card by the at least one identified entity by performing a threshold-based comparison using the time of last use and a current date; presenting, via a user interface of a card management application on a client device associated with the value transfer card, a notification indicating the dormant entity, the notification including a selectable user interface element corresponding to an operation for disabling the value transfer card for the dormant entity; receiving, via the client device, a command in response to the notification; and in response to determining that the command includes a request to disable the value transfer card for the dormant entity, transmitting, via an application programming interface (API) request to the transfer rail server, an instruction to revoke a token representing the value transfer card for the dormant entity to prevent further use of the value transfer card by the dormant entity.