Silent User Authentication via Device Fingerprinting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing user authentication processes for online and mobile payment transactions are inconvenient, particularly on mobile devices, as they require manual entry of login credentials, which can delay transactions and discourage the use of digital payments.

Innovation Solution

A system and method for silently authenticating a user on a mobile device by associating the device with the user, where the device's characteristics are used to establish trust, allowing the payment service provider to authenticate the user without requiring manual credential entry, using an SDK that communicates with a payment provider server to provide an authentication token for seamless access to payment services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual login credential entry is required for user authentication, then security is maintained, but transaction speed and user convenience deteriorate

Engineering Contradiction:
Improveauthentication securityVSAvoidtransaction speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary authentication by capturing device characteristics (hardware ID, software version, device model) when the user first accesses the payment service. This pre-captured device fingerprint is stored and used for subsequent automatic authentication, eliminating the need for repeated manual credential entry while maintaining security verification.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a digital copy of the user's device characteristics as a unique identifier. Instead of requiring the user to manually enter credentials each time, the system uses this copied device fingerprint for automatic recognition and authentication, significantly speeding up the transaction process while maintaining security.

Inventive Principle:
Principle #26Copying

2Reliability

If manual keyboard entry is required for authentication, then credential verification is ensured, but user convenience and ease of operation deteriorate

Engineering Contradiction:
Improvecredential verificationVSAvoidauthentication convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The authentication system serves itself by automatically capturing and verifying device characteristics without requiring user interaction with keyboards or other input devices. The device itself provides the authentication data through its inherent characteristics, making the process convenient while still ensuring verification through the unique device fingerprint.

Inventive Principle:
Principle #25Self-service

3Reliability

If repeated credential entry is required, then account security is maintained, but time consumption and transaction efficiency worsen

Engineering Contradiction:
Improveaccount securityVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs the authentication verification action in advance by capturing device characteristics once and storing them for future use. This preliminary capture eliminates the need for repeated authentication time consumption, as the pre-stored device fingerprint enables instant verification on subsequent transactions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10970377B2Systems and methods for authenticating a user based on a computing device
Publication Date: 2021.04.06 PAYPAL INC
  • US10970377B2 patent drawing
  • US10970377B2 patent drawing
  • US10970377B2 patent drawing

AI summary

A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a set of device characteristics from a user device and identifying, based on the set of device characteristics, the user device. The method also includes determining whether to trust the user device and determining whether the user device is associated with a user that was previously authenticated. The method further includes in response to determining to trust the user device and that the user device is associated with the user that was previously authenticated, authenticating the user based on the previous authentication.