Platform-Agnostic Authentication for Branch Fraud Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing systems lack effective methods for authenticating customers and authorizing transactions at physical locations, particularly in preventing fraud by both customers and employees, while ensuring secure and efficient transaction processing.

Innovation Solution

The implementation of a mobile device-based authentication and authorization system using platform-agnostic infrastructure, which includes low-energy transmitters for identification, a software library for selecting authentication mechanisms, and a process flow that determines transaction risk levels and initiates appropriate authentication procedures, enabling secure transactions through a combination of QR codes, biometric scans, and additional verification protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authentication methods are used at branch locations, then transaction processing is simple and quick, but security against fraud by customers and employees is insufficient

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication system is segmented into multiple independent components: low-energy transmitters at branch locations, mobile devices with authentication applications, a software library containing multiple authentication mechanisms, and a centralized system for coordinating authentication. This segmentation allows each component to perform its specific function efficiently while collectively providing robust security without requiring complete system redesign.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The software library implements multiple authentication mechanisms (biometric authentication, device-based authentication, knowledge-based authentication) that can be selectively applied based on transaction risk levels. This multi-functionality allows the system to handle both simple and complex authentication scenarios using a single unified platform, preventing fraud while maintaining operational efficiency.

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

2Reliability

If multiple authentication mechanisms are implemented to prevent fraud, then security is improved, but transaction processing time and system complexity increase

Engineering Contradiction:
Improvefraud prevention capabilityVSAvoidtransaction processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The authentication system dynamically adjusts the level of authentication required based on the determined risk level of each transaction. Low-risk transactions require minimal authentication steps, while high-risk transactions trigger more rigorous authentication procedures. This dynamic adaptation ensures fraud prevention while minimizing unnecessary delays in routine transactions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback loops where transaction risk levels are continuously assessed based on session data, user behavior patterns, and transaction characteristics. This feedback mechanism allows the system to learn from past transactions and adjust authentication requirements in real-time, preventing fraud while optimizing processing speed for legitimate transactions.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If platform-agnostic infrastructure is used for authentication, then system adaptability and security are improved, but implementation complexity and resource requirements increase

Engineering Contradiction:
Improveplatform compatibilityVSAvoidinfrastructure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The authentication system is designed as a platform-agnostic infrastructure that can operate across multiple devices and systems. The software library contains authentication mechanisms that can be deployed on various platforms without requiring platform-specific modifications, enabling widespread adoption while maintaining consistent security standards across different environments.

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

Solution Approach 2:

The system introduces an intermediary layer (the software library and centralized coordination system) that mediates between diverse authentication requirements and the underlying infrastructure. This intermediary abstracts the complexity of platform-specific implementations, allowing the system to adapt to different platforms without increasing overall infrastructure complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240338702A1Systems involving mobile devices and/or platform agnostic infrastructure features for in-branch authentication and/or authorization and methods of use thereof
Publication Date: 2024.10.10 CAPITAL ONE SERVICES LLC
  • US20240338702A1 patent drawing
  • US20240338702A1 patent drawing
  • US20240338702A1 patent drawing

AI summary

Systems and methods involving platform agnostic infrastructure for in-branch authentication and authorization, e.g., for customers and/or transactions, are disclosed. In one embodiment, an exemplary method may include initiating, upon an account access attempt, an authentication-authorization session based on account information, receiving a transaction request from an app running on a customer computing device, updating the session data of the current authentication/authorization session with the transaction request, determining a transaction risk level based on session data of current and/or prior session(s), initiating an authentication procedures based on transaction information, selecting an authentication mechanism from a library based on the authentication procedures, utilizing the authentication mechanism to authenticate the user according to the authentication procedure(s), enabling the app, upon authentication, to proceed to perform the transaction, and/or concluding the session and/or updating the session data with the one or more authentication procedures and/or transaction details of the completed transaction.