Dynamic Multifactor Authentication Using Transaction History

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current payment transaction processing systems face challenges in authenticating users effectively, as they rely solely on static credentials and lack correlation with previous transaction locations and times, making them susceptible to fraud.

Innovation Solution

A multifactor authentication method that maintains an access history database of transactions, correlates with a client device history log, and uses dynamic data such as GPS location and time to authenticate users, ensuring that only authorized devices with a history of prior transactions can proceed with secure transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If static credentials (password, account number) are used for authentication, then ease of operation is improved, but security is worsened because compromised credentials can be used on any device

Engineering Contradiction:
Improveease of authenticationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent transforms static authentication credentials into dynamic ones by incorporating time-stamped transaction history that changes continuously. The authentication system now evaluates not just fixed passwords but evolving patterns of usage over time, making credentials difficult to compromise and reuse on different devices.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary authentication by analyzing historical transaction patterns before authorizing new transactions. By pre-establishing baseline behavior patterns from past transactions, the system can proactively identify and block suspicious activities before they result in fraud.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If transaction history analysis is implemented, then security is improved, but device complexity is worsened due to database maintenance and correlation requirements

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The client device automatically maintains its own transaction history database and performs local correlation analysis without requiring complex centralized processing. Each device independently manages its authentication data, reducing the computational burden on central systems while maintaining security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The authentication system is divided into independent components: local transaction history storage on client devices, centralized access history database, and correlation logic distributed between client and server. This segmentation allows each component to remain relatively simple while the system as a whole provides robust security.

Inventive Principle:
Principle #1Segmentation

3Reliability

If multifactor authentication with changing values is used, then security is improved, but ease of operation is worsened due to multiple authentication steps

Engineering Contradiction:
ImprovesecurityVSAvoidease of use
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system automatically performs multiple authentication checks without requiring user intervention for each factor. Transaction history correlation, location verification, and pattern analysis are executed automatically in the background, providing multifactor authentication while maintaining a simple user experience.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Multiple authentication factors (transaction history, location data, time stamps, device identifiers) are merged into a single unified authentication decision process. Rather than presenting users with separate authentication steps, the system combines all factors into one seamless evaluation that occurs transparently during the transaction process.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8095519B2Multifactor authentication with changing unique values
Publication Date: 2012.01.10 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8095519B2 patent drawing
  • US8095519B2 patent drawing
  • US8095519B2 patent drawing

AI summary

A method of authentication includes the steps of providing a transaction service provider having a secure server; providing a user; requesting access authorization to the server of the service provider by the user, the server storing a set of use parameters obtained from the authorization access request, the use parameters including at least several prior location coordinates, methods of access, transaction information and access hardware used during the authentication to be used by the transaction service provider in subsequent requests by the user to access the server, the use parameters used in the authentication to be continually updated with the most recent data.