Passkey Session Authentication to Eliminate Repeated Checkout Logins

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing authentication systems require multiple authentications during a session, creating friction for users and redundant network traffic.

Innovation Solution

Implementing a passkey authentication tied to a session ID, allowing subsequent communications within the session to bypass re-authentication, reducing network traffic while maintaining security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple authentications are performed during a session, then security is maintained, but user friction increases and network traffic becomes redundant

Engineering Contradiction:
Improveauthentication securityVSAvoiduser friction
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary authentication at the beginning of a session and extends its validity throughout the session duration. The authentication result is cached and reused for subsequent requests within the same session, avoiding repeated authentication operations while maintaining security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The authentication mechanism is designed to serve multiple functions: it not only verifies user identity but also establishes session validity for subsequent operations. A single authentication result is universally applied across multiple requests within the session, reducing redundant operations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If multiple authentications are performed during a session, then security is maintained, but network traffic increases

Engineering Contradiction:
Improveauthentication securityVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system extracts the authentication operation from each individual request and performs it once at the session level. The authentication result is then reused for multiple subsequent requests, eliminating redundant network traffic associated with repeated authentication handshakes.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If authentication is extended through session duration, then user friction and network traffic are reduced, but authentication validity period increases

Engineering Contradiction:
Improveuser frictionVSAvoidauthentication validity period
Core Design Contradiction:
Ease of operationVSDuration of action of stationary object

Solution Approach 1:

The system performs preliminary authentication and extends its validity through the session duration. This preliminary action covers multiple subsequent operations, reducing user friction while controlling the authentication validity period to match session boundaries rather than extending indefinitely.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260044855A1Systems and methods for extending authentication
Publication Date: 2026.02.12 MASTERCARD INT INC
  • US20260044855A1 patent drawing
  • US20260044855A1 patent drawing
  • US20260044855A1 patent drawing

AI summary

Systems and methods are provided for extending authentication. An example computer-implemented method includes, during a checkout session at a mobile device specific to a user, and in response to a lookup request from a first party, confirming a user profile for the user and an existing passkey for the user profile and a mobile device associated with the user. The method also includes, during the checkout session, initiating a passkey authentication of the user, through a fast identity online (FIDO) server at the mobile device; receiving a proof of authentication for the user from the FIDO server; providing the proof of authentication to the first party; receiving an instruction to initiate checkout from the first party; validating the proof of authentication based on a session ID, without a further passkey authentication of the user, and compiling an authentication payload based on the validated proof of authentication.