Method and Apparatus for Conducting Secure Financial and Informational Transactions via Portable Smart Devices
Abstract
A technique for conducting secure financial and informational transactions via portable smart devices is disclosed, in which two transaction devices, e.g. an ATM and a smartphone or other smart connected device are both substantially simultaneously accessible by the user and are both independently connected with the account server by a secure connection between the transaction device for the ATM and a secure connection between the smartphone and a cellphone tower. Thus, authentication is provided by secure login on the two devices, i.e. the transaction device and the cellphone. Once the devices are both connected to the account server, handshaking between the two devices to confirm pairing of the right two devices is prompted, at which point, a transaction may proceed.
Claims
exact text as granted — not AI-modified1 . A method for conducting any of secure financial and informational transactions, comprising:
providing at least two independent transaction devices, wherein said transaction devices are substantially simultaneously accessible by a user; independently connecting each of said transaction devices to a common account server by a secure connection between each transaction device and said account server; receiving unique information for exchange between said at least two transaction devices to pair said at least two transaction devices, once said at least two transaction devices are connected to said account server; and once pairing is confirmed, conducting a transaction between said user and a third party on one of said transaction devices.
2 . The method of claim 1 , wherein at least one of said transaction devices comprise a a smartphone or other smart device.
3 . The method of claim 1 , further comprising:
in response to said user commencing a transaction at a first transaction device, said first transaction device requesting a Temporary Transaction Number (TTN) from an account server; said transaction device receiving said TTN from said account server and displaying said TTN to said user; at substantially the same time, said user launching a secure transaction application on a second transaction device; when prompted by said application, said user operating a camera associated with said second transaction device to photograph the displayed TTN; said second transaction device transmitting said TTN to said account server; establishing a link between the first transaction device and a specific user account in response to said account server searching for and finding the TTN presented by the second transaction device, and matching said first transaction device with said second transaction device ; displaying an account nickname from said account server on said first transaction device and requesting said user's Device Identification Number (DIN); said user entering said DIN into said first transaction device; and said transaction proceeding.
4 . The method of claim 3 , wherein said second transaction device transmits said TTN to said account server via any of a cell phone data network and Wi-Fi.
5 . The method of claim 1 , further comprising:
said first and second transaction devices are in the possession of different individuals, said first transaction device comprises a point-of-sale (POS) device, said POS device requesting a Temporary Transaction Number (TTN) from an account server and printing a TTN on an invoice; said user operating a camera associated with said second transaction device to photograph the TTN; said second transaction device transmitting said TTN to said account server; establishing a link between the first transaction device and a specific user account in response to said account server searching for and finding the TTN presented by the second transaction device and matching said first transaction device with said second transaction device; displaying an account nickname from said account server on said first transaction device and requesting said user's Device Identification Number (DIN); entering said DIN into said first transaction device; and said transaction proceeding.
6 . The method of claim 1 , further comprising:
for transactions via a first transaction device comprising a website, during user checkout, making a request for a Temporary Transaction Number (TTN) during a secure checkout procedure and displaying TTN on a browser; said user operating a camera associated with said second transaction device to photograph the TTN; said second transaction device transmitting said TTN to said account server; establishing a link between the first transaction device and a specific user account in response to said account server searching for and finding the TTN presented by the second transaction device and matching said first transaction device with said second transaction device; displaying an account nickname from said account server on said first transaction device and requesting said user's Device Identification Number (DIN); entering said DIN into said first transaction device; and said transaction proceeding.
7 . The method of claim 1 , further comprising:
said at least two independent transaction devices being in the possession of at least two respective parties to a transaction, wherein said transaction devices are securely connected to a same account server and, therefore, only need to confirm their mutual identity to conduct said transaction; a first of said transaction devices associated with a first party requesting a Temporary Transaction Number (TTN) and displaying said TTN on said first transaction device; said user operating a camera associated with said second transaction device to photograph the TTN; said second transaction device transmitting said TTN to said account server; establishing a link between the first transaction device and a specific user account in response to said account server searching for and finding the TTN presented by the second transaction device and matching said first transaction device with said second transaction device; displaying an account nickname from said account server on said first transaction device and requesting said user's Device Identification Number (DIN); entering said DIN into said first transaction device; and said transaction proceeding.
8 . The method of claim 1 , further comprising:
said transaction devices are associated with different individuals, said user launching an application on said second transaction device and requesting a phone transaction; said application issuing a Temporary Transaction Number (TTN) request to said account server, which is presented to said user on said second transaction device; said user reading said TTN over a phone connection to a third party; said third party entering said TTN on said first transaction device, wherein said first and said second transaction devices are matched; said first transaction device presenting an account nickname to said third party, which said third party reads over said phone connection to said user; displaying an account nickname on said first transaction device and requesting said user's Device Identification Number (DIN); said user presenting said DIN to said third party over said phone connection; and said transaction proceeding.
9 . The method of claim 1 , further comprising:
delegating limited account access to a third party via an account management application on said second transaction device; once said user configures one or more options in said account management application, said account management application requests a Temporary Transaction Number (TTN) from said account server which is displayed on said second transaction device; an application on a delegate's transaction device activating a camera on said device to photograph said user's displayed TTN, which is then passed to said account server for confirmation; displaying an account nickname on said first transaction device and requesting said user's Device Identification Number (DIN); and once said DIN is confirmed, registering user account access with said delegate's transaction device for subsequent use.
10 . The method of claim 9 , wherein said delegation is limited by any of expiration date/time, withdrawal limit, deposit only, and transaction confirmation via an account holder's device.
11 . The method of claim 1 , further comprising:
at least one of said transaction devices having a social media application with appropriate capability to access a limited selection of the user's personal information and history as shown on the user's social media account; said user selecting information to share; said user selecting an option to embed a link in a barcode, wherein said barcode is displayed on said user's transaction device; a third party photographing said barcode with a camera on a second transaction device in possession of said third party; and a social media application on said third party's transaction device resolving and activating said link to show said user's information.
12 . The method of claim 11 , further comprising:
said user revoking or blocking said third party's access at any time.
13 . The method of claim 11 , wherein said barcode comprises an embedded icon which provide visual confirmation of a type of information encoded in said barcode.
14 . The method of claim 1 , wherein said unique information comprises a Temporary Transaction Number (TTN) embedded in a barcode.
15 . An apparatus for conducting secure financial and informational transactions, comprising:
an account server for independently connecting at least two independent transaction devices, wherein said transaction devices are simultaneously accessible to a user, said transaction devices connected by a secure connection between each transaction device and said account server; said account server generating unique information for exchange between said at least two transaction devices by user entry to pair said at least two transaction devices; wherein once pairing is confirmed, said account server authenticating a transaction between said user and a third party on one of said transaction devices.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.