Mobile Payment Authentication Using Contact List Hash Values
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile payment systems face challenges in ensuring secure and efficient transactions, particularly when users switch devices, as they often require multiple layers of authentication and can be vulnerable to unauthorized access due to linked phone numbers and account linking, which may lead to accidental account takeovers.
Innovation Solution
The system employs multi-factor authentication using hash values of contact lists stored on mobile devices, comparing these hash values between devices to verify user identity and authorize access, thereby reducing network traffic and processing burdens while enhancing security and speed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication methods are used when users switch devices, then account security is improved, but user convenience and access speed deteriorate due to multiple layers of authentication requirements
Solution Approach 1:
The system performs preliminary actions by storing hash values of contact lists and device identifiers before device switching occurs. When a user switches devices, these pre-stored hash values are immediately used for authentication comparison, eliminating the need for multiple sequential authentication steps and enabling fast, convenient access while maintaining security.
2Measurement precision
If contact data is exchanged between devices for authentication, then authentication accuracy is improved, but user privacy and data security deteriorate due to exposure of actual contact information
Solution Approach 1:
The system extracts only the essential authentication element (hash value of contact list) from the complete contact data, separating the authentication function from the private information. By using only the hash value for comparison and never transmitting or storing actual contact details, the system achieves accurate authentication while completely preserving user privacy and preventing data leakage.
Solution Approach 2:
The hash value acts as an intermediary between the contact data and the authentication process. Instead of directly comparing actual contact information, the system compares hash values generated from the contact data, providing an indirect verification method that maintains authentication accuracy while protecting the underlying private information from exposure.
3Ease of operation
If phone numbers are linked to mobile credit accounts, then account accessibility is improved, but security deteriorates due to vulnerability to unauthorized access through recycled phone numbers
Solution Approach 1:
Instead of directly using the phone number for account verification, the system creates a cryptographic copy (hash value) of the device identifier and contact list. This hash copy serves as the authentication key, maintaining the convenience of device-based access while eliminating the security vulnerability of direct phone number linkage, as recycled phone numbers cannot generate valid hash values for unauthorized access.
Data Source
AI summary
Disclosed herein are systems and methods for processing a payment request that use mobile devices to have money transferred. These mobile devices are capable of running a payment transfer application that facilitates a transfer of money. A user can then execute the payment transfer application using a mobile device to send money, through a payment processing system that runs the payment transfer application, to a recipient account. One or more techniques authenticate a user of the mobile device by multi factor authentication prior to processing requests for money transfer initiated by the user.