Multi-Factor Authentication Using Static Code and Biometrics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multi-factor authentication systems for card-based transactions are not completely secure, as two-factor authentication based on one-time passwords (OTPs) can be diverted to unauthorized devices, allowing malicious actors to initiate unauthorized transactions.
Innovation Solution
The implementation of an augmented multi-factor authentication mechanism that includes a static code and biometric identifiers, such as a 3D face map, to ensure that even if an OTP is diverted, the malicious actor cannot authenticate the transaction without the correct static code and biometric information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional two-factor authentication using OTP is implemented, then user authentication capability is improved, but security against unauthorized transactions deteriorates because OTP can be diverted to malicious devices
Solution Approach 1:
The authentication code is segmented into two distinct components: a dynamic OTP component and a static code component. The static code is device-specific and stored securely in the payment terminal's memory, while the OTP is transmitted separately. This segmentation ensures that even if the OTP is intercepted or diverted to a malicious device, the attacker cannot complete authentication without also possessing the static code that is bound to the legitimate payment terminal.
Solution Approach 2:
A payment terminal acts as an intermediary device between the user's mobile device and the payment network. The terminal receives the OTP, combines it with the static code stored in its secure memory, and only then processes the authentication. This intermediary role ensures that the static code never leaves the legitimate terminal and prevents OTP diversion attacks, as the authentication code generation happens in a trusted environment.
2Ease of operation
If OTP-based authentication is used, then ease of operation is improved, but security reliability deteriorates due to potential OTP diversion to unauthorized devices
Solution Approach 1:
The authentication process is segmented into two independent steps: receiving the OTP and providing the static code. The static code is pre-configured in the payment terminal and does not require user input, maintaining ease of operation. The segmentation ensures that the convenient OTP delivery mechanism is combined with the secure static code verification, preventing security reliability deterioration while preserving operational simplicity.
Solution Approach 2:
The payment terminal automatically retrieves and uses the static code from its secure internal memory without requiring user intervention. This self-service capability maintains ease of operation for the user while ensuring that the static code is consistently and securely applied to authenticate transactions, preventing security reliability issues.
Data Source
AI summary
A system for multi-factor user authentication for payment card-based transactions are described. The multifactor authentication may be based on a one-time passcode/password (OTP) as sent by an authentication server. A user device may, based on receiving the OTP, send an authentication code. The authentication code may be generated/determined based on the OTP. The authentication code may be augmented biometric identifier (ID) of a user associated with the user device. The authentication server may validate a transaction based on the authentication code.