Offline Mobile Payment Authorization with Digital Signatures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile payment solutions rely on internet connectivity and specific technologies like NFC, limiting offline transactions and lacking 'non-repudiation' assurance, which can lead to transaction disputes and fraud, hindering widespread adoption by both consumers and merchants.
Innovation Solution
A method for payment authorization on offline mobile devices using unidirectional data transfer, generating digital signatures with private and public keys, and ensuring authenticity through encryption algorithms, allowing transactions without internet connectivity and providing 'non-repudiation' assurance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If mobile payment solutions use internet connectivity and NFC technology, then transaction security and reliability are improved, but offline transaction capability deteriorates
Solution Approach 1:
The system segments the payment authorization process into two independent parts: (1) digital signature generation using the payer's private key stored in the mobile device, and (2) signature verification using the payee's public key. This segmentation allows the critical authentication function to operate offline while maintaining security, as the digital signature can be generated and verified without internet connectivity.
Solution Approach 2:
The system performs preliminary actions by pre-distributing public keys to payees and storing private keys securely in payer devices before offline transactions occur. This preliminary setup enables immediate offline authentication without requiring real-time server communication, thus resolving the contradiction between security and offline capability.
2Reliability
If mobile payment solutions implement digital signature with private and public keys, then non-repudiation assurance is improved, but device complexity deteriorates
Solution Approach 1:
The mobile device autonomously generates and stores the payer's private key locally without requiring external key management infrastructure during transactions. The device self-manages the cryptographic operations, signing transactions with its private key and enabling verification through its public key, thus achieving non-repudiation without adding significant system-level complexity.
3Productivity
If offline payment transactions are enabled, then transaction speed and convenience are improved, but risk of transaction disputes deteriorates
Solution Approach 1:
The system implements asymmetric cryptography where the payer's private key (secret) and public key (shared) have different functions and properties. The private key is used exclusively for signing transactions, while the public key is distributed to payees for verification. This asymmetric structure enables fast offline transactions while providing mathematical proof of authenticity that prevents disputes.
Data Source
AI summary
A methods for payment authorization (10) on mobile devices (DM) such as smartphones, tablets or any others available, which may be offline; the method for payment authorization (10) comprises the compilation of sequential steps of method (M1) of the payer (20) with method (M2) of the operational system (50) or application that constitutes a logical structure for alignment with the method (M3) of the payee (30), resulting in authenticated payment (PG) of financial transactions (TF) with assurance of “non-repudiation” through generation of a private key (51) and public key (52), as well as association of positive identification (21a) and personal identification (21b) of the payer (PG) with the mobile device (DM); said methods (M1), (M2) and (M3) are executed on mobile devices (DM) with enough processing capacity for execution of encryption algorithms and which may be used for issuing payment orders (PG), on-site or otherwise, carried out with financial resources (RF) or credit limits (LC) such as bonuses, points, products, tickets, etc. of the payer (20) of the device (DM).